contributor_covenant VS customdiscordrpc

While you are free to write your own or adopt one from another repository, project, or organization you respect, there exists a code of conduct written and maintained by the community known as the Contributor Covenant.

Many Open Source projects have adopted the Contributor Covenant as their code of conduct. Check this page to see a list of adopters.

https://www.contributor-covenant.org/ is (was?) the most widely adopted code of conduct in FOSS, initially drafted by a Ruby contributor, who also happens to be transgender if that's pertinent information to you. It's the genesis seed from which all this code of conduct madness stems from. Personally I'd stick with "be excellent to each other" or "say what you want, just don't insult other contributors" or something vague, ambiguous and universally understood as that. I'm not really a fan of rigorous social rules, so my view on this starts from that position.

You can adapt the guidelines provided by https://www.contributor-covenant.org/ to create your guideline.

The Contributor Covenant that the maintainer removed to "reclaim polymc from the leftoids" was added in February: https://github.com/PolyMC/PolyMC/pull/178. You can view a list of other communities that have adopted the covenant on their website.

For reference, the Code of Conduct they used is basically the same as this one: https://www.contributor-covenant.org/

Please follow the Contributor Covenant

As your audience grows, it is vital that you define clear rules to create a safe environment for everyone to participate. A common way of doing this is to define a code of conduct (CoC), which sets some basic guidelines on what kind of community interaction will not be tolerated. We decided to stick to well-established frameworks and based our CoC on the Contributor Covenant.

Those aren't the only ways I could see things happen, but that represents a few points on the spectrum. Having been participating in the English Wikipedia community since the early days, I know that collaborative writing on a worldwide scale is hard, and leads to misunderstandings and hurt feelings. Hence the reason why things like the Contributor Covenant came out, and why Linus Torvalds took such a long time accepting something. Note, things labeled "Code of Conduct" and "Contributor Covenant" are one small slice of governance. Dealing with things like the ideal public transit system create a massive extra layer of complexity. Governance, in general, is difficult.

Collaborate with Others: Join developer communities on platforms like GitHub and Discord to collaborate with fellow developers on projects. Participate in hackathons and coding competitions to work with others in a competitive yet supportive environment.

It’s well-established that Discord is a great platform for Developer communities. What’s less established are clear, best practices on how to configure a server from scratch to best serve a community of devs. If you are a community manager or Discord moderator, this blog post aims to give you the definitive guide to getting a working server that will feel welcoming, resourceful, and intuitive for all your community members.

There are no hard and fast rules around this other than remembering to meet your users and contributors where they already are. If you know that they are more likely to hang out on Discord rather than Slack, then having your community channel on Discord is going to serve you well. Some people prefer to keep their communication about a piece of work as close together to the issue and work as possible. One place to have these asynchronous conversations is on the issue itself. There are a few benefits to this:

Discord (https://discord.com/)

Discord is a popular instant messaging application. Originally designed for gamers, it has evolved into a versatile space for communities to connect and collaborate in real-time.

Listening is a skill that we don't practice enough. If you want to think like a consultant, learning to listen is a critical skill. If a consultant solves problems and connects with others to accomplish things for the collective, it only makes sense that gathering the requirements of problems is a highly valuable skill. And while those requirements might be written, most of the variability and detail will come from conversation. This could be an auditory conversation or it could be over a social channel like Discord or Slack. The point is, to think like a consultant, you have to be able to listen to what people are saying so that you can then begin to help solution.

Welcome to our series about building a Discord clone using Next.js and TailwindCSS. In the previous posts, we covered setting up the project and adding the server list. This one will tackle the channel list that will look like this:

Discord is a great example of an enabling platform. After getting started in the gaming industry, it has expanded to other areas as well. Its core value is connecting people and allowing them to hang out, chat, talk, have video conferences, share their screens, and more.

There's an entry in the Application Local Storage in your browser for https://discord.com