--- title: Council meeting 2024-12-20 tags: ["council", "triage-meeting", "minutes"] date: 2024-12-20 discussion: https://rust-lang.zulipchat.com/#narrow/channel/392734-council/topic/Meeting.202024-12-20 url: https://hackmd.io/XLFpRQWjQsSOZg6vgoXDtQ --- # Council meeting agenda - Meeting date: 2024-12-20 ## 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!) ### One meeting policy to open to observers TC: We had agreed to update our policies to allow participation by observers. Until we document that, we've been deciding per-meeting to allow observer participation. If it's without objection, I propose we continue that today. ## Nominated issues ### "Approve changes to the COPYRIGHT notices shipped with Rust" leadership-council#120 - **Link:** https://github.com/rust-lang/leadership-council/issues/120 - **Labels:** T-leadership-council, proposed-final-comment-period, disposition-merge, I-council-nominated ### "Invitations for the All-Hands" leadership-council#135 - **Link:** https://github.com/rust-lang/leadership-council/issues/135 - **Labels:** P-urgent, I-council-nominated ### "Create system for collecting infrastructure user stories" leadership-council#136 - **Link:** https://github.com/rust-lang/leadership-council/issues/136 - **Labels:** 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 ### "A more stable travel grant policy" leadership-council#97 - **Link:** https://github.com/rust-lang/leadership-council/issues/97 - **Labels:** S-needs-decision, A-policy, A-foundation, 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 ### "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 ## 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 ### "Remove "experimental" status of the travel grant policy" leadership-council#122 - **Link:** https://github.com/rust-lang/leadership-council/pull/122 - **Labels:** T-leadership-council, finished-final-comment-period, disposition-merge, to-announce ### "Update steps for new directors to add to team database" leadership-council#134 - **Link:** https://github.com/rust-lang/leadership-council/pull/134 ## Call for clarifications Should any points discussed in the meeting be clarified? ## Check-out (Not minuted.) ## Review of the minutes TC: We'll review the minutes and check off that we're OK with them being posted next week, after giving a few days for each of us to clarify our remarks in the document.