Hello! Before you begin working on any issues under The Processing Foundation, please take a moment to review the following resources — they'll give you everything you need to get started on the right foot. You'll also find a checklist below that you'll need to complete during your internship to qualify as an active Open Source Contributor.

Note: This Onboarding Module is for CodeDay’s interns and has been approved by Kit Kuksenok, the current p5.js Project Lead at the Processing Foundation.

Resources 📜

• Before starting to set up the project please go through the General contributor guidelines and a few videos from the artist series which provides excellent short videos that will give you an idea of how p5.js is used. As a software project and a community effort, p5.js prioritises access and inclusion please make sure to be considerate about this.
• Most of you might already have some coding experience but are new to p5, we recommend you go through the postcard tutorial at least once. This gives an overview of various features.
• Some of you might have already worked with p5.js in a previous internship and would be familiar with p5.js version 1.0+. But please go through 2.0+ updates over here: detailed list of syntax changes in p5.js 2.0+ , this is where the current development is focused right now.
• If you are working on p5.js, go through these repo Essentials: unit and visual testing and how to use p5's Friendly Error Message (FES) setup.
• For p5.js 3D graphics, check: WebGL contribution guide and architecture. Most of the current graphics work is related to p5.strands API, please see these technical details and a high-level talk; the #p5js-strands channel on discord.p5js.org is a good resource to learn more.
• If you are working on p5.js-website, go through these repo Essentials: Getting started and also check the #p5js-web channel on discord.p5js.org
• If you are working on p5.js-web-editor repo, go through these repo Essentials: Full contributor documentation (we recommend you go with the Docker setup). If you need some help feel free to ask it in #contribute-to-p5.
• If your PR includes updating the reference documentation check: Reference build process for local testing of JSDocs; web accessibility of sketches and documentation style guide.
• When in doubt, you are always welcome to ask for support in the **discord.p5js.org** #contribute-to-p5 channel. Current active contributors and maintainers are frequently around and will be able to help direct!

Checklist 📋

It is important that you complete all of these checkpoints at different stages of the internship:

unchecked

• [ ] Head over to your assigned issue and claim it by commenting: "I, with my team members (@githubusername1, @githubusername2, @githubusername3…), am working on this and we are from CodeDay Labs." Please make sure to add the GitHub usernames of all your fellow teammates.
• [ ] Join the p5.js Discord server and use the relevant channels for the reasons mentioned in the resources above. We advise you to say hi or raise important questions in #codeday if you are blocked. You can also tag the maintainer @_ksen0. While we advise you to be mindful of their time, maintainers love to help with your queries and questions, and you shouldn't be afraid to ask! You can check for current maintainers and active stewards over here: **https://github.com/processing/p5.js#stewards**.
• [ ] Stay active and keep the maintainers in the loop so that they are aware of your progress. When working on your assigned issue, make sure to share how you plan to approach the solution within the first three days — a line or two on your issue and Discord is just enough.
• [ ] Keep updating the maintainers on a weekly basis about your progress until you finalize your PR, #codeday on the p5.js Discord server is a great place to do that. Raising a draft PR in the first week itself and then working on it is a great way to help them understand your progress better.