Thanks James for steering Noel in the right direction. Noel, you can
continue dialoging in the Mifos slack space. I'll make sure Aleks can give
feedback on your questions.

Dropping [email protected] to BCC. I will shift this conversation
over to the mifos-developer list. Noel, you can subscribe to that list at
https://sourceforge.net/projects/mifos/lists/mifos-developer

Ed

On Wed, Mar 11, 2026 at 9:23 AM James Dailey <[email protected]> wrote:

> Noel - I think you want the Mifos-developer listserv ,  this is a separate
> project under the Apache Software Foundation.
>
> See below
>
> ——-/ reposting previous email /—-
>
>
> A warm welcome to the GSOC candidates here and thank you for your
> proposals, ideas, and energy.
>
> To avoid some confusion - in the past, we have had Mifos GSOC projects
> discussed here and on the Mifos Slack.  As Victor highlighted below,
>
> While Mifos's members are key contributors to Fineract(R), Mifos X is an
> independent, end-to-end open-source solution that adds the UI, mobile apps,
> and reporting tools on top of the Fineract backend.
>
>
> New this year, we are also having an Apache Software Foundation (the ASF)
> Fineract GSOC program.
>
> *To keep this straight, if you are applying for a Mifos GSOC project (or
> any other Mifos coding efforts), your primary source of information is the
> Mifos #GSOC channel on slack, email list, confluence, and mifos jira[1].  *
>
> If your specific code project at Mifos overlaps with Fineract code (i.e.
> requires changes to Fineract = MifosX backend), then tickets are also
> required in the Fineract Jira. [2]  This is our longstanding practice.
>
> If you are applying for a Fineract GSOCproject, your primary source of
> information will be the fineract wiki [3], this email (listserv), and
> Matrix account.[4]  I invite all GSOC candidates to join Matrix and the
> GSOC channel there.
>
> As a community, we welcome you. As an open source project, the demands on
> our time are many.  If you DM to someone, you may not get a response. There
> are many of you and few of us.  Public discussion, if well forumulated, has
> a higher chance of getting a response but also not guaranteed. Apologies in
> advance.
>
> By well formulated, I mean you have spent the hours and hours going
> through the many resources available to you first: website, jira,
> documentation, tests, email archive, etc etc... before asking questions.
>
> I do not want to discourage anyone, but take small steps first. If you do
> not intend to work on fineract after GSOC, then speaking for myself, I
> invite you to consider carefully. The investment in time can be intense.
> Only a few of you will be selected for the Fineract GSOC program and even
> then, the allocated spots are not guaranteed.
>
> Conversely, documenting your onboarding experience in detail—pointing out
> the good and the bad to help the next person—is itself a contribution to an
> open source project.
>
> I will place some FAQs in the Matrix GSOCchannel.  We will introduce the
> mentors there and on the list.  Victor's points below are valid.  There are
> some issues which we will address in discussion.
>
> We will come back to this email (listserv) with summaries or important
> discussions. Good luck with the applications. The GSOCprogram opens for
> applications in mid-March.  More information later. See you in the Matrix.
> (ha!)
>
> James
> Fineract PMC
>
>
> [0] a link such as https://fineract.apache.org
>
> [1]  Mifos
> https://mifosforge.jira.com/wiki/spaces/MDZ/pages/90243316/Getting+started
>
> https://mifos.slack.com
> https://mifosforge.jira.com/wiki
>
> [2] Fineract
> https://issues.apache.org/jira/projects/FINERACT/issues
> <https://issues.apache.org/jira/projects/FINERACT/issues>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554327.
> (FAQ)
>
> [3] GSOC at Fineract
> https://cwiki.apache.org/confluence/display/FINERACT/GSOC
> +Program+at+Fineract
>
> https://fineract.apache.org/docs/current/ (documentation)
>
> [4] Matrix
> https://lists.apache.org/thread/y972vl7xy7695w9zf7gj17fxvsztppjz
>
> Also, ASF vendor neutrality
> https://cwiki.apache.org/confluence/display/INCUBATOR/Vendor+Neutrality
>
>
>
>
> Sent from Gmail Mobile
>
>
> On Wed, Mar 11, 2026 at 8:33 AM Noel Mugisha <[email protected]>
> wrote:
>
>> Dear David Higgins and the Fineract Mentors,
>>
>> My name is Noel, and I am a backend-heavy engineer writing to formally
>> express my interest in the "Event Driven Architecture for Standalone
>> Modules" project for Google Summer of Code 2026.
>>
>> I recently introduced myself on Slack, but I wanted to provide a more
>> structured overview of why I am excited about this specific project.
>> My background is primarily in Java and Spring Boot, and I have
>> hands-on experience working with Apache Kafka and Avro schemas for
>> message serialization in microservices environments.
>>
>> Why I am a good fit for this project:
>>
>> EDA Experience: I understand the challenges of decoupling monolithic
>> systems and have implemented the Outbox Pattern in previous
>> personal/professional projects.
>>
>> Tech Stack: I am very comfortable with the Fineract core stack
>> (Spring, JPA, Gradle) and have already successfully built the project
>> locally.
>>
>> Commitment: I am eager to contribute to the mission of financial
>> inclusion through open-source software and plan to be highly active in
>> the community.
>>
>> I am currently analyzing the infrastructure/event package in the
>> Fineract repository to understand the current event flow. I would
>> appreciate any guidance on specific areas where the community feels
>> the transition to a pluggable event-driven system is most urgent.
>>
>> I have attached my GitHub profile below for your reference. Thank you
>> for your time and for the opportunity to contribute to Apache
>> Fineract.
>>
>> Best regards,
>>
>> GitHub: [https://github.com/noel-mugisha]
>>
>

-- 
*Ed Cable*
President/CEO, Mifos Initiative
[email protected] | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>

Reply via email to