Re: Inkscape's Inbox (gitlab "friendly feedback" tracker)
Maren Hachmann <[email protected]>
| Newsgroups | gmane.comp.graphics.inkscape.devel |
|---|---|
| Message-ID | <[email protected]> |
Sorry, another one: Please ensure that it's allowed for people to request membership in the new inbox subproject (if that isn't allowed yet, I cannot test). This is where new triagers would apply for the team to offer their help, I think? No idea which permissions they would need for moving a bug to the other tracker, though. Maren Am 17.01.19 um 17:39 schrieb Maren Hachmann: > Am 17.01.19 um 17:18 schrieb Maren Hachmann: >> Am 17.01.19 um 16:56 schrieb Maren Hachmann: >>> Am 17.01.19 um 08:28 schrieb Bryce Harrington: >> ... >> >>>> 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? >>> >>> Who is supposed to watch for duplicates now? >>> - Users? >>> - Triagers? >>> - Developers? >> >> - One more question/thing to decide upon: >> >> Will access to the developer-facing bug tracker be restricted? >> >> If not, how are you going to ensure that users do not circumvent the new >> system in the hopes of getting their pet bug tackled faster? > > And another one: please update the bug reporting template at > https://gitlab.com/inkscape/inbox/issues/new if you want quality reports > from users. It's currently near empty, except for: > > "How do you think Inkscape could be improved?" > > Maren > > >> Maren >> >