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

推荐订阅源

Forbes - Security
Forbes - Security
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
F
Fortinet All Blogs
B
Blog
T
The Blog of Author Tim Ferriss
Engineering at Meta
Engineering at Meta
GbyAI
GbyAI
Y
Y Combinator Blog
Microsoft Azure Blog
Microsoft Azure Blog
L
LangChain Blog
Recent Announcements
Recent Announcements
U
Unit 42
Martin Fowler
Martin Fowler
M
MIT News - Artificial intelligence
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
The Register - Security
The Register - Security
Recorded Future
Recorded Future
C
Check Point Blog
V
V2EX
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Hugging Face - Blog
Hugging Face - Blog
WordPress大学
WordPress大学
Google DeepMind News
Google DeepMind News
酷 壳 – CoolShell
酷 壳 – CoolShell
F
Full Disclosure
小众软件
小众软件
A
About on SuperTechFans
云风的 BLOG
云风的 BLOG
宝玉的分享
宝玉的分享
Last Week in AI
Last Week in AI
有赞技术团队
有赞技术团队
MongoDB | Blog
MongoDB | Blog
爱范儿
爱范儿
P
Proofpoint News Feed
罗磊的独立博客
量子位
D
Docker
博客园_首页
D
DataBreaches.Net
Project Zero
Project Zero
博客园 - 司徒正美
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
博客园 - Franky
Security Latest
Security Latest
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
N
Netflix TechBlog - Medium
K
KPMG report finds enterprise disconnect between AI and its ROI | CIO
博客园 - 三生石上(FineUI控件)
H
Hackread – Cybersecurity News, Data Breaches, AI and More
大猫的无限游戏
大猫的无限游戏

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 The Rust Team All Hands in Berlin: a Recap Increasing Rust’s Reach 2018 Announcing Rust 1.25 Rust's 2018 roadmap Announcing Rust 1.24.1 Announcing Rust 1.24 The 2018 Rust Event Lineup Announcing Rust 1.23 New Year's Rust: A Call for Community Blogposts Rust in 2017: what we achieved Announcing Rust 1.22 (and 1.22.1) Fearless Concurrency in Firefox Quantum Announcing Rust 1.21 impl Future for Rust Rust 2017 Survey Results Announcing Rust 1.20 Announcing Rust 1.19 The 2017 Rust Conference Lineup Rust's 2017 roadmap, six months in Increasing Rust’s Reach Announcing Rust 1.18 Two years of Rust The Rust Libz Blitz Launching the 2017 State of Rust Survey Announcing Rust 1.17 Announcing Rust 1.16 Rust's language ergonomics initiative Announcing Rust 1.15.1 Rust's 2017 roadmap Announcing Rust 1.15 Announcing Rust 1.14 Announcing the First Underhanded Rust Contest Announcing Rust 1.13 Announcing Rust 1.12.1 Announcing Rust 1.12 Incremental Compilation Announcing Rust 1.11 Shape of errors to come The 2016 Rust Conference Lineup Announcing Rust 1.10 State of Rust Survey 2016 Announcing Rust 1.9 One year of Rust Taking Rust everywhere with rustup Launching the 2016 State of Rust Survey Cargo: predictable dependency management Introducing MIR Announcing Rust 1.8 Announcing Rust 1.7 Announcing Rust 1.6 Announcing Rust 1.5 Announcing Rust 1.4 Announcing Rust 1.3 Rust in 2016 Announcing Rust 1.2 Rust 1.1 stable, the Community Subteam, and RustCamp Announcing Rust 1.0 Abstraction without overhead: traits in Rust Rust Once, Run Everywhere Mixing matching, mutation, and moves in Rust Fearless Concurrency with Rust Announcing Rust 1.0 Beta Announcing Rust 1.0.0.alpha.2 Rust 1.0: status report and final timeline Announcing Rust 1.0 Alpha Rust 1.0: Scheduling the trains Yehuda Katz and Steve Klabnik are joining the Rust Core Team Cargo: Rust's community crate host Stability as a Deliverable Road to Rust 1.0
December 2024 Leadership Council Update | Inside Rust Blog
Eric Huss on behalf of Leadership Council · 2024-12-09 · via Rust Blog

