>A common item I have read in various newsgroups for eclipse, is for the community to vote for a bug. If it gets enough votes, it’s more than likely to get addressed sooner rather than later. While I think this practice works in theory, I’m not necessarily convinced it’s working in reality.
The reality is that the items that the Adopters and the Foundation Members want, get higher precedence than those items that the community wants. Asking the community to vote for a bug doesn’t necessarily work, especially when a community member is limited on the number of votes they can have per project. Some projects have this set pretty high, others have it set very low. I’m not sure what the rational is on limiting the number of votes, but that is what community members have to live with.
So, just for fun, I took a look at the Web Tools Project, only because that is where I spend most of my time as both a community member and a committer on the XSL Tools project. I did a quick bugzilla search on all Non-Enhancement requests, that had votes. Here is the bug list.
There are a total of 191 open new, assigned, or reopened bugs that have at least 1 vote. Theoretically, with the way that WTP can crank out bug fixes at times, all 191 could possibly be fixed in one Milestone. Now that is only in theory, and it actually won’t happen.
The bigger question is do all the bugs with at least 1 vote, get higher precedence than bugs with no votes? How many votes does it take to get a bug noticed and on the radar to be fixed? Just curious how other projects are handling community related requests and prioritizing them compared to the Adopter and Foundation member requests? I would hope that all Adopter and Foundation member requests also go through bugzilla.