search

jupyter / governance

The governance process and model for Project Jupyter
https://jupyter.org/governance/index.html
Creative Commons Zero v1.0 Universal
81 stars 69 forks source link

Add Jupyter Book to list of sub-projects #229

Closed choldgraf closed 5 days ago

choldgraf commented 6 days ago

Questions to answer ❓

Background or context to help others understand the change.

Recently the Jupyter Book project has petitioned to become a Jupyter subproject. See https://github.com/jupyter/enhancement-proposals/issues/122 for an explanation and discussion, and https://github.com/jupyter/enhancement-proposals/pull/123 for the SSC vote. Since the SSC already voted, this PR is for the EC to vote.

A brief summary of the change.

Adopt the Jupyter Book project as a Jupyter subproject. See this document for the comprehensive proposal and a list of repos that would be included in this new subproject.

What is the reason for this change?

Alternatives to making this change and other considerations.

Voting

Vote is expected to close in TBD

EC members/voting checkboxes

The process ❗

The process for changing the governance pages is as follows:

  • Open a pull request in draft state. This triggers a discussion and iteration phase for your proposed changes.
  • When you believe enough discussion has happened, move the pull request to an active state. This triggers a vote.
  • During the voting phase, no substantive changes may be made to the pull request.
  • The Executive Council and Software Steering Council will vote, and at the end of voting the pull request is merged or closed.

The discussion phase is meant to gather input and multiple perspectives from the community. Make sure that the community has had an opportunity to weigh in on the change before calling a vote. A good rule of thumb is to ask several Council members if they believe that it is time for a vote, and to let at least one person review the pull request for structural quality and typos.

choldgraf commented 6 days ago

cc @jupyter/executive-council and @jupyter/software-steering-council

jasongrout commented 6 days ago

@choldgraf - I took the liberty of adjusting your description to use the PR template, so it is consistent with other votes in this repo. Feel free to elaborate or expand on the info, or put a closing date on the vote. Since this has already had a discussion over in the JEP process and with the SSC, I went ahead and put a ballot here. If there are EC members that would like to have more discussion, of course feel free to post a comment here.

Chris, I think minimally a new subproject needs to have a council for making decisions. Do you have one already in place for the new subproject? I'm aware that the executablebooks project has a steering council - would that continue to be the jupyter books council?

choldgraf commented 6 days ago

Hey Jason - thanks for that, I appreciate it!

And yes the council will be the same people to begin (they will be two distinct councils and have the same membership for now, but will likely diverge in the future)

ellisonbg commented 5 days ago

@choldgraf can you clarify more of what you mean by "two distinct councils"? The governance model requires subprojects to have a single council to ensure that there is clear ownership and decision making for the subproject. Councils can use whatever internal structure they want to manage the project, but there should still be a single body that is ultimately responsible for making decisions. For example, the frontends subproject has many different repos and different subsets of people informally tend to work on and make decision and the different repos in the orgs. When major cross-cutting decisions come up though, it is the entire and single council that makes the decision. The EC is more than willing to meet and talk through more of how this would work for Jupyter Book. Excited to see this moving forward :-)

rowanc1 commented 5 days ago

Hi @ellisonbg -- there is only one Steering Council in Jupyter for JupyterBook. @choldgraf was referring to the fact that some portions of the project we are not bringing with us (e.g. there are hundreds of repositories that we created in that project, and not all of them are appropriate to be stewarded by Jupyter). There is more information in the proposal here: https://github.com/jupyter/enhancement-proposals/pull/123#pullrequestreview-2145856036 I hope that helps!

ellisonbg commented 5 days ago

Ahh, thanks for the context that makes complete sense.

fperez commented 5 days ago

Just for the record - I voted in the affirmative quickly b/c I've been working closely with the team for a long time, but obviously we want to make sure any remaining questions are answered. Thanks @ellisonbg for checking in with those questions and @jasongrout for comments too!

I'm personally excited to see this moving forward, thanks all for the years of hard work leading to this!

jasongrout commented 5 days ago

It looks like the vote is already unanimously positive here for the EC, and is unanimously positive for the SSC over at https://github.com/jupyter/enhancement-proposals/pull/123. As such, I think this vote passes and we can merge. Thanks everyone, and welcome Jupyter Book as a subproject!

jasongrout commented 5 days ago

As a process matter, I will invite jupyter-book to join the Jupyter Enterprise org.

jasongrout commented 5 days ago

Also, can you send me the google group address for the Jupyter Book Council email list?

fperez commented 5 days ago

Woot, thanks everyone! 🎉

Special thanks to @rowanc1 @choldgraf for a huge amount of sustained work over the years to bring us here. I'm excited about the good that will come out of this now being 💯 part of Jupyter!