You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[@PLeVasseur](https://github.com/PLeVasseur)and [@traviscross](https://github.com/traviscross/) created the [Content team](https://www.rust-lang.org/governance/teams/launching-pad#team-content) ([leadership-council#206](https://github.com/rust-lang/leadership-council/issues/206)). The team is responsible for creating content that is of interest and benefit to the Rust Project and its community. This potentially includes blog posts, videos, podcasts, and other forms. The team will be talking with experts within the Project and the community to share their knowledge and experience using Rust.
19
+
Pete LeVasseur and TC created the [Content team](https://www.rust-lang.org/governance/teams/launching-pad#team-content) ([leadership-council#206](https://github.com/rust-lang/leadership-council/issues/206)). The team is charged with producing publishable content that is of interest and benefit to the Rust Project and its community including blog posts, videos, podcasts, etc. The team is talking with people in the Project and the community to share their knowledge and experience, and most immediately, the team has been organizing interviews that will be recorded at RustConf.
21
20
22
-
We are looking forward to what they create, which should be shared soon.
21
+
We are looking forward to soon seeing what they produce.
23
22
24
23
### All-hands 2026
25
24
26
-
The Council approved to schedule the 2026 All-Hands event ([leadership-council#192](https://github.com/rust-lang/leadership-council/issues/192)). This event is an opportunity for Project members to meet in person to to collaborate on the future of Rust. The event is scheduled to occur again with [RustWeek 2026](https://2026.rustweek.org/) in The Netherlands on May 21-23. More information will be coming soon.
25
+
The Council approved the 2026 All-Hands event ([leadership-council#192](https://github.com/rust-lang/leadership-council/issues/192)). This event is an opportunity for Project members to meet in person to to collaborate on the future of Rust. The event is scheduled to occur again with [RustWeek 2026](https://2026.rustweek.org/) in The Netherlands on May 21-23. More information will be coming soon.
27
26
28
27
### Additional items
29
28
@@ -32,7 +31,7 @@ And a few other items:
32
31
- Coordinated with the mods team on the creation of the venue mods team, which is responsible for moderating venues such as GitHub and Zulip. [team#1874](https://github.com/rust-lang/team/pull/1874)
33
32
- Approved the renewal of the compiler ops contract. [leadership-council#181](https://github.com/rust-lang/leadership-council/issues/181)
34
33
- Approved substitutes for the July and August Foundation board meetings. [leadership-council#187](https://github.com/rust-lang/leadership-council/issues/187)[leadership-council#194](https://github.com/rust-lang/leadership-council/issues/194)[leadership-council#201](https://github.com/rust-lang/leadership-council/issues/201)
35
-
- Coordinated with the RustConf organizers on how to distribute free or reduced-price tickets for project members. [leadership-council#190](https://github.com/rust-lang/leadership-council/issues/190)
34
+
- Coordinated with the RustConf organizers on how to distribute free or reduced-price tickets for Project members. [leadership-council#190](https://github.com/rust-lang/leadership-council/issues/190)
36
35
- Added [@jieyouxu](https://github.com/jieyouxu) to the team-repo-admins, who are responsible for updating the Rust team memberships and resources. [leadership-council#205](https://github.com/rust-lang/leadership-council/issues/205)
37
36
- Coordinated with the infra team to set up the email alias for `[email protected]` as the contact address of the rust-lang GitHub organization. [leadership-council#202](https://github.com/rust-lang/leadership-council/issues/202)
38
37
- Coordinated with the social media team to approve the creation of an official LinkedIn page for Rust, now up at <https://www.linkedin.com/company/rust-lang/>. [leadership-council#208](https://github.com/rust-lang/leadership-council/issues/208)
@@ -43,7 +42,7 @@ And a few other items:
43
42
There are various efforts underway on projects that have had significant discussions since the last update, but have not concluded with any decisions, yet.
44
43
They are:
45
44
46
-
### Shape of Rust
45
+
### Rust Society
47
46
48
47
[@JamesMunns](https://github.com/jamesmunns) has continued to develop the concept of the "Rust Society". The Rust Society will be an organizational structure for user groups (commonly called "Special Interest Groups", "Working Groups", etc. in other organizations) outside of the Rust Project, but administrated by the Rust Project via a new "T-Society-Admins" subteam of the Launching Pad.
49
48
@@ -53,26 +52,31 @@ See the latest [proposed charter](https://github.com/rust-lang/leadership-counci
53
52
54
53
### Foundation
55
54
56
-
There have been continual discussions with the Foundation on various topics. We are excited to welcome [@LoriLorusso](https://github.com/LoriLorusso), who just started as the Foundation's new [Director of Outreach](https://rustfoundation.org/media/welcoming-lori-lorusso-the-rust-foundations-new-director-of-outreach/). She has hit the ground running, and has been helping with coordinating with the Foundation and planning upcoming projects.
55
+
There have been continual discussions with the Foundation on various topics. We are excited to welcome [Lori Lorusso](https://github.com/LoriLorusso), who has started as the Foundation's new [Director of Outreach](https://rustfoundation.org/media/welcoming-lori-lorusso-the-rust-foundations-new-director-of-outreach/). She hit the ground running and has been helping to coordinate with the Foundation and plan upcoming projects.
57
56
58
-
We have been discussing with the Foundation the possibilities of providing a budget for [project priorities](https://github.com/rust-lang/leadership-council/issues/183) in 2026. The funding provided by Microsoft in 2024 is nearly spent, and we are looking for ways that we can continue some of the projects afforded by that grant, such as the travel grants, all-hands support, project grants, and the contracted positions.
57
+
We have been discussing with the Foundation the possibilities for continuing the budget for [project priorities](https://github.com/rust-lang/leadership-council/issues/183) in 2026. For 2024 and 2025, this budget was made possible by a generous unrestricted grant from Microsoft. We are looking for ways that we can continue this budget so as to continue important programs such as travel grants, the all-hands, project grants, [program management](https://github.com/rust-lang/leadership-council/issues/151), and [compiler operations](https://github.com/rust-lang/leadership-council/issues/181).
59
58
60
-
We discussed the condition of the travel grant budget of 2025 ([leadership-council#182](https://github.com/rust-lang/leadership-council/issues/182)). Many project members used most of their $2,000 limit during the all-hands earlier this year, and we had concerns that members would not be able to attend other events like RustConf. Ultimately we decided to keep with the current policy, and will be working on figuring out what our possible option might be for funding 2026.
59
+
We discussed the condition of the 2025 travel grant budget ([leadership-council#182](https://github.com/rust-lang/leadership-council/issues/182)). Many Project members used most of their $2,000 limit during the all-hands earlier this year, and we had concerns that members would not be able to attend other events like RustConf. Ultimately we decided to keep with the current policy and will be working on figuring out what our possible option might be for funding this in 2026.
61
60
62
-
Finally, on the top of our minds is the [Foundation three-year strategy](https://github.com/rust-lang/leadership-council/issues/197). We have a keen interest in working with the Foundation staff to ensure that we are all focusing on the best objectives for the Rust project. We hope to share more on this soon.
61
+
Finally, on the top of our minds is the [Foundation three-year strategy](https://github.com/rust-lang/leadership-council/issues/197). We have a keen interest in working with the Foundation staff to ensure that we are all focused together on the best objectives. We hope to share more on this soon.
63
62
64
63
### Additional items
65
64
66
-
- We have been discussing a policy for better management of the alumni status of project members. [leadership-council#218](https://github.com/rust-lang/leadership-council/pull/218)[leadership-council#175](https://github.com/rust-lang/leadership-council/issues/175)
65
+
- We have been discussing a policy for better management of the alumni status of Project members. [leadership-council#218](https://github.com/rust-lang/leadership-council/pull/218)[leadership-council#175](https://github.com/rust-lang/leadership-council/issues/175)
67
66
- We had some discussions on who is responsible for how stable and unstable features relate to the stable releases. [leadership-council#180](https://github.com/rust-lang/leadership-council/issues/180)
68
67
- The September 2025 council elections have started. [leadership-council#211](https://github.com/rust-lang/leadership-council/issues/211)
69
68
- The 2025 Foundation director elections have started. [@tomassedovic](https://github.com/tomassedovic) will be facilitating this year. <https://blog.rust-lang.org/inside-rust/2025/08/20/electing-new-project-directors-2025/>
70
69
- We launched the [2025 Leadership Council Survey](https://blog.rust-lang.org/inside-rust/2025/06/30/2025-leadership-council-survey/), and will be posting the results soon.
71
70
71
+
## Following our work
72
+
73
+
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.
74
+
75
+
To follow our work in real time, watch our repository.
76
+
72
77
## Meeting minutes
73
78
74
-
We publish minutes from all Council meetings to the [Leadership Council repo][minutes].
75
-
Links to the minutes since our last update are:
79
+
We publish minutes from all Council meetings to the [Leadership Council repo][minutes]. Links to the minutes since our last update are:
0 commit comments