-
Notifications
You must be signed in to change notification settings - Fork 10
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
Governance document is masculine coded #11
Comments
Thanks! I suppose this comment refers back to #10. |
@kmpaul - do you think we can or should rope in UCAR's Office of Diversity, Equity, and Inclusion to help with some of this? |
Yes. I’ve reached out to them, but they are busy very busy right now. I hope they can offer some help in a week or two. |
same here, I reached out to the office here, but she will reply once she has some time to take a look at the documents. |
I just pinged our Office of Diversity, Equity, and Inclusion a second time. Hopefully they will have some time to help with this soon. |
What was the resolution on this issue? Not to claim it wasn't resolved, but can it be posted here? |
It was resolved by having an open comment period on the draft governance document. During that long time, no one proposed any specific suggestions (in the form of PRs) to the governance document related to this issue. Once the governance document was merged, I closed all outstanding issues on the topic. If you or anyone else would like to propose a specific change, there is a policy for how to do that. I would be happy to reopen the issue if you wish, to indicate that it is still unresolved. |
Given the issue can be resolved by a PR at any time (at least, once we've established the Steering Council), and it is unresolved, I'd like to re-open the issue. The resolution could well be that the DEI offices said the document is fine as-is. Do @kmpaul or @chiaral have any updates from their respective DEI offices? |
The comments that I received from the NCAR Office of DEI were noted (and acted upon) in reference to issue #17. They made no comments on the masculine coding of the document, though. |
@mcgibbon Thank you! |
I am transferring this comment by @mcgibbon from #5 (which is now closed) to a new issue so we don't lose track of it.
The text was updated successfully, but these errors were encountered: