Adopt NumFOCUS code of conduct #669
Conversation
Co-authored-by: Hans Moritz Günther <moritz.guenther@gmx.de>
| <p>Astropy is dedicated to providing a harassment-free community for everyone, | ||
| regardless of gender, sexual orientation, gender identity and expression, disability, | ||
| physical appearance, body size, race, or religion. We do not tolerate harassment | ||
| of community members in any form.</p> |
There was a problem hiding this comment.
Add "ethnicity" and "nation of origin/residence"?
There was a problem hiding this comment.
@hamogu , are we allowed to add wordings that Clara suggested here and still stay opted in? Hope you can advise. Thanks!
There was a problem hiding this comment.
No, we are not. Either we use the NumFOCUS CoC verbatim, or we don't. We can make our own CoC based on NumFOCUS wording, but then it's not the NumFOCUS CoC. The reasons for that is mostly practical: If we want the NumFOCUS CoC working group to do anything for us (e.g. advise on issues, act as backstop if our own ombudsperson is conflicted), then we need to have all the same CoC. The WG simply doesn't have the capacity to keep track of > 50 CoC's with just subtly different rules.
There was a problem hiding this comment.
If we want the NumFOCUS CoC working group to do anything for us (e.g. advise on issues, act as backstop if our own ombudsperson is conflicted), then we need to have all the same CoC. The WG simply doesn't have the capacity to keep track of > 50 CoC's with just subtly different rules.
So that means we will also automatically subscribe to any updates and changes NumFOCUS makes, or opt out of their services again? Seems inevitable, but how would that be done in practice – voting on it again at every update?
There was a problem hiding this comment.
Does every update need a formal vote? Updates will be small. So maybe that can just be discussed on the mailing list and and in issue and if there are no major objections, we just update. If there are any changes on the NumFOCUS side, we probably want to inform our members anyway, so we would send out communication anyway.
| appropriate for Astropy.</p> | ||
|
|
||
| <p>All communication should be appropriate for a professional audience including | ||
| people of many different backgrounds. Sexual language and imagery is not appropriate.</p> |
There was a problem hiding this comment.
Add back in some of our no tool-shaming language from the original Astropy CoC?
There was a problem hiding this comment.
Same as above - but both of those are good suggestions for the next revision of the NumFOCUS Code of Conduct!
|
A few general thoughts: I think one of the things not in the NF CoC that we want to keep from Astropy is the "no code shaming" element. That is one of the things that's particular to our community when we originally wrote the Astropy CoC, and I think it's a thing we can add as an additional i 8000 tem/clause for this. Another one might be the "We pledge to be conscientious of the perceptions of the wider community and to respond to criticism respectfully" item. It might be covered under the NF one? But I'm not sure. I am also concerned about the fact that by linking to the NF CoC it could change at any time indepednent of this page, so we can't be sure it won't change without our consent in the future. I'm not sure if there's a good fix to this, but it is a concern... |
|
From coordination meeting:
|
|
As discussed in a co 8000 ordination meeting 2025 session, I updated this with several commits that reflect the iitems I listed above, as well as adding some examples |
|
Note I think my changes above (from coordination meeting 2025 discussion) addressed one of @ceb8's concerns (the tool-shaming one, which is nowframed as an example) but not the other one. My understanding from @hamogu is that we can't really address the other one here until NF makes the change. @ceb8 , are you ok with leaving that part unaddressed for now? |
|
@eteq sounds good to me. |
Fix astropy/astropy-project#468
Most of the text is copied wholesale from NumFOCUS template, except I replaced "NumFOCUS" with "Astropy" where appropriate.
The only section I significantly modified is the last one, "Who Will Receive Your Report" because Astropy already has an established Ombudsperson and incident handling process prior to adopting NumFOCUS version, and it is not something we can lightly change. The text could use some polishing so suggestions are welcome.
cc NumFOCUS @kamila-NF