Voting mechnism is needed for xdg discussion.

[PCMan]

Agree. A bug tracker with voting support will be good.
However a forum is good, too.
Using mailing list is convenient, but it's hard to follow all the
issues in the mailing list.
Besides, you don't know how many people agree with it.
Without issue tracker, it's hard to know the current status of every
issues since the wiki page are usually out-of-date.

On Fri, Jun 5, 2009 at 10:14 PM, Joseph Krahn<joseph.krahn at gmail.com> wrote:
> On Fri, Jun 5, 2009 at 9:02 AM, PCMan<pcman.tw at gmail.com> wrote:
>> Hi all,
>> I'm lead developer of LXDE, a lightweight desktop environment
>> following xdg standards.
>> As everyone on  this mailing list knows, current desktop environments
>> have many long-standing issues
>> without consensus. All too often someone might have some proposals on
>> the mailing list, and gets
>> replies from several people, and then, the discussion just disappears.
>> The issues are still there.
>> Otherwise, there might be someone says "If there is no objection, I'll
>> add XXXX to the spec."
>> Later, maybe nobody noticed that issue, and the spec was changed silently.
>> Besides, if the original author of that spec doesn't agree the change,
>> no matter how many people want it, the spec won't be changed.
>> This is not a really good way to achieve the goal of xdg.
>> A more democratic and efficient way is hence needed.
>>
>> I propose setting up a voting mechanism for some unresolved issues.
>> A forum hosted on freedesktop.org or some other places is acceptable.
>>
>> For unresolved but critical issues, like naming of some icons in the
>> icon theme spec,
>> we can wait a period of time (maybe one week) and let the users
>> nominate possible options.
>> Then, a vote can be held, and the users on this mailing list can vote
>> on those issues.
> ...
>
>
> I am in favor of voting. My guess is that actual changes are mostly
> driven by the Gnome and KDE teams, so that issues that are not
> important to those systems go unresolved. It is hard to know the
> status of an issue without some sort of organization. In addition to
> suggestions and voting on ways to resolve issues, there needs to be
> some prioritization. Some form of bug-tracker would probably work, if
> it included some form of voting mechanism.
>
> Joe Krahn
>