| Table of Contents |
|---|
...
| Info |
|---|
Quick Facts:
|
Contents
| Table of Contents |
|---|
Upcoming Schedule
Schedule. Please adjust as appropriate:
...
Respond to GitHub Requests within one business day.
Requests should automatically ping the
@openedx/tcril-oncallGitHub group.Assign yourself to the issue.
If you can’t resolve the request within a day, that is fine. Just give an “Ack” and a general timeline estimate.
Please note that users must also be added to the CLA check database. The specifics are in the document linked above.
By the end of the sprint, ensure each GitHub Request is either:
closed, or
explicitly reviewed & handed off to the next on-call engineer at the beginning of the following sprint.
Respond to other pings to the
@openedx/tcril-oncallgroup if they happen.Keep an eye on the
#ask-tcrilSlack channel. If tCRIL-oriented questions come up that nobody is responding to, bring them up in daily standup so we don’t forget about them.
...
⁉️ How do I handle requests
...
For common requests, see https://openedx.atlassian.net/wiki/spaces/COMM/pages/3241640370/tCRIL+Engineering+Team#Common-Request-Types
...
?
All our on-call processes are documented here: On-call Playbooks
If new things come up or if processes change, update that document!
If you are swamped during the sprint, delegate to other team members. You don’t need to do all the work yourself!.
🌀 How does the rotation work?
...