Updates about GSoC 2026 - Org Application in Progress!

Summer of Code
1

Hi everyone :sunflower:

If you’re interested in working on a project with Processing Foundation for the next GSoC, read on!

If you’re interested in being a GSoC contributor, you can read through last year’s FAQ thread to have a better idea of what to expect when applications do open (at the end, there is also a summary of how proposals were evaluated).

You can also get involved by looking for “Good First Issues” on the repositories (including p5.js, p5.js-website, processing4). Before making any PR, please be sure to read the contributor guidelines carefully. Processing Foundation does not require PRs for applicants, and PRs (and other activity in online community spaces) that consistently ignore contribution and community guidelines can actually make your proposal less likely to succeed.

As in the previous year, any questions that you have about the process - please ask them here! All public questions will be answered. I’ll be back here every couple of weeks, and much more frequently (just like last year) during the application process!

Best,
Kit (PF GSoC org admin for 2025, 2026)

10 Likes
3

Looking at the past programs I see that most projects aim to contribute towards the p5.js project, are there any plans for the processing project itself or for the new libprocessing project that is being implemented in Rust joining the GSoC project roster?

1 Like
4

Hi @bakayu ! Thanks for the question.

We will be posting an updated ideas list soon, but it’s not finalized yet. Although last year’s projects were about p5.js, the ideas list included Processing projects as well. The ideas list depends on the interests of the mentors, and on what work is possible that is not overlapping too much with other ongoing work (ideally, projects can be relatively independent, and not blocked by other work).

This year, unlike last year, we will welcome custom project proposals. So the ideas list will be there as a starting point, but it would not be meant as a limitation.

By the time we submit our org application (start of Feb 2026), the ideas list will be ready, and I’ll post here.

EDIT: Here is the 2026 ideas list and additional process info

-Kit

5 Likes
5

Hi Kit,

For someone preparing early for GSoC 2026, would you recommend starting with a specific repository (p5.js, p5.js Editor, Processing4, or p5.js-website), or is it better to let the choice be driven entirely by the proposal idea?

I want to make sure early exploration aligns well with how mentors later evaluate proposals

1 Like
6

Hi @agastya , welcome!

I’d suggest starting with the project that most resonates with your technical skills or interests. Each of the above have different stacks. Also, depending on if you are using mostly p5.js or Processing, you might be more interested in one or the other! If you use both, I’d suggest checking out p5.js mode in PDE which is a recent and really interesting project. Or if you’re interested in sound, then perhaps p5.sound.js; last year’s sound project idea was unfortunately not one of the ones that got a slot, but something related to sound will be on the list.

The project list will be published soon (next week latest). It will describe areas of current interest across multiple projects. Creative interpretations of those project ideas are welcome! For now the best way to prepare before the list is public is to reflect on which projects have technologies you’d most want to work with.

I hope this helps!
Best,
Kit

1 Like
7

Hii @kit, thanks a lot for the detailed updates - this is really helpful.

I’m preparing early for GSoC 2026 and wanted to sanity-check an idea before the official project list is published. My background is mainly front end, web, and after spending time exploring the Processing Foundation websites, I’ve been looking into a potential project around front end maintainability, accessibility and theme hardening - things like componentization of repeated UI patterns, improving long-form readability and laying proper groundwork for theme support (without redesigning or changing the visual identity).

I hope custom project proposals are welcome this year, so my question is mainly about fit and process: would it make sense to keep refining this idea and contributing small fixes in the meantime, and then formally pitch it once the applications open - assuming it aligns with mentor interest and doesn’t overlap with ongoing work?

Happy to adapt scope or direction based on what the mentors feel is most valuable. Just wanted to check whether this is a reasonable direction to explore further at this stage.

Thanks again for coordinating all of this - really appreciate it.

1 Like
8

Hi Kit! Thanks for the update :sunflower:

I’ve been contributing recently (p5.js WebGL + docs) and was wondering if there are any areas or types of issues you’d recommend focusing on right now in p5.js or p5.js-website. Happy to help wherever it’s most useful.

Thanks!

1 Like
9

Hi @Samarth and @aash.u7707 , thanks for your thoughtful questions!

Also, as an update: we have submitted the org application, and we will know if we are participating by Feb 18th. We’ve also added some more notes on process and timeline here.

Now, the questions!

@Samarth asks:

I hope custom project proposals are welcome this year

Yes, they are!

I’m preparing early for GSoC 2026 and wanted to sanity-check an idea before the official project list is published.

