[VOTE] Approve the release of Tuscany SCA Java 1.0-incubating

[ant elder]

The Tuscany project requests permission of the IPMC to release the Java SCA
1.0-incubating release.

The SVN tag for the release is:
https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/

The artifacts are available for review at:
http://people.apache.org/~antelder/tuscany/1.0-RC3a/

This includes the signed binary and source distributions, the RAT reports,
and the Maven staging repository.

The tuscany-dev vote thread has 11 +1s and is at:
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200709.mbox/[EMAIL 
PROTECTED]

Many thanks,

   ...ant

Re: Incubator Proposal: Pig

[Bertrand Delacretaz]

On 9/18/07, Olga Natkovich <[EMAIL PROTECTED]> wrote:

> ...We would like to ask that the ASF consider forming a podling according to
> the proposal

+1 to the proposal, and I'd be happy to help as a mentor.

-Bertrand

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Incubator Proposal: Pig

[Petar Tahchiev]

+1 from me, too. It looks very promising. :-)



On 9/21/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
>
> On 9/18/07, Olga Natkovich <[EMAIL PROTECTED]> wrote:
>
> > ...We would like to ask that the ASF consider forming a podling
> according to
> > the proposal
>
> +1 to the proposal, and I'd be happy to help as a mentor.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Regards, Petar!
Karlovo, Bulgaria.

EOOXML objections
http://www.grokdoc.net/index.php/EOOXML_objections

Public PGP Key at:
http://keyserver.linux.it/pks/lookup?op=get&search=0x1A15B53B761500F9
Key Fingerprint: AA16 8004 AADD 9C76 EF5B  4210 1A15 B53B 7615 00F9

Re: [VOTE] Graduate Ivy as a subproject of Ant

[Gilles Scokart]

>
> [X] Yes, I think the Ivy podling is ready to graduate as a subproject of
> Ant
>


-- 
Gilles SCOKART

Re: [VOTE] Approve the release of Tuscany SCA Java 1.0-incubating

[Matthieu Riou]

And here is my +1.

On 9/21/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> The Tuscany project requests permission of the IPMC to release the Java
> SCA
> 1.0-incubating release.
>
> The SVN tag for the release is:
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/
>
> The artifacts are available for review at:
> http://people.apache.org/~antelder/tuscany/1.0-RC3a/
>
> This includes the signed binary and source distributions, the RAT reports,
> and the Maven staging repository.
>
> The tuscany-dev vote thread has 11 +1s and is at:
>
> http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200709.mbox/[EMAIL 
> PROTECTED]
>
> Many thanks,
>
>...ant
>

Re: [VOTE] Graduate Ivy as a subproject of Ant

[Matthieu Riou]

[X] Yes, I think the Ivy podling is ready to graduate as a subproject of Ant

On 9/21/07, Gilles Scokart <[EMAIL PROTECTED]> wrote:
>
> >
> > [X] Yes, I think the Ivy podling is ready to graduate as a subproject of
> > Ant
> >
>
>
> --
> Gilles SCOKART
>

Re: Incubator Proposal: Pig

[Jim Hurley]

+1

-Jim

On Sep 18, 2007, at 3:52 PM, Olga Natkovich wrote:

Hi,

Yahoo! research and development teams have developed a proposal  
below. The

proposal is also available on wiki at

http://wiki.apache.org/incubator/PigProposal.
We would like to ask that the ASF consider forming a podling  
according to

the proposal.

Thanks,

Olga Natkovich
  [EMAIL PROTECTED]

-- 
--

-

= Pig Open Source Proposal =

== Abstract ==

Pig is a platform for analyzing large data sets.

== Proposal ==

The Pig project consists of high-level languages for expressing data
analysis programs, coupled with infrastructure for evaluating these

:
:
:

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Graduate Ivy as a subproject of Ant

[Steve Loughran]

Xavier Hanin wrote:

Hi,

As discussed recently on this mailing list [1], I would like to start a
community vote to decide if the Ivy community feels ready to graduate as a
subproject of Ant.

The graduation guide [2] can be used as a basis to collect information about
what is usually necessary to graduate.

Note that this is only a community vote, and is the first of three votes
required for graduation, as explained in the graduation guide [2].



[+1 ] Yes, I think the Ivy podling is ready to graduate as a subproject 
of Ant

 [ ] No, I don't think the Ivy podling is ready to graduate as a subproject
 of Ant because ...


-steve

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Graduate Ivy as a subproject of Ant

[Eelco Hillenius]

 [ x ] Yes, I think the Ivy podling is ready to graduate as a subproject of Ant


Eelco

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Graduate Ivy as a subproject of Ant

