forked from Baystation12/Baystation12
-
Notifications
You must be signed in to change notification settings - Fork 28
Developer Policies
babydoll edited this page Sep 4, 2019
·
3 revisions
- Developers shall not approve or merge their own pull requests.*
- Updates to the credits (header.html), changelog and Code of Conduct may be merged by the author after 24 hours have elapsed since an approving review by another developer.
- Developers shall not merge a pull request that they alone have approved until 24 hours have elapsed since the approving review.*
*These rules may be overruled in specific cases, such as a critical bug fix.
- After conference with the team, any Developer may mark any pull request Last Chance, and then close the marked pull request after the stipulated time (usually 3-5 days) if no Developer steps forward to support it.
- Provided the author is notified at the time of marking, Developers may close any pull request correctly marked Awaiting Author or Merge Conflicts after 10 days of author inactivity.
- Any Developer can re-open these pull requests once the author has time to attend to them.
Documentation regarding setting up and using Git.
Making heads or tails of specific GitHub pages, for the uninitiated.
Documentation regarding tools external to DM and Git.
Standards and guidelines regarding commenting, contributor conduct and coding standards.