Add Lang team February update post.

Author: seanchen1991

posts/inside-rust/2022-02-11-lang-team-feb-update.md

@@ -0,0 +1,42 @@
+---
+layout: post
+title: "Lang team February update"
+author: Sean Chen
+description: "Lang team February update"
+team: the lang team <https://lang-team.rust-lang.org/>
+---
+This week the lang team held its February planning meeting ([minutes]). We hold these meetings on the first Wednesday of every month.
+
+The planning meeting is used for:
+
+* Checking in on the status of our [active initiatives]
+* Planning the design meetings for the remainder of the month
+
+After each meeting, we post an update (like this one!) with notes and meeting announcements.
+
+[minutes]: https://github.com/rust-lang/lang-team/blob/master/design-meeting-minutes/2022-02-02-planning.md
+
+[active initiatives]: https://lang-team.rust-lang.org/initiatives.html
+
+## Update from active initiatives
+
+What follows are the updates that were submitted this month. Note that many of the more recent initiatives have dedicated repositories which contain other byproducts of the design process (e.g., evaluation documents, open design questions, etc). Take a look!
+
+[TODO]
+
+In addition to the reports above, you'll find more detailed discussions in the [minutes].
+
+## Upcoming design meetings
+
+We have planned the following design meetings:
+
+* February 23: Never type next steps ([lang-team#141][lang-team-141])
+
+## 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