Install VotePlugin to trac.openstreetmap.org #3972
Comments
|
Author: TomH No, absolutely not. It would be pointless - we don't have paid developers that we can order to work on particular things. We have volunteers who work on what they want to work on. End users saying that something is, in their opinion, important is not going to change that. |
|
Author: Kozuch You are not right. There might be a volunteer developer looking for a task to do. Today, there is only the "priority" field that can be used to assess how this or that bug might be important. The problem of this field is not a "crowdsourced" item, it simply has very little value for a new developer than a ticket with many votes from different people would have. Thus, I am reopening this ticket. I see now there probably is a "voting" feature in the latest version of Trac already incorporated (see http://trac-hacks.org/ticket/4447). If we have such version running, please enable voting. Thanks. |
|
Author: TomH Who are you to decide who is or isn't right? I've seen many bug tracking systems for open source projects which have voting. I've never seen one where the votes have any effect on anything other than to annoy the developers. This isn't going to happen, either as a builtin, or as a plugin, and no amount of you reopening this ticket is going to change that. |
|
Author: Kozuch
What an interesting question. Do YOU own the project? I would reply in a sence of this: http://en.wikipedia.org/wiki/Wikipedia:Ownership_of_articles This is not going to happen, because YOU decided so? Do you really think such an approach is correct? What about opinions of others? Approaches like this simply kill open source development... I am wondering you are not aware of it. |
|
Author: TomH The point is that it would have been reasonable to write "I think you are wrong because..." but it is not reasonable to write "You are not right" which is a flat out declaration that you have made the final determination on the matter. |
|
Author: Richard Kozuch: you have made exactly 20 edits to OSM and here you are telling people who have been involved in the project for years how to run it. Um, I don't think so. |
|
Author: Kozuch Do you measure quality of a contributor by number of edits? Do you refuse to take and advice from a newbie? This is the beginning of the end... |
|
Author: Richard Prove that you're worth listening to, and we'll listen to you. |
|
Author: Kozuch Can you list all your measures for being listened to then? Wikipedia struggles with editor retention becuase it matures - basic content was created already and thus low-hanging fruit was collected like this - now they struggle to raise participation, because it is much harder to contribute somehow. Their correct goal now is to have better demographics of contributors (engage more females for instance and basically reflect the demographics of general public distribution in the world). OSM will come to similar point sooner or later too, so listening what people say and not repell them is pretty much basic task to do within a project. There is a common problem of bugzillas (at Wikimedia and here too) that they require one to be quite technical savvy to file a reasonable ticket. If one does this already (or tries to do) the ticket is usually wontfixed within minutes and the person might never return like this. This is a way to hell, not only yours but Wikimedias also, at Wikimedia they are realizing it already and they started to take more care at least... |
|
Author: TomH The bug tracker is not the place to have a debate on how we get and retain contributors, that's for sure! The mailing lists would be an appropriate forum for such a debate, not that it has any relevance to this ticket that I can see. |
|
Author: Kozuch Any news here? |
Reporter: Kozuch
[Submitted to the original trac issue database at 9.49am, Sunday, 21st August 2011]
Please install VotePlugin (http://trac-hacks.org/wiki/VotePlugin) to this Trac so we can have users vote on tickets - to see which tickets should have higher priority. This will be better than individuals assessing the priority themselves.
The text was updated successfully, but these errors were encountered: