Suggest enabling the GitHub Discussions (community forum) in this repository and then also expose that in the Sendspin orginazation on GitHub:
In my opinion best would be if you could enable it at the the GitHub organizational top level similar to how Music Assistant has it:
GitHub Discussions can be activated in any GitHub repo and either be only for that specific repo or have a symbolink link with GitHub originazation
Better yet, you can use organization discussions to facilitate conversations that span multiple repositories in your organization. For more information, see:
The main reason for wanting to have this is so discussions are moved away from issues and pull requests, encuraging non-code contributions such as posting feedback or ideas, while another reason is that discussions are not tracked so a discussion thread can be left open indefinitely if you want.
This helps keep issues focused and makes it easier to collaborate and share ideas openly.
That os, it promote starting a discussion before opening a GitHub Issue. And then only if and when a discussion turns into a concrete bug, task, or actionable item, it will be asked to create an issue from it for tracking.
Quote from OHF-Voice initial discussion board welcome post for the linux-voice-assistant repo below:
In Discussions, feel free to:
- Ask questions you’re wondering about
- Share ideas
- Engage with other community members
- Welcome others and stay open-minded
Remember that this is a community we build together 💪
Help us improve
Have ideas on how we can improve collaboration, communication, or contributions in this project?
- Share suggestions on how we can work better together
- Point out things that could be clearer or more welcoming
- Propose improvements to our processes, tooling, or documentation
Your feedback helps shape this community — let’s improve it together 🚀
Thanks for being part of the community let’s improve it together 🚀
Suggest enabling the GitHub Discussions (community forum) in this repository and then also expose that in the Sendspin orginazation on GitHub:
In my opinion best would be if you could enable it at the the GitHub organizational top level similar to how Music Assistant has it:
GitHub Discussions can be activated in any GitHub repo and either be only for that specific repo or have a symbolink link with GitHub originazation
Better yet, you can use organization discussions to facilitate conversations that span multiple repositories in your organization. For more information, see:
The main reason for wanting to have this is so discussions are moved away from issues and pull requests, encuraging non-code contributions such as posting feedback or ideas, while another reason is that discussions are not tracked so a discussion thread can be left open indefinitely if you want.
This helps keep issues focused and makes it easier to collaborate and share ideas openly.
That os, it promote starting a discussion before opening a GitHub Issue. And then only if and when a discussion turns into a concrete bug, task, or actionable item, it will be asked to create an issue from it for tracking.
Quote from OHF-Voice initial discussion board welcome post for the linux-voice-assistant repo below: