Mailinglist Archive: opensuse-project (783 mails)

< Previous Next >
Re: [opensuse-project] Decision making for the distribution
  • From: Lars Marowsky-Bree <lmb@xxxxxxx>
  • Date: Tue, 4 Aug 2009 15:14:31 +0200
  • Message-id: <20090804131431.GH8816@xxxxxxx>
On 2009-08-04T09:58:37, Druid <marcio.ferreira@xxxxxxxxx> wrote:

I dont think voting works. Maybe the decision should be made by a
technical commitee, or the release manager, or the board, I dont know.
But wide vote I dont believe it works at all.

This is quite opposite to the literature, by the way. Decision-markets,
through polling a large audience and aggregating the results, deliver
excellent and empirically sound feedback on the usefulness of features.
They're an excellent and open way of gathering "market research" data.
Compared to focus groups or expert panels, they have a pretty good
accuracy, are cheaper to setup, and by definition "more open".

Of course, you must describe them properly (ie, use case/benefit, not
the detailed technical specification) - users are the wrong group to
vote on the _implementation_, but the only group that can reliably vote
on the usefulness.

Now it's true that some aspects of voting in bugzilla aren't appropriate
for this - for example, decision markets try to avoid feedback loops, so
the votes from other users shouldn't necessarily be exposed, but those
are more or less implementation details.

I can dig out some references in case someone is really interested.

But "expert judgment", in particular if it is only one expert, has -
both for market research and effort estimation, by the way - an
extremely bad track record, yet it often is the best (-> only) tool we
have, which is somewhat of a pity.


Regards,
Lars

--
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups