-
Notifications
You must be signed in to change notification settings - Fork 12.2k
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
Update CODE_OF_CONDUCT.md #15677
base: master
Are you sure you want to change the base?
Update CODE_OF_CONDUCT.md #15677
Conversation
How did you envision writing "unacceptable" would be understood? |
This project is using Contributor Covenant code of conduct. It would be best to discuss changes upstream: https://github.com/ContributorCovenant/contributor_covenant |
There is a spelling error in here, in what is insult added to injury. Get rid of the CoC instead. |
@jtojnar The premise of adding an invariant section saying "unacceptable" is the same as any other time it is done, only now worse as a result of diverging from the original. How well do you think an appeal to logic is going to go over at the Covenant CoC repo? The scope of interpretation is a wide as the thinking behind how it supposedly works is wishful. Sadly that isn't how it actually works, and its authoritarian appeal is to the contrary crystal clear, consequently also as a by-product of its vagueness.
Clear as mud.
This is actually clear on the assumption "private" is understood, though if that isn't clear, it doesn't really need pointing out, nor did it originally… Much less in something to pledge allegiance to.
Where it applies is then established, but then:
Someone didn't notice that it already said "instances of unacceptable behavior", and now there is a PR to add a third instance, where its magic is applied to "username" and "commit message" in "Update CODE_OF_CONDUCT.md". From the contribution guidelines:
There is (maybe) something to the intention of not piling on here, but this is all change and no clear intent.
That shouldn't be "devlopers", and "gain or devote" is as unqualified as its relation to "welcoming". We continue in the theme of things from what is already in the CoC:
is clear, however ill devised it is. The contact form is e-mail without PGP(?)
And then the icing on the cake
Where it is vague isn't in being an instrument to establish a higher domain of power, but it is forever vague in limiting it. |
As a newcomer to this repo, why is this PR still open? shouldn't it just get closed/rejected? |
@mantism Maybe someone actually read the original that this breaks the licensing terms of, and understood it in terms of my critique. There is nothing wrong with rules, so why this has to be called a CoC is beyond me. Harassment is of course illegal already, and there are rules nobody seems to read on GitHub already.
This is professionalism over community, and there the authoritarian nature of CoCs shows its true colours. If someone can reasonably assume what is expected in a professional environment, how is that in any way different when it is in writing from reasonably expecting what to get reprimanded or banned for when it is not? Strip away more and it would be a mantra. Bloat isn't good, and does nothing better. |
I understand that:
I understand that it will not be merged and I will not be listed as a contributor on this project.