|
| 1 | +_model: page |
| 2 | +--- |
| 3 | +_template: page-with-toc.html |
| 4 | +--- |
| 5 | +title: Information for Potential Outreachy Applicants |
| 6 | +--- |
| 7 | +body: |
| 8 | + |
| 9 | +Creative Commons is participating in Outreachy's round of internships running from **Dec 2019 to Mar 2020**. Please see **[the official Outreachy Creative Commons internship page](https://www.outreachy.org/december-2019-to-march-2020-internship-round/communities/creative-commons/#better-visualization-tools-for-the-cc-network)** for project-specific information. Some general information and tips are below. |
| 10 | + |
| 11 | +### Contacting Mentors |
| 12 | + |
| 13 | +All the CC Outreachy 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. |
| 14 | + |
| 15 | +Remember that the mentors are busy – they're all either full time students or work at Creative Commons. It's good to follow up if you don't get a response, but wait a couple of days first. |
| 16 | + |
| 17 | +### Contributing |
| 18 | + |
| 19 | +Before you contribute, read a little bit about Creative Commons and what we do. We're not simply an open source software project like many other Outreachy mentorship organization – we're a nonprofit organization and we do a lot of different things. Some of the projects we are mentoring are not software related at all (although some are quite technical). Feel free to ask us questions about what we do, our various programs, our licenses, and so on. There is a lot about us out there. You'll need to know a lot about us in order to help us effectively, especially if you're looking to contribute to projects like the FAQ or the Platform Toolkit. |
| 20 | + |
| 21 | +If you're contributing to a more technical project, please read our [Contributing Code](/contributing-code) page. Keep in mind that you can record any contribution to any Creative Commons project as an Outreachy contribution as long as it is accepted – it does not have to be to the same repository as the project you're applying to. |
| 22 | + |
| 23 | +### Project List |
| 24 | + |
| 25 | +Here's a quick reference of the projects, their mentors (plus their roles on the project), and the specific Slack channel for the project (if any). |
| 26 | + |
| 27 | +<table class="table table-sm table-striped"> |
| 28 | + <thead class="thead-light"> |
| 29 | + <tr> |
| 30 | + <th scope="col">Project</th> |
| 31 | + <th scope="col">Mentors</th> |
| 32 | + <th scope="col">Slack Channel</th> |
| 33 | + </tr> |
| 34 | + </thead> |
| 35 | + <tbody> |
| 36 | + <tr> |
| 37 | + <td>Extend the scope and/or usage of CC Vocabulary</td> |
| 38 | + <td><code>@dhruvkb</code> (technical), <code>@hugo</code> (technical)</td> |
| 39 | + <td><code>#cc-dev-cc-vocabulary</code></td> |
| 40 | + </tr> |
| 41 | + <tr> |
| 42 | + <td>Improving the Creative Commons License Chooser</td> |
| 43 | + <td><code>@Ari</code> (technical), <code>@kriti</code> (technical)</td> |
| 44 | + <td><code>#cc-dev-license-chooser</code></td> |
| 45 | + </tr> |
| 46 | + <tr> |
| 47 | + <td>Revamp CC's Platform Toolkit guide for platforms interested in offering CC licenses to users</td> |
| 48 | + <td><code>@eric</code> (content), <code>@kriti</code> (technical)</td> |
| 49 | + <td><code>#cc-outreachy-platform-toolkit</code></td> |
| 50 | + </tr> |
| 51 | + <tr> |
| 52 | + <td>Revamp the Creative Commons FAQ so that it's easier to use</td> |
| 53 | + <td><code>@eric</code> (content), <code>@mari</code> (content), <code>@kriti</code> (technical), <code>@hugo</code> (technical)</td> |
| 54 | + <td><code>#cc-outreachy-faq</code></td> |
| 55 | + </tr> |
| 56 | + <tr> |
| 57 | + <td>Supercharge our Elasticsearch indexer</td> |
| 58 | + <td><code>@aldenpage</code> (technical), <code>@Maria Belen Guaranda</code> (technical)</td> |
| 59 | + <td>-</td> |
| 60 | + </tr> |
| 61 | + <tr> |
| 62 | + <td>Revamp the workflow and design of our legal tools</td> |
| 63 | + <td><code>@kriti</code> (technical), <code>@shinchpearson</code> (legal)</td> |
| 64 | + <td>-</td> |
| 65 | + </tr> |
| 66 | + <tr> |
| 67 | + <td>Better visualization tools for the CC Network</td> |
| 68 | + <td><code>@hugo</code> (technical), <code>@claudio</code> (CC Network)</td> |
| 69 | + <td>-</td> |
| 70 | + </tr> |
| 71 | + <tr> |
| 72 | + <td>Create a QR code generator to attribute projects with CC licenses</td> |
| 73 | + <td><code>@hugo</code> (technical), <code>@aldenpage</code> (technical)</td> |
| 74 | + <td>-</td> |
| 75 | + </tr> |
| 76 | + </tbody> |
| 77 | +</table> |
| 78 | + |
| 79 | +### Intern Selection Criteria |
| 80 | + |
| 81 | +Interns will be selected based on our confidence that they will be able to get the project completed and will be a good long term member of the community. We will evaluate a combination of: |
| 82 | +* Project timeline and plan submitted as part of the application |
| 83 | +* General understanding of goals of the project and goals of Creative Commons |
| 84 | +* History of contributions and quality of past work |
| 85 | +* General frequency and quality of communication |
| 86 | +* Good community behavior and participation e.g. history of helping others |
0 commit comments