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

Next phase of CZI EOSS Diversity and Inclusion grant for JupyterHub community #709

Open
KirstieJane opened this issue Feb 20, 2024 · 2 comments

Comments

@KirstieJane
Copy link
Contributor

Proposed change

Kirstie Whitaker (@KirstieJane) and Alexandra Araujo Alvarez (@AlexandraAAJ) to take forward the work that was started in 2022 investigating pathways to increase diversity in the JupyterHub contributor community.

The workplan breaks down to broadly 3 goals:

  • Develop a community engagement strategy and identify current blockers to contributor participation
  • Refresh the Team Compass as a community development guide
  • Develop and adapt training for community members to mentor new contributors
  • Embed inclusive practices in the JupyterHub community

We've put together a report to CZI that includes the proposed adjustments to the original workplan in this google doc: https://docs.google.com/document/d/1pSU9kG_XDOSTF4JcbIt18hep1rCHIjuUYuYi5mg0q-0/edit?usp=sharing.

Alternative options

@choldgraf explored two options of keeping @sgibson91 in post and closing the project. Keeping Sarah working as Community Strategic Lead was contributing to significant burnout and closing the project would miss a huge opportunity to consolidate the great work that is ongoing in the JupyterHub community.

Other options very welcome!

Who would use this feature?

Initially the work will be focused on working with the JupyterHub Council (https://jupyterhub-team-compass.readthedocs.io/en/latest/team/index.html) but the impact of the work should support everyone in the community, and reinforce the sustainability of the project.

(Optional): Suggest a solution

We've written up a project plan in this google doc: https://docs.google.com/document/d/1pSU9kG_XDOSTF4JcbIt18hep1rCHIjuUYuYi5mg0q-0/edit?usp=sharing.

Please leave comments here or in the document (rather than editing the text directly) 🙏

In particular it would be great to hear from the community what they think of this broad budget breakdown:

Role Cost Notes
Turing Way - Kirstie Whitaker $37,749.4 Salary
Turing Way Support - Alexandra Araujo Alvarez $31,278.13 Salary
Leadership Development Design & Consultancy $60,000.00 Subject to quotations
Stuart G - Technical writing $20,000 Previously worked with for The Turing Way
Leadership Convening Meetings $65,000 2 x international meetings, each with professional facilitation
Miscellaneous $27,5000 Workshops and/or contingency funds
Copy link

welcome bot commented Feb 20, 2024

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@choldgraf
Copy link
Member

choldgraf commented Feb 20, 2024

Just wanted to say thanks so much to @KirstieJane and the Turing Institute team for helping to design the plan for the final phase of the grant, and to @sgibson91 for serving in the Community Strategy Lead role for the first phase. I think we've learned a lot already, and I'm hopeful we can continue to do so with the Turing team's leadership.

If anybody on the team has questions for me or would like to discuss something regarding the grant and plan, I'm happy to talk! Just send me a message at (my github handle at gmail) if you don't know how to get in touch otherwise!

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

No branches or pull requests

2 participants