Jupyter Governance Refactoring

[choldgraf]

Project Lead: Chris Holdgraf (@choldgraf)

Mentor: Meag Doherty (@EmDohh)

Welcome to OL6, Cohort E! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Leadership Training :tada:.

---

Before Week 1 (Sept 13): Your first mentorship call

• [ ] Complete the OLF self-assessment (online, printable). If you're a group, each teammate should complete this assessment individually. This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
• [ ] Make sure you know when and how you'll be meeting with your mentor.

Before Week 2 (Sept 20): First Cohort Call (Open by Design)

• [ ] Complete Assignment 'Write Your Vision or Mission Statement'. Leave a comment on this issue with your draft vision statement & be ready to share this on the call.
• [ ] Watch 'Mozilla & Working Open'.
• [ ] Check the Syllabus for notes and connection info for all the cohort calls.

Before Week 3 (Sept 27): Mentorship call

• [ ] Look up two other projects and comment on their issues with feedback on their vision statement.
• [ ] Complete your Open Canvas (instructions, canvas). Comment on this issue with a link to your canvas.
• [ ] Start your Roadmap. Comment on this issue with your draft Roadmap.

Before Week 4 (Oct 4): Cohort Call (Build for Understanding)

• [ ] Look up two other projects and comment on their issues with feedback on their open canvas.
• [ ] Pick an open license for the work you're doing during the program.
• [ ] Use your canvas to start writing a README, or landing page, for your project. Link to your README in a comment on this issue.

This issue is here to help you keep track of work during the first month of the program. Please refer to the OL6 Syllabus for more detailed weekly notes and assignments past week 4.

[Carreau]

Well @choldgraf is at a conference, so filling in for him.

https://paper.dropbox.com/doc/Mission-Statement--ANOnSGCWMeVS1hFHyfVIJAnrAQ-fNmVOnXrXCfl9dOBzOHIR

Who with

We are three member of the Jupyter Project (Chris Holdgraf, Damian Avila, Chris Holdgraf) and we may consult with other member of our community.

What

Want to restructure the current governance of the Jupyter Project

Who for

Both for our users and contributors (to be more transparent, welcoming, open), and for the current member of the governance team.

Why

In the past few years the project has grown from a handful of members, that were all highly involved and mostly technical, to a few dozens with different levels of commitment and skills. The structure of Project governance is not suitable for its size, and does not make enough consideration for people that have non-code-based impact on the project.

Summary

I am working with other member of the Jupyter project, to restructure its governance in order to better match the size of the project, empowers its users, and recognize their contribution equally regardless of the domain.

[Carreau]

We are doing this in the open, as we have a clear intention to share, want to encourage our community to contribute, and have them be in control of the tools they use and love.