<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
Humm FYI, vote-for-fix and pay-for-fix systems could be worked
essentially for individuals but certainly not for businesses and
public organizations which have a strict accounting process.
Moreover these systems tend to over represent individual needs
because one professional TB admin can represent hundreds and even
sometimes dozens of thousands users.<br>
<br>
AFAIK, in term of number of users, Thunderbird has about 20 million
users and some Mozilla sources say only 7 or 8 millions are
individual users. So I guess the 12 other millions represent the
professional users.<br>
<br>
<div class="moz-cite-prefix">Le 12/07/2012 11:48, Tanstaafl a
écrit :<br>
</div>
<blockquote cite="mid:4FFE9D6C.6040908@libertytrek.org" type="cite">On
2012-07-11 6:41 PM, Axel <a class="moz-txt-link-rfc2396E" href="mailto:axel.grude@googlemail.com"><axel.grude@googlemail.com></a> wrote:
<br>
<blockquote type="cite">
<blockquote type="cite">My term "vouching" was meant to
represent the process of selecting
<br>
which bugs you think need fixing, and adding your "voucher" to
some
<br>
number of those. I meant it as a plural term for the noun
"vote".
<br>
</blockquote>
</blockquote>
<br>
<blockquote type="cite">exactly, shouldn't the bug votes somehow
be accounted for when
<br>
prioritizing them? guess we will need some sort of committee to
decide
<br>
which bugs are really important.
<br>
</blockquote>
<br>
If Thunderbird is going to become more community driven/oriented,
then indeed votes should count more... they shouldn't be the only
factor, but they should definitely matter. The problem is the flip
side - since the development is community driven/volunteer, there
is no way (nor should there be) to force any developer to work on
any given bug...
<br>
<br>
This is another reason why I am in favor of some kind of bounty
system. It is a way for 'voters' to put their money where their
mouth is - and, it is a simple and meaningful way for the
devs/maintainers to deflect criticism of bugs not getting fixed -
ie, "you want it fixed? put up or shut up! <link to bounty
system>". Also, if such a system is put in place, there needs
to be a way to identify pledgers, so if they don't follow through
on their pledges, this fact should be publicized prominently (to
hopefully shame them into making good on it), as well as to be
able to show public appreciation once they do.
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Laurent BAUVENS
Citation du jour :
> Loi Zéro : Un robot ne peut nuire à l'humanité ni, restant passif,
> permettre que l'humanité souffre d'un mal. - Isaac Asimov
</pre>
<br>
<br>
<DIV><P><HR>
*****************************************************<BR>
"Le contenu de ce courriel et ses eventuelles pièces jointes sont confidentiels. Ils s'adressent exclusivement à la personne destinataire. Si cet envoi ne vous est pas destiné, ou si vous l'avez reçu par erreur, et afin de ne pas violer le secret des correspondances, vous ne devez pas le transmettre à d'autres personnes ni le reproduire. Merci de le renvoyer à l'émetteur et de le détruire.<BR>
<BR>
Attention : L'Organisme de l'émetteur du message ne pourra être tenu responsable de l'altération du présent courriel. Il appartient au destinataire de vérifier que les messages et pièces jointes reçus ne contiennent pas de virus. Les opinions contenues dans ce courriel et ses éventuelles pièces jointes sont celles de l'émetteur. Elles ne reflètent pas la position de l'Organisme sauf s'il en est disposé autrement dans le présent courriel."<BR>
******************************************************<BR>
</P></DIV>
</body>
</html>