# GSOC 2026 : Contributor Applications Opens on March 16 ,2026 **URL:** \ **Category:** GSOC\ **Tags:** gsoc2026\ **Created:** [March 16, 2026, 1:20pm UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121 "2026-03-16T13:20:32Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Moses\_Mutesasira](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/moses_mutesasira/32/72_2.png) [@Moses\_Mutesasira](https://talk.openelis-global.org/u/Moses_Mutesasira)\ **Post date:** [March 16, 2026, 1:20pm UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121/1 "2026-03-16T13:20:32Z")
Hello Community , GSOC Contributor Applications will open from **Monday, March 16, 2026 at 18:00 UTC** and closes on **Tuesday, March 31, 2026 18:00 UTC**.. Note that GSOC Applications are submited to your organisation through the GSOC website at [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/) See Full [GSoC 2026 Tilmeline](https://developers.google.com/open-source/gsoc/timeline#2026_timeline) # Guideline. 1. Signup as a GSOC contributor with Google at [GSoC Contributor Registration](https://summerofcode.withgoogle.com/register/contributor) page. **Note**. Esure to read and uderstand the GSOC [contributor terms](https://summerofcode.withgoogle.com/terms/contributor) and [GSOC guidelines](https://google.github.io/gsocguides/student/writing-a-proposal) about writing a proposal 2. Go through the [OpenELIS ideas List](https://uwdigi.atlassian.net/wiki/spaces/oeg/pages/931594241/GSoC+2026) and select a project youre intrested in 3. Follow our [Student guidelines](https://uwdigi.atlassian.net/wiki/spaces/OG/pages/245694473/GSoC+Guidelines+for+Students) to write a proposal for the Project youre intrested in using our [proposal template](https://docs.google.com/document/d/1LaBPJluKTRhfRyV-nnHgow3oXgyLrrpI6_v835TuPHU/edit?usp=sharing) . **Note:** Make a copy of the template and esnure to Ensure to fill all mandatory fields 4. You should be able to submit the Proposal to OpenELIS Global Organization through the GSOC website [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/) for review by the Mentors 5. The final selected contributors will be Announced on April 30 ,20204 All the Best. Moses GSOC 2026 Administator ---
**Author:** ![Moses\_Mutesasira](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/moses_mutesasira/32/72_2.png) [@Moses\_Mutesasira](https://talk.openelis-global.org/u/Moses_Mutesasira)\ **Post date:** [March 16, 2026, 1:25pm UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121/2 "2026-03-16T13:25:19Z")
---
**Author:** ![Rakesh](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/rakesh/32/1213_2.png) [@Rakesh](https://talk.openelis-global.org/u/Rakesh)\ **Post date:** [March 19, 2026, 11:50am UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121/3 "2026-03-19T11:50:26Z")
Hello Moses, Thank you for sharing the GSoC 2026 timeline and guidelines. I am currently preparing my proposal for the “Improve Integration Tests Coverage” project in OpenELIS Global. To get familiar with the codebase, I have been contributing by adding unit and integration tests across multiple modules. I have opened a few pull requests and would really appreciate any feedback or suggestions when you have time: PRs: - [https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3023](https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3023) - [https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3027](https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3027) - [https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3037](https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3037) - [https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3077](https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3077) I would be grateful for any guidance on how I can improve my contributions further. Thank you! ---
**Author:** ![alikhere](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/alikhere/32/1185_2.png) [@alikhere](https://talk.openelis-global.org/u/alikhere)\ **Post date:** [March 24, 2026, 1:31am UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121/4 "2026-03-24T01:31:15Z")
Hi @Moses_Mutesasira thanks for all the updates and guidance. I’m planning to apply for the \*\*Modernizing the OpenELIS React Frontend with TypeScript and Performance Optimization. I’ve been going through the codebase and have a few PRs open mostly around TypeScript improvements, performance optimizations, and error handling. Could you please have a look, I would really appreciate any feedback on the contributions. > > > \## PR DESCRIPTION: > Was digging into the patient search code and found that exte…rnal ID search > was silently using nationalID as the bind parameter in both query methods > inside LuceneSearchResultsDAOImpl. So searching by external ID was actually > filtering by national ID the whole time. Changed both occurrences to bind > externalID instead. > > One file changed, no new logic added. > > \## Related Issue > Closes #3082 > > > \# Pull Requests Requirements > \- \[x\] The PR title includes a brief description of… the work done, including the > Issue number if applicable. > \- \[\] The PR includes a video showing the changes for the work done. > \- \[x\] The PR title follows conventional commit label standards. > \- \[\] The changes confirm to the OpenElis Global x3 > \[Styleguide and Design\](https://uwdigi.atlassian.net/wiki/spaces/OG/pages/621346838/OpenELIS+Global+Style+Guide) > documentation. > \- \[x\] The changes include tests or are validated by existing tests. > \- \[x\] I have read and agree to the Contributing > \[Guidelines\](https://openelis-global.org/community/get-involved/) of this > project. > > \## Summary > \- I noticed a bunch of \`any\` and loosely typed responses in the home dashboard, landing page, and calculated value form, so I tightened those up with concrete types and proper React event types. > \- The patient results viewer had several untyped helpers and index signatures, so I added explicit shapes for observations, concepts, meta info, and filter state instead of relying on \`any\` or bare records. > \- A few runtime paths in grouped timelines, trendlines, and overview logic were depending on loosely typed values, so I wired them through the new types and added safe casts or string conversions where needed. > \- The Jest test suite and a full \`npm run build\` (with ESLint disabled via \`DISABLE\_ESLINT\_PLUGIN=true\`) to make sure the stricter typing still compiles cleanly. > > \## Screenshots > \[Add relevant screenshots here if applicable\] > > \## Related Issue > \#3084 > > \## Other > nothing extra to note > > > \# Pull Requests Requirements > \- \[x\] The PR title includes a brief description of… the work done, including the > Issue number if applicable. > \- \[\] The PR includes a video showing the changes for the work done. > \- \[x\] The PR title follows conventional commit label standards. > \- \[x\] The changes confirm to the OpenElis Global x3 > \[Styleguide and Design\](https://uwdigi.atlassian.net/wiki/spaces/OG/pages/621346838/OpenELIS+Global+Style+Guide) > documentation. > \- \[x\] The changes include tests or are validated by existing tests. > \- \[x\] I have read and agree to the Contributing > \[Guidelines\](https://openelis-global.org/community/get-involved/) of this > project. > > \## Summary > \- I added an Error Boundary around the main app routes so a component crash can’t blank the whole UI. > \- The fallback uses \`react-intl\` strings and includes a Reload button to recover quickly. > \- I also added a Jest test that throws from a child component and verifies the fallback renders, plus the new \`en/fr\` translation keys. > > \## Screenshots > \[Add relevant screenshots here if applicable\] > > \## Related Issue > \#3088 > > \## Other > \- Ran \`cd frontend && npm run format\` > \- Ran \`cd frontend && CI=true npm test -- --watchAll=false --passWithNoTests\` > \- Ran \`cd frontend && DISABLE\_ESLINT\_PLUGIN=true npm run build\` (normal \`npm run build\` fails in this environment due to ESLint config resolution) > > > \# Pull Requests Requirements > \- \[x\] The PR title includes a brief description of… the work done, including the > Issue number if applicable. > \- \[\] The PR includes a video showing the changes for the work done. > \- \[x\] The PR title follows conventional commit label standards. > \- \[x\] The changes confirm to the OpenElis Global x3 > \[Styleguide and Design\](https://uwdigi.atlassian.net/wiki/spaces/OG/pages/621346838/OpenELIS+Global+Style+Guide) > documentation. > \- \[x\] The changes include tests or are validated by existing tests. > \- \[x\] I have read and agree to the Contributing > \[Guidelines\](https://openelis-global.org/community/get-involved/) of this > project. > > \## Summary > I focused this PR only on \`frontend/src/components/home/Dashboard.tsx\` and kept behavior unchanged while reducing repeated render-time work. > > The change adds memoization around existing computations and handlers: > \- \`useMemo\` for the filtered+sliced rows passed to \`DataTable\` > \- \`useMemo\` for the filtered count passed to \`Pagination.totalItems\` > \- \`useCallback\` for: > - \`handlePageChange\` > - \`handleMaximizeClick\` > - \`handleMinimizeClick\` > - \`loadPreviousResultsPage\` > - \`loadNextResultsPage\` ---
**Author:** ![Kartikey](https://avatars.discourse-cdn.com/v4/letter/k/b19c9b/32.png) [@Kartikey](https://talk.openelis-global.org/u/Kartikey)\ **Post date:** [March 24, 2026, 5:13pm UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121/5 "2026-03-24T17:13:06Z")
Hi Moses\_ Mutesasira I am a passionate Java Backend Developer with a strong interest in building scalable and efficient server-side applications. I have experience working with Java, object-oriented programming, and backend development concepts, along with a growing understanding of open-source collaboration. I am participating in GSoC 2026, where I am actively contributing to the OpenELIS Global project. Currently, I am working on the issue “Add more data points on the validation screen” (#2893), focusing on enhancing data visibility and improving the validation workflow for better usability and accuracy. Through this contribution, I aim to improve system efficiency, data clarity, and user experience while gaining deeper insights into real-world, large-scale open-source healthcare systems. I will be submitting my GSoC 2026 proposal very soon. @Moses Mutesasira ---
**Author:** ![Princegarg01](https://avatars.discourse-cdn.com/v4/letter/p/3d9bf3/32.png) [@Princegarg01](https://talk.openelis-global.org/u/Princegarg01)\ **Post date:** [March 27, 2026, 2:47pm UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121/6 "2026-03-27T14:47:54Z")
Hello Moses, I hope you are doing well. I am currently preparing my GSoC 2026 proposal for the project “Creating a Generic Robust Reporting Framework” in OpenELIS Global. The idea of enabling users to generate ad-hoc patient reports directly from the UI is something I find very impactful, and I’m excited to contribute to it using technologies like React, TypeScript, Java, Spring, and REST. To better understand the codebase and align my proposal with project needs, I have been actively contributing to OpenELIS. I’ve raised a couple of pull requests and would really appreciate your feedback whenever you have time: **Pull Requests:** - fix(#2890): Include retest requests in In Progress dashboard widget (merge conflict) [https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3022](https://github.com/DIGI-UW/OpenELIS-Global-2/pull/3022) - feat: Add configurable custom fields to Sample Entry form (#2878) (merge conflict) [https://github.com/DIGI-UW/OpenELIS-Global-2/pull/2949](https://github.com/DIGI-UW/OpenELIS-Global-2/pull/2949) I would be grateful for any suggestions on how I can improve my contributions and better align with the expectations for this project. Additionally, any guidance regarding the proposal direction or key areas to focus on for the reporting framework would be extremely helpful. Thank you for your time and support. Best regards, Prince Garg ---
**Author:** ![junaid](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/junaid/32/1166_2.png) [@junaid](https://talk.openelis-global.org/u/junaid)\ **Post date:** [March 28, 2026, 3:38pm UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121/7 "2026-03-28T15:38:12Z")
hello @Princegarg01 you can check out this pages for better idea and future plans [https://uwdigi.atlassian.net/wiki/spaces/oeg/pages/940769284/R+D+Future+Features](https://uwdigi.atlassian.net/wiki/spaces/oeg/pages/940769284/R+D+Future+Features) also iam trying to work on same thing (reporting framework) so please feel free to ask anything iam happy to share my knowledge on this. thank you ---
**Author:** ![vmm](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/vmm/32/1195_2.png) [@vmm](https://talk.openelis-global.org/u/vmm)\ **Post date:** [March 29, 2026, 1:51pm UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121/8 "2026-03-29T13:51:05Z")
Hello Moses, I am currently preparing my proposal for the “Creating a generic robust reporting framework” project. Could you share roughly what percentage of the work you expect to be frontend vs backend? Thanks in advance. ---
**Author:** ![Siddharth\_Singh\_Nath](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/siddharth_singh_nath/32/1224_2.png) [@Siddharth\_Singh\_Nath](https://talk.openelis-global.org/u/Siddharth_Singh_Nath)\ **Post date:** [April 16, 2026, 5:33pm UTC](https://talk.openelis-global.org/t/gsoc-2026-contributor-applications-opens-on-march-16-2026/2121/9 "2026-04-16T17:33:06Z")
Hello OpenELIS Community! My name is Siddharth Singh Nathawat, I am a 3rd year B.Tech student from India. I have strong Java and Spring Boot experience — I built an Airbnb Clone and a Smart Code Review Bot using Spring Boot and JWT Authentication. I am very interested in contributing to OpenELIS Global for GSoC 2026, specifically the Generic Robust Reporting Framework project. Can mentors guide me on how to get started and what to focus on for my proposal? Thank you!