Re: [VOTE] Graduate Sqoop podling from Apache Incubator
status page, etc looks good +1 (binding) good luck! LieGrue, strub - Original Message - From: Olivier Lamy ol...@apache.org To: general@incubator.apache.org Cc: Sent: Sunday, February 26, 2012 8:44 AM Subject: Re: [VOTE] Graduate Sqoop podling from Apache Incubator +1 (binding) 2012/2/24 Arvind Prabhakar arv...@apache.org: This is a call for vote to graduate Sqoop podling from Apache Incubator. Sqoop entered Incubator in June of 2011. Since then it has added three new committers from diverse organizations, added two new PPMC members, and made two releases following the ASF policies and guidelines. The community of Sqoop is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Sqoop community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Sqoop podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Sqoop podling [ ] -1 Reject graduation of Sqoop podling from Apache Incubator This vote will be open for 72 hours. Please find the proposed board resolution below. [1] http://markmail.org/thread/xwhjtkik7pgrmypi [2] http://s.apache.org/sqoop Thanks, Arvind Prabhakar X. Establish the Apache Sqoop 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 efficiently transferring bulk data between Apache Hadoop and structured datastores 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 Sqoop Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Sqoop Project be and hereby is responsible for the creation and maintenance of software related to efficiently transferring bulk data between Apache Hadoop and structured datastores; and be it further RESOLVED, that the office of Vice President, Apache Sqoop 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 Sqoop Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Sqoop 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 Sqoop Project: * Aaron Kimball kimba...@apache.org * Andrew Bayer aba...@apache.org * Ahmed Radwan ah...@apache.org * Arvind Prabhakar arv...@apache.org * Bilung Lee b...@apache.org * Greg Cottman gcott...@apache.org * Guy le Mar guyle...@apache.org * Jaroslav Cecho jar...@apache.org * Jonathan Hsieh jmhs...@apache.org * Olivier Lamy ol...@apache.org * Paul Zimdars pzimd...@apache.org * Roman Shaposhnik r...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar be appointed to the office of Vice President, Apache Sqoop, 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 Sqoop 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 Sqoop Project; and be it further RESOLVED, that the Apache Sqoop Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Sqoop podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Sqoop 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 -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail:
Re: [VOTE] Graduate Sqoop podling from Apache Incubator
+1 (binding) Tommaso 2012/2/24 Arvind Prabhakar arv...@apache.org This is a call for vote to graduate Sqoop podling from Apache Incubator. Sqoop entered Incubator in June of 2011. Since then it has added three new committers from diverse organizations, added two new PPMC members, and made two releases following the ASF policies and guidelines. The community of Sqoop is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. Sqoop community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Sqoop podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Sqoop podling [ ] -1 Reject graduation of Sqoop podling from Apache Incubator This vote will be open for 72 hours. Please find the proposed board resolution below. [1] http://markmail.org/thread/xwhjtkik7pgrmypi [2] http://s.apache.org/sqoop Thanks, Arvind Prabhakar X. Establish the Apache Sqoop 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 efficiently transferring bulk data between Apache Hadoop and structured datastores 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 Sqoop Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Sqoop Project be and hereby is responsible for the creation and maintenance of software related to efficiently transferring bulk data between Apache Hadoop and structured datastores; and be it further RESOLVED, that the office of Vice President, Apache Sqoop 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 Sqoop Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Sqoop 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 Sqoop Project: * Aaron Kimball kimba...@apache.org * Andrew Bayer aba...@apache.org * Ahmed Radwan ah...@apache.org * Arvind Prabhakar arv...@apache.org * Bilung Leeb...@apache.org * Greg Cottman gcott...@apache.org * Guy le Marguyle...@apache.org * Jaroslav Cechojar...@apache.org * Jonathan Hsiehjmhs...@apache.org * Olivier Lamy ol...@apache.org * Paul Zimdars pzimd...@apache.org * Roman Shaposhnik r...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Arvind Prabhakar be appointed to the office of Vice President, Apache Sqoop, 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 Sqoop 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 Sqoop Project; and be it further RESOLVED, that the Apache Sqoop Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Sqoop podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Sqoop 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
sebb, What I'm trying to get to at the moment is something that enables a release of TDB and we can apply to next module. jena is a number of modules, we have released 3 (5 actually - 2 are the parent POM and the distribution maker for the core) already; TDB is the sixth, and there are 3 more in the pipeline. People have been asking for more packaging forms - WAR file for the server functionality, OSGi for Jena as a whole, which seems to be a non-trivial exercise. One of the ones to come is not a simple jar build - it's a server that can used as a jar, as a combined dependencies jar or run from the command line. I'm trying to understand the constraints required so that will be smooth(er). We are discussing rebuilding our build strategy but doing so, and to get it working reliably and stably will take time. We chose to release with what we have, and not let reworking the build system become critical path for graduation. The apache-jena-tdb... is then merely being a renamed file for browsing apache-jena-tdb-0.9.0-incubating-distribution.zip (c.f. Ant which has renamed items in it dist/ant) I referred to Ant specifically because the incubator documentation for podling releases picks ant and httpd out as examples to look at. ant has top level items for easy discovery which are renamed duplicates of things in binaries/ `-- source-release `-- jena-tdb-0.9.0-incubating What's the point of the subdirectory? because there are other modules with their own source-release artifact. The TDB release items will be merged into the existing directory. We had been following a layout like CXF where source-release and binaries are in the same directory. Given that is where a the maven-driven process puts them, someone taking the source releease doing mvn package is going to look in target/ and expect created items to be there. That was the RC-2 proposal for dist for TDB. If, as seems necessary, we have to adopt a different layout, we'll reorganise the existing release items into the same structure. Would a structure: dist |-- binaries | `-- jena-tdb-0.9.0-incubating | |-- jena-tdb-0.9.0-incubating-distribution.tar.gz | |-- jena-tdb-0.9.0-incubating-distribution.zip | |-- jena-tdb-0.9.0-incubating-javadoc.jar | |-- jena-tdb-0.9.0-incubating-sources.jar | |-- jena-tdb-0.9.0-incubating.jar The jars are not generally needed for dist/ |-- download | |-- apache-jena-tdb-0.9.0-incubating-distribution.tar.gz | |-- apache-jena-tdb-0.9.0-incubating-distribution.zip Are these the same as the distribution archives above? `-- source-release `-- jena-tdb-0.9.0-incubating What's the point of the subdirectory? |-- jena-tdb-0.9.0-incubating-source-release.zip Name does not agree with binary archives + the .asc, .md5 .sha1 files be acceptable? Or with download/ removed its files at the top level? I still find it very confusing. e.g. where is the source file for jena-tdb-0.9.0-incubating-distribution.tar.gz? jena-tdb-0.9.0-incubating-source-release.zip Given the way maven classifiers work, it is a reasonable expectation of the user to find the various classifier artifacts in target/ after mvn package Why is there a download directory and a binaries directory? Like ant, I pulled out the items which are download-unpack-go. The dist areas serves several audiences - for (new) users, not necessarily experienced maven users, we have the Jena website (we use Apache CMS to produce the website, not maven by the way) simply point to download/ (mirrored). Ditto URLs handled out on the web as being the place to go to download Jena. I don't mind if it's download/ or (like ant) at the top level. Andy Mocked up at: http://people.apache.org/~andy/dist-tdb-proto/ See my mockups at: http://people.apache.org/~sebb/dist-tdb-proto/ one - parallel binaries/ and source/ two - single directory named after the release. The latter is likely to be easier to manage when moving to svnpubsub. $ ls -1R ./one: KEYS binaries source ./one/binaries: apache-jena-tdb-0.9.0-incubating-distribution.tar.gz apache-jena-tdb-0.9.0-incubating-distribution.zip ./one/source: apache-jena-tdb-0.9.0-incubating-source-release.zip ./two: KEYS apache-jena-tdb-0.9.0-incubating ./two/apache-jena-tdb-0.9.0-incubating: apache-jena-tdb-0.9.0-incubating-distribution.tar.gz apache-jena-tdb-0.9.0-incubating-distribution.zip apache-jena-tdb-0.9.0-incubating-source-release.zip - 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] RAT Ready To Graduate As Apache Creadur Top Level Project
The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ ] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
On 26 February 2012 15:41, Andy Seaborne a...@apache.org wrote: sebb, What I'm trying to get to at the moment is something that enables a release of TDB and we can apply to next module. jena is a number of modules, we have released 3 (5 actually - 2 are the parent POM and the distribution maker for the core) already; TDB is the sixth, and there are 3 more in the pipeline. People have been asking for more packaging forms - WAR file for the server functionality, OSGi for Jena as a whole, which seems to be a non-trivial exercise. One of the ones to come is not a simple jar build - it's a server that can used as a jar, as a combined dependencies jar or run from the command line. I'm trying to understand the constraints required so that will be smooth(er). We are discussing rebuilding our build strategy but doing so, and to get it working reliably and stably will take time. We chose to release with what we have, and not let reworking the build system become critical path for graduation. The apache-jena-tdb... is then merely being a renamed file for browsing apache-jena-tdb-0.9.0-incubating-distribution.zip (c.f. Ant which has renamed items in it dist/ant) I referred to Ant specifically because the incubator documentation for podling releases picks ant and httpd out as examples to look at. ant has top level items for easy discovery which are renamed duplicates of things in binaries/ `-- source-release `-- jena-tdb-0.9.0-incubating What's the point of the subdirectory? because there are other modules with their own source-release artifact. The TDB release items will be merged into the existing directory. So why don't you do the same for the download directory? We had been following a layout like CXF where source-release and binaries are in the same directory. Given that is where a the maven-driven process puts them, someone taking the source releease doing mvn package is going to look in target/ and expect created items to be there. That was the RC-2 proposal for dist for TDB. If, as seems necessary, we have to adopt a different layout, we'll reorganise the existing release items into the same structure. Would a structure: dist |-- binaries | `-- jena-tdb-0.9.0-incubating | |-- jena-tdb-0.9.0-incubating-distribution.tar.gz | |-- jena-tdb-0.9.0-incubating-distribution.zip | |-- jena-tdb-0.9.0-incubating-javadoc.jar | |-- jena-tdb-0.9.0-incubating-sources.jar | |-- jena-tdb-0.9.0-incubating.jar The jars are not generally needed for dist/ |-- download | |-- apache-jena-tdb-0.9.0-incubating-distribution.tar.gz | |-- apache-jena-tdb-0.9.0-incubating-distribution.zip Are these the same as the distribution archives above? `-- source-release `-- jena-tdb-0.9.0-incubating What's the point of the subdirectory? |-- jena-tdb-0.9.0-incubating-source-release.zip Name does not agree with binary archives + the .asc, .md5 .sha1 files be acceptable? Or with download/ removed its files at the top level? I still find it very confusing. e.g. where is the source file for jena-tdb-0.9.0-incubating-distribution.tar.gz? Sorry, that was a mistake - I meant where is the source for the dowload file apache-jena-tdb-0.9.0-incubating-distribution.tar.gz jena-tdb-0.9.0-incubating-source-release.zip Not only is the name different, but also the archive type is different. That is very confusing. Given the way maven classifiers work, it is a reasonable expectation of the user to find the various classifier artifacts in target/ after mvn package Yes, but what has Maven to do with the self-contained release archives? Why is there a download directory and a binaries directory? Like ant, I pulled out the items which are download-unpack-go. The dist areas serves several audiences - for (new) users, not necessarily experienced maven users, we have the Jena website (we use Apache CMS to produce the website, not maven by the way) simply point to download/ (mirrored). Ditto URLs handled out on the web as being the place to go to download Jena. There should be no need to have Maven jars in the dist/ structure. I think this is just confusing to end-users. I don't mind if it's download/ or (like ant) at the top level. What I care about is that it is: - more difficult to find the source than some of the binaries, because of the extra directory level. - not at all clear how to find the source for some of the binaries, as it is at a different level and with a different name. - binaries are available as tar.gz and zip, but source only as zip Andy Mocked up at: http://people.apache.org/~andy/dist-tdb-proto/ See my mockups at: http://people.apache.org/~sebb/dist-tdb-proto/ one - parallel binaries/ and source/ two - single directory named after the release. The latter is likely to be easier to manage when moving to svnpubsub. $ ls -1R ./one: KEYS binaries
Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
+1 (binding). Great work and really happy about this! Cheers, Chris On Feb 26, 2012, at 8:03 AM, Robert Burrell Donkin wrote: The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ ] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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 ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
On Sun, 26 Feb 2012, Robert Burrell Donkin wrote: The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) +1, good luck! Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
+1 (binding and as a mentor) This is long overdue in my opinion, well done for finally being able to call the vote. Ross On 26 February 2012 21:33, Robert Burrell Donkin rdon...@apache.org wrote: The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ ] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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 -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
On 2/26/2012 10:03 AM, Robert Burrell Donkin wrote: --8--- [X] +1 the RAT community feels ready to graduate as Apache Creadur --- Cheers! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
+1 (binding) Ralph On Feb 26, 2012, at 8:03 AM, Robert Burrell Donkin wrote: The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ ] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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] Release jena-tdb-0.9.0-incubating (RC-4)
`-- source-release `-- jena-tdb-0.9.0-incubating What's the point of the subdirectory? because there are other modules with their own source-release artifact. The TDB release items will be merged into the existing directory. So why don't you do the same for the download directory? The download/ directory would be for all modules. But as I said, top level work for me as well. One place where you can get all the jena-related unpack-and-go files. Is that not possible? We had been following a layout like CXF where source-release and binaries are in the same directory. I still find it very confusing. e.g. where is the source file for jena-tdb-0.9.0-incubating-distribution.tar.gz? Sorry, that was a mistake - I meant where is the source for the dowload file apache-jena-tdb-0.9.0-incubating-distribution.tar.gz As per ant example - there is a correctly named and positioned file and also a copy (and rename) elsewhere. The specific rename is because, long term, post rework the build, we think apache-jena-... will be the packaged up forms and jena-... the core jars but that isn't really the issue here. A systematically named file is available. What I care about is that it is: - more difficult to find the source than some of the binaries, because of the extra directory level. Maybe I don't understand how should we manage multiple modules with currently have independent version numbers. The proposal is have: /sources/jena-arq-2.9.0-incubating/ /sources/jena-core-2.7.0-incubating/ /sources/jena-iri-0.9.0-incubating/ /sources/jena-tdb-0.9.0-incubating/ /binaries/jena-arq-2.9.0-incubating/ /binaries/jena-core-2.7.0-incubating/ /binaries/jena-iri-0.9.0-incubating/ /binaries/jena-tdb-0.9.0-incubating/ Is this better? /jena-arq-2.9.0-incubating/sources/ /jena-arq-2.9.0-incubating/binaries/ /jena-core-2.7.0-incubating/sources/ /jena-core-2.7.0-incubating/binaries/ /jena-iri-0.9.0-incubating/sources/ /jena-iri-0.9.0-incubating/binaries/ /jena-tdb-0.9.0-incubating/sources/ /jena-tdb-0.9.0-incubating/binaries/ Can we put easy to find files in /? - not at all clear how to find the source for some of the binaries, as it is at a different level and with a different name. /sources/jena-tdb-0.9.0-incubating/jena-tdb-VER(-classifier)? /binaries/jena-tdb-0.9.0-incubating/jena-tdb-VER-source-release are at the same level. We did have a form like sling uses, split per module. - binaries are available as tar.gz and zip, but source only as zip Sorry - I thought I'd answered this earlier. We use org.apache:apache which comes down to this (in assemblies/source-release.xml) which just makes a zip. assembly idsource-release/id formats formatzip/format /formats componentDescriptors componentDescriptorassemblies/source-shared.xml/componentDescriptor /componentDescriptors /assembly so we just followed that. It's a tradeoff - reuse unchnaged vs forking it. For the .jar.gz: we used to ship a zip, which any Java systems must have access to as jar files are zip archives. Adding .tar.gz was courtesy for people wanting files in those forms because it very little work to help them. Andy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ATTN] Incubator releases distribution area reminder!
On 24/02/12 16:56, Daniel Shahaf wrote:
Mark Struberg wrote on Fri, Feb 24, 2012 at 09:17:57 +:
PS: txs to Daniel Shahaf for pointing me at the current docs
I didn't :)
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
As I'm discovering, the incubator guides aren't completely clear :-)
1/
Incubator guide:
[[
Distribution policy with regard to releases is simple:
The Incubator insists that artifacts for {podling} are contained
within www.apache.org/dist/incubator/{podling}.
]]
which does not mention the maven repository at all, and says that
artifacts go in the dist/incubator/ area.
Two meanings of artifact - maven artifact and Apache product.
2/
If the intention is to strongly suggest specific layouts then the text:
[[
Best Practice
Layout
A podling is free to choose a suitable layout for its released artifacts
within the podling distribution directory.
It is recommended that standard layouts (commonly used by other
projects) be studied
]]
could be revised to include the constraints
3/
[[
Often symbolic links are created from the root of the project
distribution directory to the latest version of each release. This
allows scripts or users to easily locate the latest release.
]]
is at odds with
http://www.apache.org/dev/mirror-step-by-step.html
[[
9. Do not use symbolic links in mirrored directories!
]]
although that does say Note: This file contains out-of-date information.
Sorry - I do read the documentation sometimes ;-)
Andy
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ATTN] Incubator releases distribution area reminder!
Andy Seaborne wrote on Sun, Feb 26, 2012 at 17:37:49 +: 3/ [[ Often symbolic links are created from the root of the project distribution directory to the latest version of each release. This allows scripts or users to easily locate the latest release. ]] is at odds with http://www.apache.org/dev/mirror-step-by-step.html [[ 9. Do not use symbolic links in mirrored directories! ]] although that does say Note: This file contains out-of-date information. That refers to the suggestion to ssh www. But yeah, I can assure you that until a few weeks ago no one (PMC or podling) used symlinks in that matter, and even today there exists only one such link in the entire dist/ tree. Sorry - I do read the documentation sometimes ;-) Andy - 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] RAT Ready To Graduate As Apache Creadur Top Level Project
On 26 February 2012 16:03, Robert Burrell Donkin rdon...@apache.org wrote: The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [X] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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] RAT Ready To Graduate As Apache Creadur Top Level Project
+1 2012/2/26 Robert Burrell Donkin rdon...@apache.org: The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ ] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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 -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
+1 Niall On Sun, Feb 26, 2012 at 4:03 PM, Robert Burrell Donkin rdon...@apache.org wrote: The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ ] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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] Release Apache Hama 0.4-incubating RC6
Added also bloom filter license in described Hadoop LICENSE file. http://svn.apache.org/repos/asf/incubator/hama/branches/0.4/LICENSE.txt Is this now complete, Franklin? On Sun, Feb 26, 2012 at 11:10 AM, Franklin, Matthew B. mfrank...@mitre.org wrote: On 2/25/12 8:12 PM, Edward J. Yoon edwardy...@apache.org wrote: Thanks. Actually we're trying to separate them but there's some issues related with packaging web resources e.g., https://issues.apache.org/jira/browse/HAMA-494 If it's not a blocker, I'd like to fix this issue in the next release. As I understand it the only requirement is that you have a source release; which your combined one does. As I said it isn't optimal. The blocker as I see it is that the LICENSE file is incomplete as I mentioned earlier. On Sat, Feb 25, 2012 at 9:22 PM, Franklin, Matthew B. mfrank...@mitre.org wrote: For the packaging, a clean source package and a separate binary release is preferred [1]. This isn't the blocker in my opinion, but something that you should look at. [1]: http://incubator.apache.org/guides/releasemanagement.html#best-practice-t yp es On 2/25/12 2:52 AM, Edward J. Yoon edwardy...@apache.org wrote: The LICENSE file in the binary distribution needs to include 3rd party licenses included in the libs that are being re-distributed as part of your release. Your binary release artifacts include ant 1.7 (and potentially others) that has source covered by 3rd party licenses which I don't see in your LICENSE file. The ant is released under the Apache Software License and LICENSE.txt file contains the Apache license v2.0. http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.txt I don't see any missed 3rd party licenses. Could you please check it again? Ant itself includes code under a separate license. Since your binary release includes the Ant jar, you are redistributing that code and need to include its license. http://svn.apache.org/repos/asf/ant/core/tags/ANT_171/LICENSE And, the distributions contains both source code and compiled jar files. Anyways, if we have to go to a RC7, let's merge the new jiras from trunk to 0.4.0, compression and stuff can be great improvement. I don't think we have to create new one. Moreover, new stuffs are not tested enough yet. On Sat, Feb 25, 2012 at 3:44 PM, Thomas Jungblut thomas.jungb...@googlemail.com wrote: Hmm- I always thought it is Apache Ant and therefore Apache 2.0 license. If we have to add all transitive licenses we are going to release until the overnext year. What is wrong packaging the source within a binary distribution? Anyways, if we have to go to a RC7, let's merge the new jiras from trunk to 0.4.0, compression and stuff can be great improvement. 2012/2/25 Franklin, Matthew B. mfrank...@mitre.org -1 at the moment due to source distribution and license concerns noted below. On 2/20/12 8:54 AM, Edward J. Yoon edwardy...@apache.org wrote: Hi, I've create RC6 for the Apache Hama 0.4-incubating release. This fixes the license header issue and adds rat-plugin. Signing KEYS: http://svn.apache.org/repos/asf/incubator/hama/trunk/src/site/resource s/ fi les/KEYS Artifacts: http://people.apache.org/~edwardyoon/dist/0.4-RC6/ Do you have a source artifact that is a simple archive of the SVN? Also, you can stage your artifacts at http://people.apache.org/builds/incubator/ rather than your own public html folder, but this is not required. Tag: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/ NOTICE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/NOTICE.tx t LICENSE.txt: http://svn.apache.org/repos/asf/incubator/hama/tags/0.4-RC6/LICENSE.t xt The LICENSE file in the binary distribution needs to include 3rd party licenses included in the libs that are being re-distributed as part of your release. Your binary release artifacts include ant 1.7 (and potentially others) that has source covered by 3rd party licenses which I don't see in your LICENSE file. Staging website: http://people.apache.org/~edwardyoon/site/ You can run the mvn apache-rat:check command to check for license headers. I tested this RC6 builds, single mode, and distributed mode on my 16 nodes cluster and 5 VMs with EC2. Please retry, check signatures, licenses, and vote! I hope this will be a final, and +1. Thanks. -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thomas Jungblut Berlin thomas.jungb...@gmail.com -- Best Regards, Edward J. Yoon @eddieyoon - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
-Original Message- From: Robert Burrell Donkin [mailto:rdon...@apache.org] Sent: Monday, 27 February 2012 2:03 AM To: rat-...@incubator.apache.org Cc: general@incubator.apache.org Subject: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ x ] +1 the RAT community feels ready to graduate as Apache Creadur Gav... [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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: [ATTN] Incubator releases distribution area reminder!
On 26 February 2012 18:39, Daniel Shahaf d...@daniel.shahaf.name wrote: Andy Seaborne wrote on Sun, Feb 26, 2012 at 17:37:49 +: 3/ [[ Often symbolic links are created from the root of the project distribution directory to the latest version of each release. This allows scripts or users to easily locate the latest release. AIUI, this is a bad idea, because: - the links are frequently not updated - they don't work for mirrors, which means the mirrors space usage increases - when the file is downloaded using the link, the file name does not include the version information Users will normally get the latest release from the download page, so the only possible use is for scripts. ]] is at odds with http://www.apache.org/dev/mirror-step-by-step.html [[ 9. Do not use symbolic links in mirrored directories! ]] although that does say Note: This file contains out-of-date information. That refers to the suggestion to ssh www. But yeah, I can assure you that until a few weeks ago no one (PMC or podling) used symlinks in that matter, and even today there exists only one such link in the entire dist/ tree. Huh? The use of symlinks under /www/www.apache.org/dist is unfortunately still quite common. pwd dist : pwd /www/www.apache.org/dist pwd dist : find . -type l -name *current*.asc -ls | wc -l 77 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
+1 Stefan On 2012-02-26, Robert Burrell Donkin wrote: The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ ] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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
Re: [VOTE] RAT Ready To Graduate As Apache Creadur Top Level Project
+1 (binding) Regards JB On 02/26/2012 10:13 PM, Olivier Lamy wrote: +1 2012/2/26 Robert Burrell Donkinrdon...@apache.org: The graduation guide[1] recommends that the Rat community demonstrates it's willingness to govern itself through a free VOTE before asking the IPMC to approve graduation. So, here it is :-) See [2] for a draft of the charter, excluding the list of initial committers. Unless anyone jumps into this thread, I'll assume that the current list of committers would be fine. Please read, review and jump in - but this is a vote on the principle of graduating now. This VOTE is open to all, and I'll tally this no early than Wednesday, 29 Feb 2012 17:00 UTC. Robert --8--- [ ] +1 the RAT community feels ready to graduate as Apache Creadur [ ] +0 [ ] -0 [ ] -1 Do not graduate RAT at this time --- [1] http://incubator.apache.org/guides/graduation.html#toplevel [2] Suggested Draft Charter: 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 comprehension and auditing of software distributions 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 Creadur Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Creadur Project be and hereby is responsible for the creation and maintenance of open-source software related to the comprehension and auditing of software distributions for distribution at no charge to the public RESOLVED, that the office of Vice President, Apache Creadur 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 Creadur Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Creadur 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 Creadur Project: ... NOW, THEREFORE, BE IT FURTHER RESOLVED, that Robert Burrell Donkin be appointed to the office of Vice President, Apache Creadur, 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 Creadur 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 Creadur Project; and be it further RESOLVED, that the Apache Creadur Project be and hereby is tasked with the migration and rationalization of the Apache Incubator RAT podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator RAT 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 -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release jena-tdb-0.9.0-incubating (RC-4)
On Thu, Feb 23, 2012 at 4:50 PM, Andy Seaborne a...@apache.org wrote: The Jena PPMC has voted to release Apache Jena TDB 0.9.0-incubating and we would now be grateful if members of IPMC would review and vote for this release. +1 from me. (justification: 1) I do not consider unintuitive file name and directory layout conventions blockers for release; I think this thread shows unintuitive is subjective anyway. I pointed the deviations out before on jena-dev, and then folks obviously thought about this and decided to do things differently from a lot of other projects. Even if the chosen convention is wacky that does not make it wrong. 2) Whilst LEGAL-124 remains unresolved there's plenty of precedent for not having license headers in test data and similar auxiliary files, all around apache, and so I consider it fine to continue current standard practice until different rules arrive. 3) all looks good to me ;-) ) cheers, Leo - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
