You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
minor updates to intern overview, appl guide, and project formatting
- overview
- updated mentors
- application guide
- added internal links
- updated formatting & whitespace
- project ideas formatting
- skills and mentors fields are now markdown so they can be lists
Your first step should be to understand Creative Commons and what we do. We're not simply an open source software project like many other mentorship organization. We're a nonprofit organization and we have a lot of different programs – technical, legal, educational, public policy, organizational, and more. You can start reading about us at our [official website](https://creativecommons.org) and you can find plenty of information through searching about us. You'll need to know a decent amount about us in order to help us effectively.
24
31
25
-
If you have a question about how we work, our programs, our licenses, or anything like that, please don't hesitate to ask!
32
+
Your first step should be to understand Creative Commons and what we do. We're
33
+
not simply an open source software project like many other mentorship
34
+
organization. We're a nonprofit organization and we have a lot of different
35
+
programs – technical, legal, educational, public policy, organizational, and
36
+
more. You can start reading about us at our [official
37
+
website](https://creativecommons.org/) and you can find plenty of information
38
+
through searching about us. You'll need to know a decent amount about us in
39
+
order to help us effectively.
40
+
41
+
If you have a question about how we work, our programs, our licenses, or
42
+
anything like that, please don't hesitate to ask!
43
+
26
44
27
45
### Join the Community
28
-
[Join the `#cc-dev-internships` channel on the CC Slack or the CC Developers mailing list](/community/) as early as possible to introduce yourself and get feedback on your ideas. All our mentors will be on Slack and respond to emails on the mailing list and it is better to post there rather than contacting them individually. Feel free to ask questions!
46
+
47
+
[Join the `#cc-dev-internships` channel on the CC Slack or the CC Developers
48
+
mailing list](/community/) as early as possible to introduce yourself and get
49
+
feedback on your ideas. All our mentors will be on Slack and respond to emails
50
+
on the mailing list and it is better to post there rather than contacting them
51
+
individually. Feel free to ask questions!
52
+
29
53
30
54
### Pick a Project
31
-
Your next step should be to pick a particular project that you're interested in working on. The [Overview page](/internships/) will cover the current internship rounds and link to related project ideas.
32
55
33
-
Once you pick the project you're interested in, make sure to learn about the project thoroughly. You're going to be spending three months working on the project and you'll need to understand what the work entails so that you can plan the work out ahead of time and submit a strong application. The project descriptions are quite short so we expect you to do a lot of work here duron your own taking those descriptions and fleshing them out into a more detailed project plan and implementation timeline.
56
+
Your next step should be to pick a particular project that you're interested in
57
+
working on. The [Overview page](/internships/) will cover the current
58
+
internship rounds and link to related project ideas.
59
+
60
+
Once you pick the project you're interested in, make sure to learn about the
61
+
project thoroughly. You're going to be spending three months working on the
62
+
project and you'll need to understand what the work entails so that you can
63
+
plan the work out ahead of time and submit a strong application. The project
64
+
descriptions are quite short so we expect you to do a lot of work here duron
65
+
your own taking those descriptions and fleshing them out into a more detailed
66
+
project plan and implementation timeline.
67
+
68
+
The mentors are here to help you. We expect you to have a lot of questions
69
+
along the way and we're happy to answer them.
34
70
35
-
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.
36
71
37
72
### Contribute!
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.
73
+
74
+
You will need to make at least one contribution to a Creative Commons project
75
+
so that we can see a sample of your work. This is important for our evaluation
76
+
of your application. For more details, see the [*Contributing*
77
+
section](#contributing), below. Note that for Season of Docs applicants,
78
+
mentions of "code contributions" in this guide are somewhat synonymous with
79
+
documentation contributions, and we would like to see both code and
80
+
documentation related contributions from Season of Docs applicants to show a
81
+
well rounded skill set.
82
+
39
83
40
84
### Draft Application
41
-
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.
85
+
86
+
The final step is to create a draft application and share it with your chosen
87
+
project's mentors for feedback. **Do not wait until the last minute to do
88
+
this.** You should ideally get at least two rounds of feedback from the mentors
89
+
before you submit your final application. For more details, see the
90
+
[*Application* section](#application), below.
91
+
42
92
43
93
## Contributing
44
94
95
+
45
96
### Why contribute?
46
-
Contributions are for you to get a sense of what it's like to contribute to an open source project (getting used to the GitHub workflow, interacting with other contributors, etc.) and for us to see a sample of your work/skills. If we are impressed by your contributions, we are more likely to select you as an intern.
97
+
98
+
Contributions are for you to get a sense of what it's like to contribute to an
99
+
open source project (getting used to the GitHub workflow, interacting with
100
+
other contributors, etc.) and for us to see a sample of your work/skills. If we
101
+
are impressed by your contributions, we are more likely to select you as an
102
+
intern.
103
+
47
104
48
105
### How to contribute
49
-
Please read our [Contributing Code](/contributing-code/) page for information on how to contribute. You can contribute to any Creative Commons repository, although it's better if you demonstrate skills related to the project you are applying for. Also, check your project's description for more specific contribution guidelines (not all of them will have them).
50
106
51
-
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.
107
+
Please read our [Contributing Code](/contributing-code/) page for information
108
+
on how to contribute. You can contribute to any Creative Commons repository,
109
+
although it's better if you demonstrate skills related to the project you are
110
+
applying for. Also, check your project's description for more specific
111
+
contribution guidelines (not all of them will have them).
112
+
113
+
If you're applying via Outreachy, remember to record your contribution via the
114
+
Outreachy website! You can record contributions even if you have not yet
115
+
received feedback on them or if they have not been merged – our mentors are
116
+
busy so we can be slow to provide feedback.
117
+
52
118
53
119
### 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
120
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.
121
+
If you are applying for Google Season of Docs, one of the best ways you can
122
+
contribute to documentation is to find places where documentation can be
123
+
improved, and open an issue for it on GitHub. Be sure to state what,
124
+
specifically, could be improved, and how you plan to improve it.
125
+
126
+
We prefer to see contributions that make substantive changes or improvements to
127
+
documentation such as improving the clarity of existing documentation or
128
+
creating new documentation. Typo and grammar fixes are, of course, still
129
+
welcome, but we do like to see more substantive improvements.
130
+
131
+
We would also like to see Season of Docs applicants make some code
132
+
contributions to show a well rounded skillset and understanding of the project.
57
133
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
134
60
135
## Application
61
136
62
-
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.
137
+
Your final application is very important to us. This is what we will use to
138
+
determine how well you understand the project and how likely you are to
139
+
successfully complete it. As part of the application, you should take the
140
+
project description and flesh it out into a more detailed project plan and
141
+
implementation timeline. The project descriptions are all fairly short and some
142
+
of them include multiple paths for the project. So, we expect you to do a lot
143
+
of work here to turn those into a feasible plan and timeline for a complete
144
+
project that you can ship during your internship.
145
+
146
+
**This is not something you should be working on in isolation.** We expect you
147
+
to have a lot of questions for the mentors along the way as you try and
148
+
understand the project, come up with ideas, evaluate feasibility, etc. We also
149
+
expect you to come up with a first draft and get feedback from mentors before
150
+
you submit the final application on the program's official site.
151
+
152
+
We suggest reading some articles on writing good Google Summer of Code
153
+
proposals (even if you're applying for Outreachy). Here are some examples:
154
+
-[How to write a kick-ass proposal for Google Summer of Code][kickass]
155
+
-[5 Tips to get your Google Summer of Code proposal accepted][fivetips]
156
+
-[Writing a solid Google Summer of Code Proposal][writingsolid]
63
157
64
-
**This is not something you should be working on in isolation.** We expect you to have a lot of questions for the mentors along the way as you try and understand the project, come up with ideas, evaluate feasibility, etc. We also expect you to come up with a first draft and get feedback from mentors before you submit the final application on the program's official site.
We suggest reading some articles on writing good Google Summer of Code proposals (even if you're applying for Outreachy). Here are some examples:
67
-
*[How to write a kick-ass proposal for Google Summer of Code](http://teom.org/blog/kde/how-to-write-a-kick-ass-proposal-for-google-summer-of-code/)
68
-
*[5 Tips to get your Google Summer of Code proposal accepted](https://people.csail.mit.edu/baghdadi/TXT_blog/5_advices_to_get_your_proposal_accepted.lyx.html)
69
-
*[Writing a solid Google Summer of Code Proposal](https://medium.com/@evenstensberg/writing-a-solid-google-summer-of-code-proposal-a200fc6e785b)
70
162
71
163
### Template
72
164
73
-
You must use **[our internship project template](https://docs.google.com/document/d/18LWuA_iTSGSeRFtpVQdfOoz1G30ZgJg-_K0lNSQBYd0/)** to create your application. Please make sure that your mentors have comment permissions before you share your document with them.
165
+
You must use **[our internship project template][projecttemplate]** to create
166
+
your application. Please make sure that your mentors have comment permissions
167
+
before you share your document with them.
168
+
169
+
If you are applying for Outreachy, please link to the project proposal document
170
+
created using this template from your final Outreachy application.
If you are applying for Outreachy, please link to the project proposal document created using this template from your final Outreachy application.
76
174
77
175
## Contacting Mentors
78
176
79
-
All the CC mentors are on [Slack](/community/). **Please use public channels on Slack as the primary method of communication.** Public channels are better than direct messages because it allows any available mentor (or even another applicant) to answer your questions and interact with you. It also allows other applicants who have the same questions to benefit from the answers the mentor is giving you.
177
+
All the CC mentors are on [Slack](/community/). **Please use public channels on
178
+
Slack as the primary method of communication.** Public channels are better than
179
+
direct messages because it allows any available mentor (or even another
180
+
applicant) to answer your questions and interact with you. It also allows other
181
+
applicants who have the same questions to benefit from the answers the mentor
182
+
is giving you.
80
183
81
-
**Please ask mentors specific questions.** We don't know how to help you get started unless we know what you have questions about. People come from a variety of experiences and backgrounds and the things you may be confused about may be totally different than the things that someone else has questions about. Please give us as much information as possible, the more you tell us, the better we can help you.
184
+
**Please ask mentors specific questions.** We don't know how to help you get
185
+
started unless we know what you have questions about. People come from a
186
+
variety of experiences and backgrounds and the things you may be confused about
187
+
may be totally different than the things that someone else has questions about.
188
+
Please give us as much information as possible, the more you tell us, the
189
+
better we can help you.
82
190
83
-
Remember that the mentors are busy – we've got full-time jobs or other commitments. It's good to follow up if you don't get a response, but wait a couple of days first.
191
+
Remember that the mentors are busy – we've got full-time jobs or other
192
+
commitments. It's good to follow up if you don't get a response, but wait a
193
+
couple of days first.
194
+
195
+
**Please refrain from addressing mentors as "sir" or "ma'am". We prefer to be
196
+
addressed by our first names or usernames.**
84
197
85
-
**Please refrain from addressing mentors as "sir" or "ma'am". We prefer to be addressed by our first names or usernames.**
86
198
87
199
## Intern Selection Criteria
88
200
89
201
Here are a few things we consider when selecting interns:
90
-
***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.
91
-
***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.
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.
93
-
***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.
202
+
-**Quality of the proposal**: This is the most important thing. A good
203
+
proposal includes attention to detail, externally measurable milestones,
204
+
consideration for future maintainability and community involvement, and a
205
+
demonstration of your skills.
206
+
-**Community involvement**: One of our major goals is to build an active
207
+
development community and attract long-term contributors. We see engaging in
208
+
the community, whether it's asking questions, helping other students,
209
+
contributing code, filing bugs, or whatever else, as a sign that you're
210
+
genuinely interested in our work.
211
+
-**Contributions**: We appreciate seeing your contributions, they help us
212
+
gauge your ability to orient yourself to a new codebase, or the quality of
213
+
your writing. Contribution quality is instrumental in giving us the confidence
214
+
that you have the skills necessary to implement your proposal.
215
+
-**Communication skills and initiative**: These are essential to completing a
216
+
successful project. Things we look for (among others): asking specific and
217
+
detailed questions, following up on conversations, making sure to read
218
+
available resources before asking questions, being patient and responding to
219
+
critical feedback well.
220
+
94
221
95
222
## Number of Accepted Interns
96
223
97
-
Please, note that any internship program has a limited amount of projects that are able be funded. Therefore, we will probably not be able to select an intern for every project idea that we have listed. CC will be allocated a limited number of project slots by the program and we can only accept the number of interns that we have slots for.
224
+
Please, note that any internship program has a limited amount of projects that
225
+
are able be funded. Therefore, we will probably not be able to select an intern
226
+
for every project idea that we have listed. CC will be allocated a limited
227
+
number of project slots by the program and we can only accept the number of
0 commit comments