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 n...@apache.org wrote: On Tue, 23 Feb 2010 12:51:35 -0500 Donald Woods dwo...@apache.org 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: WSRP4J stuck?
On Wed, Feb 24, 2010 at 6:12 AM, David Sean Taylor d.tay...@onehippo.com wrote: On Wed, Feb 17, 2010 at 1:36 PM, Doug Cutting cutt...@apache.org wrote: Incubator PMC, On reading this month's report to the Board from the Incubator, the Board was concerned about the inactivity in WSRP4J. Has this project been abandoned, or is there some other explanation for the lack of any activity in the last three months? There hasn't been any activity for years on this project. The project had a patent claim for related technologies from a company named WebCollage. Check the mail archives on this list for the complete story... FWIW, I think most of that story is here, from October 2008: http://markmail.org/thread/txk5ay7raux6e6dc -Bertrand - 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). OpenBeanValidation as a name will be cool :) Thanks; --Gurkan 2010/2/23 Donald Woods dwo...@apache.org 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
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 cgurkanerdo...@gmail.com wrote: +1 (non-binding). OpenBeanValidation as a name will be cool :) Thanks; --Gurkan 2010/2/23 Donald Woods dwo...@apache.org 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,
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 cgurkanerdo...@gmail.com wrote: +1 (non-binding). OpenBeanValidation as a name will be cool :) Thanks; --Gurkan 2010/2/23 Donald Woods dwo...@apache.org 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
[RESULT] [VOTE] Apache UIMA as a TLP
The vote for recommending Apache UIMA graduation passes with the following votes: +1 Jukka Zitting - binding Martijn Dashorst - binding Bertrand Delacretaz - binding Justin Erenkrantz - binding Craig L Russell - binding Sam Ruby - binding Loren Cahlander Ian Holsman - binding Jean T. Anderson - binding Matt Hogstrom - binding Alan D Cabrera - binding Rubert Burrell Donkin - binding No other votes were cast. The vote passes. I'll take the next step of sending this resolution to the board. Thanks! -Marshall On 2/22/2010 9:24 AM, Marshall Schor wrote: Greetings, As no issues have been raised in our previous post to discuss graduation, the Apache UIMA community requests that the IPMC vote on recommending this resolution to the ASF Board. All of our mentors have agreed to pitch in as needed as members of our PMC. The community is ready to graduate (see http://markmail.org/thread/pmmf6gtr7z47ivd2 ). Please cast your vote: [ ] +1 to recommend UIMA's graduation [ ] 0 don't care [ ] -1 no, don't recommend yet, (because...) -Marshall Schor Resolution: X. Establish the Apache UIMA 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 analysis of unstructured data, guided by the UIMA Oasis Standard, 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 UIMA Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache UIMA Project be and hereby is responsible for the creation and maintenance of software related to the analysis of unstructured data, guided by the UIMA Oasis Standard, and be it further RESOLVED, that the office of Vice President, Apache UIMA 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 UIMA Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache UIMA 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 UIMA Project: * Adam Lallyala...@apache.org * Bhavani Iyer bhav...@apache.org * Burn Lewisb...@apache.org * Edward Epsteine...@apache.org * Jaroslaw Cwiklik cwik...@apache.org * Joern Kottmannjo...@apache.org * Jukka Zitting ju...@apache.org * Ken Coar c...@apache.org * Marshall Schorsc...@apache.org * Michael Baessler mbaess...@apache.org * Sam Ruby ru...@apache.org * Thilo Goetz twgo...@apache.org * Tommaso Teofili tomm...@apache.org * Tong Fin tong...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Marshall Schor be appointed to the office of Vice President, Apache UIMA, 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 UIMA 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 UIMA Project; and be it further RESOLVED, that the Apache UIMA Project be and hereby is tasked with the migration and rationalization of the Apache Incubator UIMA podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator UIMA podling encumbered upon the Apache Incubator Project are hereafter discharged. - 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 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: Subversion is now an official ASF project!
On 2/17/10 4:16 PM, Greg Stein wrote: Hi all, The ASF Board just voted to approve the graduation of Subversion from the Incubator. We are now an official project of the Apache Software Foundation! Go forth! Be merry! Congrats! Cheers, -g - 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
[VOTE] Approve the release of apache-esme-1.0-RC1-incubating
The ESME community has voted on and approved the release of apache-esme-1.0-RC1-incubating. We would now like to request the approval of the Incubator PMC for this release. Details of the ESME community vote can be found here: http://www.mail-archive.com/esme-...@incubator.apache.org/msg03120.html The candidate can be found at http://people.apache.org/~rhirsch/esme/ See the CHANGES.txt file for details on release contents. The release candidate is a tar archive of the sources in https://svn.apache.org/repos/asf/incubator/esme/tags/apache-esme-1.0-RC1-incubating/ The MD5 checksum of the apache-esme-1.0-RC1-incubating.src.tar.gz release package is 35 72 D0 B3 49 3C C3 BA D5 4F 57 E8 EA 1D 9D 54 Please vote on releasing this package as Apache ESME 1.0-incubating. Please vote to publish this release by Monday, March 1 05:41 CET, please include the testing you performed to arrive at your vote [ ] +1 Publish [ ] 0 Abstain [ ] -1 Don't publish, because... Below is a summary of the vote on the ESME mailing list. The link to the vote result is here: http://www.mail-archive.com/esme-...@incubator.apache.org/msg03156.html Thanks Dick Hello All, Voting on the ESME apache-esme-1.0-RC1-incubating has concluded Results: 5 binding +1 vote Dick Hirsch +1 Ethan Jewett +1 Anne Kathrine Petteroe +1 Gianugo Rabellino +1 Bertrand Delacretaz +1 2 non-binding +1 votes Daniel Koller +1 Uday Subbarayan +1 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
