glad it was helpful and totally agree with you point of showing both raw pixel + mode-aware coordinates as an advanced or optional view. This makes a lot more sense.
PR #4048 submitted: docs: GSoC 2026 first contribution from India by Nikki03-tech Ā· Pull Request #4048 Ā· processing/p5.js-web-editor Ā· GitHub
Hi team!
GSoC 2026 ā E2E Testing project
Skills: JS/HTML/CSS/Python
Hyderabad, India
Ready for feedback!
Nikki
hey all ā my name is sam and iām currently an educator teaching introduction to p5.js through mid-to-advanced web development skills. iāve attended @lee ās L5 meetups in nyc and am really excited to see L5 develop with a permacomputing mindset! will probably be spending a lot of time on the L5 category so hopefully will see you all around this summer ![]()
Could you help me tag a supervisor or coordinator here? I am currently researching the project idea: āCode Translation between Processing Sound and p5.sound.jsā from the GitHub idea list.
Based on my research, I plan to use JavaParser to get the Java AST for transpiling to p5.sound.js, and I will use Babel to transpile from p5.sound.js back to Java.
I will be done with a sample transpilation soon and will share it here before the deadline.
I want to ask the admins here, am I on the right path?
Welcome @samheckle ! Great to see you here.
Hey @kit, hey @lee I am ashamed to even say this, but I just submitted my proposal for a first review, yes 3 days before the final deadline and on a weekend, I would appreciate it a ton even if I could get a surface-level review on it given the tight timeline. I fell sick last week which delayed progress on it, that paired with my perfectionist tendencies led to this.
Thank you and sorry!
Hey everyone ![]()
Just submitted my final proposal for SoundBridge ā Code Translation between Processing Sound and p5.sound.js. This whole process has been one of the most learning-dense experiences Iāve had. Reading both source codebases, finding the connection inversion, building the POC, getting feedback from @kit ā all of it pushed me to go deeper than I expected to.
Thank you @kit for the detailed review and for taking the time to engage with every applicant here. The way this forum has been run ā every question answered publicly, the thread itself becoming a resource ā is something Iāll carry forward into how I approach open source going forward.
Fingers crossed
ā hoping to spend the summer building something genuinely useful for the Processing community.
ā Samarth
Welcome @Nikki03-tech to the processing foundation community.
If youāre targeting GSoC, make sure to check this out.
This contains all the useful information regarding GSoC, proposal template & other helpful resources.
Also, if you havenāt joined the Discord group yet, you can join that here.
Hello @Samarth , this sounds really interesting. Wishing you all the best for your proposal.
hi everyone!
i noticed quite a few people missed the feedback submission deadline (i submitted on the last day too, so i get it).
since itās not feasible for the org to give feedback after the deadline, iāve added a section for general feedback on the shared tldraw board.
it would be great if people could share the general feedback they received on their proposals there, so it can help those who missed it.
@nitish-bot I am currently traveling but will try to take a look in 24 hours. Thanks.
For folks interested in L5, we just received 2 Usability Studies reports from Usability Studies teams at University of Washington. One study surveyed Beginners to Creative Coding. The second study worked with Experienced Creative Coders (with p5.js experience and/or 1+ years of creative coding).
The results of those studies are currently posted in a thread here dedicated to the studies.
They are wide-ranging and useful starting points for significant ways to improve L5ās usability (including the language and its ecosystem). I havenāt written a response to them yet, nor prepared a markdown/text file nor GitHub issues based on it yet. I have only received the second study tonight for example, as a PDF file. But it is useful information that would be excellent for informing proposals for working on L5 in GSoC. (Also pinging @samheckle who had asked about these studies).
can I sumbit my pdf proposal draft for the review here
Hi @kit,
I wanted to let you know that I have submitted my GSoC 2026 proposal. Thank you so much for the detailed review feedback. I went through every point you and @raclim raised and addressed them all as thoroughly as I could.
I gave this everything I had. Whatever the outcome, this process taught me a lot and I am grateful for the guidance from Kit, Dave, and Neill, and for the great community around me throughout this journey at Discord and also here.
Looking forward to the results and continuing to contribute either way.
Welcome @Nikki03-tech ,
please Before making any PR, please be sure to read the contributor guidelines carefully.
Hi everyone! Iām excited to share that I have officially submitted my GSoC 2026 proposal for the p5.js Web Editor: Friendly UI Shell Modernization.
A huge thank you to @Kit and the community for the feedback on my Modern Dark Mode Figma concepts earlier this monthāit really helped me refine the āUI Wrapperā architecture in my final plan. Iām looking forward to potentially contributing to the CodeMirror 6 migration this summer!
Hi everyone,
I am interested in contributing to Processing Foundation for GSoC 2026.
I am planning to work on:
āEyedropper Color Debugging in the p5.js Editorā.
I have experience with JavaScript and currently learning p5.js and shaders.
Could you guide me on:
- Where to start in the codebase
- Any beginner-friendly issues related to this project
Thank you ![]()
Hi! Iāve started working on the Eyedropper Color Debugging idea.
I created an initial prototype PR that logs RGBA values from the canvas in the preview:
Iād really appreciate any feedback or guidance on improving this feature further.
Thanks!
Great thanks for the p5.js Discord link!! Already joined and started exploring:)))
Hey @pratapalok! Great to see the enthusiasm
One thing worth noting though - the Processing Foundation GSoC guidelines recommend against raising PRs for the proposed idea this early. Itās better to first get familiar with the codebase by solving existing issues, as it strengthens your proposal and shows your grasp of the project.
Here are some good first issue to get started. Also, make sure you go through the contributer guidelines thoroughly:
Good luck , the eyedropper idea is genuinely interesting and Iām looking forward to seeing where it goes.
