Hi everyone! 
Thanks to mentors @claudine and @lee for the additional info.
Meetup Highlights
It was great meeting many of you at the meetup on Monday! There were many excellent questions. Below are highlighted notes:
- For any proposals on the libraries (p5.js, processing4), maintain backwards compatibility. You can propose new functionality, but we use semantic versioning, and major version releases are not planned (so no breaking-change API updates can be considered)
- In general, technical research during the proposal phase is recommended. @clairep94 wrote that for E2E testing on the editor there “no preferred testing framework, however I believe there is some existing work either on the web editor repo, or sibling repos that have started setup to use playwright for accessibility testing. Feel free to do some research on this and add this to your application!”
- Although you can write code as part of technical research, that is not the most important part of a strong proposal. A good proposal will research its topic substantially: review older (closed or open) issues and work; get community feedback if it makes sense of the project; do market research of other relevant work. Understanding the user perspective (that can be the end user or learner for features; and developer for internal tooling or development process improvement) is really helpful here.
- For the proposal, we will ask for a breakdown of activity, week by week. Other than that, every part of the template will reflect something from the “application prep checklist” above.
- In general: we expect that your proposal presents your research and makes a recommendation of what you plan to implement and how. In individual feedback round, we will look at whether there’s any blockers or issues to be aware of, and generally give technical and conceptual feedback.
Upcoming Developer Chats
We will have more calls on the p5.js Discord related to specific technical projects (not only for GSoC contributors, but welcome to you all):
- Every Tuesday: The Processing Discord server also has the Processing4 call every Tuesday, hosted by processing project lead Moon Davé.
- March 6, 6pm CET - p5.js editor Code Mirror open issues and intro for contributor. Hosted by Rachel (p5.js editor project lead) and Connie (contributor)
- March 9, 4pm CET - p5.js website contributor onboarding. I’m hosting, and current website stewards Dora and Ego will be there. Ego was a contributor in GSoC 2025, with Dora as a mentor, and they’ve continued to work together.
- (Time TBD, I’ll add here when finalized) - Reflections on p5.js editor contribution by GSoC 2025 contributor Kamakshi. Hosted by me and Rachel (p5.js editor lead)
- March 20, 5pm CET - p5.sound.js contributor chat + demo with Tommy Martinez
Q&A
I got a question in private message I will answer here:
it okay to write the GSoC proposal using LaTeX, or is using Google Docs preferred or mandatory for submission?
The template will specify what sections and content need to be covered. It will be ~5-7 pages, but you can use a software of your choice to create the document.
@Behlool asks:
I have thought about this idea more and i would like to ask if i am able to post it on this forum so i could get feedback from you or any of the other admins
You can ask either here and I (and the others!) will respond as well as we can! Or on March 15th I’ll post a signup sheet to get individual feedback. The sign-up sheet is a google form. The feedback is given over email. Everyone ho signs up will get one round of feedback for sure, and we will try to do more rounds if possible.
Thanks for your active work @khuntvidisha13 @aakriti @Tanya10 ! Please note that because we get a high volume of requests (private messages, PRs, etc) during this time, so review may be slow, especially for large PRs. I understand this may require a bit of patience. But please rest assured, your contribution is appreciated and will be reviewed as soon as it is possible!
@aash.u7707 asks:
Are there any specific architectural considerations for e.g. injection patterns like Accessibility Settings that I should review while drafting my proposal?
That’s the main existing pattern that can be used. However, you could fork the editor and maybe see if there’s any issues with that method, and propose an alternative if it is needed. In general, it is preferred not to introduce complexity if possible, so this is only if there is a technical need to do something other than injection like the accessibility settings does.
Welcome @chandrasingh01 ! I hope @Damaris 's answer helped - it is thorough and accurate 
Best,
Kit