On 4/12/09 00:21, Nicolas Dufour wrote:
De : ~suv <suv-sf@...58...>
AFAIU 'launchpad.Edit' is a privilege or user right for the database and it seems that Inkscape administrators do have this access level to edit the project website. ()
Now that I'm in the Inkscape administrators group (thanks Bryce!), I have access to the tags list (with count!).
congrats! :)
Some suggestions (already partially discussed about two months ago):
- multi-word tags should be simplified, or grouped with several existing one-word tags (ie: objects-markers -> markers; ui-guide-grid-rulers -> ui and guide, or ui and grid...).
This would involve a great amount of reports to have their tags renamed: many bugs from a certain period (range of bug numbers) from the sf bug tracker have very consistently used this tag naming scheme (see also my notes below about the number count in the Launchpad tags list).
Unfortunately the multi-word tags don't work well with the search options current Launchpad versions offer: no search for partial strings in tag names :(
ATM it would make bug triage easier if all tags were single-worded and could be used cumulatively in the advanced search page to refine or narrow down search results - but I am still hoping that the search engine of Launchpad will improve and offer far more options in the future (search in bug comments, in attachments, for attachments by name etc., more 'exclude' options like 'doesn't contain $string', ...).
- special case: import-export. Should we get rid of it and use only exporting or importing tags instead (both if the bug affects importing and exporting).
It is a dilemma :) At the moment I am adding one of 'importing' or 'exporting' whenever I encounter a bug tagged 'import-export' if the issue is limited to either one of them. The tag 'import-export' can't be replaced e.g. by a script or e-mail command because one would have to decide for each report individually. OTOH dropping the more narrowing 'importing' and 'exporting' tags and replace them overall with 'import-export' reduces a reliable search criteria for an advanced search ('exporting eps' [x] all) or ('crash importing pdf' [x] all). And adding all of them ('exporting import-export importing') e.g. for RFEs to support of a new file format (like GSD or PES) seems 'over-tagged'
I don't know what would be best.
- the official list is far too restrictive, and some more tags (at least those related to the main features/objects/actions/..., or the more useful ones) would greatly improve bug management.
agreed.
Official tags (Dec. 3, 23:56)
<snip>
Other tags
<snip>
Thanks for keeping us up-to-date with the list. My only issue I have with what Launchpad offers here:
The list (and number count) doesn't included tags from reports marked 'Invalid' or 'Fix Released'. In my recent experience, the search for earlier reports about related or identical (duplicate) issues gives better results when including all types of 'Status' via 'Advanced Search' since many bugs are either reported based on older Inkscape versions, have been fixed in the trunk since the last released version or have been confirmed and marked e.g. 'Invalid' because they are upstream issues or in conflict to the SVG specs. In all these cases reports that Launchpad excludes from its default search results are still relevant for bug triage imho.
I am trying to keep the list in the wiki [1] updated with any tags I find in older reports that are not included in the Launchpad list but still in the bug database for Inkscape.
How should we handle this? Is my perception wrong and closed bugs (invalid, won't fix, fix released) are indeed no longer relevant?
~suv
[1] http://wiki.inkscape.org/wiki/index.php/List_of_Launchpad_bug_tags