[OpenLayers-Dev] RFC: Resolution to only change License with
Unanimous Vote
Paul Spencer
pspencer at dmsolutions.ca
Tue Oct 9 13:50:56 EDT 2007
I'm ambivalent on this. I am not convinced that we need unanimity
(?) on any given issue, but I do think we need everyone to vote so
that we are certain there are no dissenting votes. I also think
there may be a certain amount of pressure felt by someone that they
have to vote with the rest of the PSC even though they are not
necessarily fully supportive (or even just ambivalent).
Discuss ... :)
Paul
On 9-Oct-07, at 1:02 PM, Christopher Schmidt wrote:
> The PSC voting rules currently state:
>
> "A proposal will be accepted if it receives +2 (including the
> proposer)
> and no vetos (-1)." -- http://trac.openlayers.org/wiki/
> SteeringCommittee
>
> For some large changes, this seems insufficent. In the past, I don't
> think we've ever made a single decision where unanimous voting *was
> not*
> available, but for some things, we should make it spelled out that
> these
> things can not be changed without a more complete vote.
>
> Specifically, this proposal is to change the Steering Committee voting
> rules such that no license changes can be enacted in the project
> without
> unanimous support for the change.
>
> (Hopefully, this won't really be relevant, becasue we shouldn't be
> changing the license again, but it's probably 'better to be safe than
> sorry'.)
>
> I'm +1 on altering the wording of the Steering Committee voting
> rules to
> state that any licensing changes require a unanimous vote from
> Steering
> Committee members.
>
> Regards,
> --
> Christopher Schmidt
> MetaCarta
> _______________________________________________
> Dev mailing list
> Dev at openlayers.org
> http://openlayers.org/mailman/listinfo/dev
+-----------------------------------------------------------------+
|Paul Spencer pspencer at dmsolutions.ca |
+-----------------------------------------------------------------+
|Chief Technology Officer |
|DM Solutions Group Inc http://www.dmsolutions.ca/ |
+-----------------------------------------------------------------+
More information about the Dev
mailing list