Hello again from the Rust Leadership Council! We wanted to share an update on what the Council has been working on since our last update.

Accomplishments so far

Welcome Oli Scherer and TC to the Council

As announced in September, Oli Scherer and TC joined the Council representing the moderation team and lang team respectively.

Foundation updates

In November we wrapped up the election process for the Project Directors of the Rust Foundation. Ryan Levick is continuing for another term with Carol Nichols joining the board (see announcement). We'd like to thank TC for facilitating the election process.

We tried to further clarify the definition of employment which is used for determining Director eligibility (rust-lang/leadership-council#111).

We reviewed our processes for how the Council interacts with the Directors and the Foundation. We identified some concerns about maintaining good communication with the Directors since Mark Rousskov, the only Council member who was also a Director, is stepping down as Director. We also looked at our communication processes with the Foundation, and didn't have specific changes to recommend other than documenting the current status (rust-lang/leadership-council#41).

In November we also coordinated with the directors on a project-wide request for the annual feedback on the Foundation executive director.

Travel grant policy

In April we started a Travel Grant program which provides funds for project members to travel to Rust-related events. We have followed up on that program to publicly document the policy. We are also looking to remove the experimental status of the policy, as we feel like we have been happy with how the program has been working, and expect to keep it funded in the near term.

We'd like to remind all project members that they are welcome to take advantage of this program, and to reach out to your representative if you have any questions.

Compiler operations

We approved funding for a compiler operations position (rust-lang/leadership-council#114). This role is intended to help ensure the effectiveness of the compiler team. The specifics are being coordinated between the compiler team leads and the Foundation.

Project Grants

We approved the use of a portion of the Council's budget to extend one-year grants to several of the candidates of the Fellowship Program (rust-lang/leadership-council#112). We had more excellent applications to the program than the existing funding would cover, and we had the opportunity to divert some of the Council's budget toward this program.

Additional items

And a few other items:

Ongoing work

There are various efforts underway on projects that have had significant discussions since the last update, but have not concluded with any decisions, yet. They are:

Shape of Rust

Work continues to define the shape of the structure of the Rust project (rust-lang/leadership-council#33) and to determine how to organize the teams in the Launching Pad. James Munns has been working to better understand the current status of the Launching Pad teams, and to work on plans for what to do with those teams (rust-lang/leadership-council#118).

Foundation budget

We are continuously looking for ways to effectively use the Council's budget (rust-lang/leadership-council#103). Although we have approved several programs, we still have a significant portion of the budget to spend. James Munns suggested an RFQ process for soliciting quotes on potential projects.

We continue to look at how we can tackle the backlog of issues and concerns regarding the licensing and copyright handling throughout the Rust project (rust-lang/leadership-council#24). We opened a topic to try to get more input on different approaches we can take.

Jonathan Pallant has been working on improving the copyright notices shipped with Rust (rust-lang/leadership-council#120), and has asked the Council to help approve this change.

Additional items

  • Work continues to prepare for the all-hands event in May 2025 at RustWeek 2025 which corresponds with Rust's 10-year anniversary.
  • We have been looking to change the policy for meeting observers (rust-lang/leadership-council#110).
  • We have been asked to review the obligation for the Council and the Project as a whole for approval of The Update Framework RFC, but no conclusion has been reached.
  • We have been reviewing the open tasks for the Council and trying to identify what is needed to move them forward.
  • Niko Matsakis has reached out to the Council for establishing a 3-5 year plan for the project, which is in the initial stages of discussion.
  • We have been working on a coordinated analysis of the inference breakage that happened in the Rust 1.80 release, since the issue involved many teams throughout the project.

Meeting minutes

We publish minutes from all Council meetings to the Leadership Council repo. Links to the minutes since our last update are: