[Python-Dev] API refactoring tracker field for Python4

Antoine Pitrou solipsis at pitrou.net
Fri Jan 7 20:18:11 CET 2011

On Fri, 7 Jan 2011 11:11:47 -0800
Guido van Rossum <guido at python.org> wrote:

> On Fri, Jan 7, 2011 at 10:36 AM, Alexander Belopolsky
> <alexander.belopolsky at gmail.com> wrote:
> > -1 on the "star system" for the tracker
> The tracker on Google Code uses stars. We use this tracker to track
> external App Engine issues. It works very well to measure how
> widespread a particular issue or need is (even if we don't always fix
> the highest-star issues first -- the top issues are "unfixable" like
> PHP support :-).
> Maybe it works because in that tracker, a star means you get emailed
> when the issue is updated; this makes people think twice before
> frivolously adding a star. This is not quite the same as the "nosy"
> list: adding a star is less work in the UI, you don't have to think up
> something meaningful to say, and no email is generated merely because
> someone adds or removes a star.

I'd also mention that many bugzilla installs have a "voting" facility
where people can vote for a limited number of issues of their choice (I
think the number of votes also depends on the user's number of
contributions, although I'm not sure).



More information about the Python-Dev mailing list