Core Contributor Rights & Responsibilities (excluding code contributors)

[DRAFT: Comments Welcome]

All members in the Core Contributor Program



Right

Responsibility

Legal

Be an individual Core Contributor regardless of organization affiliation 

Sign individual Core Contributor Program Agreements, per edX legal requirements

Renew annual continued interest in being an individual Core Contributor 

Complete annual training for security & privacy and a11y courses (if your role requires it)

Process

Vote in the selection process for future Core Contributors

Train new/young Core Contributors to help hone their own judgment and skills, while following our code of conduct

Co-establish the selection process for Core Contributors

Lead by example

Translation Reviewers - Ready for Review



Right

Responsibility

Own

Review/accept translations for their language(s)

Identify stellar translators in their language and encourage/support them

Serve as final arbiter of correct translations

Report edX-specific and uncontextualized strings to the edX team

Admin access to their language(s)

Attend Transifex working group meetings

Translation Administrators - Ready for Review



Right

Responsibility

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

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 openedx-i18n and any other translation repositories

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.

Co-maintain translations in Transifex

Ensure translations are up to date and fix any issues caused by technical errors (such as translating variable text)

(in Future) Co-own designated repositories

Ongoing upgrade and feature maintenance and other ownership costs of designated repositories

QA (WIP)



Right

Responsibility

Own

 

 

 

 

 

 

 

 

Marketing WG members (WIP)



Right

Responsibility

Own

 

 

 

 

 

 

 

 

Documentation (Ready for Review)



Right

Responsibility

Merge

Merge to master, making sure CI/CD passes and docs publish properly

Ensure approved review process is upheld and be present to address issues with recently merged PRs

(for Pilot) 1 designated edx-internal champion to support Core Contributor with docs issues

Retain strong communication with the champion(s) as needed

Own

Review PRs and suggest changes in designated repositories

Be proficient in professional English. Advocate for quality, professional English writing standards

Commit documentation to various repositories

Take care to pick up documentation of under- or non-documented features, including developer docs

Project manager (Ready for Review)



Right

Responsibility

Own

Independently own projects from start through completion

  • Create long- and short-term plans, including setting targets for milestones and adhering to deadlines.

  • Adjust schedules and targets on the project as needed.

  • Perform quality control on the project throughout development to maintain the standards expected.

Drive meaningful communication across all parties involved in the projects

  • Communicate updates and keep the project aligned with their goals.

  • Serve as a point of contact for the project.

  • Facilitate group discussions that result in effective decision-making when multiple options are present.

  • Delegate tasks on the project to community members best positioned and interested to complete them.

  • Prefer asynchronous discussions to accommodate global timezones.

Access to various tools:

  • GH Projects write access

  • Miro

  • Calendly

  • Jira, Confluence, & shared Google docs, as needed

Use these tools to meaningfully collaborate and share with edX engineers, Product Managers, and UX.

Open Source Pull Request Project Manager (WIP)



Right

Responsibility

Own

 

 

 

 

 

 

 

 

Product managers (WIP)



Right

Responsibility

Own

 

 

 

 

 

 

 

 

UX/UI (WIP)



Right

Responsibility

Own

 

 

 

 

 

 

 

 

Forum moderators (WIP)



Right

Responsibility

Own

 

 

 

 

 

 

 

 

Open edX Named Release Managers (BTR) - Ready for Review



Right

Responsibility

Merge

Merge features and fixes to named release branches

Ensure fixes & features are first merged upstream and cherry-picked into release branches. Ensure approved review process is upheld and be on-call to address issues with recently merged PRs

(for Pilot) 2 designated edx-internal champions to support Core Contributor with any 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-maintain prioritized backlog of needed BTR technical work and improvements to named releases (using the GitHub project board)

Negotiate and allocate a regular percentage of time toward named release production and technical upkeep