Note: further conversation needs to happen regarding possible alternate
ways to handle the issues it was intended to address.

It's important to firmly establish the authority of the base team. The
guiding principles to which the base team holds itself are out-of-scope
for this document and better served elsewhere.

You have to establish what the teams are before you can establish how
they are maintained

They don't need to be here for bootstrapping and can be added as Base
team's policies (and thus applying to everyone).

This also makes making team-specific pages easier

Faster bootstrap, easier to move to per-team pages later

They can be re-added later if needed, and arguably should be in per-team
pages.

This time, developer def is moved after member def.

Avoids an unnecessary forward reference.

In some cases, it may be obvious that a project-wide vote is needed.
Make that possible to acheive faster.

1. Voting, conflicts, etc are not mentioned elsewhere.
2. Rename Core -> Packaging
3. Rename Packaging -> Packaging: Community
4. Add "Base" as an administrative team

You need an extra space between h1 and content

They should also follow policies and the CoC.

This way policies can go into a separate section.

Still stay in single-module.