Update CoC from Contributor Covenant 1.4 to 2.0 #418
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ljharb
approved these changes
Dec 3, 2019
molant
approved these changes
Dec 3, 2019
tobie
approved these changes
Dec 4, 2019
|
FWIW Node.js will need to update its code of conduct too - I can PR this change: https://github.com/nodejs/admin/blob/master/CODE_OF_CONDUCT.md |
knolleary
approved these changes
Dec 5, 2019
|
I personally think we might want to consider having the full text here. Good not to force folks to go to a third party we have no control over for this. |
codeekage
approved these changes
Jan 7, 2020
|
Rebased to account for #413 being merged. The upstream CoC v2.0 is now inlined. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 2.0 of our upstream code of conduct, the Contributor Covenant, has been released. The project's changelog has not (yet) been updated, but by manual comparison the update appears to bring two major updates:
All other changes appear to be superficial.
This PR updates our references to "v1.4.1" of the Contributor Covenant to refer to its "v2.0" instead. The covenant claims to follow semver, but does not appear to actually publish enumerated patch releases separately; hence dropping the patch number.
This PR is related to #413, which makes our references to the covenant's version more explicit. If/once one of these is merged, the other will need to be amended.