Contribute to p5.js WebGL
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24k
- Forks
- 3.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 25
Description
Hi,
For contributors who are interested in working on p5.js WebGL related issues, we have a project tracking board (screenshot pasted below) with the ~50 p5.js WebGL open issues. Thanks @davepagurek for the categorizing help. If you haven't contributed before, the issues in the 'Minor Enhancement' or 'Documentation' category could be a great place to get started.
p5.js WebGL Issue Tracking Board:
You can also use Area:WebGL label to find all open WebGL issues, as shown in the screenshot below.
Below are some contributor docs you might find helpful:
I will suggest going through the contributor docs and leave comments here if you have any questions about contributing to WebGL in general. We are in the process of updating our contributor documentation, so please feel free to let us know how we can improve the docs to make it easier for contributors to get started. Meanwhile, please feel free to go ahead and leave comments in any specific WebGL open issues when you see fits. Thank you!
CC the current p5.js WebGL stewards: @davepagurek, @aferriss, @aceslowman, @ShenpaiSharma, @ChihYungChang, @teragramgius, @JazerUCSB, @richardegil, @itsjoopark, @Gaurav-1306, @jeanetteandrews
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with contributor_docs/contributor_guidelines.md and contributor_docs/webgl_mode_architecture.md, then review the linked WebGL project board and Area:WebGL issues. The issue does not define a specific documentation change, so clarify the target issue or documentation gap and acceptance criteria before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100