I don't know who invented proposal system, but I dislike it.
Proposals votings and so-called "democratic system" is evil. If we
can't find a consensus then we are very bad team. I personally enjoy
solving phpdoc tasks and act on my own, but programming proposal for
my chaotic nature is not different from ordinary job, except that it
is my free time. IMHO a proof of concept and fix to recent commit in
many ways better than a good advice and appreciation of the work yet
undone.
I think you're looking at it the wrong way. There is no "forcing." The
doc team works very well together for the most part, and there's a lot
more respect than in many other technical circles, shown on this list.
We already vote demographically, sometimes. In fact, you're doing it in
this post with your "-1 I don't like it", and that's completely fine. We
also have a RFC directory in CVS that barely anyone looks at very often
(I'm guilty).
I look at the proposal system as a way to work ideas into a solution
that the majority (and sure, ideally everyone) can be happy with.
For example, I have a pseudo-proposal that I've been stalling on,
waiting for the RFC system. Philip also has one (that may have already
been adopted.. ?). http://wiki.phpdoc.info/RFC. My Nomenclature
proposal, for example, isn't something I want to work out on my own. I
don't want to say "Here are the rules. Follow them." I want us to come
to a concensus (as you put it) on the best practices. I think we can do
that.
Please don't look at it as "conflict" and "force", but as "problem" and
"possible solution."
S
