Congratulations to our 4 Accepted Contributors for GSoC 2026 and Next Steps

Congratulations to the 4 contributors selected to work with LibreHealth during Google Summer of Code 2026! We’re very excited about this excellent group of @gsoc2026contributors as part of our community and look forward to the work you’ll do together with your mentors and the greater LibreHealth community. If you weren’t selected, free to reach out but the answer really is that it’s a numbers game that’s coupled with project priorities.

The 4 accepted contributors and their projects are as follows:

Each of these projects has a dedicated thread and you must use this for all project communications. Under rare circumstances, you may use a private medium such as Skype (ex: you are ill, family emergency, etc) but we will, however, provide a Jitsi meet room for your projects. No private communications. This is something we are strict about.

Please read this entire post carefully. After reading this post, there are several steps you must take immediately. Failure to perform any of these tasks before the end of the community bonding period on 2026-05-24T23:59:00Z will cause you not to begin as a contributor, and you will not receive your initial payment from Google. The video below will summarize things for you.

  1. This week: Introduce yourself on LibreHealth Forums in the appropriate pinned topic at the top of the Community > Google Summer of Code category. Tell us a little bit about yourself, your interests, your selected project, and why you find LibreHealth interesting. We will use LibreHealth Forums for all official communications about the program, so check it every day. Complete this task in the next week, by 2026-05-07T23:59:00Z

  2. In two weeks’ time: Get your blog ready. You must post a blog entry every week during GSoC. Start now so you get in the habit of writing at least one post every week. You don’t have to create a new blog for GSoC; it’s OK to use an existing one. See the relevant post at the top of the Community > Google Summer of Code category of LibreHealth Forums for details and to post your URL. Complete this task by 2026-05-14T23:59:00Z

  3. Contact your mentor immediately. Make a plan for communication with your mentor and stick with it. Remember, we’re an open-source project, so all your LibreHealth communication should be in public forums such as our community chat or right here in the appropriate categories. Make sure your mentor has identified one or more backup mentors if she or he is not available. Prepare a detailed project plan (week by week) with milestones with your mentor and post it in the appropriate category on LibreHealth Forums, with the gsoc2026 tag. Complete all these tasks before the end of the community bonding period ends on 2026-05-24T23:59:00Z.

  4. Be prepared to submit a weekly status report. The status report is very short but very important since it helps us to ensure your project is on track and things are going well. If you miss filing 3 status reports, you’ll be removed from the program, so remember to add this to your weekly schedule! Consider the hard deadline to be 11:59 PM UTC every Friday.

Once again, congratulations! We are impressed by your accomplishments so far, and hope you are just as pleased to be part of our community of so many wonderful people!

Your GSoC administrators:

Robby O’Connor (@r0bby), Saptarshi Purkayastha (@sunbiz), and Judy Gichoya (@judywawira)

1 Like

I know I addressed this but it’s buried in the post if you skim it, if you were not selected that just means someone else had a better proposal. We can’t accept everybody.

Feel free to apply next year. We’ll be around so long as Google continues running it.

Thanks for steering the GSoC @r0bby; I do have a few quick follow-up questions:

(1) Was the NeoSmartML (libreahealth/5247/) realistically going to be funded in this cycle? Could there have been a successful proposal at all? It seemed much more nascent, less-defined, overly ambitious project compared to the actual selected projects? (2) Were there any red flags outright that made my proposal* not being considered at all or was it considered on its merits? (3) If yes, any big mistakes, anything truly bad that was noted (for future reference for 2027)? I am asking here as per the community guidelines e.g, “all communication happens publicly either here on the forums or on our chat” instead of privately reaching out and the main project specific post /5247/ is now locked.

* neosmart-ml proposal

1 Like

Congrats to all selected contributors. Looking forward to an amazing summer

2 Likes

Your proposal was actually really good but the issue was that you didn’t make any contact with us and at that point I set your proposal to ignored.

The things I looked for:

  • You asking questions and drafting your proposal and refining – I check the users on Discourse for your email and if I don’t find it, I consider you a risk for potentially failing. We need you to be a part of the community. Many of the projects chosen engaged us first back in February when organizations were announced.
  • Your proposal needed to be one of the ideas we had up – You passed this
  • Your proposal was substantial and had meat to it – This was also good

It’s really tragic but from the perspective of the program, contacting the organizations is not only encouraged, but it’s required. We’re looking to integrate you into the community…had you communicated to us, you would’ve been our 5th project potentially, it would’ve probably been ranked higher actually… Community engagement factors into our decisions to accept a proposal.

@sunbiz mentioned your proposal being very strong but you only contacting us now is why you weren’t selected unfortunately.

I have reasons for all communication being public, it’s how open source communities operate.

Thank you , @muarachmann and @r0bby !!! Looking forward to learning from all of you.

1 Like

@rp00444 Your proposal was very good, and I hope you continue to contribute to the project. However, as Google has mentioned multiple times before, the objective of GSoC is to produce long-term open-source contributors, and not stop at a summer only.

So, I hope each one of you, selected or started to work in LibreHealth, will become long-term contributors to open-source, whether with us or another open-source organization.

5 Likes

Congratulations on being accepted and I look forward to working with the people working on radiology. I’m very, very excited about GSOC this year coming back after a long hiatus.

2 Likes