Related to this very question: What's the status on "friendly feedback" and the idea of separate (user- and developer-facing) trackers?
During the last discussions I was involved in there seemed to be a whish to keep especially https://gitlab.com/inkscape/inkscape/issues "internal" in the sense that only developers / experienced users should directly open issues against the main project, so it would only contain valid and easily reproducible bug reports in the long run.
I think the intention was that the vast amount of "unfiltered" reports should be made against a "catch all" tracker for triaging, where the wider community could help to sort reports into the relevant sub-projects and opinions / feature requests / support requests / invalid reports could be caught early and answered accordingly (hopefully in a more friendly way than "not a bug, closing").
Is this still a goal or (to say it bluntly) do we just continue as-is, which will likely mean we just start fresh in collecting an unmanageable amount of bugs? ;-)
If we *were* to make this cut I feel like *now* would be the time to do so, before the inkscape/inkscape tracker is flooded with "random" reports triggered by the upcoming releases.
Cheers Patrick
Am 15.01.2019 um 17:54 schrieb Marc Jeanmougin:
I'll be glad to make a post in forums about this. But is this the correct link?
https://gitlab.com/groups/inkscape/-/issues
Or is it this? https://gitlab.com/inkscape/inkscape/issues
The first one shows all bugs from all the Inkscape projects (Inkscape, extensions, website, vectors…) while the second only pertains to Inkscape
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel