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

On Thu, Jan 17, 2019 at 05:18:21PM +0100, Maren Hachmann wrote:
> 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?

After playing with the settings a bit, as far as I can tell there is
only one toggle for a project's issues, which simply controls whether it
is publically visible or not as a whole.  Setting it hides both the new
bug form, and all existing bug reports.  I'm not spotting a way to
restrict bug filing to project members only, but allow visibility of
bug reports to all, which is what we specifically need.  Does anyone
else know a better way to set this?

Bryce