Re: [VOTE] Kalumet to join Incubator

[j...@nanthrax.net]

+1 (binding)

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com

- Reply message -
From: "Olivier Lamy" 
To: 
Subject: [VOTE] Kalumet to join Incubator
Date: Tue, Sep 13, 2011 9:18 am


Hello Folks,

Please vote on the acceptance of Kalumet into the Apache incubator.

The proposal is available at: http://wiki.apache.org/incubator/KalumetProposal
(for your convenience, a snapshot is also copied below)

The vote options (please cast your vote) :

[ ] +1 Accept Kalumet for incubation
[ ] +0 Don't care
[ ] -1 Reject for the following reason:

The vote is open for 72 hours.

Here my (binding) +1 .

Thanks,
-- 
Olivier Lamy
Talend : http://talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy


= Kalumet - Complete Environment Deployer Toolbox =

== Abstract ==

Kalumet a complete environment manager and deployer including J2EE
environments (application servers, applications, etc), softwares, and
resources.
It's a perfect complement to continuous integration (managed by maven
and continuum or jenkins for instance) by adding continuous
deployment.
The whole factory chain is cover and the software administrator
managed all environments in secure and safe way, whatever the
underlying application servers (Apache Geronimo, Apache Tomcat, Apache
TomEE, RedHat JBoss, Oracle Weblogic or IBM Websphere) or softwares
(printout system, Apache HTTPd, operating systems, etc) are.

Kalumet provides two kind of components :

* Apache Kalumet agent are installed locally on the target server box.

* Apache Kalumet console controls and manages the agents, allowing the
software administrator to update all environments from a central
multi-user web tool.

== Background ==

