-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[META] GitHub Discussions are now generally available #90
Comments
We have been trying "Discussions": https://github.com/orgs/ForthHub/teams/forthhub/discussions I remember there were some usability concerns about the Discussions format. I emailed GitHub support, but I don't think anything came out of it. I think this is the thread: https://github.com/orgs/ForthHub/teams/forthhub/discussions/2 |
I still think this https://github.com/ForthHub/discussion/issues is a much better user interface than this https://github.com/orgs/ForthHub/teams/forthhub/discussions |
@larsbrinkhoff I vaguely remembered about this before I posted, but I thought that it was quite a while back, and Discussions only entered limited testing in March and general release a couple of days ago, so surely I must have been misremembering? Turns out I wasn’t misremembering, but GitHub’s product branding is extremely confusing (to be fair, I’ve yet to come across corporate product branding that wasn’t extremely confusing). There are two separate things:
For how these repository discussions work, try the ones at the next.js repo (which I should’ve linked to in the initial post) and you’ll see that they’re a completely different beast from team discussions (though surely GitHub will try to unify them at some point). I also failed in my Google-fu by not finding and linking to the documentation page for repository discussions, which contrary to my initial post actually exists! |
Thanks, that clear things up! In the interest of merry experimentation, I enabled "Repository Discussions": https://github.com/ForthHub/discussion/discussions |
It seems to me the new "discussion" is more an outgrowth of "issues". So that seems promising, I think. We'll see how it plays out. |
I really like that when using "issues" I'm getting all updates via email. Will it work the same way with "discussions"? |
I really like that when using "issues" I'm getting all updates via email.
Will it work the same way with "discussions"?
I'm guessing it will! But I don't know. Try it out!
|
Ok, posted a test message. I have the same concern as @alexshpilkin : if discussions will work better (btw do we have criteria for "better"?) we will need to do full switchover to have single place for the conversations. |
My vote would be using discussions over issues. From what I've seen discussions can't be "closed" like issues can, and my guess is that over time they'll have better support for searching and other features. |
Thanks @kt97679, your test message looks good. So far I think the new "Discussions" look better than the old. But there are no defined criteria and no one in charge. But hey, it's Forth so that's normal. :-) |
@larsbrinkhoff so true :). I generally agree with @massung . Let's try to use "discussions". If folks will be unhappy for some reason we always can fallback to "issues" which worked quite well for us for some time already. |
Please just make sure it doesn't suffer the same issues as c.l.f |
As this repository essentially uses GitHub Issues as a substitute for message board software, people might be interested to know that GitHub just rolled out its own actual message board software, GitHub Discussions, for all public repositories (it was being tested in a small number of them for the last couple of months). Whether this will be useful for this particular community, either now or once this feature matures, I don’t know, and the docs are very sparse for the moment, but I suppose it’s better to be aware of the possibility than not.
I only hope that if a switchover ever happens here, the issues are unambiguously closed so that it’s indeed a switchover and we’re not left with two separate but not quite equivalent ways of conducting a conversation. (Indeed, that’s the main source of potential silliness for this feature in general, even if user support over public bug tracker is also silly in its own way.)
The text was updated successfully, but these errors were encountered: