惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
V2EX
量子位
博客园 - 司徒正美
IT之家
IT之家
V
Visual Studio Blog
Apple Machine Learning Research
Apple Machine Learning Research
博客园_首页
Google DeepMind News
Google DeepMind News
Last Week in AI
Last Week in AI
Microsoft Security Blog
Microsoft Security Blog
T
Tailwind CSS Blog
aimingoo的专栏
aimingoo的专栏
GbyAI
GbyAI
Vercel News
Vercel News
B
Blog
大猫的无限游戏
大猫的无限游戏
D
DataBreaches.Net
小众软件
小众软件
罗磊的独立博客
博客园 - 叶小钗
雷峰网
雷峰网
Martin Fowler
Martin Fowler
Hugging Face - Blog
Hugging Face - Blog
WordPress大学
WordPress大学

Rust Blog

Security Advisory for Cargo (CVE-2026-5223) | Rust Blog Security Advisory for Cargo (CVE-2026-5222) | Rust Blog Project goals update — April 2026 (end of 2025H2) | Rust Blog Rust is participating in Outreachy | Rust Blog Raising the baseline for the `nvptx64-nvidia-cuda` target | Rust Blog Announcing Google Summer of Code 2026 selected projects | Rust Blog Announcing Rust 1.95.0 | Rust Blog docs.rs: building fewer targets by default | Rust Blog Changes to WebAssembly targets and handling undefined symbols | Rust Blog Announcing Rust 1.94.1 | Rust Blog Security advisory for Cargo | Rust Blog What we heard about Rust's challenges | Rust Blog Call for Testing: Build Dir Layout v2 | Rust Blog Announcing rustup 1.29.0 | Rust Blog Announcing Rust 1.94.0 | Rust Blog 2025 State of Rust Survey Results | Rust Blog Rust debugging survey 2026 | Rust Blog Update on the October 15, 2018 incident on crates.io Announcing Rust 1.29.2 Announcing Rust 1.29 Announcing Rust 1.28 What is Rust 2018? Announcing Rust 1.27.2 Announcing Rust 1.27.1 Security Advisory for rustdoc Announcing Rust 1.27 Announcing Rust 1.26.2 Announcing Rust 1.26.1 Rust turns three Announcing Rust 1.26
Governance WG Call For Participation | Inside Rust Blog
Erin Power on behalf of The Governance WG · 2019-11-13 · via Rust Blog

Hello everyone, the governance working group has been working a few efforts, but we haven't made as much progress as we would have liked over the past few months, so we are going to try out a new process and meeting agenda aimed at trying to get more work done in the time we know we have.

New Meeting Structure

Previously we have been doing most of our work async while using our bi-weekly meeting call to triage tasks. The problem we ran into with this is that a lot of the members also heavy contributors to the Rust project as a whole, and it can be can hard for some people to schedule time write an initial draft.

To address this instead of triaging during the meeting and working on tasks in async, we're going to hold focused topic based meetings, and use the time between meetings, to publish posts like this and to research and prepare for the next topic. To help do this we're going to extend our current meeting duration from 30 minutes to an hour. (The meeting will still be every two weeks.)

The current goals are to documenting the de-facto governance structure, provide the result as a RFC and then if merged provide a version on forge.rust-lang.org so that it has greater visibility. We also want to schedule people involved in Rust and other governance structures to come and talk about their experiences.

For deciding what topics, we're going to rotate who takes the lead for each meeting. It's that person's responsibility to decide the topic and to prepare a call for participation similar to this post informing people of the topic and how they might best prepare if they wish to join.

We also hope that having a focused topic will reduce any barrier of expected knowledge in order to participate and contribute. With that said let's talk about the topic for next meeting.

Reviewing & Examining Previous Governance RFCs

Our first topic for new meeting is going to be to read RFC 1068, the original Rust Governance RFC, review how accurate it is to today's structure, and see any if there are questions that we have that it doesn't answer. Here are some other relevant RFCs for additional context:

Our next meeting is going to be at 22:00 UTC on Tuesday, November 19th and we'd like to encourage anyone who's interested, regardless of their previous experience to read those RFCs and come to the #wg-governance channel on discord to attend the meeting. (Our meetings are done over a video call with Zoom, but we use the discord channel to organise ourselves).

If some reason you know you won't be able to attend these meetings but would still like to participate. Please feel free to post any questions about Rust's governance as issues on our GitHub repository, even if you are not available to attend the working group's meetings.