# GSoC 2026: Join the Processing Foundation as a Summer of Code Contributor!

**URL:** <https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450>\
**Category:** Summer of Code\
**Created:** [October 27, 2025, 10:29pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450 "2025-10-27T22:29:16Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![clairep94](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@clairep94](https://discourse.processing.org/u/clairep94)\
**Post date:** [February 3, 2026, 12:17pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/10 "2026-02-03T12:17:39Z")

</div>

Hi Samarth,  
I’m the mentor for one of the proposed projects (E2E tests for the p5.js web editor)

While contributions to the Processing repos is not necessary for your application, I would recommend getting a feel for the repos for the potential projects so that you can assess which one feels the most interesting/fun/familiar to work on! For me, that usually means creating a fork and playing with things locally to get a feel for the codebase, and maybe seeing if I can resolve any of the “good first issue” locally.

I think in terms of approachability for a JS/TS dev, the documentation sites would have the more modern, youtube-able stacks. The p5.js web editor repo is a bit more antequated.

---

_[View the full topic](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450)._