File tree Expand file tree Collapse file tree 1 file changed +16
-2
lines changed Expand file tree Collapse file tree 1 file changed +16
-2
lines changed Original file line number Diff line number Diff line change @@ -14,8 +14,8 @@ Here's how the planning process works:
1414
1515- At the begin of the quarter, we publish a blog post in the
1616 [ Inside Rust] ( https://blog.rust-lang.org/inside-rust/ ) blog to share
17- what we've accomplished in the last quarter and what we planned for this
18- quarter.
17+ what ` t-infra ` and (optionally) the subteams accomplished in the last quarter
18+ and what we planned for this quarter.
1919- During the quarter, we execute the work planned.
2020- Before the end of the quarter, we plan the work for the next quarter.
2121
@@ -26,6 +26,20 @@ Each entry in the plan has the following fields:
2626- _ Description_ : a brief description of the work
2727 (full details should be in the GitHub issue).
2828
29+ ## Blog post
30+
31+ Here's the process to publish the blog post:
32+
33+ 1 . Write a draft of the blog post as a PR to
34+ [ rust-lang/blog.rust-lang.org] ( https://github.com/rust-lang/blog.rust-lang.org ) .
35+ 2 . Share the draft in the [ t-infra] ( https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra )
36+ Zulip channel to ask members of the infra team and subteams to add/edit items.
37+ Ping the subteams in the Zulip topic because they might not follow the channel.
38+
39+ Previous blog posts:
40+
41+ - [ 2025 Q3/Q4] ( https://blog.rust-lang.org/inside-rust/2025/10/16/infrastructure-team-q3-recap-and-q4-plan/ )
42+
2943## Are volunteers expected to own items in the plan?
3044
3145Volunteers don't have any obligation in:
You can’t perform that action at this time.
0 commit comments