Skip to content
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

Improve community support #258

Open
bjohansebas opened this issue Aug 20, 2024 · 15 comments
Open

Improve community support #258

bjohansebas opened this issue Aug 20, 2024 · 15 comments

Comments

@bjohansebas
Copy link
Member

On the Express page, links to other platforms like Gitter, the Google group or IRC channels are promoted, but these resources no longer seem to be used by the community. In the case of Gitter, the last message is spam for a Telegram group.

It would be good to consider other ways to help the community, such as setting up a Discord server, creating a community on X, etc.

@wesleytodd
Copy link
Member

Those used to all be active, times have for sure changed. The problem we have is we never had enough contributors to run those. If we would like to make a program to help folks get involved in that I would be down for it.

@bjohansebas
Copy link
Member Author

Given that many projects like ESLint, Vercel, and Biome.js use Discord, implementing a server could make it easier for people to connect and discuss Express-related topics. We could also add channels for blog ideas, announcements, releases, and support.

@wesleytodd If you like the idea, I could set up the server and show how it could look.

@wesleytodd
Copy link
Member

My only concern with Discord is we already are heavily using the OpenJS Slack, and I know I have stopped participating in the discords because it is just too many chat apps to keep open all the time. If you have not seen the activity in the OpenJS slack it might be worth checking out first before setting up a discord.

@bjohansebas
Copy link
Member Author

The problem with Slack is that it’s mostly used for internal organizational matters rather than for the community. The way I see it, Discord would be more focused on providing support and helping those who have issues with implementing Express, similar to how other platforms have done it.

@wesleytodd
Copy link
Member

Oh I fully agree. Slack sucks for communities. I just mean that the problem is collaborator participation, and we have a sponsored and well managed slack instance already.

@ljharb
Copy link
Contributor

ljharb commented Aug 20, 2024

Personally i vastly prefer slack to discord for communities; discord’s UX is awful.

@wesleytodd
Copy link
Member

Yeah thats true as well, but the community moderation things in discord are much better.

@ljharb
Copy link
Contributor

ljharb commented Aug 20, 2024

More fully featured for sure - in my experience “deactivate account” and “delete comment” have been sufficient moderation tools for slacks i manage tho :-)

@bjohansebas
Copy link
Member Author

@ljharb Keep in mind that on Discord there will be more external people interested in the project and its community, whereas Slack feels more closed-off from my perspective.

@ljharb
Copy link
Contributor

ljharb commented Aug 20, 2024

That's subjective and very much not my experience - Slack is just as easy if not easier to join than Discord - but certainly it's possible.

@wesleytodd
Copy link
Member

One thing to be clear about here is the difference between an official and unofficial community. I assumed this conversation was about an official one. If that is the case we need folks in there doing moderation and generally keeping thing in line with the projects values. This means likely TC members are around. That is my worry about discord right now, despite me using it for gaming I dont have it installed on my work computer and generally have decided my time was better spent in slack because all of the current TC members and contributors have seemed comfortable with using the OpenJS slack for our real-time comms.

Alternatively, an unofficial channel wouldn't need this stuff. So it might achieve a better community, which would be awesome if that happens. We don't need central control or anything, but I do think that people come to those things to find value in talking with the maintainers, and if the maintainers are not there they tend to fail (as happened with the previous attempts).

Anyway, I am pretty open to either as I do actively use both, but we should be clear on the goals.

@LeaderSix
Copy link

LeaderSix commented Aug 21, 2024

@bjohansebas +1 for bringing this up.

However, my vote goes to GitHub discussion. Perhaps we could just change our doc to post in our repo discussion for support. It could make more sense in terms of TC involvement.

It will be much easier to reference issues, prs and possibly convert a discussion to an issue if needed. Seems cleaner to me. I suggest we promote GitHub discussion as our official community and just see how this goes and grows. It will also not require extra moderation unlike Discord.

Edit: I am Hasan (@IamLizu), it appears I am on wrong account.

@bjohansebas
Copy link
Member Author

@wesleytodd I agree, and what I wanted when starting this discussion is to have an official community on some platform for people who are interested in using this technology, like there used to be before. I also like @IamLizu idea; the important thing is to correctly select a platform where everyone feels comfortable, as well as properly informing users of these platforms.

@wesleytodd On the other hand, can I remove references to the mailing list, Gittler, and the IRC channel from the page?

@wesleytodd
Copy link
Member

On the other hand, can I remove references to the mailing list, Gittler, and the IRC channel from the page?

Oh yeah. Please do.

@bjohansebas
Copy link
Member Author

I've seen that Node.js has an open proposal to have a Discord server.

Ref: nodejs/admin#872

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants