Selon Tobias Rundström <t...@xmms.org>: > What do you all think?
I think that for the general XMMS2 development, a benevolent dictator (or two?) is the best way to go, possibly accompanied/challenged by a group of core devs. The development of major internal features is subject to too many constraints (who can work on it? does it depend on something else? is it hard? does it fit with the release schedule?) to be reduced to a popularity vote, in my opinion. That's why there are projects managers around the world, rather than project democracies. On the other hand, I believe it'd be a great approach to get user feedback and learn more about their wishes for things like new clients (even nycli, or the future GUI). It's dynamic and feature-level, much easier to get into than a bug tracker. I quite like http://getsatisfaction.com/ for this. We could even set it up for nycli now. Any more thoughts? -- Sebastien Cevey - inso.cc -- _______________________________________________ Xmms2-devel mailing list Xmms2-devel@lists.xmms.se http://lists.xmms.se/cgi-bin/mailman/listinfo/xmms2-devel
