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

What CoC should we pick? #3

Open
vil1 opened this issue Jul 3, 2019 · 1 comment
Open

What CoC should we pick? #3

vil1 opened this issue Jul 3, 2019 · 1 comment

Comments

@vil1
Copy link
Member

vil1 commented Jul 3, 2019

Goal

Discuss and decide what Code of Conduct we will use across the organization and how we will enforce it.

Detailed question

We need to pick a CoC for the organization, there are many options to discuss:

  1. Pick the Void CoC (ie. no CoC at all)
  2. Write our own CoC
  3. Fork an existing CoC
  4. Pick an existing CoC and add stuff on top of it
  5. Pick an existing CoC verbatim

In every case (except 1.) I think we also need to discuss a way the CoC will be enforced (not every CoC out there is precise enough on that part).

Expected outcome

One (or multiple competing) pull-request(s) adding a CODE_OF_CONDUCT.md file to this repository.

@vil1
Copy link
Member Author

vil1 commented Jul 3, 2019

I am OK with the Scala Code of Conduct. Beside being a pretty decent CoC, it will help us integrate with the larger Scala community.

That being said, I don't agree with everything stated in this CoC, especially in the Moderation section. I deeply believe that conflicts are to be resolved (what's referred to as moderation in the CoC) in a transparent, public way. I also think that it should be a collective process (y'all are starting to know me, right? 😄), as opposed to being carried out by an, otherwise unspecified, group of people with special powers.

Regardless of the CoC we end up adopting, I think it is will be important to make crystal-clear:

  • That the CoC is an ongoing process. Its goal is to make sure everybody feels safe and welcome in the community, but precautions must be taken in order to prevent it from being "weaponized" and used by some to suppress some others' voices. It will certainly need to be adapted or amended from time to time, depending on each specific situation. It will never be set in stone.
  • The fact that no CoC will ever be precise enough to cover all possible cases, and that therefore, it is inevitable that some borderline cases will come up, requiring the community to collectively interpret the CoC (and possibly amend it), to decide on which side of the line such borderline cases fall.

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

No branches or pull requests

1 participant