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.

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

Merged
merged 2 commits into from
May 26, 2016

Conversation

olasitarska
Copy link
Contributor

This should close #6 :)

@@ -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.
Copy link
Member

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?

@phalt
Copy link
Member

phalt commented May 24, 2016

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we implement - present tense.

@olasitarska
Copy link
Contributor Author

@phalt thanks for the review! I corrected that, I think :)

Happy to stick to any tense, I'll let you pick one :)

@phalt
Copy link
Member

phalt commented May 26, 2016

Let's get a vote from others but I think present tense works well in guidelines. @cogat @EmilyK @jefftriplett @bmispelon - thoughts?

@olasitarska
Copy link
Contributor Author

Present is good! :)

Protip: you can also mention @django/coc-committee :)

@olasitarska olasitarska merged commit 0a7a9d6 into master May 26, 2016
@phalt phalt deleted the 6-receiving-reports branch July 19, 2016 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reports.md: describe how we handle received reports
2 participants