[Result][Vote] Move Chukwa to incubator
Original incubator proposal: http://wiki.apache.org/incubator/ChukwaProposal Vote put forward to incubator: 1. recommend TLP with guides to help the initial pmc, 2. accept incubating with tlp resource naming, but -incubating release naming 3. accept incubating requiring all incubator naming conventions, that might help the incubator simplify this decision. Result of the vote: Option 1) Ant Elder, Eric Yang, William A. Rowe Jr. Option 2) Ari Rabkin, Jerome Boulon, Chris Douglas, Greg Reddin Option 3) Bernd Fondermann Owen O'Malley +1 on proposal I am not sure about Chris Mattmann¹s position, but he raised the question about TLP. Is it ok to keep hadoop naming until we graduate to TLP, hence, we only rename once? ³-incubating² will be added to release artifacts. What is next? Regards, Eric - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Result][Vote] Move Chukwa to incubator
Hi Guys, My recommendation would be Option #1 - I think you guys would be OK as a TLP with some guidance, I'm not sure the Incubator will add anything that you guys can't learn on your own as a TLP with some mentorship from Incubator PMC'ers or ASF members helping you (Owen is an ASF member and his guidance would certainly help out). Helping you can mean just monitoring the private@ lists (like any ASF member can anyways), or sitting on your PMC for 6 months, and then leaving afterwards, IMO. Of course those sitting on the Chukwa PMC from Incubator-ville and who aren't as familiar with Chukwa code should be there more to help with guidance on releases/etc., then to actually influence the code base. Sorry for not getting back to you guys before now. I also want to point out that since I'm unlikely to be available to pick up a shovel and dig on this one, I don't want to block you guys doing the work. So if there is strong feeling for any of the other options, feel free to move forward. I think you guys have a great project and are closer to TLP maturity than Incubator community growing on this one... My 2 cents, Chris On 6/30/10 9:42 AM, "Eric Yang" wrote: Original incubator proposal: http://wiki.apache.org/incubator/ChukwaProposal Vote put forward to incubator: 1. recommend TLP with guides to help the initial pmc, 2. accept incubating with tlp resource naming, but -incubating release naming 3. accept incubating requiring all incubator naming conventions, that might help the incubator simplify this decision. Result of the vote: Option 1) Ant Elder, Eric Yang, William A. Rowe Jr. Option 2) Ari Rabkin, Jerome Boulon, Chris Douglas, Greg Reddin Option 3) Bernd Fondermann Owen O'Malley +1 on proposal I am not sure about Chris Mattmann's position, but he raised the question about TLP. Is it ok to keep hadoop naming until we graduate to TLP, hence, we only rename once? "-incubating" will be added to release artifacts. What is next? Regards, Eric - 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.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Re: [Result][Vote] Move Chukwa to incubator
On Jun 30, 2010, at 10:51 AM, Mattmann, Chris A (388J) wrote: On 6/30/10 9:42 AM, "Eric Yang" wrote: Original incubator proposal: http://wiki.apache.org/incubator/ChukwaProposal Vote put forward to incubator: 1. recommend TLP with guides to help the initial pmc, 2. accept incubating with tlp resource naming, but -incubating release naming 3. accept incubating requiring all incubator naming conventions, that might help the incubator simplify this decision. Result of the vote: Option 1) Ant Elder, Eric Yang, William A. Rowe Jr. Option 2) Ari Rabkin, Jerome Boulon, Chris Douglas, Greg Reddin Option 3) Bernd Fondermann Owen O'Malley +1 on proposal Sorry, I meant to vote for option 2. I think that it would be good to have more visibility in before they become a TLP. They also need to figure out how to add new committers to their project. -- Owen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Result][Vote] Move Chukwa to incubator
Welp, I think Owen is probably the best judge here since he has seen them in Hadoop-ville, and since he probably is way more familiar with the code and its eventual PMC members than I am. I'll amend my VOTE then. +1 to Incubation, with TLP-naming (in other words, option #2). I'll try and join the lists and help where I can too, cycles-willing :) Cheers, Chris On 6/30/10 11:23 AM, "Owen O'Malley" wrote: On Jun 30, 2010, at 10:51 AM, Mattmann, Chris A (388J) wrote: > On 6/30/10 9:42 AM, "Eric Yang" wrote: > > Original incubator proposal: > > http://wiki.apache.org/incubator/ChukwaProposal > > Vote put forward to incubator: > > 1. recommend TLP with guides to help the initial pmc, > 2. accept incubating with tlp resource naming, but -incubating release > naming > 3. accept incubating requiring all incubator naming conventions, > that might > help the incubator simplify this decision. > > Result of the vote: > > Option 1) Ant Elder, Eric Yang, William A. Rowe Jr. > Option 2) Ari Rabkin, Jerome Boulon, Chris Douglas, Greg Reddin > Option 3) Bernd Fondermann > > Owen O'Malley +1 on proposal Sorry, I meant to vote for option 2. I think that it would be good to have more visibility in before they become a TLP. They also need to figure out how to add new committers to their project. -- Owen - 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.mattm...@jpl.nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Re: [CANCELLED] [VOTE] Approve the M2 release of Apache Stonehenge
On 30/06/2010, Ben Dewey wrote: > Sebb created a JIRA ticket for us. I will repackage and return later for > another vote. That JIRA has no bearing on the release, as it only affects SVN. Otherwise I would have replied to the VOTE thread... So long as the correct EOLs are present in the release archives for specific files such as .bat and .sh (which may not work if the EOLs are incorrect), that's all that matters for the release as far as the JIRA is concerned. Fixing the SVN properties is necessary to ensure committers working on different OSes see the correct EOL when working on the source files. > Thanks, > > > -Ben Dewey > > > > -Original Message- > From: Ben Dewey [mailto:ben.de...@26ny.com] > Sent: Monday, June 28, 2010 3:27 PM > To: general@incubator.apache.org > Cc: stonehenge-...@incubator.apache.org > Subject: [VOTE] Approve the M2 release of Apache Stonehenge > > Hi, > > The Apache Stonehenge community has voted for the M2 release of Apache > Stonehenge. We are now asking the approval from the Incubator PMC to publish > the release. > > Stonehenge is a set of example applications for Service Oriented > Architecture that spans languages and platforms and demonstrates best > practice and interoperability. > > I have uploaded the Apache Stonehenge M2 release artifacts here: > http://people.apache.org/~bendewey/stonehenge/m2/take3/ > > The CHANGELOG is here: > http://people.apache.org/~bendewey/stonehenge/m2/take3/ChangeLog > > The key is here: > http://people.apache.org/~bendewey/stonehenge/m2/take3/KEYS > > RAT reports are here: > http://people.apache.org/~bendewey/stonehenge/m2/take3/rat_report/ > > This release is tagged at: > > https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take3/ > > The release vote on the stonehenge-dev mailing list resulted in > 8 +1 votes and no 0 or -1 votes. > +1 votes are from > *Ben Dewey > *Kent Brown > *Pablo Cibraro > *Selvaratnam Uthaiyashankar > *Chintana Wilamuna > *Michael Champion > *Kamaljit Bath > *Nick Hauenstein > > Vote Mail Thread is here: > http://www.mail-archive.com/stonehenge-...@incubator.apache.org/msg02544.html > > More information about the project can be found here: > [Incubation Status Page] http://incubator.apache.org/projects/stonehenge.html > [Project Page] http://incubator.apache.org/stonehenge/ > > Please vote to approve this release. > [] +1 Publish > [] 0 no opinion > [] -1 Don't publish (and reasons why) > > Regards, > > -Ben Dewey > > > > - > 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 Wink 1.1.1 (incubating)
I should also note that Wink 1.1.1 does have two binding IPMC votes from: Davanum Srinivas Kevan Miller We received these votes during the wink-dev voting. One more vote is needed to pass. -- Jesse Ramos From: Jesse A Ramos/Austin/IBM To: general@incubator.apache.org Cc: wink-...@incubator.apache.org , bri...@apache.org Date: 06/29/2010 03:04 PM Subject: [VOTE] Release Wink 1.1.1 (incubating) Hello, Wink 1.1.1 release voting has completed successfully on the wink-dev list. I'm now calling the IPMC vote to release Wink 1.1.1 (incubating) per the process indicated here: http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote The Maven staging area is at: https://repository.apache.org/content/repositories/orgapachewink-023/ The distributions are in: https://repository.apache.org/content/repositories/orgapachewink-023/org/apache/wink/apache-wink/1.1.1-incubating/ This release is tagged at: https://svn.apache.org/repos/asf/incubator/wink/tags/wink-1.1.1-incubating/ (revision 958096) The vote will be open here for at least 72 hours. Please indicate your vote: [ ] +1 to release Wink 1.1.1 incubating [ ] +0 [ ] -1 NOT to release Wink 1.1.1 incubating (and why) Please note that the staging URL repository for this vote is different than the one used for the wink-dev vote. The release was prematurely promoted from the Nexus staging repository. Brian Fox helped pull things back into the staging repository being used for this vote. The artifacts being voted on here are the same artifacts voted on on the wink-dev list. This 1.1.1 release was performed to provide a fix for the recent Axis2, CXF, and Wink XML Security vulnerability reported and disclosed through the appropriate Apache security channels. Besides plugging the XML security vulnerability holes, some other minor fixes are included.
RE: [CANCELLED] [VOTE] Approve the M2 release of Apache Stonehenge
Sebb, I suspected that may have been the case, no worries though, you will be seeing me again shortly. -Ben Dewey -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Wednesday, June 30, 2010 3:06 PM To: general@incubator.apache.org Subject: Re: [CANCELLED] [VOTE] Approve the M2 release of Apache Stonehenge On 30/06/2010, Ben Dewey wrote: > Sebb created a JIRA ticket for us. I will repackage and return later for > another vote. That JIRA has no bearing on the release, as it only affects SVN. Otherwise I would have replied to the VOTE thread... So long as the correct EOLs are present in the release archives for specific files such as .bat and .sh (which may not work if the EOLs are incorrect), that's all that matters for the release as far as the JIRA is concerned. Fixing the SVN properties is necessary to ensure committers working on different OSes see the correct EOL when working on the source files. > Thanks, > > > -Ben Dewey > > > > -Original Message- > From: Ben Dewey [mailto:ben.de...@26ny.com] > Sent: Monday, June 28, 2010 3:27 PM > To: general@incubator.apache.org > Cc: stonehenge-...@incubator.apache.org > Subject: [VOTE] Approve the M2 release of Apache Stonehenge > > Hi, > > The Apache Stonehenge community has voted for the M2 release of Apache > Stonehenge. We are now asking the approval from the Incubator PMC to publish > the release. > > Stonehenge is a set of example applications for Service Oriented > Architecture that spans languages and platforms and demonstrates best > practice and interoperability. > > I have uploaded the Apache Stonehenge M2 release artifacts here: > http://people.apache.org/~bendewey/stonehenge/m2/take3/ > > The CHANGELOG is here: > http://people.apache.org/~bendewey/stonehenge/m2/take3/ChangeLog > > The key is here: > http://people.apache.org/~bendewey/stonehenge/m2/take3/KEYS > > RAT reports are here: > http://people.apache.org/~bendewey/stonehenge/m2/take3/rat_report/ > > This release is tagged at: > > https://svn.apache.org/repos/asf/incubator/stonehenge/tags/stonehenge_m2_incubator_take3/ > > The release vote on the stonehenge-dev mailing list resulted in > 8 +1 votes and no 0 or -1 votes. > +1 votes are from > *Ben Dewey > *Kent Brown > *Pablo Cibraro > *Selvaratnam Uthaiyashankar > *Chintana Wilamuna > *Michael Champion > *Kamaljit Bath > *Nick Hauenstein > > Vote Mail Thread is here: > http://www.mail-archive.com/stonehenge-...@incubator.apache.org/msg02544.html > > More information about the project can be found here: > [Incubation Status Page] http://incubator.apache.org/projects/stonehenge.html > [Project Page] http://incubator.apache.org/stonehenge/ > > Please vote to approve this release. > [] +1 Publish > [] 0 no opinion > [] -1 Don't publish (and reasons why) > > Regards, > > -Ben Dewey > > > > - > 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
[Travel Assistance] - One week until Applications for financial assistance ends for ApacheCon NA 2010
Podling PPMCs - please re-post this message to your mailing lists. Hi All, There is only ONE WEEK to go before we stop accepting applications for financial assistance. The Travel Assistance Committee is now taking in applications for those wanting to attend ApacheCon North America (NA) 2010, which is taking place between the 1st and 5th November in Atlanta. The Travel Assistance Committee is looking for people who would like to be able to attend ApacheCon, but who need some financial support in order to be able to get there. There are limited places available, and all applications will be scored on their individual merit. Financial assistance is available to cover travel, accommodation and entrance to the event, either in part or in full, depending on circumstances. However, the support available for those attending only the barcamp is smaller than that for people attending the whole event. The Travel Assistance Committee aims to support all ApacheCons, and cross-project events, and so it may be prudent for those in Asia and the EU to wait for an event closer to them. More information can be found on the main Apache website at http://www.apache.org/travel/index.html - where you will also find a link to the online application and details for submitting. Applications for applying for travel assistance are now being accepted, and will close on the 7th July 2010. Good luck to all those that will apply. You are welcome to tweet, blog as appropriate. Regards, The Travel Assistance Committee. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
