Re: [Inkscape-devel] [bug tracker] Guideslines for tags?
-----Original Message----- From: suv@...2204... [mailto:suv@...2204...] On Behalf Of ~suv Sent: zondag 25 oktober 2009 21:35 To: Engelen, J.B.C. (Johan) Subject: Re: [Inkscape-devel] [bug tracker] Guideslines for tags?
On 25/10/09 21:11, J.B.C.Engelen@...1578... wrote:
From: Maximilian Albert [mailto:maximilian.albert@...1439...]
2009/10/25 Pajarico <pajarico@...400...>:
I started using the tag 'cli' for command line problems.
Wouldn't it be better to use a more descriptive name? Frankly, if I hadn't read this email I'd have no clue what it is supposed to mean.
I agree with Max. Just write it out "command line", like we do with the other tags. (I read it as "clear interrupts" assembly ;)
'command-line' or 'commandline' - Launchpad doesn't allow spaces in tags, and 'command' and 'line' don't make much sense as separate tags imho.
~suv
Maximilian Albert: I'm really surprised that you didn't know that 'cli' stood for 'command line interface'.
'command-line' or 'commandline' - Launchpad doesn't allow spaces in tags, and 'command' and 'line' don't make much sense as separate tags imho.
~suv
Exactly, that's why I choose 'cli' because it is really short and well known (at least I've been reading it for ages). The problem with 'command-line' or 'commandline' is that it is too long and I would have too write it entirely every time I want to add that tag, unless it's added to the official tags list. For example, starting typing 'node...' will suggest and autocomplete 'node-editing', which is kinda handy, but this mechanism doesn't kick in for unofficial tags (AFAIK).
If 'cli' is really that hard to understand, then suggest something else and add it to the official tags so it autocompletes. Already tagged bugs will be have to be changed, which brings to my memory a conversation I heard about managing simple bug tracking tasks with bots and scripts, is there any news about this? For example, is it possible to batch convert a tag into another?
Another tag I propose is 'boolops' for boolean operations related bugs (there quite a few). But there are also bugs related too Simplify, which technically is not a boolean operation, so I don't know if we should look for a better tag that includes about every node operation.
Best regards.
2009/10/26 Pajarico <pajarico@...400...>:
Maximilian Albert: I'm really surprised that you didn't know that 'cli' stood for 'command line interface'.
So am I. :-)
Exactly, that's why I choose 'cli' because it is really short and well known (at least I've been reading it for ages). The problem with 'command-line' or 'commandline' is that it is too long and I would have too write it entirely every time I want to add that tag, unless it's added to the official tags list. For example, starting typing 'node...' will suggest and autocomplete 'node-editing', which is kinda handy, but this mechanism doesn't kick in for unofficial tags (AFAIK).
Okay, I understand your concerns. On the other hand, what happens if a less experienced user or developer (or someone like me who simply doesn't know the abbreviation) is looking for command-line related bugs but can't find any because neither 'command' nor 'line' appears in any of the bug tags? I seem to remember that a similar thing happened to me a while ago but I don't recall what I was looking for. Anyway, is there a list of all existing tags available on Launchpad, apart from the tag cloud, which doesn't seem to be anywhere near complete (maybe I'm just too stupid to find it)? Perhaps we can also have a list of tags and their meanings on the wiki (or is there one already)? Although it's probably less useful if we can't link to it from Launchpad.
Max
On 26/10/09 17:21, Maximilian Albert wrote:
2009/10/26 Pajarico <pajarico@...400...>:
Exactly, that's why I choose 'cli' because it is really short and well known (at least I've been reading it for ages). The problem with 'command-line' or 'commandline' is that it is too long and I would have too write it entirely every time I want to add that tag, unless it's added to the official tags list. For example, starting typing 'node...' will suggest and autocomplete 'node-editing', which is kinda handy, but this mechanism doesn't kick in for unofficial tags (AFAIK).
Okay, I understand your concerns. On the other hand, what happens if a less experienced user or developer (or someone like me who simply doesn't know the abbreviation) is looking for command-line related bugs but can't find any because neither 'command' nor 'line' appears in any of the bug tags? I seem to remember that a similar thing happened to me a while ago but I don't recall what I was looking for. Anyway, is there a list of all existing tags available on Launchpad, apart from the tag cloud, which doesn't seem to be anywhere near complete (maybe I'm just too stupid to find it)? Perhaps we can also have a list of tags and their meanings on the wiki (or is there one already)? Although it's probably less useful if we can't link to it from Launchpad.
I put the one long list we had as cloud during a very short period of time on edge.launchpad.net (Launchpad 3.0 testversion) on my wiki page: http://wiki.inkscape.org/wiki/index.php/User:~suv#bug_tracker:_tags and try to keep an updated list extracted from the bug tracker e-mail notifications: http://wiki.inkscape.org/wiki/index.php/Extracted_bug_tags
So far no one seems to know who maintains the formerly displayed 'official' tags list that still is the underlying reference for the auto-complete of the tag entry field.
Then again there are different APIs available for Launchpad, vie e-mail or web, which maybe could be used to extract a complete list of tags (though none of them are advertized for this). But this is far beyond my current skills ;( https://help.launchpad.net/Bugs/EmailInterface https://help.launchpad.net/Bugs/PluginAPISpec
Please see the previous postings in this thread about other open questions. http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/31517
~suv
Max,
On the other hand, what happens if a less experienced user or developer (or someone like me who simply doesn't know the abbreviation) is looking for command-line related bugs but can't find any because neither 'command' nor 'line' appears in any of the bug tags?
Good point. Then I would prefer to use 'command-line' and add it to official tags for autocomplete.
I was thinking about preparing a table in the wiki with all the tags and the descriptions separated by categories, but suv, with the agility and efficiency he/she has accustomed us to, had already done it.
If suv allows me I would like to convert that to a table with better layout and a field for descriptions of each tag (maybe not every tag needs it, but some might), and a link to the tag in Launchpad.
So far no one seems to know who maintains the formerly displayed 'official' tags list that still is the underlying reference for the auto-complete of the tag entry field.
That still puzzles me.
Regards.
On 26/10/09 19:33, Pajarico wrote:
I was thinking about preparing a table in the wiki with all the tags and the descriptions separated by categories, but suv, with the agility and efficiency he/she has accustomed us to, had already done it.
...says pajarico who has updated thousands of un-tagged and mis-tagged bugs!
If suv allows me I would like to convert that to a table with better layout and a field for descriptions of each tag (maybe not every tag needs it, but some might), and a link to the tag in Launchpad.
Please - feel free to improve! I put it there just as reference for anyone interested until we have a better solution to the tag questions and didn't take the time yet to figure out the wiki syntax for tables... It would be great to have a separate 'Tags' page linked from the existing bug tracker and triage pages in the wiki.
On 26/10/09 18:25, ~suv wrote:
So far no one seems to know who maintains the formerly displayed 'official' tags list that still is the underlying reference for the auto-complete of the tag entry field.
That still puzzles me.
I will search the mailing list archives for older threads and report back if I can find any information about this.
~suv (aka V aka Véronique ;-)
I'm starting to figure something out...
* "Allow bug supervisors to make tags official" https://bugs.launchpad.net/malone/+bug/347218
It seems that someone with "launchpad.Edit" (whatever that is) has to move normal tags to official category.
On 26/10/09 20:39, Pajarico wrote:
- "Allow bug supervisors to make tags official"
https://bugs.launchpad.net/malone/+bug/347218
It seems that someone with "launchpad.Edit" (whatever that is) has to move normal tags to official category.
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. (https://launchpad.net/~inkscape.admin)
° inkscape-devel archive: about teams Subject: Launchpad Groups http://article.gmane.org/gmane.comp.graphics.inkscape.devel/23322 Subject: Launchpad team policy http://article.gmane.org/gmane.comp.graphics.inkscape.devel/23330
° Wiki page: I have moved the section 'bug tracker: tags' to a separate page: http://wiki.inkscape.org/wiki/index.php/BugTagsList so everyone should feel comfortable editing it as it's no longer part of my user page ;-)
° Bug tags: some threads when Inkscape moved the bug tracker from sf.net to launchpad: about tags Subject: Re: Bug trackers http://article.gmane.org/gmane.comp.graphics.inkscape.devel/23121 Subject: Launchpad Tips & Tricks: Tags http://article.gmane.org/gmane.comp.graphics.inkscape.devel/23327 Subject: Launchpad tags http://thread.gmane.org/gmane.comp.graphics.inkscape.devel/23403
I still plan to search for the tag list used on sf.net and migrated to launchpad (many of the compound tags like ui-* and objects-* seem to originate from the sourceforge bug tracker). Maybe I will add a summary to the wiki page if something useful can be gathered from the archives (thinking of categories/modules descriptions and previous guidelines about adding tags).
~suv
suv, you've been correcting my edits in the tag list with "~suv (nitpicking): still in use" but the fact is that if I go to this bug [1], where the tag 'style' is in use and I click on the tag I get an empty page with zero bugs [2]. What should I do? Using advance search finds bugs with that tag but going to [2] directly won't list anything.
[1] https://bugs.launchpad.net/inkscape/+bug/407893 [2] https://bugs.launchpad.net/inkscape/+bugs?field.tag=style
On 27/10/09 21:03, Pajarico wrote:
suv, you've been correcting my edits in the tag list with "~suv (nitpicking): still in use" but the fact is that if I go to this bug [1], where the tag 'style' is in use and I click on the tag I get an empty page with zero bugs [2]. What should I do? Using advance search finds bugs with that tag but going to [2] directly won't list anything.
The search interface of Launchpad doesn't make it easy for projects the size of Inkscape to manage the reported bugs imho.
Many recent and incoming reports are still based on Inkscape 0.46 (the current stable release), but all bugs with fixes committed to SVN/trunk have been marked 'Fix released' or sometimes 'Invalid' and thus don't appear in standard search results.
That's why I always start with the advanced search page with all 'status' and 'importance' fields checked and 'Hide duplicates' off when searching for related or duplicate reports. In this case I'm glad to restrict the search by relying on known tags ;-)
We need to decide whether we 'touch' reports marked 'Fix released' or 'Invalid' (there are others that also don't appear in the default search results but I haven't systematically tested which ones) when updating the tags or whether we just let the old tags in this partly hidden state and concentrate on the more recent ones. From my POV it makes sense to search _all_ reports when triaging bugs - that's why I added my 'nitpicking' comment. But I don't insist ;-)
~suv
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!). 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...). * 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). * 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.
Official tags (Dec. 3, 23:56)
* build 47 * crash 238 * exporting 183 * extensions-plugins 108 * fonts 111 * import-export 102 * linux 74 * livepatheffects 53 * node-editing 78 * osx 109 * pdf 103 * printing 65 * saving 62 * svg 104 * text 130 * transformations 96 * translation 39 * ui 489 * win32 172
Other tags
* 2geom 1 * 3d 2 * 3dbox 17 * 64-bit 2 * all-platforms 53 * amd64 2 * animation 8 * apport-bug 3 * apport-collected 2 * apport-crash 2 * autosave 7 * bidi 2 * bitmap 44 * blur 13 * bsd 1 * build-compile-code-design 13 * cairo 20 * calligraphy 4 * cjk 2 * cli 16 * clipboard 45 * clipping 17 * clones 21 * color 60 * connectors 14 * content 5 * css 4 * desktop-integration 10 * dia 1 * documentation 6 * dxf 5 * emf 14 * encoding 1 * eps 23 * eraser 15 * extensions 4 * filters-svg 65 * freehand 1 * fullscreen 4 * gnuplot 2 * gradient 22 * grids 16 * groups 17 * gsoc2009-color 4 * gtk-osx 6 * guides 22 * hpgl 3 * importing 86 * inkboard 4 * inkscape 1 * inkview 4 * java 4 * javafx 2 * latex 1 * layers 29 * licence 1 * link 3 * markers 14 * metadata 4 * needs-confirm-on-svn-head 1 * netbook 1 * object-shape 19 * object-text 24 * objects 35 * objects-freehand-calligraphic 12 * objects-gradients 5 * objects-markers 6 * objects-nodes 13 * objects-pattern 4 * ocal 5 * odg 4 * openclipart 2 * other 92 * packaging 39 * patch 3 * path 4 * pattern 23 * pen 1 * pencil 1 * performance 56 * perspective 2 * png 4 * poppler 1 * ps 3 * psfrag 1 * python 6 * regression 33 * renderer 41 * rulers 3 * shape-editing 88 * snapping 18 * soc-2008-juca 3 * solaris 3 * stroke 5 * styles 14 * svg-xml 12 * tablet 44 * tracing 5 * tutorials 8 * tweak 2 * ui-dialogs-toolbars 61 * ui-guide-grid-ruler 1 * ui-palette-color 16 * ui-preferences 15 * ui-preview 4 * ui-selection-group-layer 55 * ui-shortcuts 19 * ui-text 5 * undo 22 * ungroup 1 * uniconvertor 7 * usability 2 * viewbox 10 * website 9 * wiki 1 * win32-vista 7 * wmf 4 * x11 1 * xaml 7 * xcf 2 * xmleditor 8
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
Hi,
De : ~suv <suv-sf@...58...>
- 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.
I've moved some tags from the unofficial list to the official one: 3dbox, autosave, bitmap, boolops, cli, clipboard, clipping, clones, color, connectors, eraser, filters-svg, freehand, gradient, grids, groups, guides, importing, layers, markers, objects, packaging, pattern, performance, regression, renderer, shape-editing, snapping, spray, styles, tablet, undo, viewbox, website, xmleditor.
and I still hesitate to add the following tags: ui-preferences (after renaming it preferences?) ui-shortcuts (shortcuts?) openclipart (merged with ocal?) uniconvertor blur palette (new tag) dialogs (new tag) toolbars (new tag)
Only one move from official to unofficial: import-export. Even if this tag is present in lots of reports, I thing we should encourage bug reporters to use importing and exporting instead. And as for bug triage, the tag is not "dropped", it is just no longer official ;)
Don't hesitate to tell me if you think some other tags should be added, or if he list is too long (63 entries, including the 10 most used unofficial tags...).
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?
No, I think you're right! I almost always include closed bug (and sometimes even duplicates...) in my search.
Do you mind if I update the wiki page (new official list and some other suggestions)?
Regards, -- Nicolas
On 6/12/09 15:32, Nicolas Dufour wrote:
De : ~suv <suv-sf@...58...>
- 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.
I've moved some tags from the unofficial list to the official one: 3dbox, autosave, bitmap, boolops, cli, clipboard, clipping, clones, color, connectors, eraser, filters-svg, freehand, gradient, grids, groups, guides, importing, layers, markers, objects, packaging, pattern, performance, regression, renderer, shape-editing, snapping, spray, styles, tablet, undo, viewbox, website, xmleditor.
and I still hesitate to add the following tags: ui-preferences (after renaming it preferences?) ui-shortcuts (shortcuts?) openclipart (merged with ocal?) uniconvertor blur palette (new tag) dialogs (new tag) toolbars (new tag)
First off - I think that's a great improvement, both the dropdown list proposal when inline-editing the tags as well as the extended list now displayed as cloud.
official/unofficial tags list: - preferences: Proposing to add to official list.
- openclipart: Proposing to merge with 'ocal' and add 'openclipart' to official list.
- blur: I know it's in use (and I have added it too) but isn't this better covered by filters-svg (except if the bug is about the ui)? Hesitating to add to the official list.
- dialogs, shortcuts, toolbars, palette: proposing to keep in the unofficial list, and encourage the 'ui' tag to be used when filing new bugs. The component (dialog, toolbar...) could be added later if needed.
- uniconvertor: not an official tag for me (at least until it is clear how to deal with bugs in UniConvertor reported with Inkscape). The UniConvertor team still hasn't 'adopted' the launchpad project that was created _in_ their name but not _by_ them [1]. Until (# Bug tracker: None specified # Bug supervisor: None set # Security contact: None set ) are not changed it seems at least doubtful that linking the Inkscape UniConvertor bugs as 'Also affects project Uniconvertor' has any effect or helps them to get fixed in UniConvertor trunk.
Only one move from official to unofficial: import-export. Even if this tag is present in lots of reports, I thing we should encourage bug reporters to use importing and exporting instead. And as for bug triage, the tag is not "dropped", it is just no longer official ;)
Agreed.
Don't hesitate to tell me if you think some other tags should be added, or if he list is too long (63 entries, including the 10 most used unofficial tags...).
I still think we need a clearer framework for missing/new tags. So far we are only trying to deal with the tags accumulated over different bug tracker 'generations'. I am thinking of simple guidelines about - should every tool have its own tag? - should every object manipulation with a top-level menu entry in the 'Object' menu have its own tag? So far we use group, clipping, patterns, marker, guides, transformations. - should 'styles' include every style property that can be set in the fill&stroke dialog? what about blur, opacity? - should 'styles' include every text/font property that can be set on the controls bar and in the text&font dialog? - ...
I am missing tags for / guidelines how to handle - alignment (≠ snapping), (currently often tagged with 'transformations') - selection/bbox (currently 75 'ui-selection-group-layer' bugs) - there are a number of bugs (PDFs saved as SVG, SVGs from gnuplot) with font encoding issues that sometimes crash inkscape when loading the file. Should these get their own tag 'encoding' or is it well covered with 'text'?
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?
No, I think you're right! I almost always include closed bug (and sometimes even duplicates...) in my search.
Especially the duplicates often help to find a relevant report (due to the greater variety of summaries) - they are always 'un-hidden' in my searches too.
Do you mind if I update the wiki page (new official list and some other suggestions)?
No, of course not. It would be great if that page gets more collaborative input - admittedly I have neglected it since the discussion here stopped, only updating it once a week with newly used or removed tags and those uncovered in old reports.
~suv
[1] current 'UniConvertor in Launchpad' Maintainer: nitrofurano says: «Personally, i took the initiative on registering around 300 open-source projects in Launchpad - since i got both positive and negative reactions of this, and my only concern were the good will on helping on their popularity, and trying to avoid their becoming abandoned projects, i got very enthusiastic with it, and forgot to send mails for their main developers about it - if some problem happened, please contact me. (...)» https://edge.launchpad.net/~nitrofurano-3t
De : ~suv <suv-sf@...58...>
official/unofficial tags list:
- preferences: Proposing to add to official list.
- openclipart: Proposing to merge with 'ocal' and add 'openclipart' to official list.
Added.
- blur: I know it's in use (and I have added it too) but isn't this better covered by filters-svg
Yes, of course...
- dialogs, shortcuts, toolbars, palette: proposing to keep in the unofficial list, and encourage the 'ui' tag to be used when filing new bugs. The component (dialog, toolbar...) could be added later if needed.
- uniconvertor: not an official tag for me (at least until it is clear how to deal with bugs in UniConvertor reported with Inkscape).
Ok.
According to http://sk1project.org/forum/viewthread.php?thread_id=68, the SK1 project won't use Launchpad for bug management, but another tool, yet to be officially launched. Meanwhile I've added our UniConvertor bugs to their LP page so that we can easily link them (with remote watch)to the new tool as soon as it is available.
Regards, -- Nicolas
participants (6)
-
unknown＠example.com -
Jon Cruz -
Maximilian Albert -
Nicolas Dufour -
Pajarico -
~suv