Skip to content

Commit 068341c

Browse files
kgodeykgodey
authored
Merge branch 'master' into patch-1
2 parents b5adccb + 8455e7c commit 068341c

File tree

6 files changed

+205
-8
lines changed

6 files changed

+205
-8
lines changed

‎content/community/community-teams/contents.lr renamed to ‎content/community/community-team/contents.lr

+4-4
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ _model: page
22
---
33
_template: page-with-toc.html
44
---
5-
title: CC Community Teams
5+
title: CC Community Team
66
---
77
body:
88

@@ -57,8 +57,8 @@ Privileges and access will be granted per-repository. For example, if you are ap
5757

5858
| Name | Privileges | Requirements |
5959
| ---- |----------- |------------- |
60-
| **Project Contributor**<br>You should apply for this role if you are interested in dipping your toe into Community Teams. | <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. |
61-
| **Project Member**<br>If you've given Community Teams 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“ |
60+
| **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. |
61+
| **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“ |
6262
| **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“ |
6363
| **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. |
6464

@@ -84,7 +84,7 @@ We know that waiting can be difficult, but please refrain from sending messages
8484

8585
**What counts as a contribution?**
8686

87-
Contributions can be any of the things listed under ["How to Contribute"](https://opensource.creativecommons.org/community/community-teams/#how-to-contribute) above. If you think something should count as a contribution that's not listed above, please put that in your application.
87+
Contributions can be any of the things listed under ["How to Contribute"](https://opensource.creativecommons.org/community/community-team/#how-to-contribute) above. If you think something should count as a contribution that's not listed above, please put that in your application.
8888

8989
Individual repositories may have additional work that counts as a contribution. If this is the case, these additional contributions will be documented in that repository's README.
9090

‎content/community/community-team/members/contents.lr

+5
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
_model: page
2+
---
3+
_template: community_team_list.html
4+
---
5+
title: Community Team Members

‎content/internships/applicant-guide/contents.lr

+11-3
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ title: Open Source Internships: Applicant Guide
66
---
77
body:
88

9-
Creative Commons participates in open source mentorship programs such as [Google Summer of Code](https://summerofcode.withgoogle.com/) and [Outreachy](https://www.outreachy.org/). Details about specific programs and rounds are listed in the [Overview page](/internships); this page serves as a general guide to applicants.
9+
Creative Commons participates in open source mentorship programs such as [Google Summer of Code](https://summerofcode.withgoogle.com/), [Google Season of Docs](https://developers.google.com/season-of-docs/), and [Outreachy](https://www.outreachy.org/). Details about specific programs and rounds are listed in the [Overview page](/internships); this page serves as a general guide to applicants.
1010

1111
## Getting Started
1212

@@ -16,6 +16,7 @@ If you are interested in applying to be an open source intern at CC, here's a fe
1616

1717
Here are some resources:
1818
* [Google Summer of Code student guide](https://google.github.io/gsocguides/student/)
19+
* [Google Season of Docs technical writer guide](https://developers.google.com/season-of-docs/docs/tech-writer-guide)
1920
* [Outreachy applicant guide](https://www.outreachy.org/docs/applicant/)
2021

2122
### Understand CC
@@ -34,7 +35,7 @@ Once you pick the project you're interested in, make sure to learn about the pro
3435
The mentors are here to help you. We expect you to have a lot of questions along the way and we're happy to answer them.
3536

3637
### Contribute!
37-
You will need to make at least one contribution to a Creative Commons project so that we can see a sample of your work. This is important for our evaluation of your application. For more details, see the *Contributing* section below.
38+
You will need to make at least one contribution to a Creative Commons project so that we can see a sample of your work. This is important for our evaluation of your application. For more details, see the *Contributing* section below. Note that for Season of Docs applicants, metions of "code contributions" in this guide are somewhat synonymous with documentation contributions, and we would like to see both code and documentation related contributions from Season of Docs applicants to show a well rounded skill set.
3839

3940
### Draft Application
4041
The final step is to create a draft application and share it with your chosen project's mentors for feedback. **Do not wait until the last minute to do this.** You should ideally get at least two rounds of feedback from the mentors before you submit your final application. For more details, see the *Draft Application* section below.
@@ -49,6 +50,13 @@ Please read our [Contributing Code](/contributing-code) page for information on
4950

5051
If you're applying via Outreachy, remember to record your contribution via the Outreachy website! You can record contributions even if you have not yet received feedback on them or if they have not been merged – our mentors are busy so we can be slow to provide feedback.
5152

53+
### Contributing Documentation
54+
If you are applying for Google Season of Docs, one of the best ways you can contribute to documentation is to find places where documentation can be improved, and open an issue for it on GitHub. Be sure to state what, specifically, could be improved, and how you plan to improve it.
55+
56+
We prefer to see contributions that make substantive changes or improvements to documentation such as improving the clarity of existing documentation or creating new documentation. Typo and grammar fixes are, of course, still welcome, but we do like to see more substantive improvements.
57+
58+
We would also like to see Season of Docs applicants make some code contributions to show a well rounded skillset and understanding of the project.
59+
5260
## Application
5361

5462
Your final application is very important to us. This is what we will use to determine how well you understand the project and how likely you are to successfully complete it. As part of the application, you should take the project description and flesh it out into a more detailed project plan and implementation timeline. The project descriptions are all fairly short and some of them include multiple paths for the project. So, we expect you to do a lot of work here to turn those into a feasible plan and timeline for a complete project that you can ship during your internship.
@@ -81,7 +89,7 @@ Remember that the mentors are busy – we've got full-time jobs or other commitm
8189
Here are a few things we consider when selecting interns:
8290
* **Quality of the proposal**: This is the most important thing. A good proposal includes attention to detail, externally measurable milestones, consideration for future maintainability and community involvement, and a demonstration of your skills.
8391
* **Community involvement**: One of our major goals is to build an active development community and attract long-term contributors. We see engaging in the community, whether it's asking questions, helping other students, contributing code, filing bugs, or whatever else, as a sign that you're genuinely interested in our work.
84-
* **Code contributions**: We appreciate seeing your code, it helps us gauge your ability to orient yourself to a new codebase, as well as giving us confidence that you have the skills necessary to implement your proposal.
92+
* **Contributions**: We appreciate seeing your contributions, they help us gauge your ability to orient yourself to a new codebase, or the quality of your writing. Contribution quality is instrumental in giving us the confidence that you have the skills necessary to implement your proposal.
8593
* **Communication skills and initiative**: These are essential to completing a successful project. Things we look for (among others): asking specific and detailed questions, following up on conversations, making sure to read available resources before asking questions, being patient and responding to critical feedback well.
8694

8795
## Number of Accepted Interns

‎databags/community_team_members.json

+156
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,156 @@
1+
{
2+
"projects": [
3+
{
4+
"members": [
5+
{
6+
"name": "Charini Nanayakkara",
7+
"role": "Project Core Committer"
8+
},
9+
{
10+
"name": "K.S. Srinidhi Krishna",
11+
"role": "Project Core Committer"
12+
}
13+
],
14+
"name": "CC Catalog",
15+
"repos": "cccatalog"
16+
},
17+
{
18+
"members": [
19+
{
20+
"name": "Ari Madian",
21+
"role": "Project Core Committer"
22+
},
23+
{
24+
"name": "Ayan Choudhary",
25+
"role": "Project Core Committer"
26+
}
27+
],
28+
"name": "CC Search",
29+
"repos": "cccatalog-frontend"
30+
},
31+
{
32+
"members": [
33+
{
34+
"name": "Mayank Nader",
35+
"role": "Project Maintainer"
36+
}
37+
],
38+
"name": "CC Search Browser Extension",
39+
"repos": "ccsearch-browser-extension"
40+
},
41+
{
42+
"members": [
43+
{
44+
"name": "Dhruvi Butti",
45+
"role": "Project Core Committer"
46+
}
47+
],
48+
"name": "CC Open Source",
49+
"repos": "creativecommons.github.io-source"
50+
},
51+
{
52+
"members": [
53+
{
54+
"name": "Krystle Salazar",
55+
"role": "Project Core Committer"
56+
}
57+
],
58+
"name": "Legal Database",
59+
"repos": "caselaw"
60+
},
61+
{
62+
"members": [
63+
{
64+
"name": "Shubham Pandey",
65+
"role": "Project Contributor"
66+
}
67+
],
68+
"name": "License Buttons",
69+
"repos": "licensebuttons"
70+
},
71+
{
72+
"members": [
73+
{
74+
"name": "Ari Madian",
75+
"role": "Project Maintainer"
76+
},
77+
{
78+
"name": "Olga Bulat",
79+
"role": "Project Maintainer"
80+
},
81+
{
82+
"name": "Hemanth Kumar",
83+
"role": "Project Contributor"
84+
},
85+
{
86+
"name": "Jacqueline Binya",
87+
"role": "Project Contributor"
88+
}
89+
],
90+
"name": "License Chooser",
91+
"repos": "chooser"
92+
},
93+
{
94+
"members": [
95+
{
96+
"name": "Bhumij Gupta",
97+
"role": "Project Maintainer"
98+
}
99+
],
100+
"name": "Link Checker",
101+
"repos": "cc-link-checker"
102+
},
103+
{
104+
"members": [
105+
{
106+
"name": "Mar\u00eda Bel\u00e9n Guaranda Cabezas ",
107+
"role": "Project Maintainer"
108+
},
109+
{
110+
"name": "Subham Sahu",
111+
"role": "Project Core Committer"
112+
}
113+
],
114+
"name": "Linked Commons",
115+
"repos": "cccatalog-dataviz"
116+
},
117+
{
118+
"members": [
119+
{
120+
"name": "Ana Paula Rocha",
121+
"role": "Project Collaborator"
122+
}
123+
],
124+
"name": "Platform Toolkit",
125+
"repos": "mp"
126+
},
127+
{
128+
"members": [
129+
{
130+
"name": "Dhruv Bhanushali",
131+
"role": "Project Maintainer"
132+
},
133+
{
134+
"name": "Dhruvi Butti",
135+
"role": "Project Core Committer"
136+
},
137+
{
138+
"name": "Chidiebere Onyegbuchulem",
139+
"role": "Project Member"
140+
}
141+
],
142+
"name": "Vocabulary",
143+
"repos": "fonts, vocabulary, vue-vocabulary"
144+
},
145+
{
146+
"members": [
147+
{
148+
"name": "Ahmad Bilal",
149+
"role": "Project Core Committer"
150+
}
151+
],
152+
"name": "WordPress Plugin",
153+
"repos": "wp-plugin-creativecommons"
154+
}
155+
]
156+
}

‎templates/community_team_list.html

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
{% extends "layout.html" %}
2+
{% block title %}{{ this.title }}{% endblock %}
3+
{% block body %}
4+
<p>This is a list of all CC Community Team members, and their roles and privileges.</p>
5+
<p>For more information about CC Community Team, please see <a href="/content/community/community-teams/">the Community Team Page</a>.</p>
6+
<h2>Project Teams</h2>
7+
{% for project in bag('community_team_members.projects') %}
8+
<h3>{{ project.name }}</h3>
9+
<p>These team members have permissions in the <code>{{ project.repos }}</code> repo(s).</p>
10+
<table class="table table-striped" style="width: 75%;">
11+
<thead class="thead-dark">
12+
<tr>
13+
<th scope="col">Role</th>
14+
<th scope="col">Member Name</th>
15+
</tr>
16+
</thead>
17+
<tbody>
18+
{% for member in project.members %}
19+
<tr>
20+
<td scope="row">{{ member.role }}</td>
21+
<td scope="row">{{ member.name }}</td>
22+
</tr>
23+
{% endfor %}
24+
</tbody>
25+
</table>
26+
{% endfor %}
27+
{% endblock %}

‎templates/layout.html

+2-1
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,8 @@
7777
<div class="dropdown-menu" aria-labelledby="navbarCommunityDropdown">
7878
{% for href, title in [
7979
['/community', 'Join the Community'],
80-
['/community/community-teams', 'Community Teams'],
80+
['/community/community-team', 'Community Team'],
81+
['/community/community-team/members', 'Community Team Members'],
8182
['/community/write-a-blog-post', 'Write a Blog Post'],
8283
['/community/code-of-conduct', 'Code of Conduct'],
8384
['/community/code-of-conduct/enforcement', 'Code of Conduct Enforcement'],

0 commit comments

Comments
 (0)