Re: [Geotools-devel] What's the proper way to handle a -1 in a proposal?

[Andrea A. <aa...@op...>]

Andrea Aime ha scritto:
> Jody Garnett ha scritto:
>> Andrea Aime wrote:
>>> Hi,
>>>
>>> in the logging proposal we have a -1 vote. Ok, time to test
>>> the proposal procedures for this case too :)
>>>   
>> My understanding is that the person voting -1 is going to come up with a 
>> counter proposal. This
>> may take the form of revising your existing proposal, or may a clear 
>> alternative.
>>> What is the procedure to handle a -1? I kind of remember
>>> the concerns must be addressed if possible, and if not
>>> a second vote is required where the -1 is no more a blocker
>>> for the proposal provided it gets more positive votes...
>>> or something like that, but I can't find
>>> anything detailed in the wiki page:
>>> http://docs.codehaus.org/display/GEOT/GeoTools+change+proposal
>>>   
>> We had discussions to that effect yes; but I only ever managed to write  
>> a few things down
>> in the developers guide (and asked for a review).
>>> From the wiki page it seems a PMC member can veto any change
>>> without possibility for the rest of the PMC to make a proposal
>>> pass anyways. Is it so?
>>>   
>> I think the -1 acts as a veto; but there is an associated cost (a 
>> counter proposal).
> 
> Ok, so let's say Justin counter proposes to switch everything to
> commons logging and Martin counter vetoes that proposal (with
> the original one). Where do we end up?

Oh well, in any case just for the sake of completeness and
to follow the procedure to the letter, here is a possible counter
proposal based on Justin's ideas (Jody started it, I merely
completed the code example):
http://docs.codehaus.org/display/GEOTOOLS/Use+Commons+Logging

I guess the thing now is to vote on both proposals and update
the proposal guide so that it handles this situation too.
Cheers
Andrea