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? Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