[Martijn Dashorst]

+1

On 9/20/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> Hi,
>
> As discussed recently on this mailing list [1], I would like to start a
> community vote to decide if the Ivy community feels ready to graduate as a
> subproject of Ant.
>
> The graduation guide [2] can be used as a basis to collect information about
> what is usually necessary to graduate.
>
> Note that this is only a community vote, and is the first of three votes
> required for graduation, as explained in the graduation guide [2].
>
> [ ] Yes, I think the Ivy podling is ready to graduate as a subproject of Ant
> [ ] No, I don't think the Ivy podling is ready to graduate as a subproject
> of Ant because ...
>
> Everybody is welcome to voice his opinion. Cast your votes!
>
> Xavier
>
> [1] http://www.nabble.com/What-about-Graduation--tf4447692.html
> [2] http://incubator.apache.org/guides/graduation.html
> --
> Xavier Hanin - Independent Java Consultant
> http://xhab.blogspot.com/
> http://incubator.apache.org/ivy/
> http://www.xoocode.org/
>


-- 
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Imperius (was SPL) Incubator Proposal

[David L Kaminsky]

All,

I updated the proposal to include the new proposed project name.  Imperius
seems
to be cleaner than the alternatives.

I also added the references to the DMTF's IP policy.

Please let me know if there are more questions.  (Please CC
[EMAIL PROTECTED])

Thanks, David


Abstract
-

Policy systems allow administrators to define policies that guide the
automated administration of resources.  Such automation saves time and
effort by simplifying resource-management.


We proposed to develop a policy-based management infrastructure that
automates administrative tasks by executing policies written in the
"Simplified Policy Language" (SPL), a standards-based policy language.



Proposal
--

This proposal seeks to create a project within the Apache Software
Foundation to (1) develop a policy evaluator for the SPL policy
language, and (2) develop bindings between the policy evaluator and
projects such as Apache Geronimo.



Background
---

As computer systems become more complicated, they continue to become
increasingly complex and costly to manage.  Various studies have shown
that the cost of managing systems often exceeds the cost of purchasing
them.  The goal of the Imperius  project is to reduce management burden by
allowing administrators to specify policies that replace manual
administrative actions.


Rationale
--

Policy-based management is one approach to reducing the cost of systems
administration.  Administrators define policies that express a
"management intent", and the policy-based management system executes
the policy, thereby reducing the burden on the administrator. For
example, a policy might state "backup the database daily at 1am."  A
policy management system would interpret the policy, and trigger the
database to perform a backup at the assigned time, offloading that task
from the administrator.

To allow more flexible semantics, such policies are often expressed as
"If-Then" (also called "Condition-Action") rules.  For example, "If
the packet comes from subnet 6.7.8.*, Then place it on the
high-priority outgoing queue" or "If the data in the database have
changed by 10%, Then perform an incremental backup."  Such policies
allow for more complex automation.

To implement these kinds of rule-based policies, the policy system
must interact with the system's APIs.  In the second example above,
the system relies on the ability to measure the percentage of data
that have changed since the last backup (or to compute that value from
measurable data).  Similarly, to execute the "then" clause, the policy
system must be able to start an incremental backup on the database
using the database's API.  Expressed generally, a policy system must
have a binding to the "instrumentation layer" or API for the system
under management.

Thus, policy systems consist of two major components: an evaluation
engine and a binding to an instrumentation environment.  The
evaluation engine (1) accepts policies expressed according to a
well-defined grammar, (2) collects the data needed to evaluate the
policies, and (3) actuates the "Then" section as appropriate.

This project would build an SPL evaluation engine and bindings to
various Apache and non-Apache APIs.

The design of SPL, a Preliminary DMTF standard, is inspired by
existing policy languages and models including PDL (policy definition
language) from Bell Laboratories, the Ponder policy language from
Imperial College, and other policy languages.

The basic unit of a SPL policy is a policy rule. An SPL policy rule
consists of a condition, an action, and other fields.  Multiple policy
rules can be grouped into a policy group. Policy groups can be nested
-- i.e., a policy group can contain another policy group.  For the
specification of the policy condition, SPL provides a rich set of
operators that act on the following types: signed and unsigned short,
regular and long integers, float and long float, character, string,
Boolean, and calendar.

We expect the community to develop a number of bindings between the
evaluation engine and APIs.  Examples include the API for Geronimo,
and standard interfaces such as WSDM and CIM.  The community may
choose to develop a wide range of bindings, all leveraging the common
SPL engine and policy syntax.

The Imperius Policy Engine will be implemented in the form of a Java
application.  The SPL application will provide the following
functionality:

1.   PolicyManager - The PolicyManager acts as an orchestrator
delegating tasks to its subcomponents.

2.   PolicyDataStore - The PolicyDataStore is responsible for two major
tasks: Policy Storage and the creation of Internal Policy Objects:

 a. Policy Storage: This involves persisting of the policies
into a repository along with caching of the Internal Policy Objects for
use in evaluation
 b. Internal Policy Object Creation: This involves syntax,
semantic analysis of the textual policy stored in the repository and the
creation of abstr

Re: Imperius (was SPL) Incubator Proposal

[Craig L Russell]

I think Imperius is a great Apache project name.

And it's good that you included references to the IP policy.

Craig

On Sep 21, 2007, at 6:56 PM, David L Kaminsky wrote:


All,

I updated the proposal to include the new proposed project name.   
Imperius

seems
to be cleaner than the alternatives.

I also added the references to the DMTF's IP policy.

Please let me know if there are more questions.  (Please CC
[EMAIL PROTECTED])

Thanks, David


Abstract
-

Policy systems allow administrators to define policies that guide the
automated administration of resources.  Such automation saves time and
effort by simplifying resource-management.


We proposed to develop a policy-based management infrastructure that
automates administrative tasks by executing policies written in the
"Simplified Policy Language" (SPL), a standards-based policy language.



Proposal
--

This proposal seeks to create a project within the Apache Software
Foundation to (1) develop a policy evaluator for the SPL policy
language, and (2) develop bindings between the policy evaluator and
projects such as Apache Geronimo.



Background
---

As computer systems become more complicated, they continue to become
increasingly complex and costly to manage.  Various studies have shown
that the cost of managing systems often exceeds the cost of purchasing
them.  The goal of the Imperius  project is to reduce management  
burden by

allowing administrators to specify policies that replace manual
administrative actions.


Rationale
--

Policy-based management is one approach to reducing the cost of  
systems

administration.  Administrators define policies that express a
"management intent", and the policy-based management system executes
the policy, thereby reducing the burden on the administrator. For
example, a policy might state "backup the database daily at 1am."  A
policy management system would interpret the policy, and trigger the
database to perform a backup at the assigned time, offloading that  
task

from the administrator.

To allow more flexible semantics, such policies are often expressed as
"If-Then" (also called "Condition-Action") rules.  For example, "If
the packet comes from subnet 6.7.8.*, Then place it on the
high-priority outgoing queue" or "If the data in the database have
changed by 10%, Then perform an incremental backup."  Such policies
allow for more complex automation.

To implement these kinds of rule-based policies, the policy system
must interact with the system's APIs.  In the second example above,
the system relies on the ability to measure the percentage of data
that have changed since the last backup (or to compute that value from
measurable data).  Similarly, to execute the "then" clause, the policy
system must be able to start an incremental backup on the database
using the database's API.  Expressed generally, a policy system must
have a binding to the "instrumentation layer" or API for the system
under management.

Thus, policy systems consist of two major components: an evaluation
engine and a binding to an instrumentation environment.  The
evaluation engine (1) accepts policies expressed according to a
well-defined grammar, (2) collects the data needed to evaluate the
policies, and (3) actuates the "Then" section as appropriate.

This project would build an SPL evaluation engine and bindings to
various Apache and non-Apache APIs.

The design of SPL, a Preliminary DMTF standard, is inspired by
existing policy languages and models including PDL (policy definition
language) from Bell Laboratories, the Ponder policy language from
Imperial College, and other policy languages.

The basic unit of a SPL policy is a policy rule. An SPL policy rule
consists of a condition, an action, and other fields.  Multiple policy
rules can be grouped into a policy group. Policy groups can be nested
-- i.e., a policy group can contain another policy group.  For the
specification of the policy condition, SPL provides a rich set of
operators that act on the following types: signed and unsigned short,
regular and long integers, float and long float, character, string,
Boolean, and calendar.

We expect the community to develop a number of bindings between the
evaluation engine and APIs.  Examples include the API for Geronimo,
and standard interfaces such as WSDM and CIM.  The community may
choose to develop a wide range of bindings, all leveraging the common
SPL engine and policy syntax.

The Imperius Policy Engine will be implemented in the form of a Java
application.  The SPL application will provide the following
functionality:

1.   PolicyManager - The PolicyManager acts as an orchestrator
delegating tasks to its subcomponents.

2.   PolicyDataStore - The PolicyDataStore is responsible for two  
major

tasks: Policy Storage and the creation of Internal Policy Objects:

 a. Policy Storage: This involves persisting of the policies
into a repository along with caching of the Internal Poli