|
1 | | -_model: page |
| 1 | +_model: redirect |
2 | 2 | --- |
3 | | -_template: page-with-toc.html |
| 3 | +target: /programs/applicant-guide/ |
4 | 4 | --- |
5 | | -title: Open Source Internships: Applicant Guide |
6 | | ---- |
7 | | -description: 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. |
8 | | ---- |
9 | | -body: |
10 | | - |
11 | | - |
12 | | -## Getting Started |
13 | | - |
14 | | -If you are interested in applying to be an open source intern at Creative |
15 | | -Commons (CC), here's a few things that will help: |
16 | | - |
17 | | - |
18 | | -### Understand the Program |
19 | | - |
20 | | -Here are some resources: |
21 | | -- [Google Summer of Code student guide][gsocguide] |
22 | | -- [Google Season of Docs technical writer guide][gsodguide] |
23 | | -- [Outreachy applicant guide][outreachyguide] |
24 | | - |
25 | | -[gsocguide]: https://google.github.io/gsocguides/student/ |
26 | | -[gsodguide]: https://developers.google.com/season-of-docs/docs/tech-writer-guide |
27 | | -[outreachyguide]: https://www.outreachy.org/docs/applicant/ |
28 | | - |
29 | | - |
30 | | -### Understand CC |
31 | | - |
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 | | - |
44 | | - |
45 | | -### Join the Community |
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 | | - |
53 | | - |
54 | | -### Pick a Project |
55 | | - |
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. |
70 | | - |
71 | | - |
72 | | -### Contribute! |
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 | | - |
83 | | - |
84 | | -### Draft Application |
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 | | - |
92 | | - |
93 | | -## Contributing |
94 | | - |
95 | | - |
96 | | -### Why contribute? |
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 | | - |
104 | | - |
105 | | -### How to contribute |
106 | | - |
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 | | - |
118 | | - |
119 | | -### Contributing Documentation |
120 | | - |
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. |
133 | | - |
134 | | - |
135 | | -## Application |
136 | | - |
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] |
157 | | - |
158 | | -[kickass]: http://teom.org/blog/kde/how-to-write-a-kick-ass-proposal-for-google-summer-of-code/ |
159 | | -[fivetips]: https://people.csail.mit.edu/baghdadi/TXT_blog/5_advices_to_get_your_proposal_accepted.lyx.html |
160 | | -[writingsolid]: https://medium.com/@evenstensberg/writing-a-solid-google-summer-of-code-proposal-a200fc6e785b |
161 | | - |
162 | | - |
163 | | -### Template |
164 | | - |
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. |
171 | | - |
172 | | -[projecttemplate]: https://docs.google.com/document/d/18LWuA_iTSGSeRFtpVQdfOoz1G30ZgJg-_K0lNSQBYd0/edit |
173 | | - |
174 | | - |
175 | | -## Contacting Mentors |
176 | | - |
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. |
183 | | - |
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. |
190 | | - |
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.** |
197 | | - |
198 | | - |
199 | | -## Intern Selection Criteria |
200 | | - |
201 | | -Here are a few things we consider when selecting interns: |
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 | | - |
221 | | - |
222 | | -## Number of Accepted Interns |
223 | | - |
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 |
228 | | -interns that we have slots for. |
229 | | - |
230 | | - |
231 | | -## Thank you |
232 | | - |
233 | | -Thank you for your contributions and your time! |
| 5 | +_discoverable: no |
0 commit comments