Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Specify how to notify people who will be on duty #31

Closed
wants to merge 1 commit into from
Closed

Specify how to notify people who will be on duty #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 2 additions & 3 deletions reports.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,9 +36,8 @@ In order to achieve a fast response time to received reports, we implement a
week long on-call duty that is rotated between members of the Code of Conduct
Committee. Every week we assign one member to be the primary person on duty,
and another member to be a secondary supporter. On-call duty ends and finishes
every Monday at noon UTC, when a reminder is sent to conduct@djangoproject.com
with information who is the next primary and secondary member on-duty following
week. The schedule is managed via a [spreadsheet]. If a member won't be
every Monday at noon UTC; the outgoing people-on-duty should notify the incoming
ones on Slack. The schedule is managed via a [spreadsheet]. If a member won't be
available on given week, they should exchange their week with another member.

![spreadsheet](https://docs.google.com/a/sitarska.com/uc?authuser=0&id=0B_sMcBckSgWqX1p5cm50UmQ1VVk)
Expand Down