I just want to comment on one of the points: > Maybe we could define different type of votes (language syntax change, adding > new feature/extensions, etc.) and define the who can vote for each of those. > * This could be a good middle-ground between allowing qa/documentation/web > people to vote on language level RFCs or not. I think that this isn't a good idea. The main reason for a [php-src] vs. [php-doc et al.] distinction is that the php-src guys will be the ones maintaining the code. (At least from what I heard this is the main point.) I think this isn't a good argument. I would actually argue that most, even minor, code changes cause much more work for documentation than for core developers. Especially if you consider that every change needs to be translated into quite a number of different languages (and translation queues are looooong).
So: I would opt for keeping this point as is: Everyone with some sort of svn access should be able to vote. Nikita On Wed, Nov 9, 2011 at 9:07 AM, Ferenc Kovacs <tyr...@gmail.com> wrote: > Hi. > > As it was brought up recently that who can vote, and how are the community > representatives granted with voting rights, I created an RFC draft for > defining that- > Please feel free to discuss and extend it. > https://wiki.php.net/rfc/voting_who > > ps: it is really just a draft put together in like 5 minutes, and mainly > because I don't have the right answers, I hope that we can figure it out. > > -- > Ferenc Kovács > @Tyr43l - http://tyrael.hu > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
