A lang team initiative is some active effort with a clear goal or deliverable. Typically initiatives are changes to the language, but they could also be documentation, specifications, or something internal to the lang team.
Active initiatives are initiatives that have been assigned a lang-team Liaison and which are actively underway. A complete list can be found in this GitHub project board. Note that this list doesn't represent all unstable features; older features in particular were added without active initiatives.
Each initiative on the project board is linked to a tracking issue and has a status:
- The Owner and Liaison are assigned to the issue.
- If the initiative has a dedicated repository, the issue is created on that repository (some initiatives don't require their own repos; they are found on rust-lang/rust or rust-lang/lang-team).
- The Stage of the initiative:
- Experimental -- Drafting RFC; implementation work may begin on nightly as well
- Development -- Approved RFC; implementation is in progress on nightly
- Feature complete -- Implementation is complete on nightly and ready for widespread testing
- Stabilized -- Implementation is complete and available on stable
- To be stabilized, there must be a pending PR adding the feature to the Rust reference, but this PR may not yet have landed.
- Other forms of integration, such as rustfmt, often take place after stabilization as well.
You can see the currently proposed initiatives on Github. We review this list during triage meetings and decide whether to assign a liaison or close the proposal. If initiatives haven't received a liaison after 6 weeks of activity, we take that as a sign that there is no enthusiasm to pursue this and close the issue, but you are welcome to re-open the issue if you believe someone would be willing to liaison.
It's easy! You just open a short issue describing your idea. Read more in the process page!