Releases and IPMC votes
I was under the impression that *any* mentor is an IPMC member, has a binding +1 vote for releases and could therefore approve of releases without having to go through general@ While I find it very helpful and valuable for first time releases (and first time release managers) to go to general@ the first time, consecutive releases could go a lot smoother if Mentor votes were all that is required. The current policy states: > Therefore, should a Podling decide it wishes to perform a release, the > Podling SHALL > hold a vote on the Podling's public -dev list. At least three +1 votes are > required (see the > Apache Voting Process page). If the majority of all votes is positive, then > the Podling > SHALL send a summary of that vote to the Incubator's general list and > formally request > the Incubator PMC approve such a release. Three +1 Incubator PMC votes are > required. So there's not much leeway here. Although the three +1 incubator PMC votes are often already satisfied. Martijn - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Releases and IPMC votes
On Mon, Mar 14, 2011 at 8:13 AM, Martijn Dashorst wrote: > I was under the impression that *any* mentor is an IPMC member, has a > binding +1 vote for releases and could therefore approve of releases > without having to go through general@ > > While I find it very helpful and valuable for first time releases (and > first time release managers) to go to general@ the first time, > consecutive releases could go a lot smoother if Mentor votes were all > that is required. > > The current policy states: > >> Therefore, should a Podling decide it wishes to perform a release, the >> Podling SHALL >> hold a vote on the Podling's public -dev list. At least three +1 votes are >> required (see the >> Apache Voting Process page). If the majority of all votes is positive, then >> the Podling >> SHALL send a summary of that vote to the Incubator's general list and >> formally request >> the Incubator PMC approve such a release. Three +1 Incubator PMC votes are >> required. > > So there's not much leeway here. Although the three +1 incubator PMC > votes are often already satisfied. > > Martijn > There have been numerous releases where we have not followed exactly that process, two other common approaches these days seem to be: - the email to general@ says they already have three IPMC +1 votes on the poddling dev list, there may or may not be comments on the general@ thread and the release is done anyway after 3 days - the initial vote email is CC'ed to both the poddling dev list and general@ and the vote result is tallied from both lists and there may or may not have been votes on general@ Both of those approaches seem ok to me and I'd be fine with a simpler and more flexible policy, perhaps saying that the main thing is that general@ must be notified. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release NPanday 1.3-incubating
On 14 March 2011 06:05, Adelita Padilla wrote: > > > Hi, > > The Apache NPanday community has approved the 1.3-incubating release and we > are now looking for the approval of the IPMC to publish the release. > > These are the major changes included in this release: > > * Visual Studio 2010 and .Net 4.0 Framework support > * Removal of UAC and PAB directories > > > Subversion tag: > https://svn.apache.org/repos/asf/incubator/npanday/tags/npanday-1.3-incubating/ NOTICE file still says 2011 There is no DISCLAIMER anywhere I could find. Nor on the website, for that matter, though there is an Incubator logo. I think this is a blocker. > > Staging repository: > http://vmbuild.apache.org/archiva/repository/staged-npanday/ > > > Distribution files are located here: > http://people.apache.org/~apadilla/npanday/1.3-incubating/ The key is registered with public servers, but the name etc. should ideally have some reference to Apache: gpg: searching for "0X7580DCDB" from hkp server pgp.mit.edu (1) apadilla (adelita) 2048 bit RSA key 7580DCDB, created: 2011-01-14 I cannot find the KEYS file. The repository-builder files seem to contain chunks of a repository, and contain many non-ASF files. It's not clear if these all have compatible licences, and anyway they don't seem to be mentioned in the LICENSE file (or NOTICE, where necessary). Potential blocker. The MSI file also contains lots of 3rd party jars. > > Vote open for 72 hours. > > [] +1 > [] +0 > [] -1 > > > Thanks, > > -- > > liit > > > - > 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: Releases and IPMC votes
On Mon, Mar 14, 2011 at 09:33, ant elder wrote: > On Mon, Mar 14, 2011 at 8:13 AM, Martijn Dashorst > wrote: >> I was under the impression that *any* mentor is an IPMC member, has a >> binding +1 vote for releases and could therefore approve of releases >> without having to go through general@ >> >> While I find it very helpful and valuable for first time releases (and >> first time release managers) to go to general@ the first time, >> consecutive releases could go a lot smoother if Mentor votes were all >> that is required. >> >> The current policy states: >> >>> Therefore, should a Podling decide it wishes to perform a release, the >>> Podling SHALL >>> hold a vote on the Podling's public -dev list. At least three +1 votes are >>> required (see the >>> Apache Voting Process page). If the majority of all votes is positive, then >>> the Podling >>> SHALL send a summary of that vote to the Incubator's general list and >>> formally request >>> the Incubator PMC approve such a release. Three +1 Incubator PMC votes are >>> required. >> >> So there's not much leeway here. Although the three +1 incubator PMC >> votes are often already satisfied. >> >> Martijn >> > > There have been numerous releases where we have not followed exactly > that process, two other common approaches these days seem to be: > > - the email to general@ says they already have three IPMC +1 votes on > the poddling dev list, there may or may not be comments on the > general@ thread and the release is done anyway after 3 days > > - the initial vote email is CC'ed to both the poddling dev list and > general@ and the vote result is tallied from both lists and there may > or may not have been votes on general@ > > Both of those approaches seem ok to me and I'd be fine with a simpler > and more flexible policy, perhaps saying that the main thing is that > general@ must be notified. All PMC members have binding votes - means, they can be -1 on a particular release. I'd appreciate if more PMC members would review releases for projects they don't mentor (however I myself do fail miserably at this). (Let's remember that before mentors were formally established, all releases were ratified on general@ only and much Incubation work happened here.) So making release votes visible on general@ early can only increase overall release quality and give the whole PMC an opportunity to exercise oversight. One could also argue that binding release votes are required to happen on general@. However, in the past this led to stale votes, which does not serve the incubating projects. Bernd - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Howl as an Incubator Project
Alex Karasulu and Owen O'Malley have both volunteered on the private list and communicated to me off list their willingness to be mentors. So hopefully that is resolved as well. Alan. On Mar 12, 2011, at 1:27 PM, Upayavira wrote: I am concerned that none of the proposed mentors were Incubator PMC members at the time of the proposal. I believe Alan Gates is now joining the Incubator PMC, which is great. However, I'd like to see mentorship resolved before we proceed. Upayavira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Howl as an Incubator Project
Perfect. Upayavira On Mon, 14 Mar 2011 12:57 -0700, "Alan Gates" wrote: > Alex Karasulu and Owen O'Malley have both volunteered on the private > list and communicated to me off list their willingness to be mentors. > So hopefully that is resolved as well. > > Alan. > > On Mar 12, 2011, at 1:27 PM, Upayavira wrote: > > > I am concerned that none of the proposed mentors were Incubator PMC > > members at the time of the proposal. I believe Alan Gates is now > > joining > > the Incubator PMC, which is great. However, I'd like to see mentorship > > resolved before we proceed. > > > > Upayavira > > > > > - > 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 NPanday 1.3-incubating
On 14/03/2011, at 10:49 PM, sebb wrote: > On 14 March 2011 06:05, Adelita Padilla wrote: >> >> >> Hi, >> >> The Apache NPanday community has approved the 1.3-incubating release and we >> are now looking for the approval of the IPMC to publish the release. >> >> These are the major changes included in this release: >> >> * Visual Studio 2010 and .Net 4.0 Framework support >> * Removal of UAC and PAB directories >> >> >> Subversion tag: >> https://svn.apache.org/repos/asf/incubator/npanday/tags/npanday-1.3-incubating/ > > NOTICE file still says 2011 Fixed in SVN. Not a blocker for the release, I imagine. > > There is no DISCLAIMER anywhere I could find. Fixed in SVN. Liit, I suggest you add that to the release tarballs and re-sign them. It seems like overkill to start the release over for this. > > Nor on the website, for that matter, though there is an Incubator logo. Top right of http://incubator.apache.org/npanday/docs/1.3-incubating/index.html and http://incubator.apache.org/npanday/index.html ? I'm assuming you were looking at the old docs from the last release currently linked from the site (since it was rolled back), which points out it came from Codeplex. > > I think this is a blocker. > >> >> Staging repository: >> http://vmbuild.apache.org/archiva/repository/staged-npanday/ >> >> >> Distribution files are located here: >> http://people.apache.org/~apadilla/npanday/1.3-incubating/ > > The key is registered with public servers, but the name etc. should > ideally have some reference to Apache: > > gpg: searching for "0X7580DCDB" from hkp server pgp.mit.edu > (1) apadilla (adelita) > 2048 bit RSA key 7580DCDB, created: 2011-01-14 > > I cannot find the KEYS file. https://svn.apache.org/repos/asf/incubator/npanday/project/KEYS http://www.apache.org/dist/incubator/npanday/KEYS I don't think all users mention Apache, but it'd be good for Liit to add her ASF email address onto the key and resubmit it. > > The repository-builder files seem to contain chunks of a repository, > and contain many non-ASF files. It's not clear if these all have > compatible licences, and anyway they don't seem to be mentioned in the > LICENSE file (or NOTICE, where necessary). > > Potential blocker. > > The MSI file also contains lots of 3rd party jars. I referenced this here: http://markmail.org/message/sjlmw66a76phyn25 It's not ideal, but they are all redistributable in accordance with the legal policy. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Releases and IPMC votes
> I was under the impression that *any* mentor is an IPMC member, has a > binding +1 vote for releases and could therefore approve of releases > without having to go through general@ The issue is allowing proper oversight, and we've felt that it was important to give the PMC as a whole the opportunity to vet the release package(s). Given the frequency with which we have found issues, that seems warranted. Hence ... > > Therefore, should a Podling decide it wishes to perform a release, the Podling > > SHALL hold a vote on the Podling's public -dev list. At least three +1 votes > > are required (see the Apache Voting Process page). If the majority of all votes > > is positive, then the Podling SHALL send a summary of that vote to the > > Incubator's general list and formally request the Incubator PMC approve such a > > release. --- Noel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Incubator Board Report - March 2011
Nigel Daly, Tommaso Teofili, and Alan Gates have joined the PMC since the last report. Howl -- a table and storage management service for data created using Apache Hadoop -- has been accepted for Incubation. It will be renamed first, given that there is an ObjectWeb project also called HOWL. MRUnit -- a library to support unit testing of Hadoop MapReduce jobs -- has been accepted for Incubation. Rave -- a web And social Mashup Engine -- has been accepted for Incubation. BeanValidation and Gora failed to report this period. ALOIS ALOIS stands for "Advanced Log Data Insight System" and is meant to be a fully implemented open source SIEM security information and event management system. ALOIS is incubating since 22nd October 2010. The following items have been performed since the last reporting period: * Launch of the project website * Code review * Lightning Talk at the CCC Conference in Berlin * Promoting the project on different plaforms * Preparing several talks and booths (Chemnitz, Berlin, CeBIT, ...) Three most important issues to address in the move towards graduation: * Releasing Version 1 * Enlarge the developer base * Creating more use cases How has the community developed since the last report: * Despite the activities no real community so far How has the project developed since the last report: * The code is stable and accessable * The website is online and managed BeanValidation Failed to report. There is some degree of activity on its mailing lists, and addition of new Committers. Bluesky BlueSky has been incubating since 01-12-2008. It is an e-learning solution designed to help solve the disparity in availability of qualified education between well-developed cities and poorer regions of China. The following items have been performed since the last reporting period: * Now improving the statbility of system * Resolving the problems of having no Screen images * Resolving unstability of the 2nd focus student's data transportation. The following items are planned for the next reporting period: * Improving the stability of the system * add the fuanction of recording vedio in the teacher part. EasyAnt EasyAnt is a tool built on top of Ant and Ivy providing a standard approach to building java projects without locking the users in. Incubating since January 31st 2011 issues/agenda - 1 ICLA missing. The person does not answer since Feb 4th 2011, when he indicated he was working on getting the ICLA. - the code base has been migrated in SVN - the issues are in JIRA with component EASYANT Etch Etch was accepted into Incubator on 2 September 2008. Etch is a cross-platform, language- and transport-independent framework for building and consuming network services. The Etch toolset includes a network service description language, a compiler, and binding libraries for a variety of programming languages. For the last 3 months the main effort has been by Holger Grandy and Michael Fitzner, who contributed some bug fixes and have been converting documentation. The transition of current Etch Website to the new Apache CMS is in progress. Major parts of the sides are already available inside the CMS repository and can be seen at the staging area. The Spawn Labs team (Comer, Dixson) is working to integrate the c-binding into their product. They've been very quiet lately. We miss them. Comer wrote up something about his service cloud and is waiting for permission to publish it. Although progress is now visible, we still need to get more user and development activity on our lists. Top issues currently are: - plan features and dates for release 1.2 / 1.1.1 - work on further language bindings - website transition to Apache CMS - documentation Note by Martijn Dashorst: I met with Holger Grandy and Michael Fitzner at FOSDEM'11 and we spoke about lots of stuff concerning Etch. I think the future for the podling is bright, but we need to get more people involved by publishing articles. The biggest problem is finding the right venues for publishing the articles. I'll bring Etch under the attention of PR to see if they have any good ideas. Gora Gora is "Gora is an ORM framework for column stores such as Apache HBase and Apache Cassandra with a specific focus on Hadoop." Did not report. Has voted in new Committers. Appears quite active. Hama Hama was accepted into Incubator on 20 May 2008. Hama is a distributed computing framework based on BSP (Bulk Synchronous Parallel) computing techniques for massive scientific computations. == Top 2 or 3 things to resolve prior to graduation == * Complete first release * Invite new active committers == Issues for the Incubator PMC or ASF Board == None. == Community development == * Mailing list shows increased usage from previous report * Chia-Hung Lin has contributed a p
Re: [VOTE] Release NPanday 1.3-incubating
On 15 March 2011 03:27, Brett Porter wrote: > > On 14/03/2011, at 10:49 PM, sebb wrote: > >> On 14 March 2011 06:05, Adelita Padilla wrote: >>> >>> >>> Hi, >>> >>> The Apache NPanday community has approved the 1.3-incubating release and we >>> are now looking for the approval of the IPMC to publish the release. >>> >>> These are the major changes included in this release: >>> >>> * Visual Studio 2010 and .Net 4.0 Framework support >>> * Removal of UAC and PAB directories >>> >>> >>> Subversion tag: >>> https://svn.apache.org/repos/asf/incubator/npanday/tags/npanday-1.3-incubating/ >> >> NOTICE file still says 2011 > > Fixed in SVN. Not a blocker for the release, I imagine. > >> >> There is no DISCLAIMER anywhere I could find. > > Fixed in SVN. Liit, I suggest you add that to the release tarballs and > re-sign them. It seems like overkill to start the release over for this. > >> >> Nor on the website, for that matter, though there is an Incubator logo. > > Top right of > http://incubator.apache.org/npanday/docs/1.3-incubating/index.html and > http://incubator.apache.org/npanday/index.html ? Yes, the logos are (still) there. > I'm assuming you were looking at the old docs from the last release currently > linked from the site (since it was rolled back), which points out it came > from Codeplex. I am looking at the current website. The pages you mention above have the Incubator logo, but no disclaimer that I could find. For an example of how it can be done, see: http://incubator.apache.org/rat/ The first paragraph starts: "Apache RAT is an effort undergoing incubation at The Apache Software Foundation (ASF) ..." >> >> I think this is a blocker. >> >>> >>> Staging repository: >>> http://vmbuild.apache.org/archiva/repository/staged-npanday/ >>> >>> >>> Distribution files are located here: >>> http://people.apache.org/~apadilla/npanday/1.3-incubating/ >> >> The key is registered with public servers, but the name etc. should >> ideally have some reference to Apache: >> >> gpg: searching for "0X7580DCDB" from hkp server pgp.mit.edu >> (1) apadilla (adelita) >> 2048 bit RSA key 7580DCDB, created: 2011-01-14 >> >> I cannot find the KEYS file. > > https://svn.apache.org/repos/asf/incubator/npanday/project/KEYS > http://www.apache.org/dist/incubator/npanday/KEYS Thanks, found that later. It would help to include the link in VOTE emails. > I don't think all users mention Apache, but it'd be good for Liit to add her > ASF email address onto the key and resubmit it. > >> >> The repository-builder files seem to contain chunks of a repository, >> and contain many non-ASF files. It's not clear if these all have >> compatible licences, and anyway they don't seem to be mentioned in the >> LICENSE file (or NOTICE, where necessary). >> >> Potential blocker. >> >> The MSI file also contains lots of 3rd party jars. > > I referenced this here: http://markmail.org/message/sjlmw66a76phyn25 > > It's not ideal, but they are all redistributable in accordance with the legal > policy. Do any of them require attribution in the NOTICE file? Unless they all use the Apache Licence 2.0, then their licences need to be added to LICENSE.txt. In any case, the products should probably be mentioned in LICENSE.txt - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Board report: Gora March 2011
Hi Noel, and IPMC community, Apologies as the Champion for Gora for missing the March 2011 report deadline. Would it be possible to please include the report even though it's late? I've taken the trouble of adding it to the wiki, pasted below: Gora Gora is an ORM framework for column stores such as Apache HBase and Apache Cassandra with a specific focus on Hadoop. A list of the three most important issues to address in the move towards graduation 1. Port Gora code and license headers into ASF license headers 2. Develop a strong community with organizational diversity and with infection into existing ASF projects like Nutch and Hadoop 3. At least one Gora incubating release Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware of? No, not at this time. How has the community developed since the last report? The IPMC and Gora PPMC have elected to add Alexis Detreglode as a Gora committer and PPMC member. Mailing list activity has been picking up. We've recently been fielding questions and even a patch from some of our users who are interesting in helping to maintain a Maven-based version of the build system. How has the project developed since the last report? Gora was voted into the Incubator by the IPMC on September 26, 2010. The project is currently rolling RC3 of our first 0.1-incubating release. Henry Saputra and Andrzej Bialecki are leading the way. The first 2 release candidates were tested, and we have been working with the Incubator and Gora communities to address all of the issues raised. We expect Apache Gora 0.1-incubating to be released within the month, and expect Nutch 2.0-trunk to upgrade to the Gora release shortly thereafter. Signed off by mentor: mattmann Apologies for the tardiness. Cheers, Chris ++ 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
