p5.js 2.0 Updates

[Qianqianye]

Topic

Hi!

Earlier this year, we initiated the p5.js 2.0 RFC (Request for Comment) process to collectively re-envision the next major release of p5.js with the community, with a strong focus on our core value of access. We want to extend our gratitude for your participation—over 60 p5.js 2.0 proposals were opened and discussed. You can find all 2.0 proposals under the label ‘p5.js 2.0’. We’re excited to share some updates with you.

We’ve organized all the proposals into a p5.js 2.0 GitHub project, categorized by priority, project size, and phases. Proposals in Phase 1 are planned to be completed by the end of October, while Phase 2 proposals have a tentative completion timeframe around the end of 2024.

Governance Model and Decision-Making Process

To ensure collective decision-making on which proposals to implement, the p5.js 2.0 project follows this governance model and decision-making process, which includes three components:

1. p5.js 2.0 Core Committee: Responsible for organizing proposals, making initial approval/decline decisions, prioritizing, and assessing project size and phases.
   Qianqian Ye, @Qianqianye: p5.js lead
   Kenneth Lim, @limzykenneth: p5.js mentor
   Dave Pagurek, @davepagurek: p5.js contributor and maintainer

2. p5.js 2.0 Advisory Committee: Responsible for making final approval/decline decisions on proposals.
   Lauren Lee McCarthy, @lmccart: p5.js creator
   Nat Decker, @natdecker: p5.js accessibility consultant
   cypress masso, @outofambit: 2019 p5.js fellow
   Stalgia Grigg, @stalgiag: 2019 p5.js fellow
   Daniel Shiffman, @shiffman: p5.js educator

3. Community Input: Solicit comments on implementation details or potential implementers.
   For any proposal accepted for implementation by both the core and advisory committees, its status will be updated to ‘Implementation’ on the p5.js 2.0 GitHub project, categorized by high, medium, or low priority. Proposals not selected for implementation for now will be labeled as ‘Out of Scope’ or 'No Priority' and will not move forward to the next phase, but we are open to implement them in the near future. The broader community is encouraged to leave comments on accepted proposals, and these will be considered during implementation. However, the decision on the proposal itself will not change at this stage. The goal is to clarify the implementation approach and identify potential implementers. We are committed to work with a group of implementers that reflect the diversity of the p5.js community.

What's Next?

Several p5.js 2.0 proposals are already in progress or almost completed, such as the Functional core and modular build, Async/Await setup(), Typography module revamp, and others. Please see the latest updates in the dev-2.0 branch. We will continue to update the p5.js 2.0 GitHub project and the dev-2.0 branch as we move forward and will share updates with the community. Please feel free to leave comments in this issue if you have any questions about p5.js 2.0 process and proposals.

Our current priority is the p5.js 2.0 issues and PRs, so it might take us a bit longer to review other issues and PRs. However, we will get to them eventually! We appreciate your patience in the meantime.

Thank you!