|
1 | | -_model: page |
| 1 | +_model: redirect |
2 | 2 | --- |
3 | | -_template: page-with-toc.html |
| 3 | +target: /internships/ |
4 | 4 | --- |
5 | | -title: Google Summer of Code 2019 |
6 | | ---- |
7 | | -body: |
8 | | - |
9 | | -Creative Commons has been selected as a mentoring organization for [Google Summer of Code (GSoC) 2019](https://summerofcode.withgoogle.com/)! Increasing digital collaboration is one of CC’s primary goals as an organization, so we are very excited by the idea of helping students become acquainted with open communities. Working with us is a good opportunity to work on large and impactful technical challenges and acquire new skills, but you'll also learn what it’s like to work for a nonprofit and help advance our mission to legally share knowledge and creativity to build a more equitable, accessible, and innovative world. |
10 | | - |
11 | | -For more information about what Creative Commons as a whole does, please check out the ["What we do" page on our organization website](https://creativecommons.org/about/). |
12 | | - |
13 | | -## Accepted Proposals |
14 | | - |
15 | | -See our [organization page on the GSoC website](https://summerofcode.withgoogle.com/organizations/6514859793973248/) to see information about the proposals that we've accepted and [learn more about the students behind the projects on our blog](https://creativecommons.org/2019/05/30/meet-ccs-2019-google-summer-of-code-students/). |
16 | | - |
17 | | -## Applying |
18 | | - |
19 | | -**Applications are now closed for Google Summer of Code 2019.** Application instructions are preserved on the [Application Instructions](/gsoc-2019/application-instructions/) page for reference. |
20 | | - |
21 | | -## Mentors |
22 | | - |
23 | | -Here are short bios of each of our 2019 mentors. Please use first names or Slack/IRC nicknames to address mentors; we prefer informality. |
24 | | - |
25 | | -* [Alden Page](https://creativecommons.org/author/aldencreativecommons-org/) (`aldenpage` on Slack) |
26 | | -* [Breno Ferreira](https://creativecommons.org/author/brenoferreira/) (`brenoferreira` on Slack) |
27 | | -* [Hugo Solar](https://creativecommons.org/author/hugocreativecommons-org/) (`hugo` on Slack) |
28 | | -* [Kriti Godey](https://creativecommons.org/author/kriticreativecommons-org/) (`kriti` on Slack) |
29 | | -* [Sophine Clachar](https://creativecommons.org/author/sclachar/) (`Sophine` on Slack) |
30 | | -* [Timid Robot Zehta](https://creativecommons.org/author/timidcreativecommons-org/) (`Timid Robot` on Slack) |
31 | | - |
32 | | -## Proposal Review Criteria |
33 | | - |
34 | | -We do not have formal guidelines for reviewing proposals, but here are a few things we consider: |
35 | | -* **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. |
36 | | -* **Community involvement**: One of our major goals for GSoC 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. |
37 | | -* **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. Code samples that are not related to CC projects work too, but contributing to CC projects has the added benefits of community involvement. |
38 | | -* **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. |
39 | | - |
40 | | -However, this is all relative. For example. if you have a great proposal, but haven't contributed code to CC yet, you still have a good shot. |
41 | | - |
42 | | -## Number of Accepted Students |
43 | | - |
44 | | -We can only accept a fixed number of students, which is determined by the number of slots allocated to |
45 | | - us by the Google Summer of Code administrators. Even though there are `n` proposals |
46 | | -on the project ideas page, CC may only be allocated enough project slots to support fewer than `n` projects. |
47 | | -The number of project slots allocated to each GSoC organization varies by year. |
48 | | - |
49 | | -You can find more information about the slot allocation process in [the GSoC mentor guide][gsoc-slot-allocation]. |
50 | | - |
51 | | -## History |
52 | | - |
53 | | -CC participated in Google Summer of Code seven previous times. See below for more information about our projects and participation for each year. |
54 | | -* [Google Summer of Code 2006](https://developers.google.com/open-source/gsoc/2006/#cc) |
55 | | -* [Google Summer of Code 2007](https://developers.google.com/open-source/gsoc/2007/#cc) |
56 | | -* [Google Summer of Code 2008](https://developers.google.com/open-source/gsoc/2008/#cc) |
57 | | -* [Google Summer of Code 2009](https://www.google-melange.com/archive/gsoc/2009/orgs/cc) |
58 | | -* [Google Summer of Code 2010](https://www.google-melange.com/archive/gsoc/2010/orgs/creativecommons) |
59 | | -* [Google Summer of Code 2012](https://www.google-melange.com/archive/gsoc/2012/orgs/cc) |
60 | | -* [Google Summer of Code 2013](https://www.google-melange.com/archive/gsoc/2013/orgs/cc) |
61 | | - |
62 | | -[gsoc-slot-allocation]: https://google.github.io/gsocguides/mentor/selecting-students-and-mentors#the-formal-process |
| 5 | +_discoverable: no |
0 commit comments