Something that’s been bugging me for a while now is the way that both bug reports and feature requests are done:
- There’s a mailto link (via “contact support”), but it’s a 1:1 (at best) communication without any means to track progress.
- Discourse has the “Site Feedback” category, but there’s no clear template for bug reports, topics get lost easily, duplicate requests pop up all over, many topics suffer from scope creep in the comments, and “solved” is a rather vague status description (if it gets used at all).
- Create a new public pinned repo on Github for observablehq.com (without any code) that is only used to track bug reports and feature requests.
- Create (or enable) issue templates for bug reports and feature requests.
- Migrate existing reports and requests to GitHub (can be done by community).
- Still allow Discourse for reports and debates, but migrate reproducable bugs and clearly scoped feature requests to Github (again, community).
- Restrict all help/support requests to Discourse (think d3 and stackoverflow).
I believe this would be a win/win for everyone:
- the community, because there can now be a single source of information (and truth) for all issues, without the cruft and noise of Discourse,
- the Observable team, because you don’t have to weed through topics and posts to find actionable information.