Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Each CC in the pilot is assigned to 2 edX employees as their 2 internal champions. The champions support the CCs through the pilot to:

  • Ensure a reliable and timely communication channel exists with the CC, for example, in case of emergencies or questions on upcoming PRs.

    • Wherever possible, avoid private discussions and default to public channels.

    • Inform the CC of escaped production issues through the deployment pipeline’s auto-notification.

      • The CC can undo their changes by merging (and deploying via CD) a revert of their PR. 

    • Escalate urgent issues to edX engineering management that are impediments for the CC.

    • Help the CC connect with relevant technical owners, as required by the review process below.

Reviews and Ownership

The requirements for when edX Product must review a PR varies based on the type of change as summarized in the table below. Similarly, non-trivial changes need to be accepted by the team that owns the repository in order to ensure the owning team has the context for the change and acknowledges its future ongoing maintenance.

...

Type of change

...

Required review1
(not counting the author)

...

Required Technical Ownership

...

Maintenance updates & bug fixes

...

1 core committer

...

N/A

...

Technical enhancements

...

1 core committer

...

Acknowledgement from owning team2

...

End-user facing changes

...

1 edX product
1 core committer

...

Acknowledgement from owning team

1 In the event of any disagreement between CCs, it is expected that the CCs will demonstrate appropriate judgment and work it out amongst themselves. If moderation is required, they can reach out to Nimisha, as head of architecture.
2 The process for “acknowledgment” from the owning team is left to the discretion of the Champion and CC so they may find a working model for the relevant changes. For certain types of contributions, a one-time acknowledgment at the beginning of a project is sufficient to avoid blockers on every PR.

Initial People

We believe the following shortlist of long-time contributors are ideal candidates for this initial pilot experiment and for providing feedback to iterate and improve the program in its future. 

...