update tpa-rfc-60 and mark proposed (tpo/tpa/team#41473) (c3d60ac7) · Commits · The Tor Project / TPA / Wiki Replica

policy.md

+2 −2

Original line number	Diff line number	Diff line
		@@ -21,12 +21,12 @@ and add it to the above list.
		* [TPA-RFC-38: Setting Up a Wiki Service](policy/tpa-rfc-38-new-wiki-service)
		* [TPA-RFC-45: Mail architecture](policy/tpa-rfc-45-mail-architecture)
		* [TPA-RFC-47: Email account retirement](policy/tpa-rfc-47-email-account-retirement)
		* [TPA-RFC-60: GitLab 2-factor authentication enforcement](policy/tpa-rfc-60-gitlab-2fa-enforcement)
		* [TPA-RFC-61: 2024 roadmap](policy/tpa-rfc-61-roadmap-2024)

		## Proposed

		No policy is currently `proposed`.
		<!-- No policy is currently `proposed`. -->
		* [TPA-RFC-60: GitLab 2-factor authentication enforcement](policy/tpa-rfc-60-gitlab-2fa-enforcement)

		## Standard

+7 −2

Original line number	Diff line number	Diff line
		@@ -48,17 +48,22 @@ The vast majority of affects users already have 2-factor authentication
		enabled. This will affect those that haven't yet set it up, and accounts that
		may be created and granted privileges in the future.

		An automated listing of `tpo` sub-group and sub-project members not being
		available, a manual count of users without 2fa enabled was done for all direct
		subgroups of `tpo`: 17 accounts were found with 2fa disabled.

		# Approval

		The GitLab administrators must approve this change.

		# Deadline

		TBD
		Enforcement is to be enabled on Monday, February 5th, followed by a 48 hour
		grace period.

		# Status

		This proposal is currently in the `draft` state.
		This proposal is currently in the `proposed` state.

		# References