Note the shorter expiration time for ports bits on /internal/expire-bits

Reported by: gerald Approved by: core (emaste, implicit, documenting existing policy)
3 years ago · 89407529ff
parent 17eef34c77
commit 89407529ff
1 changed files with 1 additions and 1 deletions
--- a/website/content/en/internal/expire-bits.adoc
+++ b/website/content/en/internal/expire-bits.adoc
@ -11,6 +11,6 @@ Over time, FreeBSD committers may find other demands on their time, and decide t

 == Policy

-Committers that have not made a commit in 18 months may be removed from the access file from time to time. Committers that wish to get back their commit bits will have to reapply with the appropriate authority.
+Documentation and source committers that have not made a commit in 18 months may be removed from the access file from time to time. For ports committers this period is 12 months. Committers that wish to get back their commit bits will have to reapply with the appropriate authority.

 If all of a committer's commit bits expire, then the committer's `FreeBSD.org` account may also be suspended at the FreeBSD Core Team's discretion. An account is suspended by disabling login access and any other services (such as CGI scripts or non-trivial mail forwarding configurations) that execute under the committer's account. Simple mail forwarding will continue to work, and an individual may e-mail `core@FreeBSD.org` to update mail forwarding settings. The committer's files may or may not be preserved at the FreeBSD Core Team's discretion. A suspended account will be reactivated if any of a committer's commit bits are restored.