Thank you! Yes, now I get it:
- Old WG → new EB
- Old Docs Community → new WG
We had been calling group 1 the “Documentation Community Team” in our monthly meetings, for the community of volunteers:
- Documentation Community Team - Documentation Community documentation
- Monthly Reports Archive - Documentation Community documentation
And group 2 was called the “CPython Documentation Workgroup” for the initial formal group of decision makers:
I think two things might help:
-
For continuity, we keep the name of “Documentation Community Team” (or similar) for the community of volunteers contributing to the documentation (group 1). Avoiding “working group” for this looser group would avoid confusion with the original working group, which had a charter and membership votes and so on. Similarly with PSF Work Groups. Anyone can join in group 1: just turn up and get stuck in.
-
Update the info at CPython Documentation Workgroup - Documentation Community documentation to say the old WG is now the EB (could be mostly deleted and point to this PEP instead). Can of course wait until the PEP is accepted.