In thinking about KorGE 2.0 and alternative applications of KorGE and Korlibs I am struggling with how to best follow developments and contribute, given that I’m easily 😕. My assumption is that Github issues are a good intermediate point between real-time discussion in slack/forums at one end and code and documentation at the other.
Assuming that Github issues are used for intermediate level sharing, do the project maintainers have a preference for how to track issues that may be spread over one or more korlib libraries and are not yet clearly scoped? My guess would be to apply them as a parent tracking issue to either the korlibs project or the korGE project and then have leaf issues at the project level as they become clearer.
Two example features I would like to help develop and track are enhanced text support and video. It would be great to have high level tracking issues to keep track of child and related to the parent issue, at least for me.