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

[Docs]: Adopt OpenJS Code Of Conduct #14899

Closed
bensternthal opened this issue Feb 15, 2024 · 3 comments · Fixed by #14914
Closed

[Docs]: Adopt OpenJS Code Of Conduct #14899

bensternthal opened this issue Feb 15, 2024 · 3 comments · Fixed by #14914
Assignees

Comments

@bensternthal
Copy link
Contributor

Page(s)

https://github.com/jestjs/jest/blob/main/CODE_OF_CONDUCT.md

Description

This issue tracks adopting the OpenJS code of conduct policy. This is part of the OpenJS onboarding checklist.

@bensternthal
Copy link
Contributor Author

@SimenB I'd like to help draft this and create the PR. Do you know if Jest is planning to opt-in to manage CoC violation reports directly or will this fall to the OpenJS CoC Team? Either way works!

@bensternthal bensternthal self-assigned this Feb 16, 2024
@SimenB
Copy link
Member

SimenB commented Feb 19, 2024

If we could route it all to OpenJS, that would be ideal!

bensternthal added a commit that referenced this issue Feb 21, 2024
This PR adopts the OpenJS code of conduct. It is based on https://github.com/jquery/jquery/blob/main/CODE_OF_CONDUCT.md

- Fixes #14899
- Supersedes #14784
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants