| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
In-Progress; feel free to provide review!Under Review! Please make your thoughts known by YYYY-MM-DD |
This doc is a starting point for conversation. It takes questions that were posted on the 9/14 meeting notes and proposes a solution for each, based on research done on Open Source best practices and years of experience with the Open edX project.
...
Maintainers should have accounts on Discourse and receive some subset of notifications.
This must include direct mentions on posts and replies to posts made. Note that this is the default notification setting on Discourse:
It is recommended that maintainers include notifications on first posts in categories of interest, done by navigating to the topic, clicking the “bell” icon next to the New Topic button, and selecting “Watching First Post”.
Maintainers should check notifications weekly.
To avoid feeling overwhelmed, consider having notifications skip your inbox and go directly into a folder. Check these once a week on a regular cadence - consider putting 15 minutes on your calendar once or twice a week.
Note: when posting a new discussion topic, it is recommended you check at least daily - discussions around things like Deprecations and new Architecture will proceed better with involved discussion.
Maintainers do not need to jump into every “help me” issue, but should answer pointed/strategic questions such as ones related to timelines, deprecations, and roadmaps.
...
A new PR should be triaged within a week. During triage, a decision must be made as to whether or not the project is interested the PR, and it mustbe closed within this period if the project does not outright want it. Remember: Learn to say no.
Elaborating on the above: Your job is to look at the PR when it comes in, and make some kind of decision about it. Say what you know as soon as you know it, even if it’s only partial (for example, “This looks like it could be interesting, but we are busy right now. We expect we’ll be able to get back to you about it in two weeks”). Sometimes something that initially looks good may turn out to be something you don’t want; it is OK to initially say “this is interesting to us” just to close the PR later - the PR may end up being wrong for the project, and you may only realize that on deeper review. Remember that partial answers and some amount of uncertainty is always OK. Remember that we are people talking to people, not corporations making promises.
Once triaged, the maintainer team must respond within a week to an author’s updates (new commits/comments/questions that require attention - such as requests for re-review).
...