Currently, Apache Kalumet is named BuildProcess AutoDeploy
(http://buildprocess.sourceforge.net). The development has begun 4
years ago and several release have already been provided.

== Rationale ==

The software environments administration is heavy cost task with a
high level of human actions, especially when mixing J2EE environments,
different operating systems, softwares, etc It suffers :

* a different set of scripts or actions/procedures depending of the
application server used (Geronimo, Tomcat, JBoss, Weblogic, Websphere,
...) or other middlewares (portals or ESB like ServiceMix, HTTP
servers like Apache HTTPd, etc);

* a high level of risk due to human actions (for example, an
administrator can forget to deploy a JDBC DataSource, or forget to
change an application configuration file);

* migrate an application from an environment to another one request
boring actions (for example, migration applications and all linked
resources from a testing environment to a production one, this action
is named "promote");

* the upgrade process can be long (depending of the number of
applications and complexity);

* most of resources are stored on the application server box, not in a
central repository.

Apache Kalumet secures the environment deployment and covers the whole
environment scope including J2EE parts (EAR/WAR archives with
classloader policy, JDBC DataSources, JMS Connection Factories, JMS
Queues/Topics, etc) and resources (operating systems, softwares, etc)
in a unique way. It's heavily expendable, that means that you can
create new plugins for dedicated resources.

== Initial Goals ==

When we have begun AutoDeploy, the first goal was to provide several
J2EE application servers JMX plugins. But quickly, we have seen that
multi-application servers support was only a part of the software
administration needs.

That's why we have extended AutoDeploy to provide agents and a central
console hosting all environments knowledges (artifact versions,
resources, etc). Using the console, several administrators can use a
central tool to manage all environments in a collaborative, unique and
secure way.

The target is now to provide a complete tool to fully administrate a
data center servers, softwares and middlewares.

= Current Status =

Currently, BuildProcess AutoDeploy provides two branches :

* the 0.5 branch (with the 0.5.6 latest release) is the current stable
branch. This branch is built every night using Apache Continuum
(http://continuum.nanthrax.net).

* the 0.6 branch is in progress and it's the target one to become Apache Kalumet

== Community ==

Currently, AutoDeploy community contains two comitters, 5 contributors
and around 50 users.
BuildProcess AutoDeploy is used in production and test in several companies :

* Fimasys France (http://www.fimasys.com)

* AMP-AXA Australia (https://www.amp.com.au/wps/portal/au)

* Vodacom South Africa (http://www.vodacom.com)

* Mayo Clinic USA (http://www.mayoclinic.com)

* NSW Attorney General Australia (http://www.lawlink.nsw.gov.au)

== Core Developers ==

The core developers for AutoDeploy/Apache Kalumet project are :

* Jean-Baptiste Onofré (founder in 2004).

* Mike Duffy, WebSphere Consultant, contributes since 2005.

== Open Source ==

Sin

Re: [VOTE] accept DirectMemory as new Apache Incubator podling

[j...@nanthrax.net]

+1 (binding)

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com

- Reply message -
From: "Simone Tripodi" 
To: 
Subject: [VOTE] accept DirectMemory as new Apache Incubator podling
Date: Sun, Oct 2, 2011 9:36 am


Hi all guys,

I'm now calling a formal VOTE on the DirectMemory proposal located here:

http://wiki.apache.org/incubator/DirectMemoryProposal

Proposal text copied at the bottom of this email.

VOTE close on Tuesday, October 4, early 7:30 AM CET.

Please VOTE:

[ ] +1 Accept DirectMemory into the Apache Incubator
[ ] +0 Don't care
[ ] -1  Don't Accept DirectMemory into the Apache Incubator because...

Thanks in advance for participating!

All the best, have a nice day,
Simo

P.S. Here's my +1

http://people.apache.org/~simonetripodi/
http://www.99soft.org/

= DirectMemory =

== Abstract ==
The following proposal is about Apache !DirectMemory, a Java
!OpenSource multi-layered cache implementation featuring off-heap
memory storage (a-la Terracotta !BigMemory) to enable caching of Java
objects without degrading JVM performance

== Proposal ==
!DirectMemory's main purpose is to to act as a second level cache
(after a heap based one) able to store large amounts of data without
filling up the Java heap and thus avoiding long garbage collection
cycles. Although serialization has a runtime cost store/retrieve
operations are in the sub-millisecond range being pretty acceptable in
every usage scenario even as a first level cache and, most of all,
outperforms heap storage when the count of the entries goes over a
certain amount. !DirectMemory implements cache eviction based on a
simple LFU (Least Frequently Used) algorythm and also on item
expiration. Included in the box is a small set of utility classes to
easily handle off-heap memory buffers.

== Background ==
!DirectMemory is a project was born in the 2010 thanks to Raffaele P.
Guidi initial effort under
[[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already
licensed under the Apache License 2.0.

== Rationale ==
The rationale behind !DirectMemory is bringing off-heap caching to the
open source world, empowering FOSS developers and products with a tool
that enables breaking the heap barrier and override the JVM garbage
collection mechanism collection - which could be useful in scenarios
where RAM needs are over the usual limits (more than 8, 12, 24gb) and
to ease usage of off-heap memory in general

= Current Status =

== Meritocracy ==
As a majority of the initial project members are existing ASF
committers, we recognize the desirability of running the project as a
meritocracy.  We are eager to engage other members of the community
and operate to the standard of meritocracy that Apache emphasizes; we
believe this is the most effective method of growing our community and
enabling widespread adoption.

== Core Developers ==
In alphabetical order:

 * Christian Grobmeier 
 * Maurizio Cucchiara 
 * Olivier Lamy 
 * Raffaele P. Guidi 
 * Simone Gianni 
 * Simone Tripodi 
 * Tommaso Teofili 

== Alignment ==
The purpose of the project is to develop and maintain !DirectMemory
implementation that can be used by other Apache projects.

= Known Risks =
== Orphaned Products ==
!DirectMemory does not have any reported production usage, yet, but is
getting traction with developers and being evaluated by potential
users and thus the risks of it being orphaned are minimal

== Inexperience with Open Source ==
All of the committers have experience working in one or more open
source projects inside and outside ASF.

== Homogeneous Developers ==
The list of initial committers are geographically distributed across
the Europe with no one company being associated with a majority of the
developers.  Many of these initial developers are experienced Apache
committers already and all are experienced with working in distributed
development communities.

== Reliance on Salaried Developers ==
To the best of our knowledge, none of the initial committers are being
paid to develop code for this project.

== Relationships with Other Apache Products ==
!DirectMemory fits naturally in the ASF because it could be
successfully employed together with a large number of ASF products
ranging from JCS - as a new cache region between the heap and indexed
file ones, to ORM systems like Cayenne (i.e. replacing current OSCache
based implementation), Apache JDO and JPA implementations and also
java based databases (i.e. Derby) and all systems managing large
amounts of data from Hadoop to Cassandra

== A Excessive Fascination with the Apache Brand ==
While the Apache Software Foundation would be a good home for the
!DirectMemory project it already has some traction and it could live
on its own - however we see reciprocal benefits for both the ASF and
the project in adopting the brand to better reach the community

= Documentation =
 1. [[https://github.com/raffaeleguidi/DirectMemory|The original
DirectMemory HomePage]]
 2. [[ht

Re: [PROPOSAL][RFC] Fediz for the Apache Incubator

[j...@nanthrax.net]

Hi Nick,

Thanks for your comment, I will upgrade the proposal.

Regards
JB

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com

- Reply message -
From: "Nick Kew" 
To: 
Subject: [PROPOSAL][RFC] Fediz for the Apache Incubator
Date: Thu, Nov 3, 2011 12:25 pm



On 1 Nov 2011, at 09:22, Jean-Baptiste Onofré wrote:

> Hi,
> 
> I would like to propose Fediz to be an Apache Incubator project.

As others have pointed out, this looks like some familiar technologies.

We know that OpenID is widely supported, by web client, server and
application software, and some of the biggest providers.  OpenAuth
perhaps less so, but they're spoken of as a pair.

How about a proper exposition of:
 - Does Fediz include an implementaion of OID/OAuth?
 - If yes, does it do other things too, and what's the motivation?
   How would you react to accusations of "embrace and extend"?
- If no, why should we want another, competing framework/standard?
- If no, where is it in fact supported in the real world?

I think we should see these issues properly addressed in the proposal!

-- 
Nick Kew
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL][RFC] Fediz for the Apache Incubator

[j...@nanthrax.net]

Hi Marcel,

You're right, ir's a forgot. I'm upgrading the proposal.

Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com

- Reply message -
From: "Marcel Offermans" 
To: 
Subject: [PROPOSAL][RFC] Fediz for the Apache Incubator
Date: Thu, Nov 3, 2011 12:40 pm


On Nov 1, 2011, at 10:22 AM, Jean-Baptiste Onofré wrote:

> http://wiki.apache.org/incubator/FedizProposal

Definitely an interesting proposal! Just a comment on the affiliations section: 
isn't it true that both Olivier Lamy and Colm O'hEigeartaigh are also working 
for Talend? Of course part of the incubation process will be to attract other 
developers, I just think it's fair to list affiliations for all initial 
committers.

Greetings, Marcel


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Retire Olio [Was: Retire Olio?]

[j...@nanthrax.net]

+1 (binding)

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com

- Reply message -
From: "Benson Margulies" 
To: 
Subject: [VOTE] Retire Olio [Was: Retire Olio?]
Date: Thu, Nov 10, 2011 5:33 pm


+1 (binding)

On Fri, Nov 11, 2011 at 12:17 AM, Henri Yandell  wrote:
> Coming back to this.
>
> It unfortunately seems that there's no (even optimistic) expectation
> that Olio will graduate.
>
> So, voting:
>
> [ ] +1
> [ ] -1, no because...
>
> Hen
>
> On Tue, Aug 16, 2011 at 11:27 PM, William A. Rowe Jr.
>  wrote:
>> On 8/17/2011 12:47 AM, Henri Yandell wrote:
>>> On Tue, Aug 16, 2011 at 10:40 PM, William A. Rowe Jr.
>>>  wrote:
 On 8/17/2011 12:37 AM, Henri Yandell wrote:
> The copyright item isn't signed off at
> https://incubator.apache.org/projects/olio.html.
>
> So would need to delete the code (assuming a successful retirement vote).

 Where are the mentors?

 Wondering how conflicted-providence IP would hit svn in the first place.
>>>
>>> Digging a bit:
>>>
>>> "Initial Olio code dump from Sun" by clr. r700550
>>> "Added rails webapp" by wsobel. r705828
>>> "Adding Web20Emulator" by sheetal. r706388
>>>
>>> There were other large adds, but those were the three initial big ones.
>>>
>>> I don't see any software grants relating to Olio. I see lots in the
>>> board reports about struggling to get committer diversity because the
>>> committers were at 3 corporations.
>>>
>>> I don't believe that conflicted-providence IP would have hit svn, yet
>>> if it's not signed off and (assuming no one steps up to say otherwise)
>>> I think delete is the only option we have.
>>
>> Agreed.  Unless the mentors can check off that checkbox prior to the
>> project's dormancy, svn will need to be rm'ed.
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache ACE as a TLP

[j...@nanthrax.net]

+1 (binding)

Regards
JB

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com

- Reply message -
From: "Marcel Offermans" 
To: 
Subject: [VOTE] Apache ACE as a TLP
Date: Sat, Dec 17, 2011 12:55 pm


Hello all,

As the discussion about the resolution [1] offered no further feedback, it is 
time for the Apache ACE community to request that the IPMC vote on recommending 
this resolution [2] to the ASF board.

Please cast your vote:

[ ] +1 to recommend ACE's graduation
[ ]  0 don't care
[ ] -1 no, don't recommend yet, (because...)

The vote will be open for 72 hours.

Greetings, Marcel


[1] http://markmail.org/thread/wfrvwmnu3y22oxys

[2] see below:

## Resolution to create a TLP from graduating Incubator podling

X. Establish the Apache ACE Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software related to the management and deployment
   of OSGi based and other software artifacts for distribution
   at no charge to the public.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the "Apache ACE Project",
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further

   RESOLVED, that the Apache ACE Project be and hereby is
   responsible for the creation and maintenance of software
   related to the management and deployment of OSGi based and
   other software artifacts;
   and be it further

   RESOLVED, that the office of "Vice President, Apache ACE" be
   and hereby is created, the person holding such office to
   serve at the direction of the Board of Directors as the chair
   of the Apache ACE Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache ACE Project; and be it further

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache ACE Project:

 * Angelo van der Sijpt 
 * Brian Topping
 * Clement Escoffier
 * Carsten Ziegeler 
 * Jean-Baptiste Onofre 
 * Karl Pauls   
 * Marcel Offermans 
 * Toni Menzel  

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Marcel Offermans
   be appointed to the office of Vice President, Apache ACE, to
   serve in accordance with and subject to the direction of the
   Board of Directors and the Bylaws of the Foundation until
   death, resignation, retirement, removal or disqualification,
   or until a successor is appointed; and be it further

   RESOLVED, that the initial Apache ACE PMC be and hereby is
   tasked with the creation of a set of bylaws intended to
   encourage open development and increased participation in the
   Apache ACE Project; and be it further

   RESOLVED, that the Apache ACE Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator ACE podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator ACE podling encumbered upon the Apache Incubator
   Project are hereafter discharged.


Note to moderators: I sent this message before, over 24 hours ago, with my 
apache e-mail address (that is not subscribed to this list). It's still stuck 
in moderation, which is why I'm sending it again today. If ultimately both end 
up on the list, my apologies, I will summarize the responses over both messages.

Re: [VOTE] Clarify the role of the Champion as an "incubation coordinator"

[j...@nanthrax.net]

+1 (binding)

Regards
JB

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com

- Reply message -
From: "Mark Struberg" 
To: "general@incubator.apache.org" 
Subject: [VOTE] Clarify the role of the Champion as an "incubation coordinator"
Date: Fri, Jan 13, 2012 8:43 am


+1 (binding)


LieGrue,
strub



- Original Message -
> From: "Mattmann, Chris A (388J)" 
> To: "general@incubator.apache.org" 
> Cc: 
> Sent: Thursday, January 12, 2012 7:34 PM
> Subject: Re: [VOTE] Clarify the role of the Champion as an "incubation 
> coordinator"
> 
> +1 (binding).
> 
> Cheers,
> Chris
> 
> On Jan 12, 2012, at 7:02 AM, Bertrand Delacretaz wrote:
> 
>>  Hi Incubator PMC,
>> 
>>  Here's the result of discussions that took place around Christmas -
>>  the goal is to try and improve the PMC's oversight on podling reports
>>  and missing mentors, by having the Champion act as the main liaison
>>  between a podling and the Incubator PMC.
>> 
>>  If we agree on the below principles, I'll update the
>> 
> http://incubator.apache.org/incubation/Roles_and_Responsibilities.html#Champion
>>  description accordingly.
>> 
>>  Please cast your votes to accept the following clarifications to the
>>  Champion's role - this majority vote is open for at least 72 hours:
>> 
>>  Once a podling is created, and until it graduates, its Champion must:
>> 
>>  1. Coordinate the creation and timely delivery of the podling's board 
> reports.
>> 
>>  2. Keep an eye on the mentors' activity and take action (ask for new
>>  mentors, talk to the Incubator PMC) if they don't seem to provide
>>  enough oversight or mentorship to the podling,
>> 
>>  As far as the podling is concerned:
>> 
>>  3. The podling can elect a new Champion at any time, and must notify
>>  the Incubator PMC when that happens.
>> 
>>  4. Existing podlings will need to elect a Champion, unless their
>>  current one agrees to take on the above tasks.
>> 
>>  5. The podling reports must indicate who the current Champion is.
>> 
>>  -Bertrand
>> 
>>  -
>>  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>  For additional commands, e-mail: general-h...@incubator.apache.org
>> 
> 
> 
> ++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattm...@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache BVal as a TLP

[j...@nanthrax.net]

+1 (binding)

Regards
JB

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com

- Reply message -
From: "Niall Pemberton" 
To: 
Subject: [VOTE] Apache BVal as a TLP
Date: Thu, Feb 9, 2012 1:02 am


+1

Niall

On Wed, Feb 8, 2012 at 2:39 PM, Mohammad Nour El-Din  wrote:
> Hi...
>
>   It has been discussed, since a while, about the graduation of Apache
> BVal, whether to graduate to a TLP or Subproject and whether it is time or
> not, [1], [2] and [3].
> In the past few weeks there has been a [VOTE], [4], which formally
> discussed the graduation to a TLP project. Result announcement can be found
> here, [5]. It also has been decided to name the project Apache BVal [6].
> The resolution charter content has been discussed and reviewed here [7].
>
> *NOTE*: As per Niall's request, his name has been removed from the proposed
> PMC [8].
>
> The Apache Bean Validation community sees it is time to request an IPMC
> [VOTE] on recommending this resolution [9] to the ASF board.
>
> Accordingly, would you please cast your vote:
>
> [ ] +1 to recommend Bean Validation's graduation
> [ ]  0 don't care
> [ ] -1 no, don't recommend yet, (because...)
>
> The vote will be open for 72 hours.
>
> [1] - http://s.apache.org/oTC
> [2] - http://s.apache.org/I8C
> [3] - http://s.apache.org/EQE
> [4] - http://s.apache.org/rU
> [5] - http://s.apache.org/7Sw
> [6] - http://s.apache.org/tY
> 
> [7] - *http://s.apache.org/49R*
> [8] - http://s.apache.org/JYS
> [9] - See below:
>
> ## Resolution to create a TLP from graduating Incubator podling
>
>    X. Establish the Apache BVal Project
>
>  WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software related to the Bean Validation
> Specification and its implementation as Apache BVal
> for distribution at no charge to the public.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache BVal Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache BVal Project be and hereby is
> responsible for the creation and maintenance of software
> related to creating an implementation compliant with the
> Bean Validation Specification and a library of pre-developed
> validators and extensions; and be it further
>
> RESOLVED, that the office of "Vice President, Apache BVal" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache BVal Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache BVal Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache BVal Project:
>
>   - Albert Lee 
>   - Carlos Vara Callau 
>   - David Jencks 
>   - Donald Woods 
>   - Gerhard Petracek 
>   - Jeremy Bauer 
>   - Kevan Lee Miller 
>   - Luciano Resende 
>   - Matthias Wessendorf 
>   - Matthew Jason Benson 
>   - Mohammad Nour El-Din 
>   - Roman Stumm 
>   - Simone Tripodi 
>   - Mark Struberg 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matthew Jason Benson
> be appointed to the office of Vice President, Apache BVal, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the initial Apache BVal PMC be and hereby is
> tasked with the creation of a set of bylaws intended to
> encourage open development and increased participation in the
> Apache BVal Project; and be it further
>
> RESOLVED, that the Apache BVal Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Bean Validation podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Bean Validation podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
> --
> Thanks
> - Mohammad Nour
> 
> "Life is like riding a bicycle. To keep your balance you must keep moving"
> - Albert Einstein

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Retire Kato

[j...@nanthrax.net]

+1 (binding)

Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://wwx.talend.com

- Reply message -
From: "Benson Margulies" 
To: 
Subject: [VOTE] Retire Kato
Date: Wed, Jun 27, 2012 1:29 am


Based on the status of this podling as reported in the June board
report, I propose that the IPMC retire the Kato podling.

I'm not sure how long a vote for this should remain open.

here is my +1.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org