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

推荐订阅源

GbyAI
GbyAI
N
News and Events Feed by Topic
D
DataBreaches.Net
MongoDB | Blog
MongoDB | Blog
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Engineering at Meta
Engineering at Meta
T
Tailwind CSS Blog
博客园_首页
Microsoft Azure Blog
Microsoft Azure Blog
Y
Y Combinator Blog
博客园 - Franky
Hugging Face - Blog
Hugging Face - Blog
月光博客
月光博客
A
About on SuperTechFans
I
InfoQ
S
Securelist
Last Week in AI
Last Week in AI
S
Schneier on Security
C
CXSECURITY Database RSS Feed - CXSecurity.com
Hacker News: Ask HN
Hacker News: Ask HN
Schneier on Security
Schneier on Security
Know Your Adversary
Know Your Adversary
腾讯CDC
大猫的无限游戏
大猫的无限游戏
S
Security @ Cisco Blogs
博客园 - 三生石上(FineUI控件)
Simon Willison's Weblog
Simon Willison's Weblog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
T
Tor Project blog
美团技术团队
aimingoo的专栏
aimingoo的专栏
G
Google Developers Blog
罗磊的独立博客
Vercel News
Vercel News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
The Cloudflare Blog
S
Secure Thoughts
www.infosecurity-magazine.com
www.infosecurity-magazine.com
Latest news
Latest news
Recent Announcements
Recent Announcements
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
L
LINUX DO - 热门话题
Security Latest
Security Latest
TaoSecurity Blog
TaoSecurity Blog
Cyberwarzone
Cyberwarzone
有赞技术团队
有赞技术团队

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
Leadership Council update — September 2025 | Inside Rust Blog
Eric Huss on behalf of Leadership Council · 2025-09-10 · 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

Content team

Pete LeVasseur and TC created the Content team (leadership-council#206). The team is charged with producing publishable content that is of interest and benefit to the Rust Project and its community including blog posts, videos, podcasts, etc. The team is talking with people in the Project and the community to share their knowledge and experience, and most immediately, the team has been organizing interviews that will be recorded at RustConf.

We are looking forward to soon seeing what they produce.

All-hands 2026

The Council approved the 2026 All-Hands event (leadership-council#192). This event is an opportunity for Project members to meet in person to to collaborate on the future of Rust. The event is scheduled to occur again with RustWeek 2026 in The Netherlands on May 21-23. More information will be coming soon.

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:

Rust Society

@JamesMunns has continued to develop the concept of the "Rust Society". The Rust Society will be an organizational structure for user groups (commonly called "Special Interest Groups", "Working Groups", etc. in other organizations) outside of the Rust Project, but administrated by the Rust Project via a new "T-Society-Admins" subteam of the Launching Pad.

This structure is intended to be the long-term home for existing Domain Working Groups, which will be retired as a concept after this work is complete. In the future, this structure intends to offer "open enrollment" for any interested group of users.

See the latest proposed charter for how the Rust Society will function.

Foundation

There have been continual discussions with the Foundation on various topics. We are excited to welcome Lori Lorusso, who has started as the Foundation's new Director of Outreach. She hit the ground running and has been helping to coordinate with the Foundation and plan upcoming projects.

We have been discussing with the Foundation the possibilities for continuing the budget for project priorities in 2026. For 2024 and 2025, this budget was made possible by a generous unrestricted grant from Microsoft. We are looking for ways that we can continue this budget so as to continue important programs such as travel grants, the all-hands, project grants, program management, and compiler operations.

We discussed the condition of the 2025 travel grant budget (leadership-council#182). Many Project members used most of their $2,000 limit during the all-hands earlier this year, and we had concerns that members would not be able to attend other events like RustConf. Ultimately we decided to keep with the current policy and will be working on figuring out what our possible option might be for funding this in 2026.

Finally, on the top of our minds is the Foundation three-year strategy. We have a keen interest in working with the Foundation staff to ensure that we are all focused together on the best objectives. We hope to share more on this soon.

Additional items

Following our work

As you can see from the many links above, the work of the Council happens mostly in public on GitHub issues posted in our repository. The items on our meeting agendas are drawn from these. After discussing an item, we summarize that discussion and any shared rationales on the issue. When we make decisions, we propose on the issue a "final comment period" (FCP), and as with all FCPs in the Project, we're interested in and review any feedback that people have before or during this final comment period.

To follow our work in real time, watch our repository.

Meeting minutes

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