Create working standards/expectations for collaborative GitHub projects?

[NeuroShepherd]

Goal: minimize distractions from GitHub, and make collaboration on GitHub more effective.

Determine what appropriate timelines/expectations should be for e.g.

• Reviewing and merging pull requests
• Tagging people in issues
• Assigning issues
• Prioritization of issues/PRs
• ...?

My general approach:

• Self-enforce the use of Issues and Pull Requests.
• No issue or pull request is urgent unless someone says specifically says it is. In which case, this should also be communicated via Matrix.
• Try to review assigned pull requests within a few days, max 1 week. If they're not reviewed in that time, then it's okay to just continue working or merge if desired.
• Can always assign someone as a reviewer of a PR or assign them to an issue. They can unassign, recommend someone else, and/or state when they might be able to get to it.
• Disabled emails from new comments, assigned issues/PRs, etc. I only check these within the GitHub website. Lifesaver 🌟
• ...

This is a large topic, and would probably be a more productive discussion via a Zoom or in-person meeting. @MalikaIhle @nicebread @ree-gupta @SvonGrebmer