Ballot FORUM-35v2: Allow relative effective dates in ballots #68
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow the Chair or Vice Chair of the Forum or a Working Group to update relative effective dates found within a ballot into concrete dates when publishing a Final Guideline or Final Maintenance Guideline. This allows ballots to contain statements like "Effective [6 months after publication], CAs MUST...", which the Chair would then convert to "Effective Jan 15, 2026, CAs MUST". This allows the ballot writing and discussion process to focus on the length of the necessary transition/implementation period, rather than on the specific effective date, preventing ballots from needing to be re-proposed simply because the discussion period has taken longer than expected and now the effective date is too close.
aarongable
changed the title
aarongable
changed the title
aarongable
changed the title
CBonnell
reviewed
May 21, 2025
aarongable
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow the Chair or Vice Chair of the Forum or a Working Group to update relative effective dates found within a ballot into concrete dates when publishing a Final Guideline or Final Maintenance Guideline.
This allows ballots to contain statements like "Effective [6 months after publication], CAs MUST...", which the Chair would then convert to "Effective Jan 15, 2026, CAs MUST". This allows the ballot writing and discussion process to focus on the length of the necessary transition/implementation period, rather than on the specific effective date, preventing ballots from needing to be re-proposed simply because the discussion period has taken longer than expected and now the effective date is too close.
Proposer: Aaron Gable (ISRG)
Endorsers: Martijn Katerbarg (Sectigo), Ryan Dickson (Google)