Council meeting 2024-10-25

--- title: Council meeting 2024-10-25 tags: ["council", "triage-meeting", "minutes"] date: 2024-10-25 discussion: https://rust-lang.zulipchat.com/#narrow/channel/392734-council/topic/Meeting.202024-10-25 url: https://hackmd.io/W9tnavE_SD6efESWaH1JtA --- # Council meeting agenda - Meeting date: 2024-10-25 ## 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 ### "Schedule time for project director elections 2024" leadership-council#101 - **Link:** https://github.com/rust-lang/leadership-council/issues/101 - **Labels:** T-leadership-council, I-council-nominated TC: We did not succeed in getting consensus on this date on Zulip. The question on the table is: *Proposed: We'll be doing project director elections on 1 November at our usual meeting time and place.* There's a poll here: https://github.com/rust-lang/leadership-council/issues/101#issuecomment-2438061571 This should take less than five minutes. ### "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, I-council-nominated TC: This is expected to take fifteen minutes. I have a sketch of a proposal for how to move this forward. The design idea of this proposal is to keep things simple while taking a concrete step forward toward solving the outstanding problems. We could always do more later. Here's that sketch: 1. We want all artifacts of the Rust Project to be redistributable under the terms of `MIT OR Apache-2.0`. - Exceptions to this are to be approved by the council. - Repositories within the project should use [cargo-deny](https://github.com/EmbarkStudios/cargo-deny) or similar tooling in CI to verify license compliance and to track exceptions. - We'll start by simply asking all teams to please do this for the repositories they own. 2. Questions about licensing should be directed to the council. - E.g., PRs to add license exceptions to `deny.toml` should be marked `I-council-nominated` and `cc @rust-lang/leadership-council`. - For straightforward questions, knowledgeable members of the council may be able to provide an answer directly. - For some questions, the council may need to consider it as a group (i.e. *en banc*). - For other questions, the council may ask Foundation counsel to advise. - The council may later charter a team to handle licensing; handling this itself is an initial step to solve the immediate problem and build experience that will be useful in determining whether and how such a team should be chartered. 3. For the backlog items, the council will ask the Foundation to please draw up a plan and budget for working to solve the problems necessary so as to bring all artifacts of the project in line with item 1. What do people think? ### "Allow messages from observers during meetings" leadership-council#110 - **Link:** https://github.com/rust-lang/leadership-council/pull/110 - **Labels:** T-leadership-council, proposed-final-comment-period, disposition-merge, I-council-nominated TC: This might take ten minutes. There's a proposed FCP here: https://github.com/rust-lang/leadership-council/pull/110#issuecomment-2408179039 There's an outstanding concern and three missing checkboxes. There have been changes made to the text to address the raised concern. Can we move this forward? ### "Grant proposals for 2024-2025" leadership-council#112 - **Link:** https://github.com/rust-lang/leadership-council/issues/112 - **Labels:** A-foundation, I-council-nominated, A-budget ehuss: I would like to direct a portion of the Council's budget to fund additional grants to Rust contributors. The budget for the [Fellowship Grants](https://foundation.rust-lang.org/news/announcing-the-rust-foundation-s-2024-fellows/) did not cover as many people as we would have liked. We have four candidates that we would like to fund at $20,000 over 12 months as "Project Grants". This will come out of the $150,000 unreserved Council budget from 2024. We'll need to finalize the exact structure with the Foundation, but we are likely looking at it structured as an initial payment plus a mid-point payment contingent on how things are going (payments are unrestricted, no separate travel/hardware budget). This is also contingent on the candidates accepting the grants. @Mark-Simulacrum and @jamesmunns and Paul Lenz have reviewed these candidates and agree that we would like to extend the grants to them. I would like to ask the council to approve the proposed $80,000 for these grants. Time: ~10 minutes ## 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 ### "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 ## 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 ### "Review the top-level teams and rearrange as appropriate" leadership-council#32 - **Link:** https://github.com/rust-lang/leadership-council/issues/32 - **Labels:** S-active, A-project-structure ### "Establish team charters" leadership-council#44 - **Link:** https://github.com/rust-lang/leadership-council/issues/44 - **Labels:** S-active, 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, proposed-final-comment-period, disposition-merge, I-council-nominated ### "Add clarifications around definition of employment" leadership-council#111 - **Link:** https://github.com/rust-lang/leadership-council/pull/111 ## Call for clarifications Should any points discussed in the meeting be clarified? ## Check-out (Not minuted.)