-
Notifications
You must be signed in to change notification settings - Fork 901
Lead Caretaker Notes
Joey Lee edited this page Jan 30, 2020
·
3 revisions
This document is about the roles and responsibilities of ml5.js lead caretaker (developer). Over the years, various individuals have taken on more leading roles in the development of the project which as lead to many wonderful contributions to the library, the ml5.js ecosystem, and the community more broadly.
This document catalogs some of the things you as a ml5.js lead might think about as part of the role.
As a ml5 lead caretaker…
- You will have the overview of all the happenings in the ml5 universe.
- This means you’ll be driving the project forward by keeping your eye on all of the developments across the project — from the library itself to the website to community events and more — and organizing, supporting, and contributing to these developments throughout the time of your appointment.
- You will identify and prioritize various projects and coordinate efforts with contributors (e.g. work-study or external).
- You are watching, responding to, linking between, and generally managing issues and pull requests (this will be a bulk of the time!).
- Making sure documentation is up-to-date
- Ensuring that ml5 is considering everything, specifically with regards to ethics, accessibility, and inclusion.
- This means you will make sure that ml5 does not support features that harm, discriminate based on race, age, gender, class, or disadvantage anyone or anything, especially already vulnerable populations.
- In times of uncertainty, you are responsible to reach out to collaborators and experts that can advise on how to proceed.
- Propose ways to improve the library or the overall user experience of using or developing ml5.
- This means improving devOps processes, lowering the entry barrier to making contributions, optimizing bottlenecks or pain points, improving wording or syntax choices, improving the website, making it easier to keep things up to date, etc.
- Making new releases and ensuring that the latest release is reflect across all of the related projects (e.g. ml5-examples, website, etc)
TBD