Page History

...

Note:
All votes, releases, and policy decisions must be made on the mailing list so that they’re properly recorded and archived.

...

Examples in Practice

Scenario	Good Practice
Discussion in Slack about the next release	Post a summary and follow-up actions on `dev@`
Design proposal started in GitHub Discussions	Forward the discussion link and summary to `dev@`
Decisions made during a Zoom sync	Confirm them publicly on `dev@`

...

Communication Channel	Purpose	Transparency	Decisions Allowed?	Follow-Up Needed?
Mailing Lists (`dev@`, `user@`, `private@`)	Main discussion, voting, and recordkeeping	✅ Fully archived	✅ Yes	No
GitHub Discussions	Q&A and design ideas	⚠️ Public but not archived long-term	❌ No	✅ Yes
Chat (Slack, Matrix, etc.)	Quick coordination and Q&A	⚠️ Ephemeral	❌ No	✅ Yes
Video Meetings (Zoom, Jitsi, etc.)	Real-time syncs or planning	⚠️ Limited visibility	❌ No	✅ Yes
Private Email / DMs	Mentoring or sensitive issues	🚫 Not transparent	❌ No	✅ Yes (if appropriate)

...

Mentors should regularly check that:

...