|
| 1 | +title: Skipping Google Summer of Code (GSoC) 2025 |
| 2 | +--- |
| 3 | +categories: |
| 4 | +gsoc |
| 5 | +open-source |
| 6 | +community |
| 7 | +--- |
| 8 | +author: TimidRobot |
| 9 | +--- |
| 10 | +pub_date: 2025-01-15 |
| 11 | +--- |
| 12 | +body: |
| 13 | + |
| 14 | +The Creative Commons (CC) technology team regrets to announce **we will not be |
| 15 | +participating in Google Summer of Code (GSoC) 2025**. While the program remains |
| 16 | +excellent, we do not have the resources to participate this year and meet our |
| 17 | +core responsibilities. |
| 18 | + |
| 19 | +We are grateful to Google for the program and have found incredible value in |
| 20 | +participating in past years. We look forward to participating in future years. |
| 21 | +We are thankful for the work and time of contributors. This is not an exciting |
| 22 | +announcement, but we will be better equipped to engage with work programs in |
| 23 | +the future. |
| 24 | + |
| 25 | + |
| 26 | +## Preparing to re-engage |
| 27 | + |
| 28 | +In addition to revamping our CC Open Source website during the first quarter of |
| 29 | +this year, we will also be refreshing our structured community involvement, and |
| 30 | +improving our project lead resources. |
| 31 | + |
| 32 | +Our CC Open Source website is in the process of being updated to be less |
| 33 | +technologically complex and to leverage the current Vocabulary design system |
| 34 | +([creativecommons/vocabulary][vocabulary]). |
| 35 | + |
| 36 | +Our structured community involvement has languished since the technology team |
| 37 | +was downsized due to the COVID pandemic (202-12-07 [Upcoming Changes to the CC |
| 38 | +Open Source Community — Creative Commons Open Source][changes]). We will be |
| 39 | +simplifying community involvement so that we can be more responsive with |
| 40 | +increased visibility. |
| 41 | + |
| 42 | +The most resource intensive period of a work program is the application phase. |
| 43 | +During this time there is a deluge of activity that has often exceeded our |
| 44 | +capacity. Developing our project lead resources will allow us to better set |
| 45 | +expectations, ease communications, and better point applicants on productive |
| 46 | +trajectories. |
| 47 | + |
| 48 | +[vocabulary]: http://github.com/creativecommons/vocabulary |
| 49 | +[changes]: https://opensource.creativecommons.org/blog/entries/2020-12-07-upcoming-changes-to-community/ |
| 50 | + |
| 51 | + |
| 52 | +## Past participation |
| 53 | + |
| 54 | +For information on the excellent work completed during past participations, |
| 55 | +please see: [Open Source Work Programs: History — Creative Commons Open |
| 56 | +Source][history]. |
| 57 | + |
| 58 | +[history]: https://opensource.creativecommons.org/programs/history/ |
0 commit comments