Create Code of Conduct

[bell-kevin]

Maybe a Code of Conduct might be nice for this repo. What do you think?

[DaveAxiom]

Why?

[bell-kevin]

Why not? It details how to be respectful and decent towards one another. Sometimes people online are not as nice as they are to people in real life, face to face. People have different expectations, and a Code of Conduct is a way to set healthy expectations rather than unhealthy ones. Also, repositories with a Code of Conduct usually are more professional than repositories that don't. I can give many numerous examples if you need, just ask.

[Kirdow]

I don't think a code of conduct is something that will make bad actors vanish from existence, and from my time checking in here I haven't really seen any major bad actors. I think common sense goes a longer way than having the need to read a code of conduct in order to stay positive and healthy. That's just my opinion though.

On another note Yan usually comment about how Readme changes etc are the least of our worries atm so I don't think this is needed unless there's a ground breaking issue that requires a code of conduct.

[bell-kevin]

The Code of Conduct is definitely not about "mak[ing] bad actors vanish from existence." It's about helping good people be better and be more aware of others. Bad people are going to be bad whether we have rules to stop them or not. A Code of Conduct is just common sense written down for everybody to read and know.

Maybe this community does not need a Code of Conduct right now, but at some point someone in this community will get angry, hurt, or offended by somebody else in this repository community. It's better to have a Code of Conduct made as a preventative procedure, rather than as a reaction to a bad incident. A Code of Conduct can help a bad incident go a bit more smoothly.

I'm not here to force a Code of Conduct though, I just thought it might be something for the community of this repository to think about now and for the future.

Thank you to everyone who is commenting! This is a great discussion!

[Kirdow]

That sounds pretty reasonable. I could definitely see that as a good thing to have. It's still a matter if Yan thinks it's important now or not, but I definitely support this 👍

[bell-kevin]

Thank you, @Kirdow for your support!

[bell-kevin]

What do you think, @TheCherno ?

[DaveAxiom]

@bell-kevin A Code of Conduct is stupid!

[thygrrr]

It's not stupid, but it doesn't need to be overcomplicated.

Here's a good one, and it's CC: https://www.contributor-covenant.org/version/2/1/code_of_conduct/ https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md

[bdnugget]

It's incredibly retarded and I don't think anyone will even read it. I think code of conduct pushers do it mainly to show everyone how incredibly good they are.

[hcm444]

Sure here is my idea for a COC

Embrace the principles of transparency, collaboration, and community-driven development that define open source software. Encourage contributions and diverse perspectives that benefit the project's mission. Support respectful and constructive discussions related to the project's development and goals. Recognize that freedom of speech is valued but must align with the project's objectives and not infringe on the rights or comfort of others. Refrain from engaging in politically charged debates, as they can be divisive and detract from our core mission. Focus on technical discussions and project-related matters to maintain a neutral environment. Our project is committed to hiring and collaborating with individuals based on their technical expertise, merit, and commitment to the project's goals, rather than their political beliefs. We do not consider or inquire about the political affiliations or beliefs of contributors or potential team members.

Violations of this code of conduct may result in warnings or, in severe cases, removal of contributor privileges within the project.

[Dat-Pudding]

I second the part about appearing more professional BUT with plenty of Codes of Conduct I see the problem that it is usually written in legalese instead of human language.

Would likely go the route of the average ToS or EULA with virtually no one bothering to ReadAllat™

[Dat-Pudding]

Sure here is my idea for a COC

Embrace the principles of transparency, collaboration, and community-driven development that define open source software. Encourage contributions and diverse perspectives that benefit the project's mission. Support respectful and constructive discussions related to the project's development and goals. Recognize that freedom of speech is valued but must align with the project's objectives and not....

I felt so free as to simplify your phrasing and sprinkle some formatting on it to make it more readable and easier to understand. 💪

---

Everyone interacting with this repository is expected to adhere to the following set of rules in order to keep the repository productive and the social interactions civil:

• Embrace and apply the principles that define open source software like transparency and collaboration.

• Encourage contributions and sharing of diverse perspectives that benefit the project's mission

• Respectful and constructive discussions are welcome as long as they are related to the project's development and goals.

• Freedom of speech is valued but must align with the project's objectives and not infringe on the rights or comfort of others.

• Focus on technical or project-related discussions and matters to maintain a neutral environment.

• Keep politics and anything politics-related out since it doesn't add anything to the matter.

Violations of this code of conduct may result in warnings or removal of contributor privileges within the project, solely at the maintainer's discretion.