> This is another thing that troubles me when I read this list. How does the > PHP core dev community sets priorities?, is there some sort of roadmap?, is > there a process to create this roadmap?, or is it just all a generalized > best intention to do things. > > I'm aware that the more features the more has to be maintained, but, what I > see is that there is lot of potential for the core dev community to grow and > at its current state it doesn't seem to be able scale due to the lack of a > roadmap/process. > > I'm not trying to be a douche here, just saying: I see lots of criticism > towards everything and very few agreements. >
The roadmap is in the form of a feature list which you can find at wiki.php.net/etc There is never going to be complete agreement on any feature, but once there is enough agreement from the main stakeholders in a certain feature and the implementation looks feasible both from a technical perspective and from actually having someone willing to do the work, it gets assigned to a release. In the case of annotations there were some serious stakeholders, like Matthew, Sebastian and others who really do understand what annotations are and why they are needed, but they did not agree with the proposed approach. That's why we have the RFCs and that's why these discussions flare up around release time. It triggers people to take a really serious look at a feature to see how it would work for them. And yes there is a lot of noise. You will see quite a few uninformed opinions, and a few informed ones. We have always kept things completely open for anyone to have their say. This openness gives people access, but it also often gives people the sense that there is complete chaos. We are not .Net. -Rasmus
