# 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:** 20\
**Page:** 6

<div class="post-metadata">

**Author:** ![harshil](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@harshil](https://discourse.processing.org/u/harshil)\
**Post date:** [March 13, 2026, 7:42am UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/103 "2026-03-13T07:42:45Z")

</div>

It will be uploaded on 15th march.

---

<div class="post-metadata">

**Author:** ![kit](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/kit/32/20478_2.png) [@kit](https://discourse.processing.org/u/kit)\
**Post date:** [March 14, 2026, 7:13pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/104 "2026-03-14T19:13:26Z")

</div>

Hello everyone and welcome to the newcomers 🌻 thanks for you patience!

I’ve updated the top post in the thread to contain:

1. The [proposal template](https://github.com/processing/Processing-Foundation-GSoC/blob/main/ProposalTemplate.md)
2. The [individual feedback signup sheet](https://forms.gle/gXsNKweFzAENS3d37)

_(You can submit your questions and drafts in any format, template is only required for final submission!)_

Please let me know if there are any technical problems or anything I can help clarify!

Thanks to @NishthaJain @skyash @Damaris @harshil for helping with this Q&A, it’s really appreciated. As far as I can tell, no unanswered questions remain but @ me if I missed something.

Wish you all a nice rest of your weekend,  
Best,  
Kit

---

<div class="post-metadata">

**Author:** ![harshil](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@harshil](https://discourse.processing.org/u/harshil)\
**Post date:** [March 14, 2026, 7:41pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/105 "2026-03-14T19:41:02Z")

</div>

It was a pleasure @kit . Now will be preapring my proposal.

---

<div class="post-metadata">

**Author:** ![aash.u7707](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/aash.u7707/32/22284_2.png) [@aash.u7707](https://discourse.processing.org/u/aash.u7707)\
**Post date:** [March 14, 2026, 7:47pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/106 "2026-03-14T19:47:10Z")

</div>

Thanks for the update, @kit I will look up to the proposal template really appreciate all the guidance from you and the others here.

---

<div class="post-metadata">

**Author:** ![khuntvidisha13](https://avatars.discourse-cdn.com/v4/letter/k/c89c15/32.png) [@khuntvidisha13](https://discourse.processing.org/u/khuntvidisha13)\
**Post date:** [March 15, 2026, 4:49am UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/107 "2026-03-15T04:49:21Z")

</div>

Hi @claudine! After researching the project and exploring the visual-testing branch, I found that p5.js already has an HTML visual test report system but Processing4 does not have this yet.

I would like to propose two things for my GSoC project:

1. Add missing visual regression tests for Processing4 functions like shapes, blend modes, typography, transforms

2. Implement an HTML test report system for Processing4 — showing expected image, actual image, and diff image when a test fails — so developers can easily understand what changed

Is this a good direction for my GSoC proposal?

---

<div class="post-metadata">

**Author:** ![KhushiMishra](https://avatars.discourse-cdn.com/v4/letter/k/8c91f0/32.png) [@KhushiMishra](https://discourse.processing.org/u/KhushiMishra)\
**Post date:** [March 15, 2026, 3:35pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/108 "2026-03-15T15:35:31Z")

</div>

Hi everyone!

Thanks @kit for the template, I now have the clearer idea of how to approach writing it .  
I have been exploring the Processing repositories and discussions while trying to understand the codebase. Recently I started looking into the eyedropper tool, since while using the website I noticed how useful this feature would be, especially when working with colours from the canvas.  
Excited to keep learning from the discussions here and contribute where I can.

---

<div class="post-metadata">

**Author:** ![claudine](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/claudine/32/19798_2.png) [@claudine](https://discourse.processing.org/u/claudine)\
**Post date:** [March 15, 2026, 4:11pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/109 "2026-03-15T16:11:19Z")

</div>

Hello @khuntvidisha13 , proposing tests that are not there yet is a solid approach!

You’re right 🙂 there is a reporting system for p5.js, that we are planning to integrate into Processing4. It is the intention of the contributor who developed the reporting system to add that to Processing4, so it’s already sort of on the roadmap.

---

<div class="post-metadata">

**Author:** ![khuntvidisha13](https://avatars.discourse-cdn.com/v4/letter/k/c89c15/32.png) [@khuntvidisha13](https://discourse.processing.org/u/khuntvidisha13)\
**Post date:** [March 15, 2026, 4:55pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/110 "2026-03-15T16:55:06Z")

</div>

Thank you @claudine! That is really helpful. I will focus on adding missing visual regression tests for Processing4. I will submit my proposal draft for feedback soon!

---

<div class="post-metadata">

**Author:** ![georgeibrahim](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/georgeibrahim/32/21573_2.png) [@georgeibrahim](https://discourse.processing.org/u/georgeibrahim)\
**Post date:** [March 15, 2026, 9:25pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/111 "2026-03-15T21:25:24Z")

</div>

Hi @kit !  
I’m George Ibrahim, I’m planning my proposal for the L5 Project and I have a quick question.  
When submitting the Individual Feedback Request Form, is it okay to ask if the feedback could be reviewed by the mentor of the project (since they would be the one mentoring it)? Or should we just submit it normally without specifying? Thanks!

---

<div class="post-metadata">

**Author:** ![kit](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/kit/32/20478_2.png) [@kit](https://discourse.processing.org/u/kit)\
**Post date:** [March 15, 2026, 10:25pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/112 "2026-03-15T22:25:29Z")

</div>

Hi @georgeibrahim ! Great question, thanks for asking as I’m sure others may have a similar thought.

There is no need to specify a mentor on the form.

We (the org admins and mentors) are all coordinating. For any L5-related proposals, the associated mentor (@lee) will review. We are also open to custom proposals, and in this case we will decide on a case by case basis which is the more relevant reviewer.

(Also: Like last year, the final decisions are not made by just 1 person; we also coordinate on the selections and ranking. So during application review, multiple people will review the finalists.)

I got another question in private about **when selections are announced**. This part of the process is run by GSoC, not by mentor orgs. It works like this:

1. You submit through the GSoC portal, which opens on March 16th: [https://summerofcode.withgoogle.com/](https://summerofcode.withgoogle.com/). All formal deadlines from GSoC must be strictly followed. Please use the GSoC resources to check precise deadlines and process.
2. We (Processing Foundation admins and mentors) review, select top projects, and provide a ranking to GSoC. This is not yet announced.
3. GSoC allocates some slots to each organization. It may be not all the top-ranked projects get selected by GSoC; we also don’t find out until the official announcements.

Best,  
-Kit

---

<div class="post-metadata">

**Author:** ![georgeibrahim](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/georgeibrahim/32/21573_2.png) [@georgeibrahim](https://discourse.processing.org/u/georgeibrahim)\
**Post date:** [March 15, 2026, 10:43pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/113 "2026-03-15T22:43:45Z")

</div>

Thanks a lot for the clarification, @kit!

---

<div class="post-metadata">

**Author:** ![kanai](https://avatars.discourse-cdn.com/v4/letter/k/b77776/32.png) [@kanai](https://discourse.processing.org/u/kanai)\
**Post date:** [March 16, 2026, 4:44am UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/114 "2026-03-16T04:44:31Z")

</div>

Thanks a lot everyone, for your questions and answers, it was really insightful.

---

<div class="post-metadata">

**Author:** ![reshma045](https://avatars.discourse-cdn.com/v4/letter/r/f6c823/32.png) [@reshma045](https://discourse.processing.org/u/reshma045)\
**Post date:** [March 16, 2026, 6:47am UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/115 "2026-03-16T06:47:01Z")

</div>

Thanks for sharing the proposal template @kit

---

<div class="post-metadata">

**Author:** ![Jatin](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@Jatin](https://discourse.processing.org/u/Jatin)\
**Post date:** [March 16, 2026, 9:03am UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/116 "2026-03-16T09:03:53Z")

</div>

Hi! I’m currently reviewing the E2E testing idea and exploring the editor to define potential user flows. I noticed that downloading a sketch requires the sketch to be saved first, and saving requires authentication. However, the GSoC idea examples mention that an unauthenticated user can download a sketch. Should the download flow instead be considered part of the authenticated user flows? Just wanted to confirm before defining the flows for the proposal.

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/6/3/633a47f68413dcf9015abea88cdd055f1c3e98ce.png)

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/b/b/bb9defa7c1e24ccd79f7a797ad158dba87adc8a0.png)

---

<div class="post-metadata">

**Author:** ![manaswi](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@manaswi](https://discourse.processing.org/u/manaswi)\
**Post date:** [March 16, 2026, 1:41pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/117 "2026-03-16T13:41:57Z")

</div>

Hi @divyansh013!

Thank you for the clarification on commit dates, that makes complete sense, i’ll drop the hash-based sync tracking then.

Regarding displaying translation data on the website UI, i think a more feasible approach would be a lightweight GitHub Pages based status page, which will be generated automatically from the manifest JSON files the tracker produces.

This would:

1. give contributors clear visibility on what needs translation for every language.
2. avoid touching the main website entirely
3. make auto-update every time the tracker runs

Would this direction make sense, or do you see any limitations with this approach?

Also noted on the README updates, I’ll make sure my proposal doesn’t overlap with that!

---

<div class="post-metadata">

**Author:** ![Geeta112](https://avatars.discourse-cdn.com/v4/letter/g/94ad74/32.png) [@Geeta112](https://discourse.processing.org/u/Geeta112)\
**Post date:** [March 16, 2026, 1:59pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/118 "2026-03-16T13:59:29Z")

</div>

firstly, thankyou for sharing the proposal template @claudine. I have one question, what would be the ideal number of pages for our proposal ??

---

<div class="post-metadata">

**Author:** ![rakesh2oo5](https://avatars.discourse-cdn.com/v4/letter/r/898d66/32.png) [@rakesh2oo5](https://discourse.processing.org/u/rakesh2oo5)\
**Post date:** [March 16, 2026, 4:18pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/119 "2026-03-16T16:18:07Z")

</div>

Thanks for the reply!

After exploring the translation tracker workflow, I had a few ideas that might improve the contributor experience:

1. **Translation Progress Dashboard** – A small dashboard showing translation completion across languages and sections of the documentation.

2. **Automatic Stub Generation** – When a new English example is added, automatically create placeholder translation files for other languages.

3. **Improved Issue–PR Workflow** – Automatically close translation issues when the corresponding PR is merged.

4. **Better Contributor Onboarding** – A CLI script or documentation to help new translators set up the environment quickly.

I’m currently exploring the codebase under `.github/actions/translation-tracker` and testing how the commit comparison works.

Would love to hear your thoughts on which of these directions might be most useful for the project.

Thanks!

---

<div class="post-metadata">

**Author:** ![sakshamJain](https://avatars.discourse-cdn.com/v4/letter/s/a88e57/32.png) [@sakshamJain](https://discourse.processing.org/u/sakshamJain)\
**Post date:** [March 16, 2026, 5:32pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/120 "2026-03-16T17:32:08Z")

</div>

Hi @kit,

I recently contributed to the dev-2.0 branch by filing issue 8621 (replacing raw console.log calls with FES across Data, DOM, Events, and Image modules) and PR 8622 for the same.

While auditing the codebase, I noticed there are ~20+ raw console.log calls in the WebGL modules on dev-2.0 that appear to be leftover debug statements leaking to the user console.

These are in:

ShapeBuilder.js — tesselation error/debug callbacks (L441, L446-447)

p5.Shader.js — inspectHooks() dumps shader info to console (L146-166)

p5.RendererGL.js — multiple debug logs (L253, L295, L308, L354, L541)

p5.Camera.js — debug logs (L209, L216)

webgl/text.js — debug logs (L677, L687)

webgl/utils.js — debug logs (L279, L316)

3d\_primitives.js — multiple debug logs (L1701, L2246, L2330, L2394, L2435, L2476, L2544)

Would it be appropriate to file an issue to clean these up? Some could be replaced with p5.\_friendlyError(), and others (pure debug leftovers) could be removed entirely.

One question: p5.Shader.inspectHooks() seems like an intentional debug utility — should that be left as-is, or should it also be updated?

Happy to open an issue and a PR for this if the approach sounds good.

---

<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:** [March 16, 2026, 7:41pm UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/121 "2026-03-16T19:41:40Z")

</div>

Hi @jatin, good spot! Feel free to add it to the authenticated flows.

The examples written [here](https://github.com/processing/Processing-Foundation-GSoC/wiki/Project-Ideas-List-(GSoC-2026)#e2e-testing-for-the-p5js-web-editor) are examples and not exhaustive. We would want you to define your own flows during the project and to proposed which ones are priority to the web editor experience to secure.

---

<div class="post-metadata">

**Author:** ![harshil](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@harshil](https://discourse.processing.org/u/harshil)\
**Post date:** [March 17, 2026, 9:17am UTC](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450/122 "2026-03-17T09:17:40Z")

</div>

Hey @kit I’ve uploaded my draft proposal to the signup form, when should I expect a response?

[Previous page](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450.md?page=5)

[Next page](https://discourse.processing.org/t/gsoc-2026-join-the-processing-foundation-as-a-summer-of-code-contributor/47450.md?page=7)