+* Obvious, small changes may be made to any repository, subject to the specific rules of each repository.
+* Committers should exercise good judgement and seek review or sanity checks if they have any doubt.
+* Committers are expected to know and understand the rules of the repositories they commit changes to.
+* When a committer does not have direct permission to commit to another repository, the project trusts the committer to use their best judgement, consistent with the following considerations.
+** The change has recieved sufficient review for the nature of the change.
+** The proper validation tools have been used to check the commit.
+** Experts in that repository or that portion of the repository are consulted for non-trivial changes.
+** When portions of a repository require approval or other oversight, such as Mk tree in ports, the committer is defferential those rules.
+** When mistakes happen, accepting the default action is an immediate backout and increased scrutiny for the change.
+** Committers are expected to accept feedback, whether about the process or the changes itself.
+Often times doing something once is OK, but in the future there's better ways to make the change.
+** The larger the change, the more one should seek review and wait for approval of the change.
+* When in doubt, ask.
+
+This policy is to allow flexibility.
+Small changes that have limited impact should be easy to commit without heavy weight proccess.
+Larger changes should not bypass the normal reviews and oversight.