Have separate point of contact for Code of Conduct violations

[matthewfeickert]

trafficstars

Summary

From feedback from the pyhf NumFOCUS affiliate project application:

This is a nice project and does almost everything right. I would only recommend not having one of the maintainers as the point of contact for CoC, and having a separate entity/contact point for those issues.

This probably makes the most sense to have another Scikit-HEP developer serve here. It shouldn't just be the Scikit-HEP admin mailing list as the pyhf dev team is all on that, so we'll have to find a volunteer for this and also maybe shape up the Code of Conduct as we mentioned in our application that

We will adopt the NumFOCUS Code of Conduct and extend it to include our existing Code of Conduct "Responsibilities" and "Scope" sections which come from the Contributor Covenant v1.4 (http://contributor-covenant.org/version/1/4).

... It would also be nice for the library to improve its intro sections so that people who are not particle physicists can better understand what the package does.

This is already covered in Issue #2064 (which I hope to get to before 2023).

Documentation Page Link

https://github.com/scikit-hep/pyhf/blob/78c0da043a57c904daf0106fe23a2154ec9abd7e/CODE_OF_CONDUCT.md

Code of Conduct

• [X] I agree to follow the Code of Conduct