Policies
Communication
The work happens in public, on GitHub, where everyone involved can follow it. This page says where each kind of message goes, how to reach @mmcky and what to expect.
Where things go
| Topic | Where |
|---|---|
| The lecture you are reviewing | Its review pull request |
| Questions after a review | The follow-up issue (see After your review) |
| Anything else about your edition | A new issue in your edition's repository |
| A house-style rule that seems wrong | The review pull request (see Terms and house style) |
| A mistake in the English lecture | The English repository (see Errors in the English) |
| Onboarding and personal matters | Email to Matt McKay (@mmcky) |
Anything that affects the text of a lecture belongs on GitHub, so that it is recorded where everyone can see it.
The edition repositories are public, so anyone can read what you write there. Use email for personal matters.
Reaching @mmcky
To get attention, mention @mmcky in a comment by typing @mmcky. GitHub then sends a notification. Mention @mmcky on the thread where the topic already is, so that the whole discussion stays in one place.
When your review is complete, approve the pull request and mention @mmcky in the summary. The approval and the mention together signal that the lecture is ready to merge. See Reviewing on GitHub.
Write in English
Write on GitHub in English, so that everyone involved can follow. Examples in your language are fine, and often necessary.
What to expect
We make no promises about response times. These are guidelines only:
- Replies come on the same thread as your message.
- If a thread has been quiet for a while, a reminder is welcome. Mention @mmcky again on that thread.
- If you disagree with a decision, say so on the thread where it was made.
- There is no deadline for a review. See How a review round works.
Public progress
The public translation status page shows progress across the editions.