Versions Compared

Key

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

...

We take requests via issues to the openedx/tcril-engineering repository. Your requests will be triaged and initially responded to within one business day by the engineer(s) in the @openedx/tcril-oncall GitHub team during standard Monday-Friday US-Eastern business their own working hours. They may be delegated to other engineers. tCRIL does not generally provide support during US-Eastern evenings or weekends.

...

So, you just started at 2U OCM? Congrats! 🎉 Either 2U IT or your manager should file a GitHub Request - Onboarding issue on your behalf. (Please don’t file file the request yourself--we need someone who is already in the openedx organization to vouch that you are indeed a new 2U OCM employee).

2U IT and managers: For new hires, file a GitHub Request - Onboarding issue with us. We can’t guarantee that we’ll often do not get to requests the request same- day they are filed, so consider filing please file the request as far in advance of when the access is neededthe employee’s start date as possible. Please provide a helpful title, but make sure it remains prefixed with [GH Request] so that our automation picks it up. Thanks!

Offboarding, access changes, and other requests

...

File an issue using the tCRIL Engineering board above, selecting the most appropriate template. Please provide reasoning for your change and as much supplemental detail as possible. Please provide a helpful title, but make sure it remains prefixed with [GH Request] so that our automation picks it up.

Transferring repositories into the openedx organization

If you have read “What code should be in the openedx organization?" and believe that a repository of yours should be moved into the openedx organization, then submit a GitHub Request - Generic issue on the board linked above, detailing what repository should be transferred in and why.

...

  • integrate nicely with pull requests and other GitHub workflows,

  • let us locate issues closer to the code that they pertain to,

  • are automatable via GitHub Actions,

  • use the same authn/z scheme that GitHub repository contribution doesGitHub accounts that all Open edX engineers already have,

  • have a simpler access control scheme that is tied to repository access (which we already manage and intentionally default to “publicly-visible”),

  • are included in our non-profit GitHub Teams plan,

  • work across different GitHub organizations, with some limitations,

  • have a fast UI, and

  • have already been adopted by others in the Open edX community, such as the Build-Test-Release Working Group.

...