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

Maximilian Gaukler <development-2i6qpEp9gt/[email protected]>
Newsgroups gmane.comp.graphics.inkscape.devel
Message-ID <[email protected]>
Hi everyone,

First, it seems there is a misconfiguration: I can create issues for 
everything except the inbox.

Can someone please explain to me the benefit of a separate inbox 
compared to just tagging all valid bug reports with something like "bug" 
or "confirmed", and all others reports with "question"?

I'm not sure if I miss a point, but both the current "Inbox" and the 
"real bugtracker" could be views of the same bugtracker, just filtered 
by tags.

By splitting up into two trackers we loose a valuable feature of GitLab, 
where related bugs are automatically suggested if you create a new one 
in the *same* GitLab project, which means that duplicates will keep 
popping up in the inbox although the bug is already in the development 
tracker.


It seems that the main motivation of the inbox is to move away the very 
"low-quality", discussion-forum like entries. If this is the case, I 
think we should state that technically complete bug reports should 
shortcut the inbox and go directly to the issue tracker. It could also 
be a motivation that if you manage to completely fill out the "real bug" 
template, developers will be able to take care of the bug. To avoid the 
usual questions, the developer template should also include "Does the 
bug happen on the latest version? [link] (Please state the version 
number and result). Does the bug happen on the latest development 
version? [link to something like 
http://wiki.inkscape.org/wiki/index.php/Installing_Inkscape ] (Please 
state the version number and result.)".


In some answers it was suggested to close (make read-only?) the issue 
tracker for everyone except Inkscape developers. I don't like the idea, 
as it feels more like a closed company with front-desk and back-office, 
and less like a meeting of friendly people where you can simply join. A 
read-only bug tracker is also really annoying to downstream 
distributions and users with developer-like knowledge. They should not 
be forced to use the "newbie support forum" and have to wait until 
someone discovers their high-quality report and moves it to the real 
bugtracker.

Max
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.