Jonas Borgström kirjoitti: > Noah Kantrowitz wrote: >> >> On Jun 23, 2008, at 1:13 PM, Alec Thomas wrote: >> >>> 2008/6/24 Scott Bussinger <[EMAIL PROTECTED]>: >>>>> Christian has made a very useful report on the popular tickets: >>>>> http://trac.edgewall.org/report/32 >>>> This _is_ an interesting report. To make it truly useful though I >>>> think would require two things: >>>> >>>> 1) Explicitly stating that development on the project is going to be >>>> at least partially guided by the number of people who "vote" for a >>>> feature request by entering themselves in the CC field. >>>> >>>> >>>> 2) A definite show of support from the active developers on the >>>> project to actually implement some of the popular features requested >>>> (either in the core or as a supported plugin). >>> I agree 100%. I think we need to shift to a model of actively trying >>> to >>> implement features users want. Workflow is a good example of this, but >>> we need to continue. > > Ok, so you're saying that we currently focusing on unwanted features? ;)
Well maybe one of the reasons here is very very long release cycle between 0.10.4 and 0.11. It really feels... focusing somewhere else... :D > Seriously though. "Voting" and other forms of feature popularity > indicators are good tools that we probably should use more. > > But we also need to remember that even if somehow half the internet > voted on a particular feature doesn't automatically mean it's a good > candidate to include in the next release or at all. How about going middle way like we do in our business environment - before every release we have community meeting where we propose set of features for our product. There usually is one or two that we think is "essential" and it will be included anyway. Then there is small set (usually five) of possible candidates to vote for 2 or 3 of them _will_ get on release. Leftovers are kept in case someone really wants them and we will sell it for extra money. >> Can we install VotePlugin on t.e.o? I have a report to do summaries >> using that instead and it might be clearer to people that those >> numbers matter. > > Sure, why not it's a lot better than abusing the cc field. Is it > possible to configure it to give each user (or email) a limited number > of votes? I think you'll give your decisions a bit more thought if you > know you can only vote on 5-10 tickets at a time. IIRC bugzilla has (at least somewhere I've seen) this kind of "top 5 of my issues" implementation. There you can have always 5 issues open and based on that you might get your issue implemented - or not. But this kind of voting system requires some more strict login system and user accounting. -- Jani Tiainen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
