You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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:
Void
CoC (ie. no CoC at all)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.The text was updated successfully, but these errors were encountered: