[5.4] Add Contributor Covenant Code of Conduct #19224
Merged
Conversation
This file contains hidden or 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
|
Nice! Should this maybe also go somewhere on the website? |
|
FYI .. we are considering to adopt the same CoC for Symfony symfony/symfony#24896 Generally I feel it would be a good idea to ensure that the entire eco-system gets a CoC and more importantly gets a board to look over enforcement that isn’t tied to one entity. I am not quite sure how the selection process should be, but Laravel is certainly part of the Symfony eco-system, so I would be happy to collaborate on this topic. |
|
NB this was changed in bdf5e28. |
|
ah thx for the info .. didn’t think of checking the current state :) |
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.
While there are no major issues currently outstanding in the Laravel community, having an established Code of Conduct would allow the core team to have concrete guidelines to point to in the event that harassment, or other inappropriate behavior by contributors or commenters becomes an issue.
This code of conduct is a slight modification of the Contributor Covenant Code of Conduct which is used by many prominent open source communities including Ruby on Rails, Elixir, Vue.js, and Yarn.
Currently I have included the suggestion to email Taylor directly for abuse questions, but in the instance that Taylor doesn't want the drama, we could set up an abuse@laravel.com or similar email address to forward to trusted community members.