Re: Inkscape's Inbox (gitlab "friendly feedback" tracker)

On Thu, Jan 17, 2019 at 04:56:52PM +0100, Maren Hachmann wrote:
> Am 17.01.19 um 08:28 schrieb Bryce Harrington:
> > Following Patrick's proposal and feedback collected from several others,
> > I've set up a new project in the Inkscape gitlab called "Inbox".
> > 
> >     https://gitlab.com/inkscape/inbox/issues/new
> > 
> 
> ...
> 
> > 
> > A few tasks:
> > 
> > 0.  Let me know if there are any issues with this plan, or ways we can
> >     improve it.  In particular, is there more we could do to streamline
> >     and simplify the UX?
> 
> Are tags ported from one tracker to the other when moving a bug?
> Do we need them to be group-wide for that to work?

Good questions, worth experimenting with.

> Who is supposed to watch for duplicates now?
> - Users?
> - Triagers?
> - Developers?

The intention is that obvious dupes would be spotted and dealt with
entirely within Inbox by people towards the top of your list.

I expect part of the escalation process will naturally include looking
if its already a known issue in the target bug tracker.  There is no
need to escalate a low-quality report about a bug that is already known.

Some dupe bugs may be worth escalating anyway, if they provide valuable
analysis or context.  Developers sometimes find this gives new insights
into known issues.


> > 1.  Please change the inkscape.org/report redirect to go to
> > 
> >     https://gitlab.com/inkscape/inbox/issues/new
> > 
> > 2.  Please add a redirect inkscape.org/inbox to go to
> > 
> >     https://gitlab.com/inkscape/inbox/issues
> > 
> > 3.  Adjust our 1.0alpha bug reporting guidelines to direct users to
> >     these addresses.
> 
> - I will make preliminary changes at
> https://inkscape.org/contribute/report-bugs/ , but I suppose there will
> still be further adaptations required. Please someone from the bug
> wranglers adapt as you see fit. Please notify me or translators mailing
> list when you are done.
> 
> I will also update the news article for this and the releases app contents.

Thanks

> Instructions for bug triagers at
> https://inkscape.org/develop/bug-management/ need to be updated, too. We
> need a volunteer for this task who is familiar with bug triage and can
> come up with a suitable workflow.
> 
> I will make a preliminary update there, adding the new link, but I will
> not dive into explanations etc. Whoever does the final update,  please
> notify me or translators mailing list when you are done.

Posted as https://gitlab.com/inkscape/inbox/issues/4
(not sure if this should be moved to inkscape-web or vectors or ...?)

Bryce