~suv: I haven't forgotten about your reply, I didn't have time to think about it.
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.
I think we should use the major ones. But then there are tags like 'javafx' (1 bug only), what to do with those??. There was 'cdr' too (it is part of UniConvertor, not Inkscape). Let's leave UniConvertor formats (like cdr) to the tag 'uniconvertor'. The problem that might happen is when a bug is not in uniconvertor but in the extension that manages it. In that case we could use tags 'extensions-plugins' (or 'import-export'/'exporting'/'importing', see next point).
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?
I always use 'extensions-plugins' for bugs related to the Extensions menu only. I see your point since some file filters are based on python proxy scripts. Which is better?: * Use 'extensions-plugins' only for Extensions; index reports with a tag related to the file format: pdf, eps, emf, uniconvertor... accompanied by 'import-export', 'exporting' or 'importing'. * Use 'extensions-plugins' for both Extensions and import/export formats based on scripts.
I'm unsure. It seems clearer to me to use the first method.
[ 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? ]
See above.
I see you started using the tag renderer. I will make some searches and add to that category.
Regards.