mobxjs / mobx-state-tree

Full-featured reactive state management without the boilerplate
https://mobx-state-tree.js.org/
MIT License
6.94k stars 640 forks source link

chore: update GitHub issue templates to focus on bugs #2017

Closed coolsoftwaretyler closed 1 year ago

coolsoftwaretyler commented 1 year ago

At the June maintainers' meeting, we said the ongoing philosophy for this project is to prioritize stability over just about everything.

Right now, our GitHub issue templates include:

  1. Bug reports
  2. Conceptual questions
  3. Feature requests

I think we can demonstrate our approach to stability by encouraging folks to use our discussions for feature requests, and conceptual questions make sense to go there as well.

If we focus our issues board on mostly bugs, I'm hoping that the issue count will accurately reflect "things that are broken and being resolved", rather than a laundry list of future-facing ideas that might get stuck in discussion for a long time.

This PR is also somewhat related to this discussion thread: https://github.com/mobxjs/mobx-state-tree/discussions/1961. I think the discussions/issues boards have duplicative topics, and we've got some items that are doubled up as discussions/issues. I'd personally prefer to see them in discussion only.

I would be happy doing this the other way - remove discussion categories and move things to the issue tracker. One way or another, I think we should de-duplicate our templates.

This PR also links to the discussions board in a few new places, and leaves the blank issue template basically blank, just to give folks a little more flexibility if they really think there's something appropriate for an issue and not discussion, but the bug report template fails them.