---
title: Council meeting 2025-01-31
tags: ["council", "triage-meeting", "minutes"]
date: 2025-01-31
discussion: https://rust-lang.zulipchat.com/#narrow/channel/392734-council/topic/Meeting.202025-01-31
agenda-url: https://hackmd.io/qH3hrUn9RzGiyjwzFRbN-w
---

# Council meeting agenda

- Meeting date: 2025-01-31

## 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!)

### Rethinking minutes review

TC: We've been reviewing the minutes after checkout, but I don't think this really works, and it causes a kind of ragged ending to the meeting. I'd suggest either we do this before checkout, or people set aside the time to do it themselves immediately after we end.

## Nominated issues

### "Allocate budget to Edition/Project Goals teams in support of program management" leadership-council#151

- **Link:** https://github.com/rust-lang/leadership-council/issues/151
- **Labels:** T-leadership-council, I-council-nominated

### "[launching-pad] Find a home for the Security Response WG" leadership-council#141

- **Link:** https://github.com/rust-lang/leadership-council/issues/141
- **Labels:** A-teams, I-council-nominated

### "Inconsistent handling of potentially build failing changes between different rust teams" leadership-council#145

- **Link:** https://github.com/rust-lang/leadership-council/issues/145
- **Labels:** T-leadership-council, proposed-final-comment-period, disposition-close, A-policy, 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

## 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

## Call for clarifications

Should any points discussed in the meeting be clarified?

## Check-out

(Not minuted.)