On 24/9/09 18:35, Pajarico wrote:
- I searched for tags with the wildcard -*, which means "search for
bugs without tags". Turns out there are 1032, many of them recent. I think these should be tagged because right now they're in no man's land. The number of 'pdf', 'ui', 'livepatheffects'... tagged bugs might grow considerably.
As you mention 'pdf':
question about _filetypes_: should we use the file extensions as tags or delete them in general and only keep an agreed-upon subset of major ones like 'pdf' and 'eps' ('ps')? At the moment I'd favour to always add them as separate tag when relevant.
question about importing/exporting/import-export and _extensions/plugins_: many of the import-export bug reports are related to (python) extensions or their helper applications - how to tag these bugs? Always add both im/ex and ext-pl plus the filetype?
[ Background of above questions: there have recently been several (?) bug reports about importing failures (cdr, 0.47pre) that are really _UniConverter_ bugs. On windows, UniConverter is part of the Inkscape package - who is now responsible for handling the bug reports? How to tag them? ]
BTW, Launchpad was updated yesterday and the tag cloud is showing for everyone but, where are the official tags?
The criteria for a tag to appear in the cloud remain mysterious ;-)
From looking at google search results for launchpad bugs I gather that
previous Launchpad versions did allow to search for partial tags like 'ui-*' or 'objects-*'. These kind of queries are not possible with the current Launchpad 3.0 advanced bug search (at least I could not figure out how ;-). AFAIU that means that only _fully known_ tags are now useful for bug management. It would be convenient if we had a way to query the launchpad inkscape bug database for all used tags and keep an updated list as reference somewhere on launchpad or the wiki.
Does anybody from the Inkscape bug team have more insight what is/isn't possible within the (somewhat) limited tools Launchpad 3.0 offers for the bug tracker? (yes, I'm critical because I don't understand their priorities for launching v3.0 with gimmicks like in-page-editing of summary etc. but at the same time removing tools like 'bug activity' - at least I can't find it anymore. Do members of the bug team have a different set of tools when logged in?)
~suv