Should we disable GitHub discussions? #25946
Replies: 7 comments 3 replies
|
I think we should disable it. I suggest high-level discussions continue to happen on contributors, and we use GitHub issues with |
|
What about feature suggestions? Where should they go? |
|
fwiw, Lukas points out that in Scala 2 we have long used https://github.com/scala/scala-dev/issues for discussions that are internal-facing, yet not so sensitive that they must be private. Perhaps GitHub Discussions could play that role for Scala 3. |
|
every discussion opened here (from me anyway) pretty much goes silent so i think it is not a place people are scanning or have notifications for and it is discouraging IMO to point people to open "feature suggestions" here for that reason |
|
@odersky is in favor of keeping this, because he's been using the discussion section to document design drafts, as a place to have ideas available that do not require immediate scrutiny by the broader community. Maybe it's indeed the best course of action to just clean up the categories and point to other communication channels for anything else. |


Uh oh!
There was an error while loading. Please reload this page.
They seem mostly a write-only forum. And the scope is not very clear. We have several other places where people can discuss at various levels.
Though I could see it useful as a forum for deep technical discussions about the compiler. Apart from the internal Slack (which isn't open to the general public/might miss out some key contributors), we don't have such a focused forum. That comes with the downside of "yet another discussion channel". Thoughts?
All reactions