hi, On Mon, Sep 17, 2012 at 5:36 PM, Johannes Schlüter <johan...@schlueters.de> wrote:
> There are very few special processes. In fact the only RM-specific > things are around packaging the tarballs up, while that's described in > an README. Besides that all processes affect everybody in the community > and everybody should be aware of it. The RM simply is the last instance > to identify/judge if things are unclear. the requirements for that are > a) knowing the code quite well b) knowing whom to ask for a given issue. > both things are good qualifications for *any* contributor. > > In my mail I also suggested to "train" a successor later in the game. > Nowadays,thanks to all the RFCs and so on, the role of the RM is on the > one hand very limited and on the other hand requires maing clear > decisions. And well, two persons give two clear decisions or increase > workload for themselves (due to extra coordination) and everybody else > (for having two guys to follow) That's where you see it wrong. There is only one team to follow, not two guys. The RMs have regular contacts, approve together important changes (aka no one liner or similar), etc. They are also more keen to get a better judgment than a single person (different views, etc.). There is no extra work load, only benefits. Also seeing what happened with the latest 5.3, I wonder if we should not have two again for 5.3 as well (kidding but.. ;-). Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
