We are the engineering team of the Center for Reimagining Learning (aka tCRIL, pronounced “tea-krill”). tCRIL is the temporary name for a lasting non-profit which stewards the codebase and community of the Open edX Project.
Seeing if your issue is represented on the platform roadmap and commenting your support on the issue.
Please keep in mind: community companies and working groups are busy with their own initiatives. Still, they might be excited to help you get started with developing a solution to your problem!
One Broadway 14th Floor Cambridge, MA 02142
tCRIL Request Process
The New Issue portal, where you can submit tCRIL requests
We take requests viathe New Issue portal on the openedx/tcril-engineering repository. tCRIL’s rotating “on-call” engineer will triage your issue within one business day during their own working hours. They will try to give you a time estimate for completion. They may do the work themselves or delegate it to someone else. Note that tCRIL does not generally provide support on weekends, holidays, the early morning, or the evening (~US-Eastern timezone).
Please fill out all request fields, including a helpful title. Make sure the title remains prefixed with [GH Request] so that our automation picks it up and routes it to the on-call engineer. So your ticket’s title would look something like, [GH Request] Onboard New User Bob Jones
Common Request Types
Onboarding 2U OCM Employees
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 often do not get to requests the day they are filed, so please file the request as far in advance of the 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!
tCRIL On-Call:Ensure that the request is coming from a known 2U OCM manager or IT staff member. If so, invite the new hire to the openedx organization. Until further notice, as part of the invitation, add all new hires to the @openedx/push-pull-all group as well as any other sensible groups as requested. Close the issue once the invitation is sent.
a repository from another GitHub organization should be moved intoopenedx, or
a repository from openedx should be moved out to another GitHub organization,
then submit a GitHub Request - Generic issue on the board linked above, detailing what you think should be transferred in and why. (Not sure? We are working on an OEP to formalize which repositories should be in the openedx organization and what the implications of being in said organization are. In the meantime, though, tCRIL is just using our best judgement. If you’re not sure, open a request anyway! Thanks for your patience here.)
If you want to make a new repository in the openedx organization, then first create it in your personal/company organization, and then follow the transfer request process above.
(tCRIL On-Call:Bring transfer requests to the team for discussion.)
Offboarding & access changes, and other requests
Do you need us to:
add or remove GitHub permissions from a user?
change the configuration of a GitHub application?
remove someone from the openedx GitHub organization?
help you out with anything else?
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. In the case of adding or removing permissions, please have your manager ask on your behalf.
tCRIL On-Call:Use your best judgement. Ask in Slack or at standup if you’re unsure. Record any action you take and your reasoning in the issue comments before closing it.