Change 6 months extension requirement to be an expectation #283
Conversation
This file contains 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
plehegar
added
the
substantive
|
There still should be a definition of what is short-term and what is long-term. You could set an expectation of six months, but keep a hard limit of nine months or a year, for example. |
Having a hard limit of one year seems appropriate to me. |
|
LGTM |
deniak
force-pushed
the
charter-extension-6-months
branch
from
7a4a21a to
26371b3
Compare
|
Unless I hear otherwise, I'll merge this PR at the end of January. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This relax the requirements that a Group cannot be extended for more then 6 months. It would be an expectation instead.