[Tracker-discuss] schema ideas

"Martin v. Löwis" martin at v.loewis.de
Mon Nov 13 23:24:45 CET 2006


Stefan Seefeld schrieb:
> * I'd like to add a 'severity'. A severity reflects the impact this
>   issue has on the user. The 'priority' is a ranking to be done by
>   developers, not users, and should be read-only for users.

This should come with precise guidelines of what value to use in what
cases. Users are unlikely to fill out such a field, even in presence
of clear guidelines (unless filling out the value is enforced, in which
case they will give each issue the highest possible severity).

> * Speaking of which, I'd like to know whether it wouldn't be meaningful
>   to introduce a 'Developer' role. I'm not familiar enough with python's
>   development model, but I'd expect it to allow the distinction between
>   'user' and 'developer'. For example, bugs can only be assigned to
>   developers, and certain changes can only be made by developers.

Currently, there is a group of people which are members of the SF python
project, and SF classifies them as "developers". Those are the ones that
bugs can be assigned to. By tradition, each of them has nearly full
access rights to the tracker, with the reasoning that they all have
(had) CVS commit access, which is a higher privilege. The only thing
they can't do is to change the "schema" (ie. the value list of
enumerated types, and the creation of new trackers); you have to be
admin to do that.

Of these developers, some only ever get assigned issues (and never
triage themselves), some others do triage. We currently make no
distinction between these groups.

Regards,
Martin


More information about the Tracker-discuss mailing list