Weekly Schedule
Week 1
Make GitHub issues to handle feedback from usability testing surveys
Identify and track existing issues in website documentation
Send out surveys among current p5.js students
Week 2
Build out community guidelines based off of: p5.js community, ml5.js community, and permacomputing (including the L5 page on it).
Look at other open-source references, such as Arduino, Hydra Live Coding.
Co-lead L5 workshop and surveying at ITP camp.
Week 3
Analyze survey responses and set up meetings to see what other changes could be made.
Start with quick wins on documentation updates from week 1 issues. This will likely focus most on “getting started” changes.
Get early community feedback on changes so far.
Week 4:
Start listing out tutorials that need to be added.
Begin work on VS Code Extension with the following objectives:
Compile and run L5 for local development
Bundle L5 and Love2D into a single executable for sharing.
Week 5:
Continue work on VS Code Extension.
Tooling experiment #1: Test LoveJS to run L5 in the browser. Test with VSCode integration and whether or not LoveJS is a viable tool for sharing in the browser or to continue with sharing executable.
Begin planning on a week-long jam to be run by the end of the summer. Set up itch.io page to host L5 as a tool and start building assets for the jam promotion
Week 6:
Get feedback on VS Code extension and iterate on feedback.
Write tutorials using VS Code extension.
Tooling experiment #2: Create a repository for apt or homebrew package install for L5.
Week 7:
Facilitate Github issues and delegate contributors. Update new issues based on technical tests in week 6.
Tooling experiment #3: Fork Love2D to build a single executable with a program loader screen.
Week 8:
Make changes based on feedback from VS Code extension
Tooling experiment #4: Based on viability from week 5 research, fork LoveJS to build an executable for the web.
Week 9:
Document existing experiments.
Research into community project sharing:
Mastodon bot (potential server: genart.social)
Sharing via a form and an approval
Online computational magazines (https://randomwalk.club/)
Translating to p5 for browser integration
Uploading to itch.io
Week 10:
Begin community jam (7-10 days long hosted on itch.io) and assist with needs from the community. Sam will be facilitating the jam, assisting with any L5 issues.
Tooling experiment #5: Test using Codeberg as the code repository and if Codeberg pages is a better platform to host.
Make updates for the L5 website and research into other Static-Site Generators that will have better long-term support.
Week 11:
Adjust tutorials as needed based on feedback from the jam. Any documentation updates, tutorial changes, or other quick fixes will be implemented and create Github / Codeberg issues for larger projects to encourage community development.
Week 12:
Write up a blog on documentation updates, make guidelines for documentation contributions, and create handoff guide for future contributions.