This aligns us with many projects in the scientific Python ecosystem and provides a clear, externally supported framework for maintaining a welcoming and inclusive community.
Adopting the NumFOCUS version would formalise this and allow us to draw on their guidance and support when handling any Code of Conduct matters.
What this means:
The NumFOCUS Code of Conduct would apply across all SunPy spaces
Our Steering Committee and Ombudsperson will handle these matters regarding any violation of the Code of Conduct
We would be able to draw on NumFOCUS guidance and support when handling any issues
We are asking project custodians to vote on this proposal. If there are no major concerns, we will proceed to a formal vote shortly. This will be updated on our webpage, see this open PR for details: Code of Conduct — sunpy.org
I’m confused by what exactly is meant by adopting the NumFOCUS CoC. According to the NumFOCUS CoC, the NumFOCUS CoC Working Group (WG) formulates the response to a CoC violation and executes that response. There does not appear to be any provision for the involvement of our Steering Committee or our Ombudsperson, much less deferring to them to “handle these matters”.
There is a statement in the NumFOCUS CoC that the WG has “an advisory role toward other Code of Conduct Committees in the NumFOCUS ecosystem”, but that reads to me as saying that the WG will assist NumFOCUS projects that are using a non-NumFOCUS CoC. It doesn’t read to me as allowing the WG to not follow through on its charter for handling reported violations of the NumFOCUS CoC.
In other words, it sounds like we are not literally adopting the NumFOCUS CoC. It seems weird to say that the NumFOCUS CoC is our CoC but then not follow its stated violation-resolution procedure.
So I think the NumFOCUS CoC page is confusing as it deals with two different uses. NumFOCUS own events and projects where the WG execute the sanctions and they are binding and affiliated project spaces and events where the WG has an advisory/supportive capacity.
In the Definitions section way down the bottom
The group will also have an advisory role toward other Code of Conduct Committees in the NumFOCUS ecosystem, as well as a supportive role for NF
and then in the Consequence section
Working Group or a Code of Conduct Event Response Team may recommend or take any action
which seem like deliberate wording.
Also this is the exact model astropy has report go direct to NumFOCUS but the process involves the ombudsperson and the recommendation go to the ombudsperson and their coordination committee.
So as long as our process is clearly documented similar to Astropy it should be ok?
My understanding of how this process will work (and we will reconsider if this turns out to not be the case) is:
We adopt the wording of the NumFOCUS CoC.
The first point of contact for someone who wants a potential violation investigated is the NumFOCUS CoC WG form.
The NumFOCUS CoC WG do the initial investigation in collaboration with us and then make recommendations to the Steering Committee and Ombudsperson about what actions to take.
The Steering Committee and Ombudsperson take whatever actions they deem appropriate based on the recommendations.
The way that Astropy’s CoC is written, the Astropy Ombudsperson and Coordination Committee are not involved in the evaluation of the incident and the generation of the recommended actions. In fact, Astropy’s CoC explicitly notes that the NumFOCUS CoC WG makes decisions independently from Astropy. I think that such a relationship is consistent with the NumFOCUS CoC as written.
The words in the initial post (“Our Steering Committee and Ombudsperson will handle these matters”) and in @Cadair’s workflow (“in collaboration with us”) indicate a different relationship with the NumFOCUS CoC WG. If our relationship is in fact going to be analogous to Astropy’s, we need to be accurate with descriptions.
This is a little less than I’d like, so I would encourage people to express their concerns here and we can incorporate any feedback before we move further along this process.