I really won't make it long, but with another person to give final decisions the RTBC queues would deplete faster, the workload on Dries would lessen, the patches going in to core would almost double, and everything will be swell for everyone.
<br><br>Real leaders delegate and I have faith that Dries has or will in fact do that when he finds someone who can share this load. Unfortunately, Dries is the current bottleneck, not because he's not doing a splendid job but because he's a human who can't take the load no matter how hard he tries to prioritize.
<br><br>Dries, why don't you choose a person and hold the right to revoke that authority from him if he goes off track? You'll really have to choose wisely but you will speed things by about the double. And just keep a close eye on him or any complaints that you may get.
<br><br>If this doesn't sound convincing enough then just imagine how things will become once the core developers double in number! Without a sub-Dries things will look twice as bad for core developers as they are now. This is flagging a warning that we should heed.
<br><br><div><span class="gmail_quote">On 7/1/07, <b class="gmail_sendername">Fernando Silva</b> <<a href="mailto:fsilva.pt@gmail.com">fsilva.pt@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 7/1/07, Chad Phillips -- Apartment Lines <<a href="mailto:chad@apartmentlines.com">chad@apartmentlines.com</a>> wrote:<br>> Nedjo wrote:<br>><br>>> There are very few members of our community who consistently meet these
<br>>> measures. Dries is one of them, and Drupal's success is due insignificant<br>>> measure to that fact.<br>><br>> i agree. but let me suggest that there's a bit of a self-fulfilling<br>> prophecy going on here. i think more members of the community could
<br>> meet the measures you outlined, if they were given the chance to<br>> assume the responsibility, make some mistakes, and learn.<br><br>Just to name a few:<br>* more chx involvement<br>* Bčr being taken more seriously
<br>* more support for decision made by robertDouglass and Kjartan<br><br>Anyway, the problem taking more people into core development is that<br>there is not a "clear roadmap" to accept new core developers. The
<br>current situation can be resumed in some steps:<br>* a developer starts using and developing drupal<br>* until that developer makes some real good module (that should be in<br>core) or "extraordinary something" it will not be "accepted" into core
<br>even if he lives to patch bugs<br>* after acception based in meritocracy, there exists a small democracy<br>based on "influence"<br>* finally there is a monarchy to "rule them all"<br><br>These are the facts and, before anything else, one thing must be said:
<br>in this exact moment Drupal lives well, has fantastic developers and a<br>guy that knows how to rule.<br><br>So where is the problem? Nowhere! There is no problem... yet. And is<br>this small "yet" that should make some of the more influent guys
<br>around here think about.<br><br>Will Drupal community wait for a real problem, to solve it, or prepare<br>the vaccine before the disease comes?<br></blockquote></div><br>