Council meeting 2025-10-24

--- title: Council meeting 2025-10-24 tags: ["council", "triage-meeting", "minutes"] date: 2025-10-24 discussion: https://rust-lang.zulipchat.com/#narrow/channel/392734-council/topic/Meeting.202025-10-24/ agenda-url: https://hackmd.io/5aa9R1VtRX25DuxZ5VuSmQ --- # Council meeting agenda - Meeting date: 2025-10-24 ## Attendance - Council members: - Observers: ## Meeting roles - Facilitator: - Minutes: ## Check-in (Not minuted.) ## Consent to agenda Do we have consensus to move forward with this agenda? ## Announcements or custom items (Meeting attendees, feel free to add items here!) ## Nominated issues ### "Update on program management program" leadership-council#161 - **Link:** https://github.com/rust-lang/leadership-council/issues/161 - **Labels:** T-leadership-council, I-council-nominated, A-program-management Tomas: * I've sent a [short summary](https://rust-lang.zulipchat.com/#narrow/channel/392734-council/topic/Meeting.20minutes.20.26.20summaries/with/545656887) of what was discussed at the Council meeting. People appreciated it, I'll keep doing these. * I've set up the PD election retrospective ([hackmd](https://hackmd.io/4SgDbeQ9Sd2KlknfT85X0Q), [thread](https://rust-lang.zulipchat.com/#narrow/channel/392734-council/topic/pd.20retrospective/with/546308172)). Comments slowed down, I'd like to summarise it and start opening PRs in the next week or so. If you haven't responded yet, please do! * I've shared feedback with the PD candidates who weren't selected. * Made more progress on writing the RustConf C++ summary blog post, but it's slow going. * Synced with Niko on Project Goals. I've updated [the announcement PR](https://github.com/rust-lang/blog.rust-lang.org/pull/1700) and we're aligned on the next steps: publish the September and October updates, set up a "goals retrospective" and start getting ready for the next year's cycle (and roughly how we want that to go -- we'll write up an announcement & RFC). ### "Discuss Rust Society proposal" leadership-council#159 - **Link:** https://github.com/rust-lang/leadership-council/issues/159 - **Labels:** T-leadership-council, I-council-nominated ### "Contributor Survey" leadership-council#222 - **Link:** https://github.com/rust-lang/leadership-council/issues/222 - **Labels:** question, S-triage, I-council-nominated ### "Invite Rust for Linux to All Hands 2026" leadership-council#236 - **Link:** https://github.com/rust-lang/leadership-council/issues/236 - **Labels:** T-leadership-council, I-council-nominated ### "Proposal: Require all project team members to have Zulip IDs" leadership-council#228 - **Link:** https://github.com/rust-lang/leadership-council/issues/228 - **Labels:** A-teams, I-council-nominated ### "Discussion: Updating and Formalizing Council Expections for Project Director Communication" leadership-council#230 - **Link:** https://github.com/rust-lang/leadership-council/issues/230 - **Labels:** T-leadership-council, I-council-nominated ### "Discuss Resident Project Maintainer idea" leadership-council#233 - **Link:** https://github.com/rust-lang/leadership-council/issues/233 - **Labels:** I-council-nominated ### "Discussing "Project Representative" needs" leadership-council#226 - **Link:** https://github.com/rust-lang/leadership-council/issues/226 - **Labels:** A-communication, I-council-nominated ### "Add Graydon Hoare to the Rust website" leadership-council#231 - **Link:** https://github.com/rust-lang/leadership-council/issues/231 - **Labels:** I-council-nominated ### "Consider linking to the community discord from rust-lang.org" leadership-council#219 - **Link:** https://github.com/rust-lang/leadership-council/issues/219 - **Labels:** I-council-nominated ### "Explicit team membership term durations" leadership-council#175 - **Link:** https://github.com/rust-lang/leadership-council/issues/175 - **Labels:** question, I-council-nominated ### "Discuss Project inputs to Foundation three year strategy" leadership-council#197 - **Link:** https://github.com/rust-lang/leadership-council/issues/197 - **Labels:** T-leadership-council, A-foundation, I-council-nominated ### "Document and improve processes for interaction with the Rust Foundation" leadership-council#41 - **Link:** https://github.com/rust-lang/leadership-council/issues/41 - **Labels:** S-active, A-foundation, P-high, I-council-nominated ### "Establish team charters" leadership-council#44 - **Link:** https://github.com/rust-lang/leadership-council/issues/44 - **Labels:** S-active, A-project-structure, I-council-nominated ### "Minor Editorial Proposal for Upcoming Release Notes" leadership-council#203 - **Link:** https://github.com/rust-lang/leadership-council/issues/203 - **Labels:** question, S-triage, I-council-nominated ## P-high issues ### "Review and organize overall project team structure" leadership-council#33 - **Link:** https://github.com/rust-lang/leadership-council/issues/33 - **Labels:** S-active, P-high, A-project-structure ## Issues that need a council decision ### "Figure out a strategy for licensing considerations" leadership-council#24 - **Link:** https://github.com/rust-lang/leadership-council/issues/24 - **Labels:** S-needs-decision, A-legal ## Active issues ### "Document the council's internal decision making process" leadership-council#31 - **Link:** https://github.com/rust-lang/leadership-council/issues/31 - **Labels:** S-active ### "Find homes for launching pad teams" leadership-council#118 - **Link:** https://github.com/rust-lang/leadership-council/issues/118 - **Labels:** S-active, A-teams, A-project-structure ## Pending PRs on the leadership-council repo ### "Allow messages from observers during meetings" leadership-council#110 - **Link:** https://github.com/rust-lang/leadership-council/pull/110 - **Labels:** T-leadership-council ### "rust-foundation-project-director.md: use more clear language" leadership-council#215 - **Link:** https://github.com/rust-lang/leadership-council/pull/215 ### "Add alumni policy" leadership-council#218 - **Link:** https://github.com/rust-lang/leadership-council/pull/218 - **Labels:** T-leadership-council, proposed-final-comment-period, disposition-merge ## Call for clarifications Should any points discussed in the meeting be clarified? ## Check-out (Not minuted.)