Hello everyone! It has now been a week since the release of 2.0, and I wanted to stop by in this thread and give some ideas on how to get involved in the future of p5.js 2.0
TypeScript @ the pr05 grant
We’ve just announced Incremental TypeScript Migration for the p5.js Editor as a pr05 grant project:
This project focuses on initiating the migration of the p5.js editor to TypeScript. The goal is to improve maintainability and the developer experience by enhancing readability, enforcing consistency, and reducing the likelihood of errors. The migration process will involve selecting a portion of the editor, converting it to TypeScript, and ensuring compatibility with the existing codebase. Additionally, updating tests and documentation will be important to onboard future contributors.
Read more about this grant, or ask questions about it in the open call Discourse thread. We’re looking forward to your ideas!
Contributing code, documentation, and tests to 2.0
To help make it easier for all contributors get an overview of what’s in progress and what’s available, we’ve set up this status board for 2x.:
We’ll continue to go through the issue backlog on both p5.js and p5.js-website and update other project boards as needed, but this is the best place to get started with contribution to 2.0 / 2.x.
If you’d like to contribute to the next minor release of 2.1 (for end of May/June), please check the issues marked as Ready for Work for the 2.1 milestone. This will include bug fixes, documentation improvements, and highest-priority features, so you can check back over time if anything’s been added.
Bug fixes, documentation updates, and tests will be included in patches before 2.1, whenever work is ready. For example, you cab see the kinds of updates that were part of the first patch: release notes for 2.0.1
If there is nothing marked for the 2.1 milestone, you can check the issues Ready for Work anytime - but keep in mind that review on these may also bit a bit slower.
Contributing ideas for improvements in 2.x
Typing 2.0 and see a bug / weird behavior? Report it in Issues > New Issue > Bug Report
If have an idea, you’re welcome to create new issues, but please check if there is an ongoing discussion about this topic already.
Get in touch!
You’re also welcome to share ideas and ask questions here, on Discord, or drop by my public office hours.
Best,
Kit