Adjust the naming to refer to end date rather than expire for peers #384
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
jonasbardino
added
documentation
jonasbardino
force-pushed
the
adjust/peers-to-say-end-date-rather-than-expire
branch
from
d3408c6 to
9ea28b0
Compare
Contributor
Author
|
A quick preview of one of the tabs is included here |
Contributor
Author
|
Lint errors are from old unrelated code and should be fixed by PR #386 . |
…Hopefully that will reduce the confusion about the difference between the date that the local contact puts as hard end date and the individual account access expire value. The latter needs at least annual renewal and the users can handle that themselves until end date.
copyright header. Tested in deployment. Minor style fixes from autopep8.
jonasbardino
force-pushed
the
adjust/peers-to-say-end-date-rather-than-expire
branch
from
7367df4 to
7f9538f
Compare
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.
Adjust the naming to refer to end date rather than expire for peers. Hopefully that will reduce the confusion about the difference between the date that the local contact puts as hard end date and the individual account access expire value. The latter needs at least annual renewal and the users can handle that themselves until end date.
It is somewhat related to issue #130.