Governance
Symposium operates under the Rust Code of Conduct.
Teams
When a contributor has shown enduring interest in the codebase and made multiple non-trivial changes over time, they are invited to join the Symposium maintainers team:
- Maintainers team —
- Members of this team can review and merge other PRs.
- Members are expected to attend the regular sync meeting.
Overall project leadership is provided by the core team:
- Core team —
- Final decision makers
- Approve releases
- All members of the core team are also members of the maintainers team
Decisions proceed by consensus at each level; if needed, @nikomatsakis acts as BDFL to resolve contentious questions.
PR disclosure policy
We request PRs answer the questions in our PR template regarding AI use, confidence level, and questions.
PR merge policy
We want to keep moving quickly, especially in this early phase, therefore we have established the following review policy:
| Category | Policy |
|---|---|
| New contributors | PRs need review from a maintainer |
| Maintainer team member | PRs should be reviewed by another maintainer before landing |
| Core team member | Review by another maintainer is preferred but not required |
Sync meeting
We hold a regular sync meeting to discuss recent changes, plans, and direction. The meeting is open to all maintainers and contributors. If you’re interested in attending, reach out to a core team member on Zulip.
Releases
Merging a release PR is coordinated among core team members.
Getting involved
The best way to get started is to pick up an issue, open a PR, and join the conversation on Zulip. Landing non-trivial contributions and attending the sync meeting is the path to joining the devs team.