Alaskan-Season-of-Code

Google Summer of Code (GSoC) is a wonderful program that funds several open-source organizations and open-source research entities, such as Alaska. However, due to the limited funding (Google cannot always fund all the contributors we like to hire) and the relatively fixed northern hemisphere summer schedule of GSoC, we sometimes miss some of the great candidates.

This is especially unfortunate when we lose one of the top candidates for a project idea when,

1. Another slightly better candidate gets accepted.
2. No one gets accepted into that project idea despite the candidate being the top choice, as Google has to decide how many contributors are accepted for each organization. So, that means we are ranking the candidates on a global organizational-wide scale rather than individually for each project idea.
3. The candidate decides to give up on GSoC as they realize they are not eligible (already participated in GSoC more than twice or have a conflict of interest due to being a student at the University of Alaska System) or lack of time during the GSoC timeframe. This can be a disappointing outcome for both the applicants and mentors, especially when the applicants have already put effort into research and implementation.

We propose an "Alaskan Season of Code" for the top candidates who are not accepted into GSoC for whatever reason, but specifically for the reasons listed above. We also aim to mentor contributors throughout the year (not limiting to May - August, the summer in Alaska) to support diverse populations whenever we can.

The goal of this initiative is supporting and recognizing the applicant's effort and preference to work outside the support frame of GSoC. At this point, we do not have funding opportunities available through this initiative. But we are working towards that. We will also likely be hit with roadblocks with funding contributors outside the USA under this initiative, based on the funder requirements. But a funding opportunity for US-based residents can be a reality in the upcoming years.

In the meantime, the Alaskan Season of Code aims to provide the below support systems in place.

1. For those who contributors applied through the GSoC system and couldn't get accepted, they could seek out to the mentor to see whether there is a potential to volunteer to work on the topic.
2. The contributors get direct one-to-one mentoring similar to GSoC.
3. The contributors have a more flexible timeline, especially when they are not funded (which is true for this initiative at this point). If the students are funded, we will have to follow a timeline similar to that of GSoC, to satisfy the funder's requirements.
4. The contributors can finetune the goals to fit their timeline and available time frame.
5. Continued research and implementation, similar to GSoC.
6. Support letters and completion documents to successful participants.
7. Potential to be a co-author (and even first authors!) on research papers (similar to how we do research with GSoC).

This model is not new. We are only mimicking previous success stories such as Xorg EVoC and Season of KDE.

If you are someone who did not get accepted into GSoC or did not apply to GSoC because of other reasons, you can contact us for potential collaborations under the Alaskan Season of Code.

For potential project ideas, look for the project ideas listed under our GSoC project ideas page and contact the mentors.