Skip to content

lang-team march update #945

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 9, 2022
Merged

lang-team march update #945

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions posts/inside-rust/2022-03-09-lang-team-mar-update.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
---
layout: post
title: "Lang team March update"
author: Niko Matsakis
description: "Lang team March update"
team: the lang team <https://lang-team.rust-lang.org/>
---
Two weeks ago, the lang team held its March planning meeting ([minutes]). We hold these meetings on the first Wednesday of every month and we use them to schedule [design meetings] for the remainder of the month.

[minutes]: https://github.com/rust-lang/lang-team/blob/master/design-meeting-minutes/2022-03-02-planning-meeting.md

[active-initiatives]: https://lang-team.rust-lang.org/initiatives.html

## Upcoming design meetings

We have planned the following design meetings:

* March 9: Draft lang team roadmap (this already happened! [minutes](https://github.com/rust-lang/lang-team/blob/master/design-meeting-minutes/2022-03-09-lang-roadmap.md))
* March 16: [Backlog bonanza](https://lang-team.rust-lang.org/meetings/backlog-bonanza.html)
* March 23: Return Position Impl Trait in Dyn Trait (RPITIDT) [lang-team#144](https://github.com/rust-lang/lang-team/issues/144)
* March 30: Lint policy [lang-team#132](https://github.com/rust-lang/lang-team/issues/132)

## Design meeting expectations

* The document for the meeting must be prepared by the triage meeting on Tuesday and posted to the tracking issue.
* If it is not sent out by then, the meeting will be canceled. This gives folks 24 hour notice.
* There is no expectation that people will read the document before the meeting. The meeting will begin with a recap of the document.
* However, there is no rule **against** reading the document beforehand and providing feedback or advice on how to improve it.

[lang-team-141]: https://github.com/rust-lang/lang-team/issues/141
[backlog bonanza]: https://lang-team.rust-lang.org/meetings/backlog-bonanza.html
[design meetings]: https://lang-team.rust-lang.org/meetings/design.html