On Fri, Jan 19, 2018 at 02:20:46AM +0100, Eduard Braun wrote:
Two quick comments:
Am 19.01.2018 um 01:40 schrieb Bryce Harrington:
I tend to agree, but have to acknowledge that there's a risk of putting too much burden on end-users to select where to report their feedback, when they may simply not know enough to make that determination. Or at least may not feel comfortable with it.
That's exactly why I think it's essential to have an easy possibility to move reports around as needed (i.e. let end-users try to make their best guess but without putting any pressure on them) and let more experienced folk sort out the reports which ended up in the wrong tracker. Good example is GitLab itself: They have three trackers (GitLab EE, GitLab CE and gitlab.com) and I never now where to report anything, so I make my best guess and report away - until now almost always somebody moved the bug according to whatever internal guidelines they have (I have no idea what they are but I feel perfectly fine with not caring ;-) ).
Part of the argument of the two-layer approach would be to address this by having a one-stop-shop inbox that is friendly and suitable for non-technical users. And then a second layer where the individual items are broken out into more technically detailed repositories which are sensibly grouped in ways that are more manageable for triagers and developers.
Here I have to ask for a quick clarification:
- Up to now we were discussing about splitting bugs and feature requests in this mailing list thread
- Here you are suggesting to split "user-facing" and "developer-facing" trackers
As I assume we don't want four trackers
- are "feature requests / user-facing" and "bugs / developer-facing" synonymous for you? (e.g. handle discussion/designing/prioritizing of features on the user side and only migrate bugs away from that tracker to the developer-facing tracker)?
- or are we discussing an either/or possibility here? (e.g. either split features/bugs or split users/developers)
It's the latter. So if both splits were done there'd be three trackers (apologies if the ascii/unicode diagramming gets borked):
+-------------------+ | Friendly Feedback | +-------------------+ ↓ ↑ Crowdsourced Triaging ↓ ↓ +-----------+ +------------+ Feature ← | Feature | | Bug | → Bug Triager → | Request | | Report | ← Triager Team | Tracker | | Tracker | Team +-----------+ +------------+ ↓ ↓ Developers Developers Developers
Bryce