-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Glossary #1483
Improve Glossary #1483
Conversation
This commit addresses the false statements mentioned in #1477 (comment).
Please don't merge this yet, I have one more thing to address. |
You could set the PR to Draft if you don't want it reviewed or merged yet. |
I've now addressed one more inaccuracy and this is PR is ready to merge @dsarkar! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change title regarding validity (Gültigkeit).
Co-authored-by: Mike McCready <66998419+MikeMcC399@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We cannot strictly specify "Gültigkeit eines Impfzertifikats", sorry. The validity really depends on the type of the certificate (vaccination certificate, test certificate, and recovery certificate). The article uses the vaccination certificate as an example only. But we need to enhance this article by the different validity periods for the different types. This is already in preparation.
Maybe it's better to call it "Gültigkeit eines COVID-Zertifikats", which would be correct and covers all types.
Okay, thanks for the feedback @GisoSchroederSAP! I'll revert the change for now, but please don't forget to adjust this, especially if every certificate has a different validity. |
This reverts commit 909d4a6.
So, reverted. I can adjust the wording tomorrow (if needed). But tbh, the entry really is all about vaccination certificates, so why can't we leave "Impfzertifikat" there for now and only change it once the entry was made more general? Please think about it again @GisoSchroederSAP. Thank you for your work, have a good night! |
Basically, the intention of the whole article is to explain the proper separation of the "technical" validity from the "effective" validity. |
Yes, but then the title covers all three types but not the entry, so this is (in my opinion) not really helpful for the user. But I'm fine with that, I'll change the title to "Gültigkeit eines COVID-Zertifikats" and I'm sure you'll come up with a more general explanation then. Thanks for your feedback. |
This commit changes the title of a glossary entry.
Title changed, ready for merge (from my POV)! |
|
This commit further improves the glossary entry "Gültigkeit eines COVID-Zertifikats".
Done in a8374a5.
Done in a8374a5 too, but now I see the problem that the second bullet point is a bit out of context?
Also done in a8374a5. |
@GisoSchroederSAP Please take another look if these changes are fine with you. Thanks! |
@Ein-Tim If @GisoSchroederSAP can soon add the information about the other types of certificate that would be perfect. |
Since Giso (not mentioning him here intentionally) said he will take a (well deserved) summer break, I guess we won't here feedback from him in the next few weeks. So maybe @dsarkar, could you take this over and get an approval on the changes? If not, please apply the Thanks everyone, enjoy the evening and sleep well! 😴 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my perspective, all changes are okay to be accepted; the first commented proposal could be even more polished, but I don't insist here.
Thanks for having an eye on our Glossary.
Co-Authored-By: GisoSchroederSAP <69585203+GisoSchroederSAP@users.noreply.github.com>
@Ein-Tim @MikeMcC399 @GisoSchroederSAP Thanks! Merged. |
This PR addresses the false statements mentioned in #1477 (comment).
This is a follow up to PR #1478.