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
{{ message }}
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
This PR adds a list of the project-specific CoC reporting emails to our code of conduct, closing the loop for projects that wish to reference our code of conduct by providing a pointer to the URL https://code-of-conduct.openjsf.org.
For additional context, I've just pushed a commit that documents the available reporting addresses for Impact, Growth, At Large and Incubating projects. As you can see there are ~16 projects with no explicit reporting email address. Projects fall into a number of cases:
The CoC reference points to this document, but no reporting address is provided.
The Code of Conduct file or reference was not found.
The Code of Conduct file points to the old JS Foundation Code of Conduct, or a corporate contributor's CoC.
A CoC file is present but the reporting path is not.
IMO items 2-4 above can and should be addressed as each project completes its onboarding tasks; this PR would provide the lowest friction way for smaller projects to keep their CoCs up-to-date and make sure their reporting paths are discoverable.
@jorydotcom commented on Tue Apr 07 2020
This PR adds a list of the project-specific CoC reporting emails to our code of conduct, closing the loop for projects that wish to reference our code of conduct by providing a pointer to the URL https://code-of-conduct.openjsf.org.
@jorydotcom commented on Wed Apr 22 2020
For additional context, I've just pushed a commit that documents the available reporting addresses for Impact, Growth, At Large and Incubating projects. As you can see there are ~16 projects with no explicit reporting email address. Projects fall into a number of cases:
IMO items 2-4 above can and should be addressed as each project completes its onboarding tasks; this PR would provide the lowest friction way for smaller projects to keep their CoCs up-to-date and make sure their reporting paths are discoverable.
@jorydotcom commented on Tue May 05 2020
Transferring this issue to the new / code-of-conduct repo
The text was updated successfully, but these errors were encountered: