Merge pull request #168 from Aaronepower/master

Add State Of Rust triage procedure

Author: Mark-Simulacrum

triage-procedure.md

@@ -240,3 +240,37 @@ will be made available to anyone. After 14 days re-add the help tag and
 deassign them if necessary.
 
 [list of untagged issues]: https://github.com/rust-lang/rust/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20sort%3Acreated-asc%20-label%3AC-feature-request%20-label%3AC-enhancement%20-label%3AC-cleanup%20-label%3AC-bug%20-label%3AC-tracking-issue%20-label%3AC-future-compatibility%20-label%3AC-question%20-label%3AC-feature-accepted
+
+# State Of Rust Triage
+
+1. Visit the [State Of Rust] project page. Each card has three pieces of
+   information.
+     * “Feature” — The name of the feature with a link to the tracking issue.
+     * “What’s next?” — What we are waiting on to implement and stabilise
+       the RFC.
+     * “Last Update” — The last time this card has been triaged.
+2. For each card that you choose to triage:
+3. Visit the respective tracking issue, and any related issues that the tracking
+   issue is recently mentioned in.
+4. If the “What’s next?” on the card does not match what you think the current
+   state is, update it with the new information.
+5. If the implementation of an RFC has changed since the last update, move it to
+   the relevant column. 
+     * If there are PRs merged that implement the RFC the card would move
+        to “Implemented”.
+     * If there are only open PRs or the PRs don’t implement the full RFC the
+        card would be moved to “Implementation in progress”.
+     * If there has been a decision to deprecate the RFC, move that to the
+        “Deprecated” column.
+6. If there have been no meaningful changes to the RFC within 21 days,
+   ping someone for an update on the status of the feature.
+     * If there have been PRs implementing the RFC, ping the author(s).
+     * If author has not responded within a week, or there are no relevant PRs,
+       ping the relevant team.
+     * If there is no clear choice for the team that should be doing the
+       implementation, please add this to release team meeting notes (which
+       can be found in the #rust-release IRC channel).
+7. Update the date on the “Last update” and move that to the bottom of
+   the column.
+
+[State Of Rust]: https://github.com/rust-lang/rust/projects/8