---
# System prepended metadata

title: Libs Meeting 2022-06-01
tags: [Minutes, Libs Meetings]

---

# Libs Meeting 2022-06-01

###### tags: `Libs Meetings` `Minutes`

**Meeting Link**: https://meet.jit.si/rust-libs-meeting-ujepnbwg2lzqgt6wvrndwimi
**Attendees**: Amanieu, Jane, Josh Stone, Josh Triplett, Mara, Ashley Mannix, The 8472, tshepang, saethlin

## Agenda

- [Open Action Items](https://hackmd.io/Uehlc0qUQfWfvY1swYWRgQ)
- Triage
- ICP - Initial Commenting Period
  - First step for new unstable APIs: RFC with FCP is too heavy, but just a PR with a single review is not enough. ICP allows for feedback/input, without blocking things on the entire team.
  - 10 day period, but without the necessary FCP checkboxes. One checkbox and no objections seems enough.
  - Josh: This is similar to what other teams are doing, for reversible decisions.
  - Name bikeshedding: Minor Change Proposal / Unstable Change Proposal
  - Everyone on board. Let's go.
  - Rustbot/triagebot automation.
- std-dev-guide
  - Approving your own PRs is fine.
  - Clarify that the guide is just 'helpful tips' and not any 'normative guidelines' (e.g. about how APIs or docs should be).
  - We can expand the write permissions to include libs-contributors + rustc dev guide.
- glob crate
  - Move to rust-lang?
  - BurntSushi wanted to maintain it, but doesn't have the time right now.
  - Let's move it back to rust-lang and give libs permissions.
- process for rust-lang crates in general. Reviewers? Direct pushes? Could we automate the publish process?
  - Consistency between these is important
  - Opening PRs and merging your own PRs is preferable to just pushing directly to main
  - Ideally we should have a second person looking at each PR, but in practice that isn't happening, and 
  - A subteam for maintaining those crates could be nice.
  - Some discussion about `log` and `tracing` and long-term maintenance.
  - Conclusion: switch to opening PRs but letting people merge their own PRs, for any crate that doesn't specifically have regular reviewers, and continue looking for ways to get more reviewers
- Anything else?

## Triage

### FCPs

None

### Critical

None

### Backports

None

### Prioritization Requested

None

### Nominated

- [2 `rust-lang/rust` `I-libs-nominated` items](https://github.com/rust-lang/rust/issues?q=label:I-libs-nominated+is:open)
  - [[95026](https://github.com/rust-lang/rust/pull/95026)] *Increase the minimum linux\-gnu versions*
    - Bumping minimum to Linux 3.2, which was released in 2012.
    - Question is if we want to allow cross compiling to older linux/libc.
    - Relevant for clock_boottime, and a few other minor things.
    - None of us opposed to go forward with this.
  - [[97467](https://github.com/rust-lang/rust/pull/97467)] *Experiment: force debug\_assertions in consteval context*
    - Large performance hit. Unacceptable in this form.

### Waiting on team

None

### Needs decision

None

### Regressions

- [1 `rust-lang/rust` `T-libs` `regression-from-stable-to-nightly` items](https://github.com/rust-lang/rust/issues?q=label:T-libs+label:regression-from-stable-to-nightly+is:open)
  - [[97124](https://github.com/rust-lang/rust/issues/97124)] *Synchronous Windows stdin pipes broke tokio*


