Re: loomio

[Sriram Ramkrishna <sri ramkrishna me>]

Well the non-coding parts might accept it.  The problem with voting is that it is an emotional choice when it comes to people who are voting and are not part of development.  Which can lead to all kinds of conflicts in trying to decide how things develop.

If we had voting, we would have had to revert everything and go back to GNOME 1.  While at the same time people will be voting to update everything.  It's just wrong.

But decision making for teams like marketing might work okay if we restrict to a particular set of people.  Kind of like having commit access, you get to vote when you put in the time.

On Wed, Apr 24, 2013 at 10:13 AM, Marco Scannadinari <marco scannadinari co uk> wrote:

        Hi, is there any progress with this?

        I there a Gnome team willing to be the "pioneer" and try loomio,
        and report about the experience? I don't belong to any team so I
        can't take responsibility personally (but I'll help you, if you
        decide to give loomio a try).

Unfortunately, it seems both the design-team and desktop-devel teams are
quite against the whole idea of loomio or any other community voting
system. Andre Klapper also posted a link [0] to a study which suggest
that commitee-oriented design processes aren't a good idea. I'm (and
probably not a lot of other people) are not in a position to argue or
disprove such a study, so, as much as I would like to see it be
implemented, I guess that's that...

[0] http://nat.org/blog/2006/02/dan-winship-on-design-by-committee/
--
Marco Scannadinari <marco scannadinari co uk>

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list