On Sat, Jun 8, 2013 at 12:12 AM, ant elder <[email protected]> wrote: > On Fri, Jun 7, 2013 at 7:45 PM, Patrick Hunt <[email protected]> wrote: > >> On Thu, Jun 6, 2013 at 1:16 PM, Flavio Junqueira <[email protected]> >> wrote: >> > I have some comments inline: >> > >> > On Jun 6, 2013, at 6:21 PM, Patrick Hunt <[email protected]> wrote: >> > >> >> On Thu, Jun 6, 2013 at 2:04 AM, ant elder <[email protected]> wrote: >> >>> Hi Patrick thanks for replying. Some comments and questions inline. >> >>> >> >> >> >> Thank you ant for checking in. :-) >> >> >> >>> >> >>> On Wed, Jun 5, 2013 at 6:15 PM, Patrick Hunt <[email protected]> wrote: >> >>>> I've been hesitant to push for graduation for the following reasons: >> >>>> >> >>>> 1) only one new committer has been added to the project since it's >> inception. >> >>> >> >>> Have there been contributors that you feel might have merited being >> >>> made a committer but weren't? What we're looking for is that the >> >>> podling is open to new people, from the Incubator policy page - "new >> >>> committers are admitted according to ASF practices" - >> >>> >> http://incubator.apache.org/incubation/Incubation_Policy.html#Graduating+from+the+Incubator >> . >> >>> >> >> >> >> I'd turn that around and ask the community to ask themselves this >> >> question. Who do they want as a new committer? (keep in mind that >> >> discussion of personnel matters should typically be conducted on the >> >> private list). >> > >> > I haven't observed the degree of commitment I have observed when we >> invite new committers in other projects. At the same time, I have been >> seeing more messages flowing on the list, which is very positive. Perhaps >> in the near future we will have the opportunity to invite new committers. >> > >> >> >> >>>> 2) there have only been two releases. The second of which required 5 >> >>>> release candidates. >> >>>> >> >>> >> >>> Many podlings only do one release before graduating and that often >> >>> requires a few RCs. Looking back in the archives at the S4 RC votes i >> >>> think they will have learnt a lot about how to do releases from all >> >>> the respins. Also, some of these haven't been helped but the vagaries >> >>> of the Incubator release voting which will be avoided after >> >>> graduation. >> >> >> >> Absolutely. As I mentioned I think the community is doing fine. I >> >> wouldn't stand in the way of graduation if others were interested, I >> >> just don't personally think they are ready for the reasons I stated - >> >> hence why I haven't pushed for graduation. >> > >> > The release process doesn't concern me as much. It took this community a >> while to produce releases, but other than that I think they are quality >> releases. >> > >> >> I agree, the releases have been good. However IMO having multiple >> release candidates indicates that there were issues that everyone >> (PPMC) thought were fine, but still had to be addressed (based on >> further feedback from IPMC). I'm part of the PPMC and I missed some of >> those details, so it's not really a blame issue, but I'm just saying >> the process/content itself is still in flux. That will smooth out as >> folks get more experience and there's more visibility on the >> process/artifact. Good to have incubator insight during that process. >> >> > However preventing graduation till more incubating releases are done is > requiring a higher bar to graduation than what is required for other > podlings. Release voting in the Incubator is difficult and inconsistent, > lots of podling releases are made to do multiple respins but thats more a > problem with the incubator process not the podling.
I don't see is this as a quantity issue and as I said (see my comments earlier in the thread) I wouldn't prevent graduation if other folks were to push for it. Patrick
