I’m currently looking into making the issue template in github/ipfs/go-ipfs nicer and noticed that
a lot of “issues” are actually more kind of a discussion without beeing really “actionable”.
This results in a lot of stale tickets floating around (it’s now nearly 1000 tickets!).
With issue templates we could move people seamlessly to the discussion platform and present a
nice looking selection page, which let them choose which kind of feature or topic they like to
This would allow us to clean up the issues, to boil them down to “just” issues, which need to be
addressed - like limitations, performance issues and actual bugs - and move everything not related to a single actionable thing, like meta issues, discussions about potential features and maybe even release checklists to thd Github discussion page.
I think that would make the issue tracker much more clearly for the programming team, while the
discussion section can be used for feature discussions, without having to move them to other repos,
like github/ipfs/notes/issues where they seem to just stale and get duplicated from time to time in
the go-ipfs repo.
We could also use the github/ipfs/notes repo for general discussions with the discussion function of
the protocol, which are currently in
github/ipfs/roadmap/issues, and sometimes now in
This would also allow us to remove the split between the two platforms. I think all development
stuff should stay on github, while the forum is more for technical support as well as open
technical discussions without a development purpose.
- Issues should be actionable
- Discussions about features/bugs/limitations should be in
- General community discussions, questions, technical help etc should be posted here (discuss.ipfs.io).
Let me know what you think!