Proposed policy for bug report and feature-request maintenance


#1

Proposal:

Bug reports and feature requests should land either in this forum or a github issue. If a bug or problem is reported on Slack, someone (any participant or even just a witness of the conversation) should post a summary in a topic on the forum. Getting detailed information into that report is not as important as just making sure the issue is logged.

New topics which are duplicates of others should be moved over to the duplicate (or on Github, content copied over, and the duplicate closed). This way, we’ll be able to quickly see which issues are most frequently reported.

Ideally, topics are categorized with a prefix on the topic of the form:

  • Bug Report:
  • Documentation Needed:
  • Feature Request:

Responsibility for managing these reports — initially, we can trade off on weekly basis, but eventually, some people will need to be designated “Report Moderators”.

Importantly – this is about codifying the ways in which we intend to moderate the content. We’re an open-source community, and people will report problems in ad-hoc ways and we shouldn’t try to change that. Instead, we want a policy for how we integrate all this unstructured feedback.

Merging Duplicates

On the forum, topics should be merged using the moderation tools instead of copying content.

  1. click the wrench on the right

16%20PM

  1. click select posts

  1. click move to existing topic.

#2

I like this a lot. Thanks @aaron!

On the forum, topics should be merged using the moderation tools instead of copying content.

  1. click the wrench on the right

16%20PM

  1. click select posts

  1. click move to existing topic.

#3

I’d say that we should try to move all repository-related issues to GitHub (and e.g. label them with question if they aren’t a bug report or feature request). I think there they are way more visible to other developers who have the same problems, it’s closer to the origin of the questions/bugs/etc (easier to track etc), and it also makes it a little bit more sure that these get resolved.

Also, if people have a single point to go to, it’s easier to find things (simply because they only have to check one source).

For people that aren’t familiar with GitHub we probably have to open these issues ourselves.


Besides, I’m really liking a more fixed process for error reports :slight_smile:


#4

I agree that we should create github issues for bugs especially. However, I want a policy that meets the users where they are — if someone reports a bug in the forum, I think it should be merged into a thread on the forum, then we can link that to a Github issue. Github issues are great, but I want to make sure that issues are reported more frequently than not — and that means reducing friction as much as possible, and letting people report bugs wherever they can.

Yeah, that’s great.


#5

Totally agree with that :+1:
Just thinking about how we could let people discover bugs/requests/questions raised on the forum also on GitHub. There must be a better solution than copying the information over to GitHub after resolving an issue here :smiley: