net4people
Use `Discussions` instead of `Issues`
I suggest considering the possibility of creating a Discussions section in bbs, moving all Issues to it and deleting the Issues section.
More about this tool, which is much more suitable for replacing a forum than Issues:
- About discussions. Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on GitHub
- Quickstart for GitHub Discussions. Enable GitHub Discussions on an existing repository or organization and start conversations with your community
- GitHub Discussions documentation. GitHub Discussions is a collaborative communication forum for the community around an open source or internal project
if it's not broken, don't fix it
Apparently, there really are people for whom the concept of FR is alien by its very nature.
If the stick is intact, continue using the stick. If the stick breaks, just find another stick and don't try to make something better out of it.
@Korb I share & support your view to adopt Discussions over Issues section, even when Issues section isn't broken, otherwise most things in life wouldn't improve until/unless they break.
Perhaps @wkrp would consider trialling Discussions section & assess potential impact/improvement over Issues section to elevate experience for the community? I do feel Issues section is somewhat lacking at times & wasn't aware of Discussions section being a potential answer to it until @Korb mentioned so.
I have thought a few times about using discussions instead of issues. I believe the option for discussions didn't exist at the time the forum was started. Discussions are arguably a better format for a use case like this. Plenty of circumvention projects on github are already using discussions alongside their normal issues.
The downside I see, at this point, is splitting the existing body of threads across two places. No matter what happens, the issue threads that already exist will not be deleted. There are many existing references to these threads (even in print) that need to remain stable. Another thing that would need to happen is modifying the archive script to archive discussions. Maybe if discussions offer some really compelling advantage—if URL references are nicer, for example. If discussions have some kind of built-in RSS or Atom feed of recent comments (issues do not), that could be enough to convince me. I've often sorely felt the lack of an easy read-only subscription option that doesn't require a github account.
If discussions have some kind of built-in RSS or Atom feed of recent comments
There is no full functionality yet.
https://openrss.org/net4people/bbs/discussions (RSS, source) and https://github.com/net4people/bbs/discussions.atom may work. But it's not certain.
It's not obvious, but you can subscribe to the thematic categories.
There's a website called openrss that can make an RSS Feed from discussions. You can see how it works here. If you own the repository, you could try using the discussion workflow event on GitHub Actions.
(Source)