Edward, You are correct. Actually a -1 indicates a need for discussion (-1 because ...) which can have the outcome go or not to go. This is at least my experience.
--Stephan On 05.03.14 00:41, "Eduard Koller (MS OPEN TECH)" <[email protected]> wrote: > >> "For example a release requires at least 3 positive binding votes and >>no -1 vote." > >It is my understanding that only code contributions are vetoeable (and >even then only with a strong supported technical argument) > >According to the ASF requirements [1] releases may not be vetoed - that >is, they can go on with -1 votes, there just need to be at least 3 >positive votes and there must be more positive than negative votes. > >--Eduard > >[1] http://apache.org/dev/release.html#approving-a-release >[2] http://www.apache.org/foundation/voting.html > > > >-----Original Message----- >From: Klevenz, Stephan [mailto:[email protected]] >Sent: Tuesday, March 4, 2014 12:24 AM >To: [email protected] >Subject: Re: Proposal for Resolution > >About PMC have a look here: > >https://www.apache.org/dev/pmc.html > >In a very short form, a PMC member has a binding vote. For example a >release requires at least 3 positive binding votes and no -1 vote. >Committers can vote as well but their vote is not binding. > >About mentioning data.js in resolution. It is mentioned with "client". >Description and scope is a very short form, not so much details. > >-- Stephan > > >On 04.03.14 07:32, "Challen He" <[email protected]> wrote: > >>Should datajs be mentioned as part of the project? by the way, what >>does it take to be a project member? >> >>Thanks,-Challen >> >>-----Original Message----- >>From: Dave Fisher [mailto:[email protected]] >>Sent: 2014年3月3日 4:07 >>To: [email protected] >>Subject: Re: Proposal for Resolution >> >>+1. >> >>On Feb 28, 2014, at 3:58 AM, Bolz, Michael wrote: >> >>> Hi, >>> >>> From me +1 to resolution and proposed DESCRIPTION-AND-SCOPE = >>> "providing an implemention of the OASIS OData (Open Data Protocol) >>> specifications, in server and client form²; >>> >>> Kind regards, >>> Michael >>> >>> >>> >>> >>> >>> On 28/02/14 10:38, "Klevenz, Stephan" <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> Below you can find the first proposal for resolution to graduate >>>> Apache Olingo. The original template can be found here [1] and it is >>>> the template for graduation to a top level project. >>>> I have filled in initial PMC members as a result of feedback from >>>> private list. I have named me as VP and I have already replaced the >>>> project label with "Olingo" or "Apache Olingo". >>>> >>>> There is one label left which is ${DESCRIPTION-AND-SCOPE}. Here I >>>> would like to propose the following sentence: "providing an >>>> implemention of the OASIS OData (Open Data Protocol) specifications, >>>> in server and client form" >>>> >>>> Please reply to provide your feedback. The next step will be to have >>>> a community vote on the final resolution. >>>> >>>> - Stephan >>>> >>>> [1] >>>> https://svn.apache.org/repos/private/committers/board/templates/podl >>>> i >>>> ng-tl >>>> p-resolution.txt >>>> >>>> ## Resolution to create a TLP from graduating Incubator podling >>>> >>>> X. Establish the Apache Olingo 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, for distribution at no charge to >>>> the public, related to ${DESCRIPTION-AND-SCOPE}. >>>> >>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management >>>> Committee (PMC), to be known as the "Apache Olingo Project", >>>> be and hereby is established pursuant to Bylaws of the >>>> Foundation; and be it further >>>> >>>> RESOLVED, that the Apache Olingo Project be and hereby is >>>> responsible for the creation and maintenance of software >>>> related to ${DESCRIPTION-AND-SCOPE}; >>>> and be it further >>>> >>>> RESOLVED, that the office of "Vice President, Olingo" 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 Olingo Project, and to have primary responsibility >>>> for management of the projects within the scope of >>>> responsibility of the Apache Olingo 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 Olingo Project: >>>> >>>> * Florian Mueller <[email protected]> >>>> * Dave Fisher <[email protected]> >>>> * Christian Amend <[email protected]> >>>> * Francesco Chicchiriccò <[email protected]> >>>> * Jens Huesken <[email protected]> >>>> * Michael Bolz <[email protected]> >>>> * Stephan Klevenz <[email protected]> >>>> * Tamara Boehm <[email protected]> >>>> >>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Stephan Klevenz >>>> be appointed to the office of Vice President, Olingo, 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 Olingo 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 Olingo Project; and be it further >>>> >>>> RESOLVED, that the Apache Olingo Project be and hereby >>>> is tasked with the migration and rationalization of the Apache >>>> Incubator Olingo podling; and be it further >>>> >>>> RESOLVED, that all responsibilities pertaining to the Apache >>>> Incubator Olingo podling encumbered upon the Apache Incubator >>>> Project are hereafter discharged. >>>> >>>> >>>> >> >
