Hi @nitish-bot , it should also enable capture! I have an example of testing out one way this could be implemented, here GitHub - lee2sman/L5-webcam-testing · GitHub It’s not written with a full idiomatic L5-specific way yet FYI. For example, I added in love.quit() to close the camera capture.
2 Likes
I will also submit my draft proposal in the signup form by tommorow 
1 Like
Hi @kit , Thanks for checking! It seems my earlier submission didn’t go through properly. I’ll fill out and submit the form again right away.
1 Like
Just to confirm, we only have to fill the sign up form to recieve a feedback right?
1 Like
Yes @NishthaJain we only have to fill the signup form & submit our draft proposal to get mentors feedback on it, so that we can improve it accordingly.
The final proposal submission deadline for GSoC is 18:00 UTC on March 31.
1 Like
Hi, I’m Darshan. I’m interested in the Translation Tracker project for GSoC 2026. I went through the existing Action in .github/actions/translation-tracker/index.js and the open issue backlog, and identified a few specific problems:
-
The Git diff comparison triggers false positives when only math formulas or code blocks change — issue #1174 is an example where a formula edit flagged a translation request unnecessarily.
-
The tracker has no memory of issues it has already created, which causes duplicates — issues #1174 and #1209 both track the same file.
-
There’s no assignment mechanism, so contributors end up competing for the same task without any locking — I noticed Divyansh manually routing people in issue comments as a workaround.
My proposal is to address these with AST-aware parsing using remark/rehype to skip non-prose content, a GraphQL pre-check before issue creation to prevent duplicates, and a /claim slash command for assignment locking.
Are these the right problems to focus on, or are there higher-priority gaps I’m missing?
1 Like
While exploring the codebase, I see some “TODO” comments but they do not have any issues created on github. Can I create issues for these myself and fix them.
Also, I requested a feedback on my proposal. Just wanted to confirm if it was received.
1 Like
hey @kit , would it be possible to extend the feedback form deadline to the 24th if possible? i’d really appreciate a little more time to go through everything properly.
3 Likes
Hi @kit,
Thank you so much for the response and for forwarding my question to Kevin — that means a lot at this stage.
The survey data is incredibly useful and honestly changes how I’m framing the problem. The fact that ~20% of Processing educators identify sharing project files as their single biggest teaching challenge, and that ~17% of all respondents use Processing Sound, gives the tool a concrete audience I can design for rather than assume. I’ll be building the problem statement around this directly.
I missed the Tommy Martinez session unfortunately, but I’m going through the p5.sound.js repo and recent commits to get a sense of where the API is stable vs. still evolving — which matters a lot for deciding which translation rules to build with confidence first.
Your offer to connect with survey respondents for user testing is something I want to take you up on seriously. I’m planning a community feedback phase mid-project (around week 6) where I’d show a working prototype to 3–5 educators or artists and document their responses before iterating. If that’s a good moment to make those introductions, I’d be really grateful.
Currently working through a full API surface mapping between Processing Sound and p5.sound.js — categorizing every class and method pair by translation type (direct, rename, method-split, unsupported, etc.). Will share progress as it develops.
Looking forward to hearing from Kevin as well.
Best,
Samarth
1 Like
Hey , @kit and @claudine I have a quick question regarding the proposal template , for the section where we need to share a p5/Processing sketch made by someone else that inspires us, I have added it to my collection on my p5.js editor profile. Can I share the link from my collection, or should I share the original link of the sketch?
1 Like
Hello @Geeta112 ,
You could provide both? You want to make it as easy as possible for people to click through to links, hence putting the link directly in the application. But if you wanted to share your collection with us, feel free, but sometimes less is more - a curated list tells us something about you, while we probably won’t explore a long list.
Take care, Claudine
2 Likes
Hello @NishthaJain ,
Creating an issue is a great place to start the conversation, so yes, if there is a TODO that you would like to work on that isn’t already discussed in a Github issue, please start a new issue thread. But then, wait and see what people say before starting a fix - sometimes there’s information that’s only in someone’s head and not more publicly shared that you’ll want to know - maybe the work is already started in a local branch, for instance.
We’ve definitely been processing feedback requests, yours among them.
All the best,
Claudine
2 Likes
@Divyansh013 following up on my post above — happy to discuss any of these points if it’s helpful for evaluating the proposal.
Thank you so much for the clarification @claudine, I will share the original link of the sketch directly in my proposal.
1 Like
Thanks @claudine , it was helpful for me too.
1 Like
Hi @clairep94,
I am targeting the E2E Testing for the p5.js Web Editor project.
While exploring the p5.js web editor codebase I found out that currently the tests that requires a test database to run uses mongodb-memory-server. (Currently being used in the /server/models/__test__/user.test.ts file.
My question is, is it mandatory to use only mongodb-memory-server to spin up a test database for E2E testing too?
Or can we also use docker containers to spin up a test database for E2E testing?
Kindly guide me for both local testing & the workflows (test.yml) that run on GitHub Actions.
Heyy @kit I’ve just submitted my draft proposal for feedback. I’ve also addressed your earlier feedback. Looking forward to your thoughts!
1 Like
Hi @Darshan-k , welcome to the discussion.
Great point but the issue you pointed out, #1174 is actually a case of missing translation file, do you think we should open an issue in such case or not?
This will be a good addition to the project.
I feel this is true across all the processing repos? I am personally not in view of implementing something related to issue assignment which stands true only for a particular set of issues. Also in issues, we are notifying stewards of particular languages to review the issue and act upon it ( whether to themselves take them up or assign someone). However yes this can be tedious process, can you elaborate more of how auto assigning issues will remove this friction?
Also cc @kit for this point.
Hi! @divyansh013 ,
Hoping some feedback on this approach, so that I can know I am going in the right direction, and hence will be able to submit my proposal for feedback soon!
1 Like
Hi @manaswi, sorry for missing out on your follow up query. The approach seems in a good direction, please go ahead with a draft so that I can have a wide review of the same
1 Like