Minutes of the mozilla.org Staff Meeting of Wednesday 26th February 2003
Wednesday March 5th, 2003
The minutes of the mozilla.org staff meeting of Wednesday 26th February 2003 are now online. Issues discussed include Camino, the 1.3 final release, the 1.4 release cycle, the new roadmap, the next Phoenix release, the appointment of Marcia Knous as a mozilla.org Staff Associate Member, the new Mozilla MinGW port, mail about porting fixes to 1.0 branch and reorganisation of the mozilla.org front page navigation.
#39 Re: Re: Re: votes...
Friday March 7th, 2003 10:43 AM
You are replying to this message
If I'm some random open source developer wants to get involved with Mozilla, or if a regular Mozilla developer is looking for some new feature to work on, votes are a good place to see where he might get the most "fame" for the fix. Voting doesn't necessarily change the project priorities but it may influence individual prioroities of individual contributors and it may influence project management in some cases.
Right now there are 10 bugs with more than 50 votes. There are over 50 fixed bugs with more than 20 votes. There are about 150 fixed bugs that currently have more than 10 votes. Keep in mind that most people move their votes when a bug gets fixed so those are bugs where the votes haven't all already been moved and which probably had many more votes before they were fixed. To repeat, most of those bugs had lots more votes before the bug got fixed. Active voters tend to move all their votes to the next bug(s) they care about once a bug has been fixed.
Votes are probably not _the_ deciding factor for anyone evaluating a bug but they can be _a_ factor. Just as a nomination for fixing a bug by a particular milestonee isn't _the_ deciding factor for <firstname.lastname@example.org>, it is definitely _a_ deciding factor. Just as severity isn't _the_ deciding factor, etc., etc.
Lots of things are taken into consideration by the different people and groups that evaluate bugs for different reasons. Votes are payed some attention by some of the people making these evaluations. They are not "just a number that displays on the bug page."
Feel free to encourage people not to vote by telling them that votes are completely useless but know that you're misinforming them and potentially taking away one of their mechanisms for making their wishes known to <email@example.com> (since I'm a driver and I watch votes) and to the developers that do now or might in the future use votes to decide which feature to add or bug to fix next. Just because you think votes don't have enough weight doesn't mean that they don't have any weight.