The Processing Foundation joined hands with CodeDay to facilitate our Open Source Mentorship Programs by helping provide issues and Subject Matter Expertise for the interns.
By leveraging the Processing Foundation's deep expertise in creative coding and digital arts education, interns will gain hands-on experience working on real-world projects that have a meaningful impact on artists, designers, and educators worldwide.
This repository serves as a combined effort to reflect on this collaboration by serving as a place to have submissions for proposals that interns will be putting together during their internships.
If you are an intern working with CodeDay on an issue from The Processing Foundation, the information below shows how you can submit your proposals to get them reviewed by maintainers.
Note: You can start with your fork as soon as your maintainer approves your idea of working in a particular direction. You can then make progressive commits to complete the given template.
Step 1 — Fork this repository
Create a fork of this repository on your GitHub account. Name it as:
proposal-submission-team-"your mentor's name"-sose26
For example, if your mentor's name is John Doe, your repository's name should be:
proposal-submission-team-john-sose26
If you're a group of interns working as a team, ask any one team member to create the fork and submit the proposal on behalf of team.
Step 2 — Create a branch
Create a branch on your fork to make changes and add your submission. The branch should be named:
patch-sose26-team-"mentor's name"
For example, if your mentor's name is John Doe, your branch name should be:
patch-sose26-team-john
Step 3 — Create your proposal file
Inside the Submissions SOSE 2026 folder, there is a file named submissions.md. This file contains a template you should use to put together your proposal.
Copy the contents of submissions.md and create a new .md file named:
proposal-team-"mentor's name"
For example, if your mentor's name is John Doe, your file name should be:
proposal-team-john.md
Step 4 — Fill in your proposal
Fill in the contents to complete your proposal with all required fields.
⚠️ Please make sure not to raise a Pull Request until you feel the proposal is ready for final review.
Step 5 — Raise a Pull Request
Once the proposal is all set, raise a Pull Request from your branch to the main branch in the repository you created the fork from. Make sure to mark the checklist in your PR description before submitting. Your PR title should be populated.
Step 6 — Wait for review
Wait until the maintainers review your request.
- ✅ If approved — the maintainer will create an issue on the particular p5.js project you wanted to work on for your proposal, and you can start working on it.
- 🔁 If changes are requested — they will ask for revisions before it finally turns into a mergeable proposal. Make sure to update your proposal according to their feedback.
-
Initial ideas due on: 2026/07/29
-
Final submissions due on: 2026/08/06
Refer to the Onboarding module for more detailed information on the proposal drafting timeline.
Questions regarding submissions? Check with the maintainers from p5.js on Discord or with the staff on CodeDay's Slack.
This is a collaborative space maintained by CodeDay with input from Kit Kuksenok, current Engineering Manager / p5.js Project Lead representing The Processing Foundation.
We welcome thoughtful contributions from interns, mentors, and the wider community. Whether you spotted a typo, think a step in the guide could be clearer, or have a suggestion that would make the submission process smoother for future interns — we'd love to hear from you.
This repository is licensed under the MIT License.
The license covers the repository structure, documentation, templates, and workflows maintained by CodeDay. Proposal submissions made by interns inside the Submissions SOSE 2026 folder remain the intellectual property of the respective interns and their mentors. CodeDay and The Processing Foundation make no claim of ownership over intern-authored proposal content.