Here is an interesting case study in how Debian gives maintainers a lot of autonomy and control, but still has a Technical Committee that can override decisions when they broadly impact the community. This is about decisions in the Debian community about the which command-line program: Debian's which hunt [LWN.net]
Attending: Brian, Fernando, Ana, Zach, Jeremy, Tony, Adam Patterson for the first hour (daylight savings time confusion), then Steve, Sharan and Darian joined.
First part of the meeting: wrap up plans to move forward with the notebook6/7/retrolab plans
How do we prioritize and proceed so the nb7 plan happens in 6 months and not in 3y?
From the Notebook Wednesday meeting - We need a QA team! Many of our users don’t really know how to report any issues.
We need a tactical approach to this problem, with some project management, tracking, Q&A, etc.
Wednesday Notebook team meetings will become coordination/activity meetings for this effort.
Tony volunteered to start some project tracking structure for about a month unable to fully manage beginning to end.
Accessibility is a crucial topic to be addressed in the near term. It will be a positive for the transition: something new that solves an important problem, not only “upgrade so you’re not left behind.” It’s important to find these specific advancements, so we’re not only helping folks keep what they had before, but actually improve their experience as part of the transition.
Idea: could we have a super-pre-release version of nb7 out for the new year?
Goal would be to set up the repo structure, finalize decisions on where issues go, etc, so that we start 2022 with the code structured as necessary for the transition, so teams can begin setting up testing against a known target, etc.
Second part of the meeting: back to drafting governance docs.
PR 103 has votes to pass - pinging last SC members in case they’d like to vote, but we now begin planning its implementation as it seems certain to pass. Vote formally closes on Nov 12, but can be closed earlier as we have 14 yes votes.
Given the urgency and importance of the discussion around the notebook v7 transition, and the positive reception so far to the ideas we put out after @Zsailer’s posts, we figured today we should double down in moving the ProtoJEP a bit closer to a real JEP.
Because we haven’t had time for key Notebook folks to pitch in, we started gently with some draft text on my fork of the JEP repo. If by next Wednesday we see no major concerns, I’ll make a formal PR out of this into the JEP repo itself.
But feedback is welcome already there if anyone is interested, it’s just that we wanted everything to be openly and quickly, while giving key stakeholders a chance to pitch in before a formal JEP was created.
Attending: Tony Fast, Brian Granger, Jason Weill, Piyush Jain, Ana Ruvalcaba, Afshin Darian, Fernando Pérez.
Bootstrapping decision-making bodies for some projects like nbviewer that currently don’t have one. We will ping the Jupyter Distinguished Contributors list in case anyone there would be interested in participating.
Tony Fast will look into whether he can commit some bandwidth to shepherd this type of process for some of the web-facing projects that are now lacking in this regard. He will report back over the next few days.
Jason will look at some of the broken links and make a suggestion/PR to fix the more visible ones for now.
Attending: Jason Weill, Afshin Darian, Brian Granger, Fernando Pérez, Jason Grout, Piyush Jain, Ana Ruvalcaba, Sharan Foga
How to best communicate to the community that subproject councils have
Subprojects are starting to establish steering councils. Suggestion to create Python cookie cutter for Team Compass and socialize it at various subproject meetings. Discussed the possibility of writing a blog post or otherwise announcing the governance remodel in social channels. This process was last shared in November 2021 at the community call.
(Darian/Zach?) This will be communicated with (soon) participation in team meetings to socialize this plan and iterate on the language of the cookie-cutter so that it best serves all subprojects.Reach out to Community Building Committee if we want to explore hosting a recorded Zoom on this topic only.
(Ana)Research permissions in Discourse: can there be a public view with a closed permission to post? How fine grain are notifications - can folks get emails only for the topic they subscribe to?
(Jason) search and replace in governance docs/PRs “decision-making body” → “council” or “subproject council” and put in the relevant PR.