-
Notifications
You must be signed in to change notification settings - Fork 29
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.
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
Fixes #6 -- Add details about receiving reports, on-call duty and example initial responses #10
Conversation
…mple initial responses
@@ -4,11 +4,77 @@ | |||
|
|||
## Report handling procedure | |||
|
|||
> Work in progress | |||
This document aims to present the way we handle received reports. This is not a complete guide, or a template we absolutely always follow. Each issue is different and requires individual consideration on case-to-case basis. However, this is a set of guidelines or best practices that guide the way we provide support to the community. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
on a case-to-case basis
Perhaps a set of guidelines and best practices
instead of or
?
What type of tense do we want this document to have? Do we want to pick a tense and try to stick with it? |
|
||
### On-call duty | ||
|
||
In order to achieve a fast response time to received reports, we implemented a week long on-call duty. Every week we assign one member of the Code of Conduct committee 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. Schedule is managed via spreadsheet. If a member won't be available on given week, they should exchange their week with another member. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we implement
- present tense.
@phalt thanks for the review! I corrected that, I think :) Happy to stick to any tense, I'll let you pick one :) |
Let's get a vote from others but I think present tense works well in guidelines. @cogat @EmilyK @jefftriplett @bmispelon - thoughts? |
Present is good! :) Protip: you can also mention @django/coc-committee :) |
This should close #6 :)