-
Notifications
You must be signed in to change notification settings - Fork 40
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
Correct meeting minutes 2024-02-28 #716
Conversation
tschmidtb51
commented
Apr 3, 2024
- try to unify format
- add questions to unclear points
- improve wording from memory
- try to unify format - add questions to unclear points - improve wording from memory
meeting_minutes/2024/2024-02-28.md
Outdated
- TC should fix in 2.1 or another version. | ||
- For current implementations, a router may be needed. | ||
- For current implementations, a router <!-- Just marking here that this makes no sense to me. Maybe it should refer to an errata? --> may be needed. |
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.
This is a point for discussion - I think errata might be the correct wording instead of "router"
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.
Close captioning for precedence 😁
Yes, having observed Webex close captioning closely, I assume this is a correct hypothesis:
a router
→ errata
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.
LGTM - a tad over engineered maybe, but February is long gone.
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.
Thank you so much for catching those!