I don't think this is prudent, having only one binding vote is too low a check. We at the ASF have a responsibility to the public. I want to be certain that no one steam rolls the process. Just the fact that there are edge cases means we need to be careful.
Regards, Dave Sent from my iPhone On Nov 10, 2013, at 4:04 AM, ant elder <ant.el...@gmail.com> wrote: > How about simply changing the rules for Incubator releases so that > they don't require at least three binding votes, but instead make it > at least three votes only one of which must be binding. That would > mean there would still be the element of oversight that a mentor vote > gives but avoids all the problems with not having three mentors. I'm > sure the board would grant the Incubator authority to implement that > change. > > ...ant > > On Sun, Nov 10, 2013 at 8:00 AM, Alex Harui <aha...@adobe.com> wrote: >> IMO, there are two problems: >> >> 1) We're trying to train folks to manage IP for their community but they >> have to seek approval from folks are aren't as vested in their community. >> My analogy is telling a new city council member: "Welcome to the city >> council. For the next year all of your decisions will require >> ratification by 3 state senators". >> >> 2) Release voting takes a long time. It would seem like tools should be >> able to reduce the time on several of the steps, except for this one from >> [1] "compile it as provided, and test the resulting executable on their >> own platform". >> >> Sometimes I think about trying to get on the IPMC and helping some podling >> get a release out but: >> A) Really, I just want to help check the legal aspects of a podling's >> release and don't have bandwidth to want to take on the other roles >> implied by being on the IPMC. >> B) I don't want to take the time to figure out how to build and test a >> release that I have no vested interest in. >> >> Now, incubating releases are not official releases, right? So why have >> such time- consuming requirements to get approval from the IPMC? Let's >> assume that the podling folks tested the building and operation of the >> source package. Could we build an ant script that any IPMC member or any >> PMC member from any TLP (to expand the pool of potential helpers to folks >> who supposedly know how) can run just to check: >> >> 1) source package has the name "incubating" --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
