Hi Sir
I’m Israr, a contributor interested in p5.js and GSoC.
I just wanted to let you know that I’ve started working on a new beginner-friendly library for p5.js sketches.
I’m excited to contribute and would really appreciate any guidance or advice you might have as I continue developing it.
Thank you for your time! 
You should follow the application checklist GSoC 2026: Join the Processing Foundation as a Summer of Code Contributor!, and should look in the idea list of gsoc 2026 of processing foundation on github, and see which idea excites you the most and should making notes towards it.
Welcome @israr! Just adding to a previous comment, there are multiple ways to contribute. You can find more about this in application checklist above. It might be helpful to try out other community-created library too.
hi all!
i’m yash, exploring creative coding (especially shaders).
i’m interested in improving accessibility and debugging features for writing shaders in p5.js, more specifically strands.
i’m still exploring what kind of interfaces would work best in the web editor.
also, i found it a bit hard to keep track of context across the forum, discord, calls, etc., so i started mapping things here:
sharing in case it’s helpful to others too 
Hi @skyash, its really great actually!
Welcome to you and to all of the new faces here! As an FYI, we are a diverse community of people, and Sir is not the correct pronoun for everyone here. I appreciate you are trying to be polite here. Thanks for joining us.
Hi @claudine! I have been exploring the visual-testing branch and I have a question about project scope.
I understand that when a new version of Processing is released, the internal rendering behavior may change slightly. This can break the visual output of existing sketches even though the developer did not change anything in their code.
I have an idea — when a version change causes a baseline to fail, can we create something that suggests the minimal code changes needed to preserve the original visual output in the new version? I know this might be a bit advanced for the scope, but I feel this is what developers and artists actually need — they just want their sketch to look the same, without manually figuring out what changed.
This also aligns with Processing Foundation’s mission of making things easier for developers and artists.Could you help me understand if this direction fits within the project scope? Or should I focus more on adding visual regression tests for missing functions?
Thank you!
“Hi!
I’m interested in the Eyedropper Color Debugging project for GSoC 2026. I have JavaScript experience and have already experimented with the get() function in p5.js to read pixel colors. I’d love some guidance on getting started with the p5.js Web Editor codebase.”
Hii @Geeta112 The Contributor Documentation will help you to get started. You can also look into Good first issues or Good Medium Issues to familiarize yourself with the codebase by resolving them.
Hello @khuntvidisha13 , great to see you brainstorming.
What comes into my mind is there is a difference between tools for developers, and tools for users. The visual tests are a tool for developers of Processing to detect unintended regressions when developing for the application. The visual tests let us know something in the output has changed, so that we can try to correct it in our application code, and an indication that we might have fixed it is that the test will pass again.
If this was a software suite where there were frequent changes in the output, and therefore people would need to tweak their sketches, then your idea would have legs, as a tool for users. However, we do try to not change application output from version to version.
So I think it’s a matter of how often do we think someone would need to use this tool? At the moment, I would say the need is not great for users to have such a tool. However, there is a current need for developers of Processing to have more tests. Feel free to brainstorm more, also.
Hello @claudine @kit My name is Rahul, and I’m a full-stack web developer interested in the E2E Testing for the p5.js Web Editor project for GSoC.
I joined the discussion a little late, so unfortunately I couldn’t attend the meeting on March 9. I’m currently going through the meeting notes and exploring the repository to better understand the current testing setup.
If possible, could you please share a brief summary of the key points discussed in the last meeting and also guide me on the best way to start contributing to the testing workflow?
GSoC 2026: Join the Processing Foundation as a Summer of Code Contributor! - #65 you can refer to this.
Hello, Could you please share the link to join the p5.js or Processing Discord server ? The links I found online seem to be expired.
Welcome @rahulchaudhary ! There are meeting highlights shared in this previous comment from the GSoC meeting:
The past meeting on Match 9th was in regards to p5.js website contributor onboarding. You can find the highlights and notes about that meeting in the p5.js discord server, under the “#p5js-website” channel. The upcoming meeting time for “p5.js website dev chat” is there too, on March 16th.
Hope this helps!
Hi @claudine! Thank you so much for the guidance and for taking the time to explain the difference between developer tools and user tools. It really helped me understand the project better.
After thinking more about it, I realized that the baseline tells us that something changed — but it does not tell us what changed or why. The developer still has to manually compare images and investigate the issue.
My idea is — when a test fails, instead of just showing PASS/FAIL, we automatically show:
Which pixels changed
How much % changed
A suggested code fix
This way developer does not have to manually investigate — they get the information directly. This would make testing easier for developers and save their time.
Would this be a valuable addition to the project?
Hello @khuntvidisha13 ,
Thanks for your further thoughts on the project. Your instincts are spot on, providing information on which pixels were changed is important information - and that is what happens at the moment with the visual tests. Because the visual tests are … visual, accompanying the run is a test report with visual feedback. This visual feedback also provides a sense of the amount of deviation.
I wish you more fruitful brainstorming
Hii, is there any template provided for Gsoc proposal for the processing foundation??
