-
Notifications
You must be signed in to change notification settings - Fork 138
Add community and RDMkit CLub page #1496
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
Conversation
pages/about/rdmkit_club.md
Outdated
title: RDMkit Club | ||
--- | ||
|
||
RDMkit Club is an informal drop-in session held on the **last Thursday of each month at 10:00 CEST/ 9:00 BST**, where we come together and discuss all topics related to RDMkit including its impact and future directions. |
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.
at 10:00 CEST/ 9:00 BST**
Do we change these when the summertime is over? Use UTC?
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.
Fair point, if the online calculators are correct this will be 8h UTC, but does this solve the problem? Because summer or winter, it will be at 10h / 9h ?
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.
It is my understanding that UTC does not change depending on the time of the year, so that would solve the problem, I believe.
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.
The fact that it does not change, does that not create the problem? Sorry I feel stupid about this :D Because if CET is UTC +1 and CEST UTC +2, than it means with a fixed UTC time, the time of the meeting changes winter vs summer?
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.
The UTC can be very confusing!
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.
The UTC can be very confusing!
Agreed, shall we use "CE(S)T" instead
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.
@bedroesb Thinking about this, I suspect you are right.
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.
I think the 10:00 CEST/ 9:00 BST option is more intuitive as well. Even if we forgot to change it, I think I'd find it easier to convert from BST to GMT than from UTC to whatever time zone we're in! It's what you're used to, I guess.
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.
@martin-nc What do you think of the CE(S)T solution, are is it obvious enough?
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.
I think so. Would you miss out BST/GMT then?
Co-authored-by: Federico Bianchini <72258479+bianchini88@users.noreply.github.com>
Fair enough, now I only need an approval 😄 |
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.
Okay, let's see how that time format goes!
Thanks for the reviews! |
Uh oh!
There was an error while loading. Please reload this page.