On 06/04/14 12:48, Markus Neteler wrote:
PSC;
since the voting discussion is scattered around in various email
threads, I start a new one to separate it from ongoing motions. Please
re-express your comments as answer to this email.
RFC3: PSC Voting Procedures
http://grass.osgeo.org/programming7/rfc3_psc.html
Thank you for this revised version !
I agree with Madi on the way the delay is expressed.
I have two major remarks, though:
- We should define more clearly what should be subject to voting. At
this stage we only have this in the PSC guidelines:
"The following issue(s) must have a vote called before a decision is
reached:
Granting source code repository write access for new developers
Selection of a committee Chair
"
Maybe we need to amend this a bit in the light of the current votes
being put onto this list ?
- "Proposals are written up and submitted on the mailing list for
discussion. Any committee member may call a vote on any proposal,
although it is normal practice for the proposer to call the vote."
I would propose that in order to avoid vote inflation, any proposal
should be submitted by at least three members of the PSC, not just one.
This should ensure a bit of discussion and peer review before
submission, thus avoiding long debates on proposals that just are not
ripe for vote, yet.
Moritz
_______________________________________________
grass-psc mailing list
grass-psc@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-psc
