|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "February 2024 Leadership Council Update" |
| 4 | +author: Leadership Council |
| 5 | +team: Leadership Council <https://www.rust-lang.org/governance/teams/leadership-council> |
| 6 | +--- |
| 7 | + |
| 8 | +Hello again from the Rust Leadership Council! |
| 9 | +We wanted to share an update on what the Council has been working on since [our last update][update]. |
| 10 | + |
| 11 | +[update]: https://blog.rust-lang.org/inside-rust/2023/11/13/leadership-council-update.html |
| 12 | + |
| 13 | +## Accomplishments so far |
| 14 | + |
| 15 | +### Project Structure |
| 16 | + |
| 17 | +The Council has agreed to make the [Release team] a subteam of the [Infra team] in [RFC #3533]. |
| 18 | +[Ryan Levick] has stepped off the Council as part of this transition, and we thank him for the very significant help he has provided. |
| 19 | +Ryan has been a part of the Core team since 2021, and was part of the group that designed and created the Leadership Council, and has earned a well deserved break. |
| 20 | + |
| 21 | +[Release team]: https://www.rust-lang.org/governance/teams/infra#Release%20team |
| 22 | +[Infra team]: https://www.rust-lang.org/governance/teams/infra |
| 23 | +[RFC #3533]: https://rust-lang.github.io/rfcs/3533-combine-infra-and-release-teams.html |
| 24 | +[Ryan Levick]: https://github.com/rylev |
| 25 | + |
| 26 | +We created the [Project Structure Committee] to help drive the discussion about the "shape" of the Rust project, and to define the goals and responsibilities of that committee. |
| 27 | +There is not much progress to report at this time, as the group is still trying to get a grasp on how to approach it. |
| 28 | +In the meantime, [Eric Huss] created a [org visualizer] to visually see the entire scope of the project. |
| 29 | + |
| 30 | +There is an [untracked people] document where we are exploring people in the project who are in an ambiguous state, or not properly tracked in the team database. |
| 31 | +Additionally, [Jakub Beránek] has done fantastic work in updating the team database to make sure all repositories are tracked and tied to teams correctly, submitting well over [100 PRs][kobzol-prs], and improving the infrastructure that manages the teams. |
| 32 | + |
| 33 | +[untracked people]: https://hackmd.io/@rust-leadership-council/Bk6ge9Xu6 |
| 34 | +[Eric Huss]: https://github.com/ehuss |
| 35 | +[Project Structure Committee]: https://github.com/rust-lang/leadership-council/blob/main/committees/project-structure.md |
| 36 | +[org visualizer]: https://ehuss.github.io/org-chart/org-chart.html |
| 37 | +[kobzol-prs]: https://github.com/rust-lang/team/pulls?q=is%3Apr+is%3Aclosed |
| 38 | + |
| 39 | +There is a [new policy][team-policy] for management of the [Rust Team Database], which records the list of all teams, members, repositories, and their permissions. |
| 40 | +Additionally, the [team-repo-admins] ([Mark-Simulacrum], [Ryan Levick], and [Jack Huey]) are a group of people responsible for approving changes to the team database under that policy. |
| 41 | + |
| 42 | +[team-repo-admins]: https://github.com/rust-lang/team/blob/master/teams/team-repo-admins.toml |
| 43 | +[Mark-Simulacrum]: https://github.com/Mark-Simulacrum |
| 44 | +[Ryan Levick]: https://github.com/rylev |
| 45 | +[Jack Huey]: https://github.com/jackh726 |
| 46 | +[Rust Team Database]: https://github.com/rust-lang/team |
| 47 | +[team-policy]: https://github.com/rust-lang/rust-forge/pull/707 |
| 48 | + |
| 49 | +### Wrapping up Project Director Elections |
| 50 | + |
| 51 | +[Eric Holk][eholk] created a [retrospective of the Project Director elections][retro]. |
| 52 | +This gathers the lessons we learned during the process in October and ideas to improve the process in the future. |
| 53 | +We have agreed to hold the next Foundation Project Director election in September 2024 for the two seats of Ryan Levick and Mark Rousskov, which we hope will run more smoothly based on this review. |
| 54 | + |
| 55 | +[eholk]: https://github.com/eholk |
| 56 | +[retro]: https://github.com/rust-lang/leadership-council/blob/main/reports/project-director-elections/2023-project-director-elections-retrospective.md |
| 57 | + |
| 58 | +### Google Summer of Code |
| 59 | + |
| 60 | +We agreed that the project should explore the possibility of participating in [Google Summer of Code][gsoc], thanks to the efforts of [Jakub Beránek] and [Jack Huey], along with the Foundation agreeing to help with submitting the application. |
| 61 | +Proposals and coordination are happening in the [google-summer-of-code repo][gsoc-repo]. |
| 62 | +More information about this will be shared in the future if our application is approved. |
| 63 | + |
| 64 | +[gsoc]: https://summerofcode.withgoogle.com/ |
| 65 | +[gsoc-repo]: https://github.com/rust-lang/google-summer-of-code |
| 66 | +[Jakub Beránek]: https://github.com/kobzol |
| 67 | +[Jack Huey]: https://github.com/jackh726 |
| 68 | + |
| 69 | +### Leads Summit |
| 70 | + |
| 71 | +We agreed to have a Leads Summit in London, UK just before RustNation in March. |
| 72 | +This is an opportunity for project leads to meet in person, to discuss project-wide goals, and to develop leadership skills. |
| 73 | + |
| 74 | +### Council Representative Appointments |
| 75 | + |
| 76 | +We have agreed that the next Council Representative appointments will happen in March. |
| 77 | +We are in the process of finalizing which half of teams will be going through the appointment process, and will follow up soon with more details. |
| 78 | + |
| 79 | +### Additional Items |
| 80 | + |
| 81 | +And a few minor items: |
| 82 | + |
| 83 | +* Approved TWiR to be added to the <https://social.rust-lang.org/> Mastodon service. The infra team is working on getting this finalized. |
| 84 | +* The [RustConf Steering Committee RFC][rfc-3549] had various discussions among the Council, but it was ultimately closed by the author to reconsider how this will be approached in the future. |
| 85 | +* [issue #22][issue-22]: The Council formally adopted the T-core RFCs ([RFC#2872] [RFC#3259] [RFC#3339]), and has begun work to move those forward. |
| 86 | +* [issue #60][issue-60]: The Council approved a policy for handling [private meeting minutes]. |
| 87 | +* Permissions for the [Rust Forge] are now formally written down ([PR #725][forge-725]), indicating that the infra team is responsible for it, and any Rust team, working group, or project group may post their content on it. |
| 88 | +* Thanks to [David Tolnay], the team representation of the Council is now displayed on the [website][lc-gov]. |
| 89 | + |
| 90 | +[Rust Forge]: https://forge.rust-lang.org/ |
| 91 | +[forge-725]: https://github.com/rust-lang/rust-forge/pull/725 |
| 92 | +[rfc-3549]: https://github.com/rust-lang/rfcs/pull/3549 |
| 93 | +[issue-22]: https://github.com/rust-lang/leadership-council/issues/22 |
| 94 | +[issue-60]: https://github.com/rust-lang/leadership-council/issues/60 |
| 95 | +[RFC#3339]: https://github.com/rust-lang/rfcs/pull/3339 |
| 96 | +[RFC#3259]: https://github.com/rust-lang/rfcs/pull/3259 |
| 97 | +[RFC#2872]: https://github.com/rust-lang/rfcs/pull/2872 |
| 98 | +[private meeting minutes]: https://github.com/rust-lang/leadership-council/blob/main/procedures/synchronous-meetings.md#private-minutes |
| 99 | +[lc-gov]: https://www.rust-lang.org/governance/teams/leadership-council |
| 100 | +[David Tolnay]: https://github.com/dtolnay |
| 101 | + |
| 102 | +## Ongoing work |
| 103 | + |
| 104 | +There are various efforts underway on projects that have had significant discussions since the last update, but have not concluded with any decisions, yet. |
| 105 | +They are: |
| 106 | + |
| 107 | +* Planning around the Foundation's upcoming budget. |
| 108 | +* Investigation and discussions around the Rust trademarks, and what if any policy changes we should enact. |
| 109 | +* Work on defining and clarifying affiliation limits and the substitute policy, for both the Foundation Project Directors ([PR #61]) and the Council itself ([issue #27]). |
| 110 | + There is a [work in progress][affiliation-limits] exploring this. |
| 111 | +* Investigating process for managing external requests for the council via ZenDesk. |
| 112 | + |
| 113 | +[affiliation-limits]: https://hackmd.io/@rust-leadership-council/BJMOxfP5p |
| 114 | +[PR #61]: https://github.com/rust-lang/leadership-council/pull/61 |
| 115 | +[issue #27]: https://github.com/rust-lang/leadership-council/issues/27 |
| 116 | + |
| 117 | +## Meeting Minutes |
| 118 | + |
| 119 | +We publish minutes from all Council meetings to the [Leadership Council repo][minutes]. |
| 120 | +Links to the minutes since our last update are: |
| 121 | + |
| 122 | +* [November 10, 2023](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2023-11-10.md) |
| 123 | +* [December 8, 2023](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2023-12-08.md) |
| 124 | +* [January 5, 2024](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2024-01-05.md) |
| 125 | +* [January 19, 2024](https://github.com/rust-lang/leadership-council/blob/main/minutes/sync-meeting/2024-01-19.md) |
| 126 | + |
| 127 | +[minutes]: https://github.com/rust-lang/leadership-council/tree/main/minutes |
0 commit comments