GitHub Discussions vs Issues

[czyzby]

KTX recently qualified for GitHub Discussions beta. I think it used to be related to the number of contributors and you actually had to ask to sign up explicitly, but now they might be opening the feature for a broader audience. Anyway, I've set up a Discussions board (mostly with the default settings) and converted some of the historic issues with the question tag into discussions. I encourage you to check it out.

I think the GitHub forum is a great halfway measure between issues and chats. Issues tend to be more formal tasks, feature requests and bug reports, while chats are completely separated from the repository, and are often too unstructured and informal to build anything resembling a knowledge base.

From now on, I ask you to create discussions rather than issues when you want to:

• Ask a question about the framework.
• Discuss new possible features.

Since they're basically a forum, Discussions also open up some new possibilities to post content that typically isn't very common in GitHub issues. Feel free to:

• Advertise your KTX project, open sourced or otherwise.
• Ask for a code review or coding tips.
• Discuss game jams.
• Create a personal dev log for your project.
• Have a general discussion related to gamedev, Kotlin or anything you want to talk about with fellow KTX developers.

You should still use issues when submitting bug reports and feature requests. Don't worry about posting in the wrong place - issues and discussions can be converted into one another and I'll do it whenever necessary.

See you on the board.

[czyzby]

If you have any suggestions for the KTX Discussions, feel free to post them here. I'll eventually convert this issue into a discussion, but since this feature is pretty new and not every developer might know about it (I sure didn't until recently), I wanted to set up a pinned issue for visibility.