Herein, I propose closing this Discourse instance in favor of utilizing the GitHub Issue tracker.
As can be seen in GitHub scala/scala-dev #267 (comment), I was not sure about this Discourse instance when I first learned about it.
I have since learned more about this Discourse instance and given the platform a try.
I believe I now understand my initial reaction and that this Discourse instance (Scala contributors) would be better provided by GitHub Issues.
There are two main reason for this:
- Moving to GitHub eliminates barriers to use which come from using a different system. This barrier is real in a number of ways.
- GitHub has good integration with GitHub, and the rest of the Scala ecosystem is on or is moving to GitHub (from what I have observed anyway)
Many of the conversations on here concern the “Scala Platform” idea, which is not itself a work of code.
It is still an open project with artifacts and outputs that needs a home and hopes for community involvement.
As such, I do not see any impedance between its needs and what GitHub provides.
In fact, GitHub Pages is already utilized to publish information pertaining to the "Scala Platform Process."
Perhaps that repository’s issue tracker would be a suitable home?
If the goal of this Discourse instance, is to be a single place of conversation for across projects (thus the “contributors” name), I would propose that GitHub’s support for referencing issues across projects within its platform is sufficient.
Additionally, the Collective Code Construction Contract (C4) that is being proposed in the context of the Scala community seems to support my view. Platform is previously defined as GitHub:
The project SHALL use the Platform issue tracker.
Explanation on the above requirement given in Social Architecture by
[…] keeping the issue tracker on the same platform means one less UI to learn, one less login, and smooth integration between issues and patches.