That’s really helpful thank u!!
Hi everyone! Great work with the collaboration here, it’s wonderful to see.
Deadline coming up soon! Additional requests for feedback probably will not receive in-depth responses at this point, but we try to respond to as many as we are able to.
I am continuing to monitor this thread for anything urgent that has not already been answered.
One thing worth noting though - the Processing Foundation GSoC guidelines recommend against raising PRs for the proposed idea this early.
Thanks for raising this @KhushiMishra , that is a correct and very helpful reminder!
Good luck, everybody!
Best,
Kit
9 Likes
Hello everyone,
Although I already had discussions in this discourse even before the p5.js was selected for GSoC 2026, I realise I never introduced myself earlier. Going through the proposal template again, I realised this.
So, hi I’m Aashish from Nepal. I learned about p5.js when I was starting out with JavaScript, from The Coding Train Youtube Channel. I’ve been using the editor to make sketches in the past, and this year I also did contribute because I realised the editor didn’t have the Nepali language support. So, I added. Hoping this reflects soon on the actual web editor.
Thank you for reading! Excited to be a part of the community.
Heyy Kit!
Thanks a lot for this guideline. I cloned the p5.js repo and the translation tracker part seems quite intriguing.
Looking forward to more insights along the way!
Hi everyone! 
My name is Avni, and I’m a Computer Science student from India. I recently started exploring p5.js and have been experimenting with small sketches, which I found really interesting.
I’m currently focused on web development (HTML, CSS, JavaScript, and React) and enjoy building interactive projects while improving my problem-solving skills.
I’m planning to submit a GSoC 2026 proposal with the Processing Foundation and wanted to introduce myself here. Looking forward to learning from the community and contributing!
Thanks 
Hello everyone! My name is Islam Salem I am an Engineering student by day and an artist by very late evening.
I will be entering with a quality of life improvement that I have wanted for a while in Processing’s 3D renderer… Native .glb/glTF support without blender processing workarounds. .glb support will allow more complex geometry faster support given it is already in binary and would not need intermediate parsing, and will not require separate texture support and hold environment data.
With all, creating the proposal, trials, and learning the repo was already a very useful experience. Best of luck to everyone this year!
Hi everyone! I have submitted my GSoC 2026 proposal for Extend Tests in Processing4. Thank you so much @claudine for the helpful feedback and I have addressed all your suggestions including the bounding box approach, test design examples for rect() and ellipse(), and edge cases for each function. Looking forward to the review process!
Hey @kit, I have already moved code snippets and screenshots to an
appendix. I am also planning to move some additional technical details to
the appendix to keep the Proposed Work section within the page limit. Just
wanted to confirm whether this approach is acceptable??
“Thanks! PR #4048 submitted, E2E Testing proposal ready for review.”
Hi Rahul,
Thanks for the welcome!
- PR #4048 submitted: https://github.com/processing/p5.js-web-editor/pull/4048
- E2E Testing proposal submitted
- Contributor guidelines read
Excited for feedback!
Nikitha Singh Raj Purohit (Nikki03-tech)
Hey @Nikki03-tech !
Good initiative taking your first contribution
Just a small tip — Processing/p5.js repos usually don’t allow adding personal names or GSoC notes in README, that’s why it got closed. Totally normal for first PR 
You can instead:
-
Fix small docs issues (typos, broken links)
-
Improve explanations or add examples
-
Or pick beginner-friendly issues from the repo
Best of luck for your GSoC proposal, last date is today so give your best! 
Also feel free to join the community discussion here:
https://discord.gg/KFy63yZat
Hello everyone! I am a Full-Stack developer currently looking into the architecture of the p5.js Web Editor for the Eyedropper Color Debugging project. As I am outlining my proposal, I had a quick question regarding the initial scope: When building the data extraction logic to pass back to the React UI, should the priority be establishing support for CanvasRenderingContext2D.getImageData() first, or is the expectation to support WebGL’s readPixels() simultaneously for the MVP?
I’m excited to dive deeper into the codebase and learn from this community!
Hi @kit,
I am preparing for GSoC 2026, and currently I am contributing to the p5-web-editor project. My background is mainly in the MERN stack, and I have experience working on major full-stack projects, which has helped me build strong skills in both frontend and backend development.
Through these projects, I have gained practical experience in building scalable applications, managing APIs, handling databases, and creating user-friendly interfaces. I am very interested in open-source contribution and excited to improve my skills by working on real-world projects with the community.
I would love to learn from your guidance and understand how I can contribute effectively to the p5-web-editor project for GSoC 2026.
@rahulchaudhary Thanks for the feedback! 
Will fix docs without personal names.
Any beginner-friendly issues I can tackle today?
GSoC proposal ready - any tips?
Hi everyone! I’m Shreya Sharma (github: menacingly-coded), and I’m interested in contributing to p5.js for GSoC 2026.
I’ve been exploring the p5.js Web Editor codebase and working on a proposal around improving debugging support for shader-based workflows, especially for p5.strands. I’m excited to learn more, interact with the community, and hopefully contribute something useful. Looking forward to connecting with everyone!
Hi @hemantGavali ,
Great to see your interest in GSoC 2026 and p5-web-editor.
Since you’re getting started, I’d recommend first exploring the codebase and understanding how things work before jumping into major contributions. You can begin with beginner-friendly issues, documentation improvements, or small bug fixes to get familiar with the workflow.
Consistency matters more than experience here, so try to contribute regularly and gradually take on more impactful tasks. Also, make sure to follow discussions and project guidelines—it really helps in understanding how to contribute effectively.
If you’d like to connect with other contributors and get guidance, you can also join our Discord:https://discord.gg/KFy63yZat
Feel free to ask questions anytime—happy to help!
Hey! That’s a great question - I actually spent some time thinking this through while working on the proposal.
My current plan is to support both Canvas 2D (getImageData) and WebGL (readPixels) from the start, rather than doing them one after the other. Since both paths live inside the same injected script in EmbedFrame.jsx, the context detection already happens at runtime.
If I split them, it might end up as a half-working feature that doesn’t work for WebGL sketches, which is actually the main use case for debugging with p5.strands.The tricky part isn’t really the API difference, but the WebGL edge cases - things like the Y-axis flip, HiDPI scaling, and the preserveDrawingBuffer behavior.
So yeah, the MVP would ideally support both, the real challenge is just getting the WebGL side right.
Hi @menacingly-coded !
Welcome to the community! It’s great to see you exploring p5.js and working around shader debugging—sounds really interesting
you can connect with with everyone on p5.js discord:
https://discord.gg/KFy63yZat
I guess I’m late but just submit the proposal for E2E testing for p5.js web editor. hoping for the best
Hi @rahulchaudhary ! Thank you for the warm welcome <3.
I’ve already joined the Discord 
and looking forward to connecting with everyone there!