Hi everyone, I’d also like to express my interest in contributing as a mentor to GSoC next year.
Participating this past summer has really opened my eyes to the world of open source, and I respect the dedication and effort that made GSoC 2026 at Fineract a reality. I’d love to contribute where I can to pay it forward and help others get started building in this community as well. Sincerely, Edward Edward E. Kang [email protected] 972-768-6940 On Sat, Oct 10, 2026 at 7:58 AM Kevin Mugarura <[email protected]> wrote: > Thank you so much Aman > > > On Sat, Oct 10, 2026 at 5:46 PM Aman Mittal <[email protected]> > wrote: > >> Hi All, >> >> Created a page at ASF Wiki >> >> >> https://cwiki.apache.org/confluence/spaces/FINERACT/pages/451979814/PROPOSED+Google+Summer+of+Code+GSoC+2027+Guidelines+%E2%80%94+Apache+Fineract >> >> >> >> On Fri, Oct 9, 2026 at 1:49 PM Sujan <[email protected]> wrote: >> >>> Hi James and Aman, >>> >>> Following up on the discussion, I wanted to express my interest in >>> continuing to contribute to the Fineract community and taking on more >>> responsibility over time. >>> >>> I’d be happy to help mentor smaller or side projects in future >>> initiatives, particularly where my experience with the Loan Origination >>> System, backend APIs, security, workflows, and Fineract integration could >>> be useful in guiding new contributors. >>> >>> At the same time, I recognise that there is still a lot for me to learn >>> about the broader Apache development process, including release management, >>> deployment, and the maintenance of the core platform. I’d like to build >>> that understanding while continuing to contribute in areas where I can add >>> value. >>> >>> I’m also interested in working towards becoming an Apache Fineract >>> committer. I’m not entirely familiar with the process or the expectations >>> involved, so I’d really appreciate your guidance on how contributors can >>> work towards that responsibility and what I should focus on to get there. >>> >>> Best regards, >>> Sujan >>> >>> On Fri, 9 Oct, 2026, 13:04 James Dailey, <[email protected]> wrote: >>> >>>> Thanks Aman for kicking this off. It’s good to have ideas discussed in >>>> public and to have a clear process. >>>> >>>> We should update the wiki page w guidance and refer to that. >>>> >>>> To clarify, ‘GSOC Mentors’ must be Committers. >>>> >>>> Last year we asked for submissions for six idea areas and received a >>>> large number of submissions. We scrambled to review and to cover at least >>>> five projects w Committers. I served as the ‘Mentor of record’ for more >>>> than one. This is a known pattern but is not preferred. >>>> >>>> So, my sense is that recruiting and confirming the Committers is >>>> equally or even more important. >>>> >>>> Thanks, >>>> >>>> James >>>> PMC member and chair >>>> >>>> >>>> Sent from Gmail Mobile >>>> >>>> On Fri, Oct 9, 2026 at 7:45 AM Aman Mittal <[email protected]> >>>> wrote: >>>> >>>>> >>>>> Hi Abhishek, >>>>> As this is the early phase, there may be chance that you will get >>>>> response late. As this is a volunteering work. >>>>> For second question, yes if even a small change is required in Apache >>>>> Fineract committer-mentor is necessary. All code that is contributed to >>>>> Apache Fineract must be release ready. >>>>> >>>>> On 2026/10/09 05:42:14 Abhishek Chaudhary wrote: >>>>> > Hi Aman, thanks for laying this out early. >>>>> > I had a few questions: >>>>> > >>>>> > 1. For core Apache Fineract ideas, are there any areas where >>>>> committers are >>>>> > available to mentor? This would help alot choose ideas that can get >>>>> proper >>>>> > guidance and review. >>>>> > >>>>> > 2. What's the preferred flow for an idea: a short design note on the >>>>> dev >>>>> > list to find a mentor or maybe discussing in matrix first? followed >>>>> by a >>>>> > Jira issue with the "gsoc2027" label? >>>>> > >>>>> > 3. If a non-core project (e.g., the back-office UI or a plugin) >>>>> turns out >>>>> > to need a small change in Apache Fineract, does the committer-mentor >>>>> > requirement then apply to that project as well? >>>>> > >>>>> > Thanks! >>>>> > >>>>> > On Fri, 9 Oct, 2026, 10:26 am Shivaansh Pandey, < >>>>> [email protected]> >>>>> > wrote: >>>>> > >>>>> > > Hi all, >>>>> > > >>>>> > > Thanks for writing down the guidelines; it's very helpful to have >>>>> the >>>>> > > process clear early. >>>>> > > >>>>> > > I posted an idea on this list earlier, under the subject "[DISCUSS] >>>>> > > GSoC 2027 idea: customization and extension framework for the >>>>> > > Backoffice UI". It only touches apache/fineract-backoffice-ui, so >>>>> > > under this proposal it would fall in the non-mainline category and >>>>> > > would not need changes to apache/fineract. >>>>> > > >>>>> > > Two questions: >>>>> > > >>>>> > > 1. Is anyone willing to mentor it? As I read the proposal, a >>>>> community >>>>> > > member could mentor it since it doesn't touch the core repo. I'm >>>>> happy >>>>> > > to rescope it to something smaller if the mentoring load is the >>>>> > > concern. >>>>> > > >>>>> > > 2. When the ideas list opens, should I draft the GSOC Jira ticket >>>>> text >>>>> > > (background, goals, expected outcome, size) and post it here for >>>>> > > review before anyone files it? >>>>> > > >>>>> > > If this isn't the right fit, I'm also glad to look at other >>>>> Backoffice UI >>>>> > > work. >>>>> > > >>>>> > > Thanks, >>>>> > > Shivaansh Pandey >>>>> > > GitHub: shivaansh0610-LUFFY >>>>> > > >>>>> > > On Fri, Oct 9, 2026 at 8:57 AM Aman Mittal <[email protected]> >>>>> wrote: >>>>> > > > >>>>> > > > Hi All, >>>>> > > > >>>>> > > > I think it should be the right time to establish guidelines >>>>> regarding >>>>> > > how the GSoC 2027, please note that this is proposal. And nothing >>>>> is final >>>>> > > (mentors, project ideas, candidates). >>>>> > > > >>>>> > > > First of all the most important factor that will affect how many >>>>> ideas >>>>> > > we will consider is the mentors who will able to guide the mentees. >>>>> > > > >>>>> > > > Requirements of the mentor at fineract: >>>>> > > > Someone who has a good standing preferred if it is PMC member or >>>>> a >>>>> > > committer. >>>>> > > > If they do not have committer access, any existing PMC member >>>>> can vouch >>>>> > > for him/her then one can mentor for Apache Fineract GSoC. >>>>> > > > Note: this process is similar to how ASF admins will give >>>>> mentors access >>>>> > > to the GSoC dashboard. Only difference is that even for existing >>>>> PMC member >>>>> > > they need acknowledgement from other PMC member in same PMC. >>>>> > > > >>>>> > > > Project Ideas: >>>>> > > > They are being tracked at ASF level on >>>>> > > > >>>>> > > > >>>>> > > >>>>> https://cwiki.apache.org/confluence/spaces/COMDEV/pages/440304577/GSoC+2027+Ideas+list >>>>> > > > >>>>> > > > Regarding the ideas for Apache Fineract I invite community to >>>>> submit >>>>> > > project idea. >>>>> > > > Important: If project proposal requires changing in >>>>> "apache/fineract" >>>>> > > codebase the core product of the Apache Fineract PMC. We will only >>>>> consider >>>>> > > for evaluation if any pmc member or committer is willing to mentor >>>>> on this >>>>> > > and take care of merges. >>>>> > > > >>>>> > > > However if this does not require any changes (non mainline repos >>>>> such as >>>>> > > fineract-backoffice-ui , loan origination, consumer facing and bi >>>>> plugin or >>>>> > > new repo will be created) then we need someone who can mentor for >>>>> that >>>>> > > (this may be general community member or non committee mentor). >>>>> > > > >>>>> > > > A message to gsoc aspirants: Please use public channels (matrix >>>>> or dev >>>>> > > list) as much as possible for queries and proposals and avoid >>>>> private >>>>> > > messages to potential mentors. >>>>> > > > >>>>> > > > >>>>> > > > Note: this is only proposal, can be changed based on apache >>>>> community >>>>> > > development pmc or gsoc guidelines and community suggestions. >>>>> > > > >>>>> > > > >>>>> > > > Regards, >>>>> > > > Aman >>>>> > > >>>>> > >>>>> >>>> > > -- > Kevin Mugarura >
