Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
Already done, unless there is something I missed... http://old.nabble.com/-VOTE---PROPOSAL--Validation-incubator-for-JSR-303-Bean-Validation-to27705544.html#a27751839 -Donald On 3/2/10 3:46 PM, Kevan Miller wrote: > > On Feb 26, 2010, at 7:18 PM, Nick Kew wrote: > >> >> On 26 Feb 2010, at 19:01, Kevan Miller wrote: >> >>> >>> On Feb 23, 2010, at 4:03 PM, Nick Kew wrote: >>> On Tue, 23 Feb 2010 12:51:35 -0500 Donald Woods wrote: > I'm open to suggestions BeanValidation, OpenValidation, Validera, ... Any of those work for me, though OpenValidation has a hint of the same problem. BeanValidation might be ideal, and scans better than, say JSR303-Validation :) >>> >>> Most likely outcome -- this ends up becoming Commons Validator version 2. >>> If project decides to go TLP, the BeanValidation would be good with me. I >>> would certainly expect this to be resolved by the community for graduation. >> >> Sounds OK to me. >> >> Since it looks as if my previous reply got lost in the ether, let me confirm, >> I'm happy to withdraw my -1 on the basis that the issue has been raised >> and will be resolved before or during incubation. > > Thanks Nick. Donald -- you called the vote. Can you close it, also? > > --kevan > - > 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] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Feb 26, 2010, at 7:18 PM, Nick Kew wrote: > > On 26 Feb 2010, at 19:01, Kevan Miller wrote: > >> >> On Feb 23, 2010, at 4:03 PM, Nick Kew wrote: >> >>> On Tue, 23 Feb 2010 12:51:35 -0500 >>> Donald Woods wrote: >>> I'm open to suggestions BeanValidation, OpenValidation, Validera, ... >>> >>> Any of those work for me, though OpenValidation has a hint of the >>> same problem. BeanValidation might be ideal, and scans better than, >>> say JSR303-Validation :) >> >> Most likely outcome -- this ends up becoming Commons Validator version 2. If >> project decides to go TLP, the BeanValidation would be good with me. I would >> certainly expect this to be resolved by the community for graduation. > > Sounds OK to me. > > Since it looks as if my previous reply got lost in the ether, let me confirm, > I'm happy to withdraw my -1 on the basis that the issue has been raised > and will be resolved before or during incubation. Thanks Nick. Donald -- you called the vote. Can you close it, also? --kevan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
Thanks Matthias and I've added you as a mentor. -Donald On 2/23/10 10:22 PM, Matthias Wessendorf wrote: > +1 to accept Validation into the Incubator > > afterwards we still can see where it actually ends up > > however I for sure want to see this at Apache. > > If you guys need a champion or mentor, count me in !! > > -M > > On Tue, Feb 23, 2010 at 11:45 PM, Donald Woods wrote: >> We're leaving the TLP/sub-project decision till graduation... >> >> -Donald >> >> >> On 2/23/10 5:36 PM, Brett Porter wrote: >>> As I understand it from the proposal, they intend to be Apache Commons >>> Validation. >>> >>> On 24/02/2010, at 4:19 AM, Nick Kew wrote: >>> On Tue, 23 Feb 2010 10:57:33 -0500 Donald Woods wrote: > Given the lack of response on the proposal and the push from our > champion to get moving :-), I'll assume lazy consensus and call a vote. > > I would like to present for a vote the following proposal to be > sponsored by the Incubator PMC for a new Validation podling. The goal > is to build a community around delivering a JSR-303 Bean Validation > implementation based on a new incoming codebase from Agimatec GmbH. > > The proposal is available on the wiki at and included below: > > http://wiki.apache.org/incubator/ValidationProposal -1 to a project that could end up being called "Apache Validation" or just "Validation". That's too big/general a word for a project name. No objection under a changed name. I'd suggest adding an adjective to indicate what is being validated. -- Nick Kew - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> -- >>> Brett Porter >>> br...@apache.org >>> http://brettporter.wordpress.com/ >>> >>> >>> >>> >>> >>> - >>> 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] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On 26 Feb 2010, at 19:01, Kevan Miller wrote: > > On Feb 23, 2010, at 4:03 PM, Nick Kew wrote: > >> On Tue, 23 Feb 2010 12:51:35 -0500 >> Donald Woods wrote: >> >>> I'm open to suggestions BeanValidation, OpenValidation, Validera, ... >> >> Any of those work for me, though OpenValidation has a hint of the >> same problem. BeanValidation might be ideal, and scans better than, >> say JSR303-Validation :) > > Most likely outcome -- this ends up becoming Commons Validator version 2. If > project decides to go TLP, the BeanValidation would be good with me. I would > certainly expect this to be resolved by the community for graduation. Sounds OK to me. Since it looks as if my previous reply got lost in the ether, let me confirm, I'm happy to withdraw my -1 on the basis that the issue has been raised and will be resolved before or during incubation. -- Nick Kew - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
Hi Donald, Names are a common issue to be resolved *during* incubation. See JSecurity mail threads for a somewhat extreme example. So, no, don't restart the vote. Craig On Feb 26, 2010, at 11:18 AM, Donald Woods wrote: Given the feedback so far, I'm leaning towards BeanValidation as the name and BVAL as the short name (for JIRA and mailing lists), since this is a new codebase and not a natural follow-on to Common Validator 1.x. There are features in Validator 1.x that will probably never be implemented in this codebase (like JSP extensions) as this will be handled by MyFaces, so any users seeing a new commons-validator-2.0 may be surprised that nothing is backwards compatible If we decide to update the project name and resource names now, does that require a new vote? -Donald On 2/26/10 2:01 PM, Kevan Miller wrote: On Feb 23, 2010, at 4:03 PM, Nick Kew wrote: On Tue, 23 Feb 2010 12:51:35 -0500 Donald Woods wrote: I'm open to suggestions BeanValidation, OpenValidation, Validera, ... Any of those work for me, though OpenValidation has a hint of the same problem. BeanValidation might be ideal, and scans better than, say JSR303-Validation :) Most likely outcome -- this ends up becoming Commons Validator version 2. If project decides to go TLP, the BeanValidation would be good with me. I would certainly expect this to be resolved by the community for graduation. --kevan - 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 Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@sun.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
Given the feedback so far, I'm leaning towards BeanValidation as the name and BVAL as the short name (for JIRA and mailing lists), since this is a new codebase and not a natural follow-on to Common Validator 1.x. There are features in Validator 1.x that will probably never be implemented in this codebase (like JSP extensions) as this will be handled by MyFaces, so any users seeing a new commons-validator-2.0 may be surprised that nothing is backwards compatible If we decide to update the project name and resource names now, does that require a new vote? -Donald On 2/26/10 2:01 PM, Kevan Miller wrote: > > On Feb 23, 2010, at 4:03 PM, Nick Kew wrote: > >> On Tue, 23 Feb 2010 12:51:35 -0500 >> Donald Woods wrote: >> >>> I'm open to suggestions BeanValidation, OpenValidation, Validera, ... >> >> Any of those work for me, though OpenValidation has a hint of the >> same problem. BeanValidation might be ideal, and scans better than, >> say JSR303-Validation :) > > Most likely outcome -- this ends up becoming Commons Validator version 2. If > project decides to go TLP, the BeanValidation would be good with me. I would > certainly expect this to be resolved by the community for graduation. > > --kevan > - > 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] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Feb 23, 2010, at 4:03 PM, Nick Kew wrote: > On Tue, 23 Feb 2010 12:51:35 -0500 > Donald Woods wrote: > >> I'm open to suggestions BeanValidation, OpenValidation, Validera, ... > > Any of those work for me, though OpenValidation has a hint of the > same problem. BeanValidation might be ideal, and scans better than, > say JSR303-Validation :) Most likely outcome -- this ends up becoming Commons Validator version 2. If project decides to go TLP, the BeanValidation would be good with me. I would certainly expect this to be resolved by the community for graduation. --kevan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On 2/23/10 10:57 AM, Donald Woods wrote: Given the lack of response on the proposal and the push from our champion to get moving :-), I'll assume lazy consensus and call a vote. I would like to present for a vote the following proposal to be sponsored by the Incubator PMC for a new Validation podling. The goal is to build a community around delivering a JSR-303 Bean Validation implementation based on a new incoming codebase from Agimatec GmbH. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/ValidationProposal [] +1 to accept Validation into the Incubator [] 0 don't care [] -1 object and reason why. +1 Bill - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
The proposal says that this will take over for Commons Validator. Why are we still discussing names? We already have one, Commons Validator. On Thu, Feb 25, 2010 at 9:06 AM, Gurkan Erdogdu wrote: > +1 (non-binding). > > OpenBeanValidation as a name will be cool :) > > Thanks; > > --Gurkan > > 2010/2/23 Donald Woods > >> Given the lack of response on the proposal and the push from our >> champion to get moving :-), I'll assume lazy consensus and call a vote. >> >> I would like to present for a vote the following proposal to be >> sponsored by the Incubator PMC for a new Validation podling. The goal >> is to build a community around delivering a JSR-303 Bean Validation >> implementation based on a new incoming codebase from Agimatec GmbH. >> >> The proposal is available on the wiki at and included below: >> >> http://wiki.apache.org/incubator/ValidationProposal >> >> >> [] +1 to accept Validation into the Incubator >> [] 0 don't care >> [] -1 object and reason why. >> >> >> Thanks, >> Donald Woods >> >> >> Proposal text from the wiki >> >> Validation >> >> Abstract >> >> The Validation project will deliver an implementation of the Bean >> Validation Specification (JSR303) >> >> Proposal >> >> The initial Validation codebase will use the Agimatec Validation source, >> which is an implementation of the Bean Validation Specification (JSR303). >> >> Although the destination of the Validation podling is not fixed, the >> idea is that it will graduate to Apache Commons and replace the existing >> Validator 1.x component as a new 2.0 codebase. >> >> Background >> >> Agimatec Validation has been developed by Agimatec Gmbh and is about 90% >> complete towards implementing the JSR303 specification. The >> Agimatec-Validation project is currently hosted on Google Code and is >> ASL 2.0 licensed. Agimatec has no intention to complete or maintain the >> implementation but has given the lead developer permission to continue >> working on the project on his own time. >> >> A number of existing Apache projects (Geronimo, OpenJPA, MyFaces, >> OpenEJB, Commons) are interested in an implementation of the Bean >> Validation specification and Donald Woods suggested adopting the >> Agimatec Validation code rather than starting from scratch. >> >> Rationale >> >> There is currently no Apache project focused on providing a JSR-303 >> implementation. The existing Commons Validator 1.x project codebase does >> not include support for Java 5 annotations and predates the JSR-303 >> specification effort. By using the Agimatec-Validation code, we can >> bootstrap the effort to create a Validator 2 release and focus on >> polishing/enhancing the code, certification activities and integration >> and support of other Apache projects. >> >> Current Status >> >> Agimatec Validation and is about 95% complete towards implementing the >> JSR303 specification. >> >> An SGA for the Agimatec Validation has been received and on file from >> Agimatec Gmbh. >> >> 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. >> >> Community >> >> Even though the reference implementation for the JSR-303 Bean Validation >> specification is licensed under ASL 2.0, it is not being developed with >> meritocracy in mind, as the release process is controlled by the JBoss >> division of Red Hat to meet their own product needs. >> >> Validation aims to build a community of developers interested in the >> definition and delivery of a JSR-303 compliant runtime, which can be >> reused as a common component by a number of different projects (like >> Geronimo, OpenJPA, MyFaces, ) By maintaining independence of the >> target runtime, it is our intention to build the broadest possible >> community of developers. >> >> Core Developers >> >> The lead developer from the Agimatec Validation project will be joined >> by a number of committers from existing ASF projects. >> >> Alignment >> >> The purpose of Validation is to develop a certified implementation of >> JSR-303. Some components may be developed and delivered by other Apache >> projects, like: >> >> * Bean Validation 1.0 spec API - Apache Geronimo Specs subproject >> * JSF2 integration - MyFaces ExtVal components >> >> Known Risks >> >> The current JSR-303 portions of the Agimatec-Validation code was >> developed by a single developer from Agimatec (Roman) with no available >> documents on the structure of the code. >> >> Orphaned Products >> >> The project will be implementing the JSR-303 Bean Validation >> specification, which is a required component for both the Web and Full >> profiles of Java EE 6. There is minimal risk of this work becoming >
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
:-) that's OK, but somehow I like more fancy names. -M On Thu, Feb 25, 2010 at 3:06 PM, Gurkan Erdogdu wrote: > +1 (non-binding). > > OpenBeanValidation as a name will be cool :) > > Thanks; > > --Gurkan > > 2010/2/23 Donald Woods > >> Given the lack of response on the proposal and the push from our >> champion to get moving :-), I'll assume lazy consensus and call a vote. >> >> I would like to present for a vote the following proposal to be >> sponsored by the Incubator PMC for a new Validation podling. The goal >> is to build a community around delivering a JSR-303 Bean Validation >> implementation based on a new incoming codebase from Agimatec GmbH. >> >> The proposal is available on the wiki at and included below: >> >> http://wiki.apache.org/incubator/ValidationProposal >> >> >> [] +1 to accept Validation into the Incubator >> [] 0 don't care >> [] -1 object and reason why. >> >> >> Thanks, >> Donald Woods >> >> >> Proposal text from the wiki >> >> Validation >> >> Abstract >> >> The Validation project will deliver an implementation of the Bean >> Validation Specification (JSR303) >> >> Proposal >> >> The initial Validation codebase will use the Agimatec Validation source, >> which is an implementation of the Bean Validation Specification (JSR303). >> >> Although the destination of the Validation podling is not fixed, the >> idea is that it will graduate to Apache Commons and replace the existing >> Validator 1.x component as a new 2.0 codebase. >> >> Background >> >> Agimatec Validation has been developed by Agimatec Gmbh and is about 90% >> complete towards implementing the JSR303 specification. The >> Agimatec-Validation project is currently hosted on Google Code and is >> ASL 2.0 licensed. Agimatec has no intention to complete or maintain the >> implementation but has given the lead developer permission to continue >> working on the project on his own time. >> >> A number of existing Apache projects (Geronimo, OpenJPA, MyFaces, >> OpenEJB, Commons) are interested in an implementation of the Bean >> Validation specification and Donald Woods suggested adopting the >> Agimatec Validation code rather than starting from scratch. >> >> Rationale >> >> There is currently no Apache project focused on providing a JSR-303 >> implementation. The existing Commons Validator 1.x project codebase does >> not include support for Java 5 annotations and predates the JSR-303 >> specification effort. By using the Agimatec-Validation code, we can >> bootstrap the effort to create a Validator 2 release and focus on >> polishing/enhancing the code, certification activities and integration >> and support of other Apache projects. >> >> Current Status >> >> Agimatec Validation and is about 95% complete towards implementing the >> JSR303 specification. >> >> An SGA for the Agimatec Validation has been received and on file from >> Agimatec Gmbh. >> >> 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. >> >> Community >> >> Even though the reference implementation for the JSR-303 Bean Validation >> specification is licensed under ASL 2.0, it is not being developed with >> meritocracy in mind, as the release process is controlled by the JBoss >> division of Red Hat to meet their own product needs. >> >> Validation aims to build a community of developers interested in the >> definition and delivery of a JSR-303 compliant runtime, which can be >> reused as a common component by a number of different projects (like >> Geronimo, OpenJPA, MyFaces, ) By maintaining independence of the >> target runtime, it is our intention to build the broadest possible >> community of developers. >> >> Core Developers >> >> The lead developer from the Agimatec Validation project will be joined >> by a number of committers from existing ASF projects. >> >> Alignment >> >> The purpose of Validation is to develop a certified implementation of >> JSR-303. Some components may be developed and delivered by other Apache >> projects, like: >> >> * Bean Validation 1.0 spec API - Apache Geronimo Specs subproject >> * JSF2 integration - MyFaces ExtVal components >> >> Known Risks >> >> The current JSR-303 portions of the Agimatec-Validation code was >> developed by a single developer from Agimatec (Roman) with no available >> documents on the structure of the code. >> >> Orphaned Products >> >> The project will be implementing the JSR-303 Bean Validation >> specification, which is a required component for both the Web and Full >> profiles of Java EE 6. There is minimal risk of this work becoming >> non-strategic and the contributors are confident that a larger community >> will form
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
+1 (non-binding). OpenBeanValidation as a name will be cool :) Thanks; --Gurkan 2010/2/23 Donald Woods > Given the lack of response on the proposal and the push from our > champion to get moving :-), I'll assume lazy consensus and call a vote. > > I would like to present for a vote the following proposal to be > sponsored by the Incubator PMC for a new Validation podling. The goal > is to build a community around delivering a JSR-303 Bean Validation > implementation based on a new incoming codebase from Agimatec GmbH. > > The proposal is available on the wiki at and included below: > > http://wiki.apache.org/incubator/ValidationProposal > > > [] +1 to accept Validation into the Incubator > [] 0 don't care > [] -1 object and reason why. > > > Thanks, > Donald Woods > > > Proposal text from the wiki > > Validation > > Abstract > > The Validation project will deliver an implementation of the Bean > Validation Specification (JSR303) > > Proposal > > The initial Validation codebase will use the Agimatec Validation source, > which is an implementation of the Bean Validation Specification (JSR303). > > Although the destination of the Validation podling is not fixed, the > idea is that it will graduate to Apache Commons and replace the existing > Validator 1.x component as a new 2.0 codebase. > > Background > > Agimatec Validation has been developed by Agimatec Gmbh and is about 90% > complete towards implementing the JSR303 specification. The > Agimatec-Validation project is currently hosted on Google Code and is > ASL 2.0 licensed. Agimatec has no intention to complete or maintain the > implementation but has given the lead developer permission to continue > working on the project on his own time. > > A number of existing Apache projects (Geronimo, OpenJPA, MyFaces, > OpenEJB, Commons) are interested in an implementation of the Bean > Validation specification and Donald Woods suggested adopting the > Agimatec Validation code rather than starting from scratch. > > Rationale > > There is currently no Apache project focused on providing a JSR-303 > implementation. The existing Commons Validator 1.x project codebase does > not include support for Java 5 annotations and predates the JSR-303 > specification effort. By using the Agimatec-Validation code, we can > bootstrap the effort to create a Validator 2 release and focus on > polishing/enhancing the code, certification activities and integration > and support of other Apache projects. > > Current Status > > Agimatec Validation and is about 95% complete towards implementing the > JSR303 specification. > > An SGA for the Agimatec Validation has been received and on file from > Agimatec Gmbh. > > 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. > > Community > > Even though the reference implementation for the JSR-303 Bean Validation > specification is licensed under ASL 2.0, it is not being developed with > meritocracy in mind, as the release process is controlled by the JBoss > division of Red Hat to meet their own product needs. > > Validation aims to build a community of developers interested in the > definition and delivery of a JSR-303 compliant runtime, which can be > reused as a common component by a number of different projects (like > Geronimo, OpenJPA, MyFaces, ) By maintaining independence of the > target runtime, it is our intention to build the broadest possible > community of developers. > > Core Developers > > The lead developer from the Agimatec Validation project will be joined > by a number of committers from existing ASF projects. > > Alignment > > The purpose of Validation is to develop a certified implementation of > JSR-303. Some components may be developed and delivered by other Apache > projects, like: > >* Bean Validation 1.0 spec API - Apache Geronimo Specs subproject >* JSF2 integration - MyFaces ExtVal components > > Known Risks > > The current JSR-303 portions of the Agimatec-Validation code was > developed by a single developer from Agimatec (Roman) with no available > documents on the structure of the code. > > Orphaned Products > > The project will be implementing the JSR-303 Bean Validation > specification, which is a required component for both the Web and Full > profiles of Java EE 6. There is minimal risk of this work becoming > non-strategic and the contributors are confident that a larger community > will form within the project in a relatively short space of time. > > Inexperience with Open Source > > Many of the committers have experience working in one or more open > source projects including Apache Commons, Geronimo, OpenJPA, OpenEJB, > OpenWebBeans a
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
Allow me to introduce an Arabic name, cause I really would like to see a project in a well known open community like ASF with an Arabic name at least for once :D. The Arabic word for validation is "Mohaqeq", which also means to investigate the validity of something. Thoughts ? On Tue, Feb 23, 2010 at 11:03 PM, Nick Kew wrote: > On Tue, 23 Feb 2010 12:51:35 -0500 > Donald Woods wrote: > >> I'm open to suggestions BeanValidation, OpenValidation, Validera, ... > > Any of those work for me, though OpenValidation has a hint of the > same problem. BeanValidation might be ideal, and scans better than, > say JSR303-Validation :) > > I'm looking at it from a perspective of not polluting global namespace. > Someone who's never heard of it (or even Java beans) might be looking > for validation of their own process of interest, whether it be in a > computing field (HTML validation, signature validation, ...) > or somewhere completely different (Tax return validation, > Fire Safety Compliance Validation ...). A project called "Validation" > will turn up when they google - especially if someone's successive blog > entries are about "[this] Validation" and "my tax return". So the name > should carry some hint about it. > > -- > Nick Kew > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein "Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best." - Clean Code: A Handbook of Agile Software Craftsmanship - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Tue, 23 Feb 2010 12:51:35 -0500 Donald Woods wrote: > I'm open to suggestions BeanValidation, OpenValidation, Validera, ... Any of those work for me, though OpenValidation has a hint of the same problem. BeanValidation might be ideal, and scans better than, say JSR303-Validation :) I'm looking at it from a perspective of not polluting global namespace. Someone who's never heard of it (or even Java beans) might be looking for validation of their own process of interest, whether it be in a computing field (HTML validation, signature validation, ...) or somewhere completely different (Tax return validation, Fire Safety Compliance Validation ...). A project called "Validation" will turn up when they google - especially if someone's successive blog entries are about "[this] Validation" and "my tax return". So the name should carry some hint about it. -- Nick Kew - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
+1 Niall On Tue, Feb 23, 2010 at 3:57 PM, Donald Woods wrote: > Given the lack of response on the proposal and the push from our > champion to get moving :-), I'll assume lazy consensus and call a vote. > > I would like to present for a vote the following proposal to be > sponsored by the Incubator PMC for a new Validation podling. The goal > is to build a community around delivering a JSR-303 Bean Validation > implementation based on a new incoming codebase from Agimatec GmbH. > > The proposal is available on the wiki at and included below: > > http://wiki.apache.org/incubator/ValidationProposal > > > [] +1 to accept Validation into the Incubator > [] 0 don't care > [] -1 object and reason why. > > > Thanks, > Donald Woods > > > Proposal text from the wiki > > Validation > > Abstract > > The Validation project will deliver an implementation of the Bean > Validation Specification (JSR303) > > Proposal > > The initial Validation codebase will use the Agimatec Validation source, > which is an implementation of the Bean Validation Specification (JSR303). > > Although the destination of the Validation podling is not fixed, the > idea is that it will graduate to Apache Commons and replace the existing > Validator 1.x component as a new 2.0 codebase. > > Background > > Agimatec Validation has been developed by Agimatec Gmbh and is about 90% > complete towards implementing the JSR303 specification. The > Agimatec-Validation project is currently hosted on Google Code and is > ASL 2.0 licensed. Agimatec has no intention to complete or maintain the > implementation but has given the lead developer permission to continue > working on the project on his own time. > > A number of existing Apache projects (Geronimo, OpenJPA, MyFaces, > OpenEJB, Commons) are interested in an implementation of the Bean > Validation specification and Donald Woods suggested adopting the > Agimatec Validation code rather than starting from scratch. > > Rationale > > There is currently no Apache project focused on providing a JSR-303 > implementation. The existing Commons Validator 1.x project codebase does > not include support for Java 5 annotations and predates the JSR-303 > specification effort. By using the Agimatec-Validation code, we can > bootstrap the effort to create a Validator 2 release and focus on > polishing/enhancing the code, certification activities and integration > and support of other Apache projects. > > Current Status > > Agimatec Validation and is about 95% complete towards implementing the > JSR303 specification. > > An SGA for the Agimatec Validation has been received and on file from > Agimatec Gmbh. > > 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. > > Community > > Even though the reference implementation for the JSR-303 Bean Validation > specification is licensed under ASL 2.0, it is not being developed with > meritocracy in mind, as the release process is controlled by the JBoss > division of Red Hat to meet their own product needs. > > Validation aims to build a community of developers interested in the > definition and delivery of a JSR-303 compliant runtime, which can be > reused as a common component by a number of different projects (like > Geronimo, OpenJPA, MyFaces, ) By maintaining independence of the > target runtime, it is our intention to build the broadest possible > community of developers. > > Core Developers > > The lead developer from the Agimatec Validation project will be joined > by a number of committers from existing ASF projects. > > Alignment > > The purpose of Validation is to develop a certified implementation of > JSR-303. Some components may be developed and delivered by other Apache > projects, like: > > * Bean Validation 1.0 spec API - Apache Geronimo Specs subproject > * JSF2 integration - MyFaces ExtVal components > > Known Risks > > The current JSR-303 portions of the Agimatec-Validation code was > developed by a single developer from Agimatec (Roman) with no available > documents on the structure of the code. > > Orphaned Products > > The project will be implementing the JSR-303 Bean Validation > specification, which is a required component for both the Web and Full > profiles of Java EE 6. There is minimal risk of this work becoming > non-strategic and the contributors are confident that a larger community > will form within the project in a relatively short space of time. > > Inexperience with Open Source > > Many of the committers have experience working in one or more open > source projects including Apache Commons, Geronimo, OpenJPA, OpenEJB, > OpenWebBeans and MyFaces. > > Homogeneous Developers > > T
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Wed, Feb 24, 2010 at 9:11 AM, Kevan Miller wrote: > Yes. That's how I view it. It's more than code clearance, however. There are > processes for that, already. Community building is why it is starting off as > an Incubator project. I think graduating to become Commons Validator v2 is a > great outcome. But that's something for the new community to decide. > With the names on the proposal already interested, it would seem that there's already a community (definitely enough for a Commons project). Heck, I'm the only one who has ever worked on Commons Proxy. The folks who are ASF committers already and they're not Commons committers could become Commons committers pretty easily I'd guess. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Feb 24, 2010, at 8:55 AM, James Carman wrote: > Sorry, didn't read the proposal very closely. The idea was that it > would be brought into Commons Validator and become the 2.x codebase. > I like that idea and I would think it would be wise to go through the > incubator to make sure the codebase is donated "cleanly" to the ASF. > My point was mainly about the name. If it takes over the Commons > Validator project, then we already have a name. Issue closed. Right? Yes. That's how I view it. It's more than code clearance, however. There are processes for that, already. Community building is why it is starting off as an Incubator project. I think graduating to become Commons Validator v2 is a great outcome. But that's something for the new community to decide. --kevan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Feb 23, 2010, at 10:22 PM, Matthias Wessendorf wrote: > +1 to accept Validation into the Incubator > > afterwards we still can see where it actually ends up > > however I for sure want to see this at Apache. > > If you guys need a champion or mentor, count me in !! We have 3 mentors. If you're interested in making it 4, your help would certainly be appreciated! --kevan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
I'm +1 to bringing this into the incubator with the intention of it becoming Apache Commons Validator 2.x (per the proposal). I'm willing to help from the Apache Commons side of things if I can or need to. On Wed, Feb 24, 2010 at 8:52 AM, Kevan Miller wrote: > +1 > > --kevan > On Feb 23, 2010, at 10:57 AM, Donald Woods wrote: > >> Given the lack of response on the proposal and the push from our >> champion to get moving :-), I'll assume lazy consensus and call a vote. >> >> I would like to present for a vote the following proposal to be >> sponsored by the Incubator PMC for a new Validation podling. The goal >> is to build a community around delivering a JSR-303 Bean Validation >> implementation based on a new incoming codebase from Agimatec GmbH. >> >> The proposal is available on the wiki at and included below: >> >> http://wiki.apache.org/incubator/ValidationProposal >> >> >> [] +1 to accept Validation into the Incubator >> [] 0 don't care >> [] -1 object and reason why. >> >> >> Thanks, >> Donald Woods >> >> >> Proposal text from the wiki >> >> Validation >> >> Abstract >> >> The Validation project will deliver an implementation of the Bean >> Validation Specification (JSR303) >> >> Proposal >> >> The initial Validation codebase will use the Agimatec Validation source, >> which is an implementation of the Bean Validation Specification (JSR303). >> >> Although the destination of the Validation podling is not fixed, the >> idea is that it will graduate to Apache Commons and replace the existing >> Validator 1.x component as a new 2.0 codebase. >> >> Background >> >> Agimatec Validation has been developed by Agimatec Gmbh and is about 90% >> complete towards implementing the JSR303 specification. The >> Agimatec-Validation project is currently hosted on Google Code and is >> ASL 2.0 licensed. Agimatec has no intention to complete or maintain the >> implementation but has given the lead developer permission to continue >> working on the project on his own time. >> >> A number of existing Apache projects (Geronimo, OpenJPA, MyFaces, >> OpenEJB, Commons) are interested in an implementation of the Bean >> Validation specification and Donald Woods suggested adopting the >> Agimatec Validation code rather than starting from scratch. >> >> Rationale >> >> There is currently no Apache project focused on providing a JSR-303 >> implementation. The existing Commons Validator 1.x project codebase does >> not include support for Java 5 annotations and predates the JSR-303 >> specification effort. By using the Agimatec-Validation code, we can >> bootstrap the effort to create a Validator 2 release and focus on >> polishing/enhancing the code, certification activities and integration >> and support of other Apache projects. >> >> Current Status >> >> Agimatec Validation and is about 95% complete towards implementing the >> JSR303 specification. >> >> An SGA for the Agimatec Validation has been received and on file from >> Agimatec Gmbh. >> >> 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. >> >> Community >> >> Even though the reference implementation for the JSR-303 Bean Validation >> specification is licensed under ASL 2.0, it is not being developed with >> meritocracy in mind, as the release process is controlled by the JBoss >> division of Red Hat to meet their own product needs. >> >> Validation aims to build a community of developers interested in the >> definition and delivery of a JSR-303 compliant runtime, which can be >> reused as a common component by a number of different projects (like >> Geronimo, OpenJPA, MyFaces, ) By maintaining independence of the >> target runtime, it is our intention to build the broadest possible >> community of developers. >> >> Core Developers >> >> The lead developer from the Agimatec Validation project will be joined >> by a number of committers from existing ASF projects. >> >> Alignment >> >> The purpose of Validation is to develop a certified implementation of >> JSR-303. Some components may be developed and delivered by other Apache >> projects, like: >> >> * Bean Validation 1.0 spec API - Apache Geronimo Specs subproject >> * JSF2 integration - MyFaces ExtVal components >> >> Known Risks >> >> The current JSR-303 portions of the Agimatec-Validation code was >> developed by a single developer from Agimatec (Roman) with no available >> documents on the structure of the code. >> >> Orphaned Products >> >> The project will be implementing the JSR-303 Bean Validation >> specification, which is a required component for both the Web and Full >> profiles of Java EE 6. There is minimal risk of this work b
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
Sorry, didn't read the proposal very closely. The idea was that it would be brought into Commons Validator and become the 2.x codebase. I like that idea and I would think it would be wise to go through the incubator to make sure the codebase is donated "cleanly" to the ASF. My point was mainly about the name. If it takes over the Commons Validator project, then we already have a name. Issue closed. Right? On Wed, Feb 24, 2010 at 8:49 AM, Kevan Miller wrote: > > On Feb 24, 2010, at 8:18 AM, James Carman wrote: > >> We already have Apache Commons Validator. Why not just bring this >> code into that project? > > Heh. That's been pretty well discussed, already, by both Commons and > Incubator. You can scan the logs for details. The subject was "[PROPOSAL] > Validation incubator for JSR-303 Bean Validation". I think the following sums > up where we landed on that issue (at least it pretty well sums up where I > landed on the issue): > > On Jan 18, 2010, at 9:55 PM, Noel J. Bergman wrote: > >> Kevan Miller wrote: >> >>> I think we'd agree that a fair amount of community building will be >>> required for this new codebase and group of committers. [However,] >>> given the small makeup of the Commons Validator community, I don't >>> think it's reasonable to expect the Commons community to do this >>> community building. >> >> That seems a cogent enough explanation to warrant Incubation. Thank you. I >> also believe that when you talk about multiple projects collaborating >> actively on a shared, but separately useable, codebase, a TLP is often >> justified. > > > --kevan > - > 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] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
+1 --kevan On Feb 23, 2010, at 10:57 AM, Donald Woods wrote: > Given the lack of response on the proposal and the push from our > champion to get moving :-), I'll assume lazy consensus and call a vote. > > I would like to present for a vote the following proposal to be > sponsored by the Incubator PMC for a new Validation podling. The goal > is to build a community around delivering a JSR-303 Bean Validation > implementation based on a new incoming codebase from Agimatec GmbH. > > The proposal is available on the wiki at and included below: > > http://wiki.apache.org/incubator/ValidationProposal > > > [] +1 to accept Validation into the Incubator > [] 0 don't care > [] -1 object and reason why. > > > Thanks, > Donald Woods > > > Proposal text from the wiki > > Validation > > Abstract > > The Validation project will deliver an implementation of the Bean > Validation Specification (JSR303) > > Proposal > > The initial Validation codebase will use the Agimatec Validation source, > which is an implementation of the Bean Validation Specification (JSR303). > > Although the destination of the Validation podling is not fixed, the > idea is that it will graduate to Apache Commons and replace the existing > Validator 1.x component as a new 2.0 codebase. > > Background > > Agimatec Validation has been developed by Agimatec Gmbh and is about 90% > complete towards implementing the JSR303 specification. The > Agimatec-Validation project is currently hosted on Google Code and is > ASL 2.0 licensed. Agimatec has no intention to complete or maintain the > implementation but has given the lead developer permission to continue > working on the project on his own time. > > A number of existing Apache projects (Geronimo, OpenJPA, MyFaces, > OpenEJB, Commons) are interested in an implementation of the Bean > Validation specification and Donald Woods suggested adopting the > Agimatec Validation code rather than starting from scratch. > > Rationale > > There is currently no Apache project focused on providing a JSR-303 > implementation. The existing Commons Validator 1.x project codebase does > not include support for Java 5 annotations and predates the JSR-303 > specification effort. By using the Agimatec-Validation code, we can > bootstrap the effort to create a Validator 2 release and focus on > polishing/enhancing the code, certification activities and integration > and support of other Apache projects. > > Current Status > > Agimatec Validation and is about 95% complete towards implementing the > JSR303 specification. > > An SGA for the Agimatec Validation has been received and on file from > Agimatec Gmbh. > > 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. > > Community > > Even though the reference implementation for the JSR-303 Bean Validation > specification is licensed under ASL 2.0, it is not being developed with > meritocracy in mind, as the release process is controlled by the JBoss > division of Red Hat to meet their own product needs. > > Validation aims to build a community of developers interested in the > definition and delivery of a JSR-303 compliant runtime, which can be > reused as a common component by a number of different projects (like > Geronimo, OpenJPA, MyFaces, ) By maintaining independence of the > target runtime, it is our intention to build the broadest possible > community of developers. > > Core Developers > > The lead developer from the Agimatec Validation project will be joined > by a number of committers from existing ASF projects. > > Alignment > > The purpose of Validation is to develop a certified implementation of > JSR-303. Some components may be developed and delivered by other Apache > projects, like: > >* Bean Validation 1.0 spec API - Apache Geronimo Specs subproject >* JSF2 integration - MyFaces ExtVal components > > Known Risks > > The current JSR-303 portions of the Agimatec-Validation code was > developed by a single developer from Agimatec (Roman) with no available > documents on the structure of the code. > > Orphaned Products > > The project will be implementing the JSR-303 Bean Validation > specification, which is a required component for both the Web and Full > profiles of Java EE 6. There is minimal risk of this work becoming > non-strategic and the contributors are confident that a larger community > will form within the project in a relatively short space of time. > > Inexperience with Open Source > > Many of the committers have experience working in one or more open > source projects including Apache Commons, Geronimo, OpenJPA, OpenEJB, > OpenWebBeans and MyFa
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Feb 24, 2010, at 8:18 AM, James Carman wrote: > We already have Apache Commons Validator. Why not just bring this > code into that project? Heh. That's been pretty well discussed, already, by both Commons and Incubator. You can scan the logs for details. The subject was "[PROPOSAL] Validation incubator for JSR-303 Bean Validation". I think the following sums up where we landed on that issue (at least it pretty well sums up where I landed on the issue): On Jan 18, 2010, at 9:55 PM, Noel J. Bergman wrote: > Kevan Miller wrote: > >> I think we'd agree that a fair amount of community building will be >> required for this new codebase and group of committers. [However,] >> given the small makeup of the Commons Validator community, I don't >> think it's reasonable to expect the Commons community to do this >> community building. > > That seems a cogent enough explanation to warrant Incubation. Thank you. I > also believe that when you talk about multiple projects collaborating > actively on a shared, but separately useable, codebase, a TLP is often > justified. --kevan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
We already have Apache Commons Validator. Why not just bring this code into that project? On Tue, Feb 23, 2010 at 5:36 PM, Brett Porter wrote: > As I understand it from the proposal, they intend to be Apache Commons > Validation. > > On 24/02/2010, at 4:19 AM, Nick Kew wrote: > >> On Tue, 23 Feb 2010 10:57:33 -0500 >> Donald Woods wrote: >> >>> Given the lack of response on the proposal and the push from our >>> champion to get moving :-), I'll assume lazy consensus and call a vote. >>> >>> I would like to present for a vote the following proposal to be >>> sponsored by the Incubator PMC for a new Validation podling. The goal >>> is to build a community around delivering a JSR-303 Bean Validation >>> implementation based on a new incoming codebase from Agimatec GmbH. >>> >>> The proposal is available on the wiki at and included below: >>> >>> http://wiki.apache.org/incubator/ValidationProposal >> >> -1 to a project that could end up being called "Apache Validation" or >> just "Validation". That's too big/general a word for a project name. >> >> No objection under a changed name. I'd suggest adding an >> adjective to indicate what is being validated. >> >> -- >> Nick Kew >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > -- > Brett Porter > br...@apache.org > http://brettporter.wordpress.com/ > > > > > > - > 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] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
Nick, are you still -1 because of the name, or will you change your vote based on Alan's comment that the name could change when it graduates? My thinking, is that if the project graduates to Commons then it'll naturally be Commons Validator v2, whereas if it graduates to Geronimo it would be a Geronimo Validation component. -Donald On 2/23/10 12:19 PM, Nick Kew wrote: > On Tue, 23 Feb 2010 10:57:33 -0500 > Donald Woods wrote: > >> Given the lack of response on the proposal and the push from our >> champion to get moving :-), I'll assume lazy consensus and call a vote. >> >> I would like to present for a vote the following proposal to be >> sponsored by the Incubator PMC for a new Validation podling. The goal >> is to build a community around delivering a JSR-303 Bean Validation >> implementation based on a new incoming codebase from Agimatec GmbH. >> >> The proposal is available on the wiki at and included below: >> >>http://wiki.apache.org/incubator/ValidationProposal > > -1 to a project that could end up being called "Apache Validation" or > just "Validation". That's too big/general a word for a project name. > > No objection under a changed name. I'd suggest adding an > adjective to indicate what is being validated. > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
+1 a big one of course! I communicated with agimatec-validator guys a few times and they needed at longest 4 hours to respond to my questions and apply my patches :) This project will be a great add to Apacheland! LieGrue, strub --- Matthias Wessendorf schrieb am Mi, 24.2.2010: > Von: Matthias Wessendorf > Betreff: Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean > Validation > An: general@incubator.apache.org, "Mark Struberg" > Datum: Mittwoch, 24. Februar, 2010 04:22 Uhr > +1 to accept Validation into > the Incubator > > afterwards we still can see where it actually ends up > > however I for sure want to see this at Apache. > > If you guys need a champion or mentor, count me in !! > > -M > > On Tue, Feb 23, 2010 at 11:45 PM, Donald Woods > wrote: > > We're leaving the TLP/sub-project decision till > graduation... > > > > -Donald > > > > > > On 2/23/10 5:36 PM, Brett Porter wrote: > >> As I understand it from the proposal, they intend > to be Apache Commons Validation. > >> > >> On 24/02/2010, at 4:19 AM, Nick Kew wrote: > >> > >>> On Tue, 23 Feb 2010 10:57:33 -0500 > >>> Donald Woods > wrote: > >>> > >>>> Given the lack of response on the proposal > and the push from our > >>>> champion to get moving :-), I'll assume > lazy consensus and call a vote. > >>>> > >>>> I would like to present for a vote the > following proposal to be > >>>> sponsored by the Incubator PMC for a new > Validation podling. The goal > >>>> is to build a community around delivering > a JSR-303 Bean Validation > >>>> implementation based on a new incoming > codebase from Agimatec GmbH. > >>>> > >>>> The proposal is available on the wiki at > and included below: > >>>> > >>>> http://wiki.apache.org/incubator/ValidationProposal > >>> > >>> -1 to a project that could end up being called > "Apache Validation" or > >>> just "Validation". That's too big/general a > word for a project name. > >>> > >>> No objection under a changed name. I'd > suggest adding an > >>> adjective to indicate what is being > validated. > >>> > >>> -- > >>> Nick Kew > >>> > >>> > - > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>> For additional commands, e-mail: general-h...@incubator.apache.org > >>> > >> > >> -- > >> Brett Porter > >> br...@apache.org > >> http://brettporter.wordpress.com/ > >> > >> > >> > >> > >> > >> > - > >> 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 > > > > > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > __ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
+1 (non-binding) On Wed, Feb 24, 2010 at 10:14 AM, Martijn Dashorst wrote: > +1 > > Martijn > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Thanks - Mohammad Nour - LinkedIn: http://www.linkedin.com/in/mnour "Life is like riding a bicycle. To keep your balance you must keep moving" - Albert Einstein "Writing clean code is what you must do in order to call yourself a professional. There is no reasonable excuse for doing anything less than your best." - Clean Code: A Handbook of Agile Software Craftsmanship - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
+1 Martijn - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On 02/23/2010 04:57 PM, Donald Woods wrote: > Given the lack of response on the proposal and the push from our > champion to get moving :-), I'll assume lazy consensus and call a vote. > > I would like to present for a vote the following proposal to be > sponsored by the Incubator PMC for a new Validation podling. The goal > is to build a community around delivering a JSR-303 Bean Validation > implementation based on a new incoming codebase from Agimatec GmbH. > > The proposal is available on the wiki at and included below: > >http://wiki.apache.org/incubator/ValidationProposal > > > [X] +1 to accept Validation into the Incubator Cheers Jean-Frederic - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
+1 to accept Validation into the Incubator afterwards we still can see where it actually ends up however I for sure want to see this at Apache. If you guys need a champion or mentor, count me in !! -M On Tue, Feb 23, 2010 at 11:45 PM, Donald Woods wrote: > We're leaving the TLP/sub-project decision till graduation... > > -Donald > > > On 2/23/10 5:36 PM, Brett Porter wrote: >> As I understand it from the proposal, they intend to be Apache Commons >> Validation. >> >> On 24/02/2010, at 4:19 AM, Nick Kew wrote: >> >>> On Tue, 23 Feb 2010 10:57:33 -0500 >>> Donald Woods wrote: >>> Given the lack of response on the proposal and the push from our champion to get moving :-), I'll assume lazy consensus and call a vote. I would like to present for a vote the following proposal to be sponsored by the Incubator PMC for a new Validation podling. The goal is to build a community around delivering a JSR-303 Bean Validation implementation based on a new incoming codebase from Agimatec GmbH. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/ValidationProposal >>> >>> -1 to a project that could end up being called "Apache Validation" or >>> just "Validation". That's too big/general a word for a project name. >>> >>> No objection under a changed name. I'd suggest adding an >>> adjective to indicate what is being validated. >>> >>> -- >>> Nick Kew >>> >>> - >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> -- >> Brett Porter >> br...@apache.org >> http://brettporter.wordpress.com/ >> >> >> >> >> >> - >> 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 > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
We're leaving the TLP/sub-project decision till graduation... -Donald On 2/23/10 5:36 PM, Brett Porter wrote: > As I understand it from the proposal, they intend to be Apache Commons > Validation. > > On 24/02/2010, at 4:19 AM, Nick Kew wrote: > >> On Tue, 23 Feb 2010 10:57:33 -0500 >> Donald Woods wrote: >> >>> Given the lack of response on the proposal and the push from our >>> champion to get moving :-), I'll assume lazy consensus and call a vote. >>> >>> I would like to present for a vote the following proposal to be >>> sponsored by the Incubator PMC for a new Validation podling. The goal >>> is to build a community around delivering a JSR-303 Bean Validation >>> implementation based on a new incoming codebase from Agimatec GmbH. >>> >>> The proposal is available on the wiki at and included below: >>> >>> http://wiki.apache.org/incubator/ValidationProposal >> >> -1 to a project that could end up being called "Apache Validation" or >> just "Validation". That's too big/general a word for a project name. >> >> No objection under a changed name. I'd suggest adding an >> adjective to indicate what is being validated. >> >> -- >> Nick Kew >> >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > -- > Brett Porter > br...@apache.org > http://brettporter.wordpress.com/ > > > > > > - > 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] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
As I understand it from the proposal, they intend to be Apache Commons Validation. On 24/02/2010, at 4:19 AM, Nick Kew wrote: > On Tue, 23 Feb 2010 10:57:33 -0500 > Donald Woods wrote: > >> Given the lack of response on the proposal and the push from our >> champion to get moving :-), I'll assume lazy consensus and call a vote. >> >> I would like to present for a vote the following proposal to be >> sponsored by the Incubator PMC for a new Validation podling. The goal >> is to build a community around delivering a JSR-303 Bean Validation >> implementation based on a new incoming codebase from Agimatec GmbH. >> >> The proposal is available on the wiki at and included below: >> >> http://wiki.apache.org/incubator/ValidationProposal > > -1 to a project that could end up being called "Apache Validation" or > just "Validation". That's too big/general a word for a project name. > > No objection under a changed name. I'd suggest adding an > adjective to indicate what is being validated. > > -- > Nick Kew > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Tue, Feb 23, 2010 at 7:57 AM, Donald Woods wrote: > Given the lack of response on the proposal and the push from our > champion to get moving :-), I'll assume lazy consensus and call a vote. > > I would like to present for a vote the following proposal to be > sponsored by the Incubator PMC for a new Validation podling. The goal > is to build a community around delivering a JSR-303 Bean Validation > implementation based on a new incoming codebase from Agimatec GmbH. > > The proposal is available on the wiki at and included below: > > http://wiki.apache.org/incubator/ValidationProposal > > > [] +1 to accept Validation into the Incubator > [] 0 don't care > [] -1 object and reason why. +1 to accept Validation into the Incubator -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
I'm open to suggestions BeanValidation, OpenValidation, Validera, ... -Donald On 2/23/10 12:27 PM, jean-frederic clere wrote: > On 02/23/2010 06:19 PM, Nick Kew wrote: >> On Tue, 23 Feb 2010 10:57:33 -0500 >> Donald Woods wrote: >> >>> Given the lack of response on the proposal and the push from our >>> champion to get moving :-), I'll assume lazy consensus and call a vote. >>> >>> I would like to present for a vote the following proposal to be >>> sponsored by the Incubator PMC for a new Validation podling. The goal >>> is to build a community around delivering a JSR-303 Bean Validation >>> implementation based on a new incoming codebase from Agimatec GmbH. >>> >>> The proposal is available on the wiki at and included below: >>> >>>http://wiki.apache.org/incubator/ValidationProposal >> >> -1 to a project that could end up being called "Apache Validation" or >> just "Validation". That's too big/general a word for a project name. >> >> No objection under a changed name. I'd suggest adding an >> adjective to indicate what is being validated. >> > > Apache BeanValidation? > > Cheers > > Jean-Frederic > > - > 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] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Feb 23, 2010, at 9:19 AM, Nick Kew wrote: On Tue, 23 Feb 2010 10:57:33 -0500 Donald Woods wrote: Given the lack of response on the proposal and the push from our champion to get moving :-), I'll assume lazy consensus and call a vote. I would like to present for a vote the following proposal to be sponsored by the Incubator PMC for a new Validation podling. The goal is to build a community around delivering a JSR-303 Bean Validation implementation based on a new incoming codebase from Agimatec GmbH. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/ValidationProposal -1 to a project that could end up being called "Apache Validation" or just "Validation". That's too big/general a word for a project name. No objection under a changed name. I'd suggest adding an adjective to indicate what is being validated. Interesting point. Not sure that it should be brought up and resolved during a vote. A project's name is always up in the air while it's incubating and should not be a barrier to its being brought in to the Incubator. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
+1 Regards, Alan On Feb 23, 2010, at 7:57 AM, Donald Woods wrote: Given the lack of response on the proposal and the push from our champion to get moving :-), I'll assume lazy consensus and call a vote. I would like to present for a vote the following proposal to be sponsored by the Incubator PMC for a new Validation podling. The goal is to build a community around delivering a JSR-303 Bean Validation implementation based on a new incoming codebase from Agimatec GmbH. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/ValidationProposal [] +1 to accept Validation into the Incubator [] 0 don't care [] -1 object and reason why. Thanks, Donald Woods Proposal text from the wiki Validation Abstract The Validation project will deliver an implementation of the Bean Validation Specification (JSR303) Proposal The initial Validation codebase will use the Agimatec Validation source, which is an implementation of the Bean Validation Specification (JSR303). Although the destination of the Validation podling is not fixed, the idea is that it will graduate to Apache Commons and replace the existing Validator 1.x component as a new 2.0 codebase. Background Agimatec Validation has been developed by Agimatec Gmbh and is about 90% complete towards implementing the JSR303 specification. The Agimatec-Validation project is currently hosted on Google Code and is ASL 2.0 licensed. Agimatec has no intention to complete or maintain the implementation but has given the lead developer permission to continue working on the project on his own time. A number of existing Apache projects (Geronimo, OpenJPA, MyFaces, OpenEJB, Commons) are interested in an implementation of the Bean Validation specification and Donald Woods suggested adopting the Agimatec Validation code rather than starting from scratch. Rationale There is currently no Apache project focused on providing a JSR-303 implementation. The existing Commons Validator 1.x project codebase does not include support for Java 5 annotations and predates the JSR-303 specification effort. By using the Agimatec-Validation code, we can bootstrap the effort to create a Validator 2 release and focus on polishing/enhancing the code, certification activities and integration and support of other Apache projects. Current Status Agimatec Validation and is about 95% complete towards implementing the JSR303 specification. An SGA for the Agimatec Validation has been received and on file from Agimatec Gmbh. 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. Community Even though the reference implementation for the JSR-303 Bean Validation specification is licensed under ASL 2.0, it is not being developed with meritocracy in mind, as the release process is controlled by the JBoss division of Red Hat to meet their own product needs. Validation aims to build a community of developers interested in the definition and delivery of a JSR-303 compliant runtime, which can be reused as a common component by a number of different projects (like Geronimo, OpenJPA, MyFaces, ) By maintaining independence of the target runtime, it is our intention to build the broadest possible community of developers. Core Developers The lead developer from the Agimatec Validation project will be joined by a number of committers from existing ASF projects. Alignment The purpose of Validation is to develop a certified implementation of JSR-303. Some components may be developed and delivered by other Apache projects, like: * Bean Validation 1.0 spec API - Apache Geronimo Specs subproject * JSF2 integration - MyFaces ExtVal components Known Risks The current JSR-303 portions of the Agimatec-Validation code was developed by a single developer from Agimatec (Roman) with no available documents on the structure of the code. Orphaned Products The project will be implementing the JSR-303 Bean Validation specification, which is a required component for both the Web and Full profiles of Java EE 6. There is minimal risk of this work becoming non-strategic and the contributors are confident that a larger community will form within the project in a relatively short space of time. Inexperience with Open Source Many of the committers have experience working in one or more open source projects including Apache Commons, Geronimo, OpenJPA, OpenEJB, OpenWebBeans and MyFaces. Homogeneous Developers The list of initial committers are geographically distributed across the U.S., Europe and Africa with no one company being associated with a majority of the developers. Many of the
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On 02/23/2010 06:19 PM, Nick Kew wrote: > On Tue, 23 Feb 2010 10:57:33 -0500 > Donald Woods wrote: > >> Given the lack of response on the proposal and the push from our >> champion to get moving :-), I'll assume lazy consensus and call a vote. >> >> I would like to present for a vote the following proposal to be >> sponsored by the Incubator PMC for a new Validation podling. The goal >> is to build a community around delivering a JSR-303 Bean Validation >> implementation based on a new incoming codebase from Agimatec GmbH. >> >> The proposal is available on the wiki at and included below: >> >>http://wiki.apache.org/incubator/ValidationProposal > > -1 to a project that could end up being called "Apache Validation" or > just "Validation". That's too big/general a word for a project name. > > No objection under a changed name. I'd suggest adding an > adjective to indicate what is being validated. > Apache BeanValidation? Cheers Jean-Frederic - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
On Tue, 23 Feb 2010 10:57:33 -0500 Donald Woods wrote: > Given the lack of response on the proposal and the push from our > champion to get moving :-), I'll assume lazy consensus and call a vote. > > I would like to present for a vote the following proposal to be > sponsored by the Incubator PMC for a new Validation podling. The goal > is to build a community around delivering a JSR-303 Bean Validation > implementation based on a new incoming codebase from Agimatec GmbH. > > The proposal is available on the wiki at and included below: > >http://wiki.apache.org/incubator/ValidationProposal -1 to a project that could end up being called "Apache Validation" or just "Validation". That's too big/general a word for a project name. No objection under a changed name. I'd suggest adding an adjective to indicate what is being validated. -- Nick Kew - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
+1 Go for it. Craig On Feb 23, 2010, at 7:57 AM, Donald Woods wrote: Given the lack of response on the proposal and the push from our champion to get moving :-), I'll assume lazy consensus and call a vote. I would like to present for a vote the following proposal to be sponsored by the Incubator PMC for a new Validation podling. The goal is to build a community around delivering a JSR-303 Bean Validation implementation based on a new incoming codebase from Agimatec GmbH. The proposal is available on the wiki at and included below: http://wiki.apache.org/incubator/ValidationProposal [] +1 to accept Validation into the Incubator [] 0 don't care [] -1 object and reason why. Thanks, Donald Woods Proposal text from the wiki Validation Abstract The Validation project will deliver an implementation of the Bean Validation Specification (JSR303) Proposal The initial Validation codebase will use the Agimatec Validation source, which is an implementation of the Bean Validation Specification (JSR303). Although the destination of the Validation podling is not fixed, the idea is that it will graduate to Apache Commons and replace the existing Validator 1.x component as a new 2.0 codebase. Background Agimatec Validation has been developed by Agimatec Gmbh and is about 90% complete towards implementing the JSR303 specification. The Agimatec-Validation project is currently hosted on Google Code and is ASL 2.0 licensed. Agimatec has no intention to complete or maintain the implementation but has given the lead developer permission to continue working on the project on his own time. A number of existing Apache projects (Geronimo, OpenJPA, MyFaces, OpenEJB, Commons) are interested in an implementation of the Bean Validation specification and Donald Woods suggested adopting the Agimatec Validation code rather than starting from scratch. Rationale There is currently no Apache project focused on providing a JSR-303 implementation. The existing Commons Validator 1.x project codebase does not include support for Java 5 annotations and predates the JSR-303 specification effort. By using the Agimatec-Validation code, we can bootstrap the effort to create a Validator 2 release and focus on polishing/enhancing the code, certification activities and integration and support of other Apache projects. Current Status Agimatec Validation and is about 95% complete towards implementing the JSR303 specification. An SGA for the Agimatec Validation has been received and on file from Agimatec Gmbh. 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. Community Even though the reference implementation for the JSR-303 Bean Validation specification is licensed under ASL 2.0, it is not being developed with meritocracy in mind, as the release process is controlled by the JBoss division of Red Hat to meet their own product needs. Validation aims to build a community of developers interested in the definition and delivery of a JSR-303 compliant runtime, which can be reused as a common component by a number of different projects (like Geronimo, OpenJPA, MyFaces, ) By maintaining independence of the target runtime, it is our intention to build the broadest possible community of developers. Core Developers The lead developer from the Agimatec Validation project will be joined by a number of committers from existing ASF projects. Alignment The purpose of Validation is to develop a certified implementation of JSR-303. Some components may be developed and delivered by other Apache projects, like: * Bean Validation 1.0 spec API - Apache Geronimo Specs subproject * JSF2 integration - MyFaces ExtVal components Known Risks The current JSR-303 portions of the Agimatec-Validation code was developed by a single developer from Agimatec (Roman) with no available documents on the structure of the code. Orphaned Products The project will be implementing the JSR-303 Bean Validation specification, which is a required component for both the Web and Full profiles of Java EE 6. There is minimal risk of this work becoming non-strategic and the contributors are confident that a larger community will form within the project in a relatively short space of time. Inexperience with Open Source Many of the committers have experience working in one or more open source projects including Apache Commons, Geronimo, OpenJPA, OpenEJB, OpenWebBeans and MyFaces. Homogeneous Developers The list of initial committers are geographically distributed across the U.S., Europe and Africa with no one company being associated with a majority of the developers. Many of
Re: [VOTE] [PROPOSAL] Validation incubator for JSR-303 Bean Validation
> [x] +1 to accept Validation into the Incubator (non-binding) > [] 0 don't care > [] -1 object and reason why. > > > Thanks, > Donald Woods > > > Proposal text from the wiki > > Validation > > Abstract > > The Validation project will deliver an implementation of the Bean > Validation Specification (JSR303) > > Proposal > > The initial Validation codebase will use the Agimatec Validation source, > which is an implementation of the Bean Validation Specification (JSR303). > > Although the destination of the Validation podling is not fixed, the > idea is that it will graduate to Apache Commons and replace the existing > Validator 1.x component as a new 2.0 codebase. > > Background > > Agimatec Validation has been developed by Agimatec Gmbh and is about 90% > complete towards implementing the JSR303 specification. The > Agimatec-Validation project is currently hosted on Google Code and is > ASL 2.0 licensed. Agimatec has no intention to complete or maintain the > implementation but has given the lead developer permission to continue > working on the project on his own time. > > A number of existing Apache projects (Geronimo, OpenJPA, MyFaces, > OpenEJB, Commons) are interested in an implementation of the Bean > Validation specification and Donald Woods suggested adopting the > Agimatec Validation code rather than starting from scratch. > > Rationale > > There is currently no Apache project focused on providing a JSR-303 > implementation. The existing Commons Validator 1.x project codebase does > not include support for Java 5 annotations and predates the JSR-303 > specification effort. By using the Agimatec-Validation code, we can > bootstrap the effort to create a Validator 2 release and focus on > polishing/enhancing the code, certification activities and integration > and support of other Apache projects. > > Current Status > > Agimatec Validation and is about 95% complete towards implementing the > JSR303 specification. > > An SGA for the Agimatec Validation has been received and on file from > Agimatec Gmbh. > > 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. > > Community > > Even though the reference implementation for the JSR-303 Bean Validation > specification is licensed under ASL 2.0, it is not being developed with > meritocracy in mind, as the release process is controlled by the JBoss > division of Red Hat to meet their own product needs. > > Validation aims to build a community of developers interested in the > definition and delivery of a JSR-303 compliant runtime, which can be > reused as a common component by a number of different projects (like > Geronimo, OpenJPA, MyFaces, ) By maintaining independence of the > target runtime, it is our intention to build the broadest possible > community of developers. > > Core Developers > > The lead developer from the Agimatec Validation project will be joined > by a number of committers from existing ASF projects. > > Alignment > > The purpose of Validation is to develop a certified implementation of > JSR-303. Some components may be developed and delivered by other Apache > projects, like: > > * Bean Validation 1.0 spec API - Apache Geronimo Specs subproject > * JSF2 integration - MyFaces ExtVal components > > Known Risks > > The current JSR-303 portions of the Agimatec-Validation code was > developed by a single developer from Agimatec (Roman) with no available > documents on the structure of the code. > > Orphaned Products > > The project will be implementing the JSR-303 Bean Validation > specification, which is a required component for both the Web and Full > profiles of Java EE 6. There is minimal risk of this work becoming > non-strategic and the contributors are confident that a larger community > will form within the project in a relatively short space of time. > > Inexperience with Open Source > > Many of the committers have experience working in one or more open > source projects including Apache Commons, Geronimo, OpenJPA, OpenEJB, > OpenWebBeans and MyFaces. > > Homogeneous Developers > > The list of initial committers are geographically distributed across the > U.S., Europe and Africa 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. It is our hope that, > through the incubator, further contributors with a broad background of > experience but common interest will become involved with this project. > > Reliance on Salaried Developers > > To the best of our knowledge, none of the initial committers a
