...
Right | Responsibility | |
Legal | Be an individual CC regardless of organization affiliation | Sign individual (and, if needed, entity) contributor agreements, per edX legal requirements |
Renew annual continued interest in being an individual CC | Complete annual training for security, privacy, a11y, and architecture | |
Merge | Merge to master, using defensive CI/CD techniques such as feature toggles | Ensure approved review process is upheld and be on-call to address issues with recently merged PRs. Follow follow guidelines. |
(for Pilot) 2 designated edx-internal champions to support CC with on-call issues | Retain strong communication with the champions, including visibility into expected merges and time availabilities | |
Own | Review PRs and suggest technical changes in designated repositories | Learn and advocate for clean code, quality, and architecture principles and practices (per repository’s definition of done) |
Co-establish technical direction of designated repositories1 | Documenting and reviewing decisions in ADRs (and OEPs) and maintaining READMEs, HowTos, etc | |
Co-maintain prioritized backlog of needed technical improvements of designated repositories. | Negotiate and allocate a regular percentage of time toward technical upkeep, including refactorings and other items listed in this column. | |
(in Future) Co-own designated repositories | Ongoing upgrade and feature maintenance and other ownership costs of designated repositories | |
Process | Vote in the selection process for future CCs | Train new/young developers2 to help hone their own judgment and skills, while following our code of conduct |
Co-establish the selection process for CCs | Lead by example |
...