Skip to content
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

Open
rabernat opened this issue Aug 22, 2018 · 11 comments
Open

Governance document is masculine coded #11

rabernat opened this issue Aug 22, 2018 · 11 comments

Comments

@rabernat
Copy link
Member

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.

As it is currently written, [the section on actions of the steering board] is strongly masculine-coded. It risks putting women off applying, but will probably encourage men to apply (paper). We should avoid coding the description of the steering committee to be masculine-biased in pursuit of diversity as is being discussed in #8. If you like I can make particular suggestions on changes to correct this, or @niallrobinson (or someone else) could make some changes focusing on masculine-coded words, phrases, and concepts and increasing the emphasis of the collaborative aspect of Pangeo.

@mcgibbon
Copy link
Contributor

Thanks! I suppose this comment refers back to #10.

@jhamman
Copy link
Member

jhamman commented Aug 30, 2018

@kmpaul - do you think we can or should rope in UCAR's Office of Diversity, Equity, and Inclusion to help with some of this?

@kmpaul
Copy link

kmpaul commented Aug 30, 2018

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.

@chiaral
Copy link
Member

chiaral commented Aug 30, 2018

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.

@kmpaul
Copy link

kmpaul commented Sep 11, 2018

I just pinged our Office of Diversity, Equity, and Inclusion a second time. Hopefully they will have some time to help with this soon.

@mcgibbon
Copy link
Contributor

What was the resolution on this issue? Not to claim it wasn't resolved, but can it be posted here?

@rabernat
Copy link
Member Author

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.

@mcgibbon
Copy link
Contributor

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?

@rabernat rabernat reopened this Oct 18, 2018
@kmpaul
Copy link

kmpaul commented Oct 18, 2018

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
Copy link
Contributor

Thank you @kmpaul, I was unaware of #17 and #20. I'm preparing a PR to address the first point brought up in #17.

@kmpaul
Copy link

kmpaul commented Oct 18, 2018

@mcgibbon Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants