Omu Maintainer and GitHub Policy: Difference between revisions

Latest revision as of 12:05, 30 January 2026

Maintenance and Repo

In line with 1a, Maintainers are to be polite and respectful when performing duties.
All push, commit, PR, and other names of files are expected to be appropriately and helpfully named.
PRs should be fully documented. Maintainers can close PRs that are not properly documented or appropriately named.
Maintainers are given admin permissions, and allowed to perform admin duties, but are held to the same standards as admins.
1. Ideally Maintainers will not do actions as admins unless it's needed
2. Maintainers can do events with an admin's assistance for the purpose of testing things.
Maintainers should not close PR’s without sufficient reason.
Maintainers should not self-merge PR’s without sufficient reason.

@@ Line 1: / Line 1: @@
--THIS DOCUMENT IS CURRENTLY SUPERSEDED BY SECTION THREE OF DOCUMENT ONE-
+Maintenance and Repo
+# In line with 1a, Maintainers are to be polite and respectful when performing duties.
+# All push, commit, PR, and other names of files are expected to be appropriately and helpfully named.
+# PRs should be fully documented. Maintainers can close PRs that are not properly documented or appropriately named.
+# Maintainers are given admin permissions, and allowed to perform admin duties, but are held to the same standards as admins.
+## Ideally Maintainers will not do actions as admins unless it's needed
+## Maintainers can do events with an admin's assistance for the purpose of testing things.
+# Maintainers should not close PR’s without sufficient reason.
+# Maintainers should not self-merge PR’s without sufficient reason.