Added project maintainer and made some content changes.

Author: kgodey

content/community/community-team/contents.lr

@@ -10,19 +10,20 @@ Creative Commons (CC) is building a community volunteer team to help us develop
 
 Joining the community team involves three steps:
 
-1.  Joining [one of our community forums](https://opensource.creativecommons.org/community/)
-2.  Making contributions
-3.  Applying for a role when you're eligible
+1. Joining [one of our community forums](https://opensource.creativecommons.org/community/)
+2. Making contributions
+3. Applying for a role when you're eligible
 
 ### Benefits of joining the Community Team
 
--   You'll  gain practical, real world, open source experience.
--   You'll build both technical and soft skills.
--   You'll work closely with and be mentored by CC's experienced software engineers and community contributors.
--   You'll build your resume.
--   You'll be given "priority" in internship applications (not an automatic bump, but if the applicant is known for good quality, that's a big advantage)
--   You'll advance the Creative Commons mission
--   You'll engage with CC's global Free/Libre and Open Source (FLOSS) community!
+- You'll  gain practical, real world, open source experience.
+- You'll gain both technical and soft skills and build up your resume.
+- You'll work closely with and be mentored by CC's experienced software engineers and community contributors.
+- You'll have the ability to get a personal letter of recommendation from CC staff if you've contributed a lot.
+- You'll be given "priority" in internship applications (not a guaranteed acceptance, but you'll have some advantage).
+- You'll engage with CC's global Free/Libre and Open Source (FLOSS) community!
+- Most importantly, you'll advance the Creative Commons mission.
+
 
 How to Contribute
 -----------------
@@ -55,19 +56,20 @@ These roles are specific to a single CC project (usually limited to a single git
 
 Privileges and access will be granted per-repository. For example, if you are applying for a role on the `cccatalog-frontend` repository, you would want to concentrate your contributions on `cccatalog-frontend`.
 
-| Name | Privileges | Requirements |
-| ---- |----------- |------------- |
+| Name | Privileges | Guidelines for Applying |
+| ---- |----------- |------------------------ |
 | **Project Contributor**<br>You should apply for this role if you are interested in dipping your toe into Community Team. | <li>Invitation to private community contributors Slack channel.</li><li>Addition to Community Team page on CC Open Source.</li> | 3 contributions.<br><br>1 merged pull request or “Great Contribution” to the project you’re applying for. |
-| **Project Member**<br>If you've given Community Team a shot and are ready to take the next step, this role is for you! As a Project Member, you will gain experience with issue triage and real-world open source governance workflows. | <li>All <strong>Project Contributor</strong> privileges.</li><li>Addition to creativecommons GitHub organization with Triage access to the GitHub repo associated with the project.</li><ul style="list-style-type: circle"><li>This will allow you to update labels on issues, etc.</li></ul> | 15 contributions with at least 4 pull requests* submitted to the project you’re applying for.<br><br>3 “Great Contributions“ |
-| **Project Collaborator**<br>You should apply for this role if you are interested in being deeply involved with a project, and engaging closely with CC Staff, Project Maintainers, and Core Committers. This role also gives you the opportunity to mentor others through GSoC and Outreachy. | <li>All <strong>Project Member</strong> privileges.</li><li>Addition to project’s CODEOWNERs file.</li><ul style="list-style-type: circle"><li>This will allow your PR reviews to block merge.</li><li>This will auto assign you PRs to review.</li></ul><li>Eligibility to mentor interns for programs like GSoC and Outreachy for Creative Commons.</li><li>Invitation to some of CC’s internal meetings and Slack channels.</li><li>Letter of recommendation from Creative Commons available on request.</li>  | 35 contributions with at least 8 pull requests* submitted to the project you’re applying for.<br><br>5 “Great Contributions“ |
-| **Project Core Committer** | <li>All <strong>Project Collaborator</strong> privileges.</li><li>Write access to the project's GitHub repo.</li><ul style="list-style-type: circle"><li>This will allow you to merge PRs.</li></ul> | *Not Applicable*<br>Maintainers will identify and invite standout contributors. |
+| **Project Member**<br>If you've given Community Team a shot and are ready to take the next step, this role is for you! As a Project Member, you will gain experience with issue triage and real-world open source governance workflows. | <li>All <strong>Project Contributor</strong> privileges.</li><li>Addition to creativecommons GitHub organization with Triage access to the GitHub repo associated with the project.</li><ul style="list-style-type: circle"><li>This will allow you to update labels on issues, etc.</li></ul> | 15 contributions with at least 4 pull requests* submitted to the project you’re applying for.<br><br>2 “Great Contributions“ |
+| **Project Collaborator**<br>You should apply for this role if you are interested in being deeply involved with a project, and engaging closely with CC Staff, Project Maintainers, and Core Committers. This role also gives you the opportunity to mentor others through GSoC and Outreachy. | <li>All <strong>Project Member</strong> privileges.</li><li>Addition to project’s CODEOWNERs file.</li><ul style="list-style-type: circle"><li>This will allow your PR reviews to block merge.</li><li>This will auto assign you PRs to review.</li></ul><li>Eligibility to mentor interns for programs like GSoC and Outreachy for Creative Commons.</li><li>Invitation to some of CC’s internal meetings and Slack channels.</li><li>Letter of recommendation from Creative Commons available on request.</li>  | 30 contributions with at least 8 pull requests* submitted to the project you’re applying for.<br><br>3 “Great Contributions“ |
+| **Project Core Committer** | <li>All <strong>Project Collaborator</strong> privileges.</li><li>Write access to the project's GitHub repo.</li><ul style="list-style-type: circle"><li>This will allow you to merge PRs.</li></ul> | 45 contributions with at least 12 pull requests* submitted to the project you’re applying for.<br><br>5 “Great Contributions“ |
+| **Project Maintainer** | <li>All <strong>Project Core Committer</strong> privileges.</li><li>Maintain access to the project's GitHub repo.</li><ul style="list-style-type: circle"><li>This will allow you to manage some repository settings.</li></ul> | *Not Applicable*<br>Maintainers will identify and invite standout contributors. |
 
 ### Community Roles
 
 These roles are not project based and are for folks interested in helping grow CC's open source community by ensuring all contributors have a good experience and spreading the word about CC's projects.
 
-| Name | Privileges | Requirements |
-| ---- |----------- |------------- |
+| Name | Privileges | Guidelines for Applying |
+| ---- |----------- |------------------------ |
 | **Community Contributor**<br>If you'd like to try out engaging with the CC community on a deeper level, but aren't familiar with the technical side of things, you might like this role! | <li>Invitation to private community contributors Slack channel.</li><li>Addition to Community Team page on CC Open Source.</li> | 3 contributions.<br><br>1 published tweet to the CC Open Source Twitter account based on an idea submitted by you or “Great Contribution” on any project.<br><br>General community interaction. |
 | **Community Collaborator**<br>So you've tried out being a Community Contributor, want to engage more directly with the CC team and more deeply with the community itself. This role is for you! | <li>All <strong>Community Contributor</strong> privileges.</li><li>Comment-only access to the Open Source Community project on Asana, with the option to pick up tasks if desired.</li>  | 15 contributions.<br><br>At least five people helped on Slack or the mailing list. |
 | **Community Maintainer** | <li>All <strong>Community Collaborator</strong> privileges.</li><li>Manager permission on CC’s developer mailing list.</li><li>Access to tweet directly from CC Open Source account.</li><li>Letter of recommendation from Creative Commons available on request.</li> | *Not Applicable*<br>Maintainers will identify and invite standout contributors |