-
Notifications
You must be signed in to change notification settings - Fork 771
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
Enable GitHub Discussions for i3 #4400
Comments
Can you provide examples of the topics you want to discuss? We currently already have IRC, a mailing list and a subreddit. I'm hesitant to add further channels to this unless there's a very good reason to do it. |
Is there a Github functionality for discussion forums or do you just mean to not close/redirect issues that are neither bugs or features? If you mean the second, that would negatively affect our ability as maintainers by adding more noise to our issues. |
@orestisfl There's a separate GitHub Discussions feature. |
Then it might be a good idea. Out of our options:
Additional benefits seem to be that we can convert issues to discussions and there is more tight coupling with github issues for discussions (e.g. by linking between issues and discussions). I do understand though why farther fragmentation of the community might be a potential problem. |
There's two concerns from my side:
If we were to open GH Discussions, I'd probably vote to retire at least some of the other channels. Let's consider this:
Overall I wouldn't mind closing all three of them in favor of one good place, but if we had to pick one to keep, I'd probably pick reddit purely because it is the de-facto community place at the moment. |
Side note, I haven't ever used GH Discussions and have no idea what it actually looks like / what it can do etc. |
Thanks @orestisfl for setting up a quick test. From an initial test Discussions looks quite useful, similar to SE in useful ways. The question that'd remain is on how to redirect traffic there, if we wanted to go with it. |
I don't see closing as the correct approach. An i3 reddit community is bound to exist even if it is unofficial, there is no point to annoy the community. We would just have to remove the reddit link from i3wm.org and maybe elect new moderators in the subreddit. An important difference between the two communities is that reddit users are usually anonymous while GitHub users are usually more professional and using their real names. Anonymity can help having more relaxed discussions. IRC and mailing lists are used by certain people that prefer them and would likely not use the alternatives that much anyway. I see no reason to close them either. |
If we were to keep everything else, I'd vote no to Discussions because I don't see the point in opening yet another communication channel that requires maintenance and would likely receive little to no traffic anyway. |
@Airblader, here is an example; https://docs.github.com/en/discussions You mantioned IRC / Mailing-List / Reddit, not everyone uses them. But by having GitHub discussions board you can have it all in the same place as Issues/Code. Here is a live example from "ungoogled-chromium"; |
But everyone can. I doubt that there's any i3 user who doesn't have an email address. There's certainly significantly more people who have any of those options than GitHub accounts. I don't want to spread this over half a dozen communication channels, because solutions given here aren't discoverable on the other channels and vice versa, and it fragments the overall community rather than having one big one. Not to mention that all of these need to be administrated as well.
Which indeed is a major benefit. I'm definitely not against GH Discussions, it looks great; I am against just adding a new channel to all the existing ones, though. |
Okay fine. |
Maybe this came across wrong, but I don't think this discussion was decisive yet. I'll reopen this. |
OK, so we internally clarified that I wasn't clear enough on what I meant previously – apologies. I didn't mean to say we'd shut down the subreddit altogether; we don't even have the access to do so. Instead, I meant to remove it as an official channel by "rebranding" it to be non-official and pinning a post redirecting users to GH Discussions instead. This seems to be agreeable with @orestisfl as well. So the question now is what @stapelberg thinks about it. |
Does reddit really require accounts? Opening /r/i3wm in an incognito tab seems to work fine. I’m okay with trying out GitHub discussions. That’s the only way to see how the community reacts :) We should probably have a trial phase, where we see for a few weeks (1 month?) how GitHub discussions works before rebranding everything. |
It seems that this is a mobile-only thing, but on mobile if I open reddit incognito, it forces me to either log in or use the app (which presumably requires a login as well). Why they're doing this for mobile only – I don't know. Reddit does have a bunch more disadvantages, and overall GH Discussions seems much closer to what we were looking for when we migrated from AskBot. We were also never actually given ownership of the Subreddit, but rather just some moderation/administration rights.
Yes, that makes sense, of course. I'd be happy to announce that on Reddit as well. |
More context of the dark pattern: https://news.ycombinator.com/item?id=18723583 |
Yeah, I have in the meantime noticed this as well (when not logged in). A friend of mine mentioned GitHub discussions works well in practice, so I think we should give it a shot! |
@stapelberg Do you want to enable them and then we can slowly start using them? It doesn't have to be final from the start. |
Done (I think?) |
I'll take care of the Subreddit now. |
@stapelberg Maybe you can delete the "General" category on Discussions? At least IMO we don't need a generic non-Q&A chat. I don't seem to be able to delete categories. |
I don't think it will hurt to have a "decompression valve" to keep other categories topical. |
Done. We can always re-add it, or perhaps a more focused off-topic (anything around i3, for example). |
I could imagine questions looking for recommendations which aren't exactly a "Q&A" kind of material (since there's no correct answer), but I would rather prevent Q&As ending up in General where they cannot be marked answered. So I'd also like to start small and re-add if necessary. |
@stapelberg Can you maybe also take care of #4512 (comment)? |
Fixed with i3/faq.i3wm.org@35426aa |
The recent 4.20 release didn’t have anything about this. Should we even bother to include a note, or can we just close this issue? :) |
I would vote to just close. Discussions have already seen quite nice traffic. |
TODOs:
Original request
I'm submitting a…
Current Behavior
Not available.
Desired Behavior
Can you please enable github discussions forum here? So we can use it to discuss i3 not related to feature or a bug?
Impact
Environment
Output of
i3 --moreversion 2>&-
:The text was updated successfully, but these errors were encountered: