[cloudkitty] Resuming CloudKitty IRC meetings
Hello, We are resuming IRC meetings for the CloudKitty project using the existing calendar schedule. The first meeting will be on Monday August 24 at 1400 UTC in #cloudkitty on freenode, then every two weeks. Everyone is welcome: contributors, users, and anyone who would like to contribute or use CloudKitty but doesn't know how to get started. The agenda is available on Etherpad [1]. The meeting description [2] was stating that meetings were on the first and third Monday of the month, but the calendar schedule was using odd weeks. I've submitted a change [3] to synchronise the description: let's meet on odd weeks instead of using a month-based schedule. Thanks in advance to all of you helping to keep the project going. Pierre Riteau (priteau) [1] https://etherpad.opendev.org/p/cloudkitty-meeting-topics [2] http://eavesdrop.openstack.org/#CloudKitty_Team_Meeting [3] https://review.opendev.org/#/c/747256/
On 8/20/20 12:09 PM, Pierre Riteau wrote:
Hello,
We are resuming IRC meetings for the CloudKitty project using the existing calendar schedule. The first meeting will be on Monday August 24 at 1400 UTC in #cloudkitty on freenode, then every two weeks.
Everyone is welcome: contributors, users, and anyone who would like to contribute or use CloudKitty but doesn't know how to get started. The agenda is available on Etherpad [1].
The meeting description [2] was stating that meetings were on the first and third Monday of the month, but the calendar schedule was using odd weeks. I've submitted a change [3] to synchronise the description: let's meet on odd weeks instead of using a month-based schedule.
With what you said above, this is actually taking place on even weeks now. Can you clarify - is it a one-off that you will be holding this on the 4th Monday next week? Or do you actually intend to switch these to even weeks (in which case that patch is incorrect)?
Thanks in advance to all of you helping to keep the project going.
Pierre Riteau (priteau)
[1] https://etherpad.opendev.org/p/cloudkitty-meeting-topics [2] http://eavesdrop.openstack.org/#CloudKitty_Team_Meeting [3] https://review.opendev.org/#/c/747256/
On Thu, 20 Aug 2020 at 19:27, Sean McGinnis <sean.mcginnis@gmx.com> wrote:
On 8/20/20 12:09 PM, Pierre Riteau wrote:
Hello,
We are resuming IRC meetings for the CloudKitty project using the existing calendar schedule. The first meeting will be on Monday August 24 at 1400 UTC in #cloudkitty on freenode, then every two weeks.
Everyone is welcome: contributors, users, and anyone who would like to contribute or use CloudKitty but doesn't know how to get started. The agenda is available on Etherpad [1].
The meeting description [2] was stating that meetings were on the first and third Monday of the month, but the calendar schedule was using odd weeks. I've submitted a change [3] to synchronise the description: let's meet on odd weeks instead of using a month-based schedule.
With what you said above, this is actually taking place on even weeks now.
Unless I am mistaken, a schedule based on the Nth day of month is not fixed to even or odd weeks. For example, in June the first and third Monday were in weeks 23 and 25 (odd), but since July they take place in even weeks. What I am proposing is we disregard the existing description and go by the frequency defined in the yaml file, which is biweekly-odd. It means that people who have already imported the calendar invite will have the correct date (although not the right description). And we'll always have two weeks between each meeting, instead of sometimes three.
Can you clarify - is it a one-off that you will be holding this on the 4th Monday next week? Or do you actually intend to switch these to even weeks (in which case that patch is incorrect)?
Thanks in advance to all of you helping to keep the project going.
Pierre Riteau (priteau)
[1] https://etherpad.opendev.org/p/cloudkitty-meeting-topics [2] http://eavesdrop.openstack.org/#CloudKitty_Team_Meeting [3] https://review.opendev.org/#/c/747256/
On 2020-08-20 19:54:16 +0200 (+0200), Pierre Riteau wrote: [...]
Unless I am mistaken, a schedule based on the Nth day of month is not fixed to even or odd weeks. For example, in June the first and third Monday were in weeks 23 and 25 (odd), but since July they take place in even weeks. [...]
Correct, this is documented in the README.rst for the yaml2ical library, which irc-meetings uses to render this metadata into scheduling: https://opendev.org/opendev/yaml2ical#user-content-frequencies "biweekly-odd Occurs on odd weeks (ISOweek % 2 == 1)" "Odd/Even and week numbers are based on the ISO week number. ISO weeks can be checked with %V in GNU date(1)" I think some people have assumed it's even/odd week numbers in a month rather than even/odd week numbers counting from the epoch. Technically we have frequencies like "first-tuesday" and "third-tuesday" to address specific week numbers in a month rather than truly alternating weeks. -- Jeremy Stanley
"biweekly-odd Occurs on odd weeks (ISOweek % 2 == 1)"
"Odd/Even and week numbers are based on the ISO week number. ISO weeks can be checked with %V in GNU date(1)"
I think some people have assumed it's even/odd week numbers in a month rather than even/odd week numbers counting from the epoch. Technically we have frequencies like "first-tuesday" and "third-tuesday" to address specific week numbers in a month rather than truly alternating weeks. Based on the existing description, that appears to be the intent. So it had been the first and third weeks of the month, so therefore the odd weeks. But then we at least have a mismatch between phrasing used and what yaml2ical generates, so the description does need to be updated.
On 2020-08-20 13:37:53 -0500 (-0500), Sean McGinnis wrote:
"biweekly-odd Occurs on odd weeks (ISOweek % 2 == 1)"
"Odd/Even and week numbers are based on the ISO week number. ISO weeks can be checked with %V in GNU date(1)"
I think some people have assumed it's even/odd week numbers in a month rather than even/odd week numbers counting from the epoch. Technically we have frequencies like "first-tuesday" and "third-tuesday" to address specific week numbers in a month rather than truly alternating weeks. Based on the existing description, that appears to be the intent. So it had been the first and third weeks of the month, so therefore the odd weeks. But then we at least have a mismatch between phrasing used and what yaml2ical generates, so the description does need to be updated.
And even I'm easily confused by this, as evidenced by the fact that above I confused epoch weeks with ISO annual week counts. As the README.rst suggests, if you have a "53-week" year then you get ISO odd weeks back to back between the end of that year and the start of the next, or a pair of ISO even weeks which are three weeks apart instead of two. -- Jeremy Stanley
Thanks for clearing up the confusion, I had not considered this alternative interpretation of even and odds weeks. And thanks for sharing the tidbit about 53-week years. Should I mention there are months with a fifth Monday as well? ;-) So, I would like to clarify that I am proposing meetings on odd ISO week numbers. This is an initial schedule, which we can adapt based on project activity. On Thu, 20 Aug 2020 at 21:34, Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2020-08-20 13:37:53 -0500 (-0500), Sean McGinnis wrote:
"biweekly-odd Occurs on odd weeks (ISOweek % 2 == 1)"
"Odd/Even and week numbers are based on the ISO week number. ISO weeks can be checked with %V in GNU date(1)"
I think some people have assumed it's even/odd week numbers in a month rather than even/odd week numbers counting from the epoch. Technically we have frequencies like "first-tuesday" and "third-tuesday" to address specific week numbers in a month rather than truly alternating weeks. Based on the existing description, that appears to be the intent. So it had been the first and third weeks of the month, so therefore the odd weeks. But then we at least have a mismatch between phrasing used and what yaml2ical generates, so the description does need to be updated.
And even I'm easily confused by this, as evidenced by the fact that above I confused epoch weeks with ISO annual week counts. As the README.rst suggests, if you have a "53-week" year then you get ISO odd weeks back to back between the end of that year and the start of the next, or a pair of ISO even weeks which are three weeks apart instead of two. -- Jeremy Stanley
participants (3)
-
Jeremy Stanley
-
Pierre Riteau
-
Sean McGinnis