Sorting out upstream and project bugtrackers

[Mark Shuttleworth]

Christian Robottom Reis wrote:
>       This would the product to select between three different options:
>
>         ( ) This product uses Malone officially
>         (*) This product uses [ Ping dynasty Bugzilla | v] 
>         ( ) This product doesn't use a bugtracker 
>
>       And, if the product had a project related to it, the last option would
>       read something like:
>
>         ( ) This product uses the GNOME Project Bugzilla
>             (defined in the GNOME Project)
>   

Rather, I would suggest going with freeform associations. You already
have ProjectBugtracker, I would add to that ProductBugtracker and
DistributionBugtracker. These just link that Pillar to the bugtracker.

This could result in multiple bugtrackers for a product, and in addition
a project bug tracker. So you end up with a "set of likely bugtrackers"
for any give product.

The bugtracker selection widget can then display the set of likely
bugtrackers, and give the option to select another one (using a general
search process).

I don't like the slightly arbitrary use of a single canonical one per
product, the reality is that things are likely to be a bit fuzzy, so a
given bugtask should be able to be linked to a watch on any tracker. All
you are trying to do is make the selection optimal by hinting at the
most likely appropriate ones for a give bugtask.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/launchpad-users/attachments/20060817/beabd1d8/attachment.htm