A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-November/094150.html below:

[Python-Dev] PyPI comments and ratings, *really*?

[Python-Dev] PyPI comments and ratings, *really*?Jacob Kaplan-Moss jacob at jacobian.org
Fri Nov 13 05:55:08 CET 2009
On Thu, Nov 12, 2009 at 5:41 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> Because I want to wait for the outcome of the poll first.

I'm curious: what criteria will you use to judge the outcome of the
poll? That is, how will you translate the results of the poll into
action? Right now, the results stand as

Allow ratings and comments on all packages (status quo) 13
Allow package owners to disallow comments (ratings unmodified). 17
Allow comments, but only send them to package owners (ratings
unmodified).      2
Disallow comments (ratings unmodified). 11
Disallow ratings and comments (status three months ago).        36

If the poll ended this moment, how would you judge? Would it just be
mob rule (no comments)? Or some sort of spectrum -- there's 32 for
comments in some capacity and 47 against, so does somehow translate to
ratings but not comments? Or a weighted average? The average is 3.51
(1 being "allow comments" and 5 being "no comments")... what does
*that* mean?

On a deeper level, why are we voting at all? When else in the history
of Python have we used popular vote to decide questions of this
nature?

Jacob

[Martin, sorry for the repeat; I sent this privately first by mistake.]
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4