[Tracker-discuss] schema ideas

[Brett Cannon]

On 11/13/06, Stefan Seefeld <seefeld at sympatico.ca> wrote:
>
> I'm looking at the current schema, and I have several related
> questions / suggestions.
>
> First, I'd like to suggest that we generate some clickable schema
> diagram as part of the tracker help that will assist users to
> find their way around the tracker.
> (I once contributed a script that generates diagrams from a
> roundup schema automatically, but looking at the result I find
> it rather useless. I attach the generated diagram for the current
> schema anyways...)
>
> What I have in mind is something like what I used in the (now mostly
> defunct) Fresco tracker: http://issues.fresco.org/reports/schema.html
> This schema could pop up in a help window. It lets you click on individual
> items, displaying the available values for each property, with short
> descriptions.
>
> What this display does not capture is the life-cycle of an issue, for
> example, what status changes are expected / possible. These things
> are captured by roundup's detectors, and thus can't easily be extracted
> automatically. Yet I believe it would be very valuable to have that
> captured in a diagram, too.
>
> Now for some actual points related to the schema:
>
> * I'd like to rename 'issue' to 'bug' to make room for other issue
>   types in the future.
>
> * 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.
>
> * 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.


For this dicussion I am going to need to pull in some python-dev folk to
help figure out exactly where we want to go with all of this.  I was holding
off on this until we were at the point to discuss this.  But if you guys
want to start this discussion let me know and I will start to get people
over here to help contribute to the python-dev perspective since we are not
going to mirror SF.

-Brett

As soon as we are ready to instantiate the 'real' tracker, I'd like
> to adjust the schema accordingly, add some default initialization data
> to initial_data.py, and start working on the help system. That will help
> us understand the tracker schema and behavior better while we discuss
> subsequent changes.
>
> Comments ?
>
> Regards,
>                 Stefan
>
>
> --
>
>       ...ich hab' noch einen Koffer in Berlin...
>
>
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20061113/33da4d9b/attachment.htm