DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
- Where to I apply? How do I apply?
- Details coming soon / GSOC -->. https://summerofcode.withgoogle.com/
- See also timeline below and GSOC general application. Specific terms we expect covered → Apache Fineract(R) GSoC Candidate Application TEMPLATE
- also here is our guide [
- I am interested in being a candidate, how do I get started?
- You may join the dev list serv and introduce yourself.
Important: Please join Matrix.https://matrix.to***/#/#apache-fineract-gsoc:matrix.org. remove the *** - Sorry if we don't respond.
- Applications
- You may join the dev list serv and introduce yourself.
- I am trying to help as a Mentor, where do I go?
- Please respond on the dev list. See the qualifications listed on the GSOC pages below first.
- Matrix for mentors as well.
- How many candidates will we accept?
- Unknown. It will depend on the ASF GSOC program.
- We are hoping to have at least four.
- Should I use the #fineract or #GSOC channel at Mifos for conversation?
- The #fineract channel on Mifos slack is available for general conversation and will have lots of content but...
- the #GSOC channel on Mifos slack is only for mifos programs
- To avoid confusion — We're now on Matrix. remove the *** from this: https://matrix.to***/#/#apache-fineract-gsoc:matrix.org.
- Should I get something ready?
- You are free to start thinking about ideas or to work on a proposal... but we may also decide to only allow certain types of proposals. TBD
- To add some context, there is TOO much functionality which is not maintained... and not enough of non-functional stability - thus we need more tests, more documentation, more security improvements, and perhaps some outside components...
- What are you looking for in a candidate?
- That will depend on the mentors... but generally, we want "self starters" who are already knowledgeable in certain domain areas.
- The goal we have internally is to start to build the GSOC program with the goal of "onboarding people" who will likely stay.
- Will my contributions be accepted into the dev branch and a release?
- We are not necessarily looking to add functionality via the GSOC program, so creating a branch to check into and to offer a POC, is a likely outcome.
- How do I....
- Sorry, we cannot help with individual responses. We will try to provide general guidance and there are my public resources... use those first. see the many places on the website and int he Jira ticket for onboarding, and the FAQ, etc.
...
Here are the key dates for GSoC 2026, the full timeline is available on the GSoC website:
Tasks | Dates | What to do as a contributor |
Org research | 19 Jan – 19 Feb 2026 | Browse orgs, read websites/docs, and identify 2–3 projects that interest you. |
Idea & discussion phase | 19 Feb – 15 Mar 2026 | Join project mailing lists/chats, ask questions, and start small contributions (docs, tests, bugs). |
Proposal drafting | 1–15 Mar 2026 | Research the project deeply, draft a design outline, and share it with mentors for feedback. |
Application Opens | 16–31 Mar 2026 Closes at: 18:00 UTC on 31st | Finalize your proposal, submit it on the GSoC site, and keep in touch with your mentor. |
Waiting period | 1–25 Apr 2026 | Keep contributing small issues, respond to mentor questions, and stay active in the community. |
Selected Project Announcement | 30 Apr @ 18:00 UTC | Accepted GSoC contributor projects announced |
After selection | 30 Apr – 4 May 2026 | Confirm acceptance, read organization rules, and set up your dev environment and tools. |
Community bonding | 1–24 May 2026 | Weekly: read docs, fix starter issues, familiarize with procedure for raising PRs, and finalize project plan with your mentor |
Coding begins | 25 May – 5 June 2026 | Start implementing first tasks, open PRs frequently, and document decisions. |
Weeks 3–6 | 6 June – 1 July 2026 | Implement core features, write tests, and participate in community calls/chats |
Midterm Evaluation window | 6–10 July 2026 | Summarize progress, note challenges, and submit your midterm evaluation and work. |
Weeks 7–12 (standard) | 11 July – 16 Aug 2026 | Polish code, improve docs, fix remaining issues, and prepare for final review. |
Final week (standard) | 17–24 Aug 2026 at 18:00 UTC | Submit final code, run tests, update docs, and complete your final evaluation. |
Extended projects (if any) | 24 Aug – 2 Nov 2026 | Continue coding as agreed, keep weekly updates, and submit final work and evaluation by 2 Nov. |