With regard to front-end hardening, I think either the p5.js website or the p5.js editor would be good projects to consider. We do have the ideas list published now, but this year we are definitely happy to receive custom project proposals, and the ideas list is intended to help understand major open areas of work. There are two project directions there (translation process on website and e2e tests on editor) that might be interesting to look into - they both have some background info links.

If you’re interested in working on small fixes on the website: there is an accessibility steward (gh/@coseeian) who has been filing accessibility issues using the below labels - if this is of interest, you could also work on some of these. Typically, @coseeian makes “High Severity” fixes themselves, but the others tend to be open. You can also check out merged/closed issues with these labels for ideas. Although @coseeian is not a GSoC mentor, they are happy to steward contributors on the accessibility topics, and it might be a good place to get inspired about website improvements, esp maintainability and theme hardening.

I’ll also ping the related mentors to comment about fit, and open work on the editor you could try out; Claire Peng (mentor for e2e idea) was also interested in supporting e2e testing for the website (#827) and is more familiar with current Editor work than I am. If this particular area is of interest I can also coordinate with @coseeian about ongoing work to check where there’s no overlaps and a good fit.

@aash.u7707 asks:

I’ve been contributing recently (p5.js WebGL + docs) and was wondering if there are any areas or types of issues you’d recommend focusing on right now in p5.js or p5.js-website. Happy to help wherever it’s most useful.

Awesome, thank you! Documentation improvements are always appreciated and a great place to start. Additionally, if you’re not already on the Discord, it might be useful to monitor the contribute channel and help review tasks that you have familiarity with. Review and feedback are extremely important parts of the contributor process.

We do not require PRs in GSoC applications, though they are welcome; we also welcome evidence of contribution and community participation through:

  1. helpful, friendly, and technically thorough feedback in others’ PRs (when it’s in a technical topic you’re familiar with) is an extremely strong, positive part of an application. This is probably the most helpful thing, as you can see there are many PRs and longer wait times for review when too few people are able to review. Carefully picking PRs you have the technical knowledge to review and leaving a helpful comment is great, and helps make the overall development process a bit smoother for everyone!
  2. testing release candidates. Both for p5.js 1.x and 2.x, you can check releases page and looks for “x.y.z-rc.x” versions that are ready for testing. Particularly noting the change-log and testing the areas affected, then filing issues reporting any bugs you find. Finding an obscure bugs in a release candidate is extremely appreciated!

Even if you’re new to the community, if you’re familiar with some specific part of p5.js, I want to encourage you to get involved in all the different parts of open source development - which is definitely not limited to writing code / making PRs.

General note about github comments, reviews, and PRs

A general reminder for everyone reading, because I mentioned reviews and comments as an important form of contribution: fully or largely AI-generated PRs may be closed, and are not in line with the AI usage policy. The same goes for issue comments or PR reviews - please do not over-rely on LLMs. This defeats the purpose of multiple perspectives during discussion or review. Comments that appear to overuse AI and do not add to the discussion may be hidden or marked as spam. I know there are different policies in different orgs, and I am happy to answer any questions anyone might have about this.

I’ll be back on this thread every few days (more frequently if we are accepted into GSoC) to answer your questions as well as I can.

Best,
Kit

3 Likes
10

Hi Samarth,
I’m the mentor for one of the proposed projects (E2E tests for the p5.js web editor)

While contributions to the Processing repos is not necessary for your application, I would recommend getting a feel for the repos for the potential projects so that you can assess which one feels the most interesting/fun/familiar to work on! For me, that usually means creating a fork and playing with things locally to get a feel for the codebase, and maybe seeing if I can resolve any of the “good first issue” locally.

I think in terms of approachability for a JS/TS dev, the documentation sites would have the more modern, youtube-able stacks. The p5.js web editor repo is a bit more antequated.

1 Like
11

Hi! I’m less familiar with plans for the p5.js documentation site, and the p5.js library, but for p5.js web editor, we would love contributions to add tests!

There are some plans for ongoing refactor work, especially in the frontend, so unit tests for individual components would be great to help secure existing behaviour. There’s an awesome guide written at p5.js-web-editor/contributor_docs/testing.md at develop · processing/p5.js-web-editor · GitHub

If you have any Typescript exp, contributions to the TS migration would be great too! Smaller PRs for individual components would be preferred so that they’re easier for reviewers to look through. Please don’t hesitate to tag me if you have any other q’s!

2 Likes
12

Thanks! I have already contributed to p5.js core and the website recently, and I will take a look at the testing guide and see if there’s a small, well-scoped component I can help add unit tests for. :slightly_smiling_face:

1 Like