|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: "Lang team February update" |
| 4 | +author: Sean Chen |
| 5 | +description: "Lang team February update" |
| 6 | +team: the lang team <https://lang-team.rust-lang.org/> |
| 7 | +--- |
| 8 | +Two weeks ago, the lang team held its February planning meeting ([minutes]). We hold these meetings on the first Wednesday of every month. |
| 9 | + |
| 10 | +The planning meeting is used for: |
| 11 | + |
| 12 | +* Checking in on the status of our [active initiatives][active-initiatives] |
| 13 | +* Planning the design meetings for the remainder of the month |
| 14 | + |
| 15 | +After each meeting, we post an update (like this one!) with notes and meeting announcements. |
| 16 | + |
| 17 | +[minutes]: https://github.com/rust-lang/lang-team/blob/master/design-meeting-minutes/2022-02-02-planning.md |
| 18 | + |
| 19 | +[active-initiatives]: https://lang-team.rust-lang.org/initiatives.html |
| 20 | + |
| 21 | +## Update from active initiatives |
| 22 | + |
| 23 | +We didn't have any updates from initiatives this week and in fact are thinking of changing our |
| 24 | +"update" structure to integrate into the regular triage meeting. For the time being, though, you |
| 25 | +can check in on the progress of any active initiatives you're interested in by visiting the [active initiatives][active-initiatives] project board, which is also a great way to get a summary of the |
| 26 | +major goings on of the Lang team. |
| 27 | + |
| 28 | +## Upcoming design meetings |
| 29 | + |
| 30 | +We have planned the following design meetings: |
| 31 | + |
| 32 | +* February 23: Never type next steps ([lang-team#141][lang-team-141]) |
| 33 | + |
| 34 | +## Design meeting expectations |
| 35 | + |
| 36 | +* The document for the meeting must be prepared by the triage meeting on Tuesday and posted to the tracking issue. |
| 37 | + * If it is not sent out by then, the meeting will be canceled. This gives folks 24 hour notice. |
| 38 | +* There is no expectation that people will read the document before the meeting. The meeting will begin with a recap of the document. |
| 39 | + * However, there is no rule **against** reading the document beforehand and providing feedback or advice on how to improve it. |
| 40 | + |
| 41 | +[lang-team-141]: https://github.com/rust-lang/lang-team/issues/141 |
0 commit comments