Skip to content

Latest commit

 

History

History
50 lines (35 loc) · 1.67 KB

Ettiquette.md

File metadata and controls

50 lines (35 loc) · 1.67 KB
Raw

Collaborative Etiquette

Rosemary Hartman 12/11/2019

Some basic ground rules

Use issues to bring up things we need to work on

  • Don’t be afraid! You don’t need to submit code to contribute to the success of a project! Don’t hold back on submitting issues, commenting on discussions and helping people out.

For collaborators

  • Work in branches then send a PR any time you are working on files that aren’t “yours”. Just because you have full commit access doesn’t mean you shouldn’t use pull requests. PRs are a great way to solicit feedback from co-collaborators and to give them a nice overview of what’s going on.

  • Review outstanding PRs. Feel free to merge any you see fit, and leave comments on anything that needs revisions. If you don’t feel comfortable merging them, at least comment with a :+1: to signal your co-collaborators that it’s passed your review.

  • Push directly for micro-fixes only. Only push to master for trivial updates that would be too noisy to notify your teammates of, such as typo fixes.

  • You can self-merge your PRs. Sometimes the rest of the team may be inactive, in which case, use your best judgement to self-merge PRs.

  • Keep history clean. No --force pushing on branches that aren’t yours.

  • Communicate. You can use GitHub issues to communicate with your co-collaborators. Feel free to @mention them in issues.

  • Be nice. The collaborator team is nice, so we are all nice.


Acknowledgements

This is an extension to the Open Open Source manifesto.