Add Board Roles and Projects pages - #41
Conversation
Following the June 2026 meeting, the board adopted a proactive stance: identify significant documentation projects and lead/shepherd them, rather than only reacting to escalations (while remaining available for the rare big-picture decisions). Add two draft pages and link them in the nav: - /expectations (Board Roles): purpose, the chosen proactive stance, member expectations, and the PEP 732 process for joining. - /projects: rules (every project needs a committed lead; name the challenges; keep the list short), a copy-paste project template, and a parking lot for lead-less ideas. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for pythoneditorialboard ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
|
|
||
| ## How this list works | ||
|
|
||
| - **Every project has a committed lead.** This is not a wish list. A project is |
There was a problem hiding this comment.
When we say that all listed projects must have a committed lead, do we mean that we require all listed projects to have a project manager or just an EB board member associated with it? I like the idea of only requiring listed projects to have an EB member committed to it. That way, potential project leads have something concrete to say yes to.
| ```markdown | ||
| ### <Project name> | ||
|
|
||
| - **Lead:** <name — required; no lead, no listing> |
There was a problem hiding this comment.
We'll need to change this to "EB sponsor" if we decide that having an EB sponsor is enough to start a project.
We could follow this process:
- EB member claims a project
- EB member tries to find a project lead in the community:
- EB member finds a project lead and supports them through the project
- EB member does not find a project lead within a particular amount of time and then commits to being the project lead
That way, when an EB member commits to a project, they are committing to be a project lead if necessary but will first try to recruit a project lead from the community. We would need to set a time limit for recruiting a project lead from the community.
Co-authored-by: Ned Batchelder <ned@nedbatchelder.com>
|
My edits today were done in a meeting with Joanna and Mariatta, and represent all of our agreements. |
Summary
Following the June 2026 meeting, the board adopted a proactive stance: identify significant documentation projects and lead/shepherd them, rather than only reacting to escalations (while remaining available for the rare big-picture decisions). These two draft pages capture that direction and give us a place to track the work.
New pages
/expectations(nav: "Board Roles") — purpose (pointing to PEP 732 rather than restating it), the three stances considered and the chosen proactive one, member expectations, and the PEP 732 process for joining. IncludesTODOs for defining the project-lead commitment and linking the eventual application form./projects— the operating rules (every project needs a committed lead; each names its challenges; keep the list short and prioritized), a copy-paste project template, an empty "Active projects" section with a commented-out datetime-split example seeded from recent meetings, and a "Parking lot" for lead-less ideas.Both are marked Status: Draft at the top. They're linked in the top nav between Changelog and Archives.
Verification
hugo --gc --minifybuilds clean (71 pages, no errors); both pages render and appear in the nav.