-
Notifications
You must be signed in to change notification settings - Fork 319
Council December 2025 update #1761
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Kobzol
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great post! A lot of stuff has been happening recently :)
|
|
||
| As you can see from the many links above, the work of the Council happens mostly in public on GitHub issues posted in [our repository](https://github.com/rust-lang/leadership-council/issues). The items on our meeting agendas are drawn from these. After discussing an item, we summarize that discussion and any shared [rationales](https://aturon.github.io/tech/2018/05/25/listening-part-1/) on the issue. When we make decisions, we propose on the issue a "final comment period" (FCP), and as with all FCPs in the Project, we're interested in and review any feedback that people have before or during this final comment period. | ||
|
|
||
| To follow our work in real time, watch our repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Watching the repo is IMO not all that useful, although it definitely helps. I would mention the new Zulip stream where Tomáš posts meeting minute summaries, I think that works well for following our work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
jamesmunns
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for writing this up!
|
|
||
| ### Shape of Rust | ||
|
|
||
| We have implemented changes to the team structure to further clarify the status of teams in the Launching Pad. In particular: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Full list of teams that have been moved or archived:
| Team | Tracking Issue | Outcome? |
| :--- | :--- | :--- |
| Community Content Team | https://github.com/rust-lang/leadership-council/issues/129 | Archived |
| Community Rustbridge Team | https://github.com/rust-lang/leadership-council/issues/132 | Archived |
| Book Team | https://github.com/rust-lang/leadership-council/issues/123 | Moved to lang-docs |
| Docker Team | https://github.com/rust-lang/leadership-council/issues/124 | Moved to T-Infra |
| Async WG | https://github.com/rust-lang/leadership-council/issues/137 | Moved to T-Lang |
| Rust By Example WG | https://github.com/rust-lang/leadership-council/issues/139 | Moved to lang-docs |Also the ones that are confirmed as staying in the launching-pad:
| Team | Tracking Issue | Outcome? |
| :--- | :--- | :--- |
| This Week In Rust | https://github.com/rust-lang/leadership-council/issues/125 | Stay in Launching Pad |
| Community Survey Team | https://github.com/rust-lang/leadership-council/issues/133 | Renamed, Stay in Launching Pad |
| Security Response WG | https://github.com/rust-lang/leadership-council/issues/141 | Renamed, Stay in Launching Pad |
| Triage WG | https://github.com/rust-lang/leadership-council/issues/142 | Renamed, Stay in Launching Pad |
@rust-lang/leadership-council Please take a look and help with clarifying anything here or adding anything that is missing.
Rendered