> De : Dan Ackroyd [mailto:dan...@basereality.com] > > However I think there is a strong risk of people having to give a > reason why they voted no being abused, particularly if it is shown > while the voting was taking place, as people could be harassed for > choosing an 'invalid' reason to reject the RFC.
Some suggestions for a future hypothetical RFC software : - Individual votes are kept secret. Just make public the number of voters and overall result. Each voter sees its own vote. - Vote starts with RFC discussion. - A voter can modify its vote until vote closes. - Votes span a range from '-2' (completely disagree) to '+2' (fully agree). - A minimal number of voters (quorum) is required for an RFC to be approved. - and, most important, comments are stored with the RFC, and mirrored to the mailing list. Please comment. Even if we don't have it today, maybe we can agree on an objective for tomorrow. I was looking for such a software, as I thought such needs are very common among open source projects, but I didn't find anything convincing. The best solution I imagine would be github adding an optional voting feature to issues (would we need to restrict access to vote or would we accept anybody with a github account ?). Github issues already have almost everything we need, except voting. Cheers François -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
