You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

High Level Concept

Why are we doing this?

The "Problem statement"

The Google Summer of Code (GSOC program) is a long standing effort, sponsored by Google, to onboard new developers to a variety of open source projects.   Historically, the ASF (Apache Software Foundation) has had a very active set of projects across dozens of different PMCs.  

At Fineract, we've seen some outside efforts to involve and onboard new devs to this community.  We can build on this and do a better job of onboarding them here.  (The potential challenge is that the existing efforts onboard them primarily to an outside collaboration or vendor.)  

The GSOC program is aimed specifically at students, enrolled in a program.  


How do we judge success?

The goals are that new devs have a positive experience and learn something about how to contribute to an open source project.  They become capable of contributing to the project in some way.  They, hopefully, continue to engage in the project.  

We do not assume that the ability to have their PR accepted is a requirement for this program.  In some scenarios, it may be that the work is done as a Proof of Concept (POC).  


What is GSOC? 

https://developers.google.com/open-source/gsoc/faq

"Since 2005, the Google Summer of Code program has brought together over 23,000 new contributors/students with over 1,000 open source organizations under the guidance of 21,000+ mentors."  

It is not an internship, not a recruitment into Google, not for existing contributors.  Please read the FAQ 

https://developers.google.com/open-source/gsoc/faq


Process

GSOC Schedule  (approximate)

December of previous year - advertise for Mentors / start the ball rolling - choose a coordinator 

https://developers.google.com/open-source/gsoc/timeline (GSOC timelines) 

January second week - Generate and finalize a list of ideas for development 

January third week - align the ideas and inform the GSOC coordinators at the ASF 

Feb first week - The ASF finalizes application to GSOC 

March second week - Applications open for contributors 

April  - Applicants evaluated and selected by the project / approved by GSOC 

May third or fourth week  Start of projects 

June/July/Aug - mentoring 

Late August-  projects completed and shared  

see ==>  https://groups.google.com/g/google-summer-of-code-announce?pli=1

Linking to the broader ASF GSOC efforts 

See https://community.apache.org/gsoc/guide-to-being-a-mentor.html 

 NOTE:   Mentors working with the Fineract GSOC coordinator create JIRA tickets in the Apache Fineract project with tags  GSOC and GSOC2026  . 

These will then show up in the ASF Jira and can be seen by the GSOC Coordinator at Community Development (CommDev) for submission to the GSOC application due in late January.  


Onboarding Mentors 

https://community.apache.org/gsoc/guide-to-being-a-mentor.html

e.g. mentors must subscribe to the email list  <mentors-subscribe@community.apache.org> 

see full list of information on that page 


Tickets for 2026 (work in progress) 

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh






  • No labels