...
Right | Responsibility | |
Merge | Commit/Merge privileges on all frontend-focused code repositories. | Ensure approved review process is upheld and be on-call to address issues with recently merged PRs. Follow the merge timing guidelines. |
Maintain best practices for design, security, accessibility, and compliance on merged code. | ||
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 repositories. | Documenting and reviewing decisions in ADRs (and OEPs) and maintaining READMEs, How-Tos, etc. | |
Co-maintain prioritized backlog of needed technical improvements of designated repositories. | Negotiate and allocate a regular percentage of time toward technical upkeep, including refactoring and other items listed in this column. | |
Ongoing upgrade and feature maintenance and other ownership costs of designated repositories | ||
Training | Appropriate onboarding for using our frontend technology stack. | Educate others to help spread frontend domain knowledge throughout and beyond the working group. |
Training on new workflows/technologies. | Participate in the formalization and documentation of training and best practices. |
...
Slack: #front-end in the Open edX workspace.
Email: TBD frontend-working-group@edx.org for now.
Calendar: TBD: https://calendar.google.com/calendar/u/0?cid=Y180MjJ2OXQ2MW9uOXN0ZDk5NGV2YjAxdGd0MEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t
Rituals
Working Session
The Frontend Working Group envisions having regular working sessions in which we perform backlog grooming, roadmap planning, process improvements, and whatever else it takes to keep the working group running. That said, we want to have a bias toward inclusive, asynchronous work.
...