Update issue claim guidelines based on the new labels

Author: dhruvkb

content/contributing-code/contents.lr

@@ -13,28 +13,38 @@ body:
 
 Here's a list of [all our current projects](/projects/). We use GitHub issues associated with each project to track the work associated with that project. That's where you can find things to work on.
 
-We make extensive use of issue labels to desginate the status of various issues. We have a standard set of labels across all projects, [documented here](https://github.com/creativecommons/ccos-scripts/blob/master/normalize_repos/labels.py). Here are some of the ones that are most relevant to finding a good issue to work on:
-
-* **Issues tagged `help wanted` or `good first issue`** are available for community contribution**
-    * These issues are available for community contribution and you do not need our permission to work on one of these.
-    * You may work on an issue labeled `good first issue` even if it's not your first issue.
-    * Check the issue comments/labels to see whether someone else has indicated that they are working on it. If someone is already working on it and there has been activity within the last 7 days, you may want to find a different issue to work on.
-* **Issues tagged with one of these labels: `blocked`, `not ready for work`, `ticket work required`, `CC staff only` are not available to the community. Do not work on these.**
-    * Issues tagged `blocked` are blocked by other work that needs to be done first.
-    * Issues tagged `not ready for work` or `ticket work required` need additional work done on the issue before they can be opened to community contributors.
-    * Issues tagged `CC staff only` are not suitable for community contribution, usually because it requires infrastructure access or institutional knowledge that would be impractical to provide to the community.
-* **Issues without any of the above labels _may_ be open for contribution.**
-    * Please add a comment to ask whether the issue is available before starting work.
+We make extensive use of issue labels to designate the priority, status and beginner-friendliness of various issues. We have a standard set of labels across all projects, [documented here](https://github.com/creativecommons/ccos-scripts/blob/master/normalize_repos/labels.json). Here are some of the ones that are most relevant to finding a good issue to work on:
+
+- **Issues available for community contribution:**
+  - The following tags mark issues that are open for community contribution:
+    - `help wanted`: Open to participation from the community but not necessarily beginner-friendly
+    - `good first issue`: Open to participation from the community and friendly towards new contributors
+  - You do not need our permission to work on one of these issues.
+  - You may work on an issue labeled `good first issue` even if it's not your first issue.
+* **Issues not available for community contribution:**
+  - The following tags mark issues that are _not_ open for community contribution:
+    - `🔒 staff only`: Requires infrastructure access or institutional knowledge that would be impractical to provide to the community
+  - Do not work on these.
+- **Issues not ready for work:**
+  - The following tags mark issues that are _not_ open for community contribution:
+    - `🚧 blocked`: Blocked by other work that needs to be done first
+    - `🧹 ticket work required`: Needs additional work before it is ready to be taken up
+    - `🚦 awaiting triage`: Has not been triaged by a maintainer
+  - Do not work on these.
+- **Issues without any of the above labels:**
+  - These issues _may_ (or may not) be open for contribution.
+  - Please add a comment asking one of the maintainers to triage the issue and label it as appropriate.
 
 Some helpful saved searches on GitHub than can assist with finding an issue:
-- [issues labeled "good first issue"](https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
-- [issues labeled "help wanted"](https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22help+wanted%22)
-- [issues labeled "help wanted", and not labeled as "in progress"](https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22help+wanted%22+-label%3A%22in+progress%22)
-- [incomplete pull requests labeled "help wanted"](https://github.com/search?q=org%3Acreativecommons+is%3Apr+is%3Aopen+label%3A%22help+wanted%22)
+- [issues labeled "good first issue"](https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22+-linked%3Apr)
+- [issues labeled "help wanted"](https://github.com/search?q=org%3Acreativecommons+is%3Aissue+is%3Aopen+label%3A%22help+wanted%22+-linked%3Apr)
+- [PRs labeled "help wanted"](https://github.com/search?q=org%3Acreativecommons+is%3Apr+is%3Aopen+label%3A%22help+wanted%22)
+
+Check the issue comments/labels to see whether someone else has indicated that they are working on it. If someone is already working on it and there has been activity within the last 7 days, you may want to find a different issue to work on.
 
 ## Contribution process
 
-Once you've found an issue you'd like to work on, please follow these steps to make your contribution:
+Once you've found an issue you'd like to work on, and is not already in progress, please follow these steps to make your contribution:
 
 1. Comment on it and say you're working on that issue. This is to avoid conflicts with others also working on the issue.
     * A project maintainer may mark the issue with an `in progress` label at this point, but we don't always get around to that.