# Libs Meeting 2024-01-10 ###### tags: `Libs Meetings` `Minutes` **Meeting Link**: https://meet.google.com/jde-nduz-eps **Attendees**: Amanieu, Josh Stone, Chris Denton, The 8472, Mara ## Brainstorm: things to do in 2024 - refactoring of std::sys - reevaluate platform requirements - are current or former requirements holding us back? - we could add the platform version in the target triple, like on freebsd. - thread local storage on android is only supported since a recent version - build-std would allow cfg(os version) - cross-team interaction: feature wishlist for other teams. - list of features that would unblock our work. clearly specify which feature it unblocks/enables. - improve reviewer assignment by rustbot - backpressure to avoid swamping individual reviewers - organisation - libs and libs-api split still useful? - libs-api: who should get checkboxes? - crate-maintainers falls under libs, but in practice do their own thing. - indexmap to rust-lang? - what does it mean for something to be moved to rust-lang? discussion ongoing - shared infrastructure possible - Rust CoC and moderation - "bus factor" - RFCs, open unstable features, ACPs, .. - always going to be an infinite amount of work - goals - keep handling backports in time - improve review queue - contributors are allowed to review and can be on the rotation - actively invite them? - more documentation on how to review? - hard to write in advance - just document mistakes when made - expectations (e.g. level of detail) should be documented - mentoring? - not as a requirement, but to boost confidence. - we already have a private channel: t-libs/reviewers - only expand the review rotation, or also increase amount of folks with r+ rights for libs? - expand libs team - specifically reviewers - libc 0.3 - Amanieu can mentor anyone who is interested in that. - https://github.com/rust-lang/libc/issues/3248 - more actively recruit people for specific tasks? e.g. open an issue for researching something? - have more "help wanted" issues on rust-lang/libs-team, and collect those in a blog post or meta tracking issue or project board? - long review times discourages people to focus on implementation work personal goals/wishes? - the8472: dirfd stuff - amanieu: `is` language feature (removing the need for .is_some(), .is_none(), etc. etc.) - should we reserve `is` in 2024? - (could use `k#is` for now) - mara: deprecate thread_local!{}. would be nice if `#[thread_local]` worked everywhere, and then use that with OnceCell explicitly. - josh stone: Try trait over the finish line. - josh stone: at least namable and usable as bound. - 8472: blocked partially on never type? - solve burnout? concrete actions: - invite libs-contributors to review queue, check back next week - Josh Stone to write a message on Zulip. - ask for improvements to rustbot - The 8472 to dig up the relevant threads and post a message.