README: Document the alternate-week meeting times #719
Conversation
This file contains 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
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]: > summarizing the discussion, how about we just alternative the time like > Jonathan discussed? > > I believe that's the only fair thing to do and it's reassuring to hear from > people like Phil who would be able to make the time along with others. > > I'm fine with the current time (1000AEST/1500PST/0000CET) and then > 0400AEST/0900PST/1800CET Folks with a POSIX ‘date’ command can find the week number with [2]: $ date +%V There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway. I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). [1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 08:37:55 -0700 Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com> [2]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html Signed-off-by: W. Trevor King <wking@tremily.us>
|
Please wait until discussions are finished before making changes to any schedule. |
|
What denotes the discussion as "finished"? This seems like a hasty closure.
+1, I think the conversation today showed there are plenty of interested participants outside PST. |
|
On Thu, Mar 09, 2017 at 09:41:02AM -0800, Jonathan Boulle wrote:
What denotes the discussion as "finished"? This seems like a hasty
closure.
There seemed to be general agreement on the split (if not the times)
in the list thread, so I figured it was time to put a hashed proposal
forward to collect more formal consensus. But I'm happy to continue
to update this PR to track whatever the consensus seems to be if the
thread continues to evolve.
|
|
There were still replies coming in and much of the discussion happened over the evening where many in the US timezone have not responded or voiced their comments. |
sameo
reviewed
Mar 9, 2017
| The contributors and maintainers of all OCI projects have a weekly meeting Wednesdays at 2:00 PM (USA Pacific). | ||
| The contributors and maintainers of all OCI projects have a weekly meeting on Wednesdays at: | ||
|
|
||
| * 9:00 AM (USA Pacific), during [even weeks][iso-week]. |
There was a problem hiding this comment.
8:00 AM PST, i.e. 5:00PM CET would work better for several of us.
There was a problem hiding this comment.
thanks for chiming in, cross-reference: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ
wking
added a commit
to wking/opencontainer-runtime-spec
that referenced
this pull request
Mar 9, 2017
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]: > summarizing the discussion, how about we just alternative the time like > Jonathan discussed? > > I believe that's the only fair thing to do and it's reassuring to hear from > people like Phil who would be able to make the time along with others. > > I'm fine with the current time (1000AEST/1500PST/0000CET) and then > 0400AEST/0900PST/1800CET The 8am Pacific time ended up working out better than 9am for Jonathan and Samuel [2,3], so I've used that instead of 9am. Folks with a POSIX ‘date’ command can find the week number with [4]: $ date +%V There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway. I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). [1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 08:37:55 -0700 Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com> [2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 18:33:34 +0100 Message-ID: <CAPWU_0rByhFp=jQQ6cvagHJuYmeTvN7T1zAW+oZR3=F1W8b_rw@mail.gmail.com> [3]: opencontainers#719 (review) [4]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html Signed-off-by: W. Trevor King <wking@tremily.us>
|
On Thu, Mar 09, 2017 at 10:42:09AM -0800, Samuel Ortiz wrote:
+* 9:00 AM (USA Pacific), during [even weeks][iso-week].
8:00 AM PST, i.e. 5:00PM CET would work better for several of us.
|
wking
added a commit
to wking/opencontainer-runtime-spec
that referenced
this pull request
Mar 13, 2017
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]: > summarizing the discussion, how about we just alternative the time like > Jonathan discussed? > > I believe that's the only fair thing to do and it's reassuring to hear from > people like Phil who would be able to make the time along with others. > > I'm fine with the current time (1000AEST/1500PST/0000CET) and then > 0400AEST/0900PST/1800CET The 8am Pacific time ended up working out better than 9am for Jonathan and Samuel [2,3], so I've used that instead of 9am. The 8am slot was confirmed as the most popular slot in a Doodle poll [4], with the following folks approving that slot: * David Lyle * George Lestaris * Jonathan Boulle * Julz * Michael Crosby * Mike Brown * Mrunal Patel * Phil Estes * Rob Dolin * Samuel Ortiz * Stephen Day * Stephen Walli * Vincent Batts * W. Trevor King Removing those folks, the second most popular slot is 5pm Pacific, with the following folks approving that slot: * Aleksa Sarai * Keyang Xie * Lei Jitang * Ma Shimiao * Qiang Huang Stephen and Mrunal approved both slots, and since they frequently anchor the runtime and image conversations respectively, there should be sufficient continuity between the two meetings. The only person voting in the Doodle poll who didn't approve either slot is Tianon. Folks with a POSIX ‘date’ command can find the week number with [5]: $ date +%V There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway. I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). [1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 08:37:55 -0700 Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com> [2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 18:33:34 +0100 Message-ID: <CAPWU_0rByhFp=jQQ6cvagHJuYmeTvN7T1zAW+oZR3=F1W8b_rw@mail.gmail.com> [3]: opencontainers#719 (review) [4]: http://doodle.com/poll/zu664785gb59pwkg [5]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html Signed-off-by: W. Trevor King <wking@tremily.us>
wking
added a commit
to wking/opencontainer-runtime-spec
that referenced
this pull request
Mar 23, 2017
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]: > summarizing the discussion, how about we just alternative the time like > Jonathan discussed? > > I believe that's the only fair thing to do and it's reassuring to hear from > people like Phil who would be able to make the time along with others. > > I'm fine with the current time (1000AEST/1500PST/0000CET) and then > 0400AEST/0900PST/1800CET The 8am Pacific time ended up working out better than 9am for Jonathan and Samuel [2,3], so I've used that instead of 9am. The 8am slot was confirmed as the most popular slot in a Doodle poll [4], with the following folks approving that slot: * David Lyle * George Lestaris * Jonathan Boulle * Julz * Michael Crosby * Mike Brown * Mrunal Patel * Phil Estes * Rob Dolin * Samuel Ortiz * Stephen Day * Stephen Walli * Vincent Batts * W. Trevor King Removing those folks, the second most popular slot is 5pm Pacific, with the following folks approving that slot: * Aleksa Sarai * Keyang Xie * Lei Jitang * Ma Shimiao * Qiang Huang Stephen and Mrunal approved both slots, and since they frequently anchor the runtime and image conversations respectively, there should be sufficient continuity between the two meetings. The only person voting in the Doodle poll who didn't approve either slot is Tianon. Folks with a POSIX ‘date’ command can find the week number with [5]: $ date +%V There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway. The 8am Pacific meeting gets the odd slot because it's Europe-friendly and lots of folks will be in Europe on 2017-03-29 for KubeCon [6]. I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). Future bumps to meeting.ics should bump LAST-MODIFIED [7] or DTSTAMP [8] for any altered components. We can't use DTSTAMP in the VEVENT because VEVENTs require DTSTAMP [9]. The timezone entry is based on the America/New_York example from [10]. Figuring out a single RRULE to cover both meeting times was beyond my abilities, and while RFC 2445 allowed multiple RRULEs in a single VEVENT [11,12], RFC 5545 does not [13]. Something like: RRULE:FREQ=YEARLY;BYDAY=WE;BYHOUR=8,17;BYSETPOS=1,4,5,8,9,... should be legal (at least for 2017), but Google Calendar [14] doesn't seem to respect BYHOUR expansion, and ICAL.js [15] doesn't seem to respect the BYSETPOS limit, so I gave it up and went with two events. The ICS was validated with [16]. The CRLF line endings are intentional [17], and the .gitattributes entry ensures we keep them. [1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 08:37:55 -0700 Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com> [2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 18:33:34 +0100 Message-ID: <CAPWU_0rByhFp=jQQ6cvagHJuYmeTvN7T1zAW+oZR3=F1W8b_rw@mail.gmail.com> [3]: opencontainers#719 (review) [4]: http://doodle.com/poll/zu664785gb59pwkg [5]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html [6]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2017/opencontainers.2017-03-22-21.00.log.html [7]: https://tools.ietf.org/html/rfc5545#section-3.8.7.3 [8]: https://tools.ietf.org/html/rfc5545#section-3.8.7.2 [9]: https://tools.ietf.org/html/rfc5545#section-3.6.1 [10]: https://tools.ietf.org/html/rfc5545#page-69 [11]: https://tools.ietf.org/html/rfc2445#section-4.6.1 [12]: https://tools.ietf.org/html/rfc2445#section-4.8.5.4 [13]: https://tools.ietf.org/html/rfc5545#appendix-A.1 [14]: https://calendar.google.com/ [15]: http://mozilla-comm.github.io/ical.js/ [16]: https://icalendar.org/validator.html [17]: https://tools.ietf.org/html/rfc5545#section-3.1 Signed-off-by: W. Trevor King <wking@tremily.us>
|
I've pushed afbe47b → 8f99038 swapping the odd/even order to get next
week's meeting at 8am Pacific to be Europe-friendly for KubeCon [1].
I think we should re-open this PR at some point so GitHub will notice
the branch changes; until then, I guess folks can look at my branch
[2].
I've also added a meeting.ics file [3], which folks can import into
their calendar app to see how it plays. There are two events there,
because I was unable to find the right RRULE invocation to cover both
times in one event, and RFC 5545 does not allow multiple RRULEs in one
VEVENT [4] (maybe @tianon can figure out some RRULE magic?).
[1]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2017/opencontainers.2017-03-22-21.00.log.html
[2]: https://github.com/wking/opencontainer-runtime-spec/tree/alternating-meetings
[3]: https://raw.githubusercontent.com/wking/opencontainer-runtime-spec/alternating-meetings/meeting.ics
[4]: https://tools.ietf.org/html/rfc5545#appendix-A.1
|
wking
added a commit
to wking/opencontainer-runtime-spec
that referenced
this pull request
Mar 23, 2017
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]: > summarizing the discussion, how about we just alternative the time like > Jonathan discussed? > > I believe that's the only fair thing to do and it's reassuring to hear from > people like Phil who would be able to make the time along with others. > > I'm fine with the current time (1000AEST/1500PST/0000CET) and then > 0400AEST/0900PST/1800CET The 8am Pacific time ended up working out better than 9am for Jonathan and Samuel [2,3], so I've used that instead of 9am. The 8am slot was confirmed as the most popular slot in a Doodle poll [4], with the following folks approving that slot: * David Lyle * George Lestaris * Jonathan Boulle * Julz * Michael Crosby * Mike Brown * Mrunal Patel * Phil Estes * Rob Dolin * Samuel Ortiz * Stephen Day * Stephen Walli * Vincent Batts * W. Trevor King Removing those folks, the second most popular slot is 5pm Pacific, with the following folks approving that slot: * Aleksa Sarai * Keyang Xie * Lei Jitang * Ma Shimiao * Qiang Huang Stephen and Mrunal approved both slots, and since they frequently anchor the runtime and image conversations respectively, there should be sufficient continuity between the two meetings. The only person voting in the Doodle poll who didn't approve either slot is Tianon. Folks with a POSIX ‘date’ command can find the week number with [5]: $ date +%V There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway. The 8am Pacific meeting gets the odd slot because it's Europe-friendly and lots of folks will be in Europe on 2017-03-29 for KubeCon [6]. I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). Future bumps to meeting.ics should bump LAST-MODIFIED [7] or DTSTAMP [8] for any altered components. We can't use DTSTAMP in the VEVENT because VEVENTs require DTSTAMP [9]. The timezone entry is based on the America/New_York example from [10]. Figuring out a single RRULE to cover both meeting times was beyond my abilities, and while RFC 2445 allowed multiple RRULEs in a single VEVENT [11,12], RFC 5545 does not [13]. Something like: RRULE:FREQ=YEARLY;BYDAY=WE;BYHOUR=8,17;BYSETPOS=1,4,5,8,9,... should be legal (at least for 2017), but Google Calendar [14] doesn't seem to respect BYHOUR expansion, and ICAL.js [15] doesn't seem to respect the BYSETPOS limit, so I gave it up and went with two events. To stick strictly to the ISO weeks we could use: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=13,15,17,19,21,23,25,27,29,31,33,35, 37,39,41,43,45,47,49,51 and: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=14,16,18,20,22,24,26,28,30,32,34,36, 38,40,42,44,46,48,50,52 but that's tedious to type, and folks probably don't care all that much about ISO weeks. I've gone with WEEKLY and INTERVAL=2 to give us something that might survive the end of the year. The ICS was validated with [16]. The CRLF line endings are intentional [17], and the .gitattributes entry ensures we keep them. [1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 08:37:55 -0700 Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com> [2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 18:33:34 +0100 Message-ID: <CAPWU_0rByhFp=jQQ6cvagHJuYmeTvN7T1zAW+oZR3=F1W8b_rw@mail.gmail.com> [3]: opencontainers#719 (review) [4]: http://doodle.com/poll/zu664785gb59pwkg [5]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html [6]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2017/opencontainers.2017-03-22-21.00.log.html [7]: https://tools.ietf.org/html/rfc5545#section-3.8.7.3 [8]: https://tools.ietf.org/html/rfc5545#section-3.8.7.2 [9]: https://tools.ietf.org/html/rfc5545#section-3.6.1 [10]: https://tools.ietf.org/html/rfc5545#page-69 [11]: https://tools.ietf.org/html/rfc2445#section-4.6.1 [12]: https://tools.ietf.org/html/rfc2445#section-4.8.5.4 [13]: https://tools.ietf.org/html/rfc5545#appendix-A.1 [14]: https://calendar.google.com/ [15]: http://mozilla-comm.github.io/ical.js/ [16]: https://icalendar.org/validator.html [17]: https://tools.ietf.org/html/rfc5545#section-3.1 Signed-off-by: W. Trevor King <wking@tremily.us>
wking
added a commit
to wking/opencontainer-runtime-spec
that referenced
this pull request
Mar 23, 2017
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]: > summarizing the discussion, how about we just alternative the time like > Jonathan discussed? > > I believe that's the only fair thing to do and it's reassuring to hear from > people like Phil who would be able to make the time along with others. > > I'm fine with the current time (1000AEST/1500PST/0000CET) and then > 0400AEST/0900PST/1800CET The 8am Pacific time ended up working out better than 9am for Jonathan and Samuel [2,3], so I've used that instead of 9am. The 8am slot was confirmed as the most popular slot in a Doodle poll [4], with the following folks approving that slot: * David Lyle * George Lestaris * Jonathan Boulle * Julz * Michael Crosby * Mike Brown * Mrunal Patel * Phil Estes * Rob Dolin * Samuel Ortiz * Stephen Day * Stephen Walli * Vincent Batts * W. Trevor King Removing those folks, the second most popular slot is 5pm Pacific, with the following folks approving that slot: * Aleksa Sarai * Keyang Xie * Lei Jitang * Ma Shimiao * Qiang Huang Stephen and Mrunal approved both slots, and since they frequently anchor the runtime and image conversations respectively, there should be sufficient continuity between the two meetings. The only person voting in the Doodle poll who didn't approve either slot is Tianon. Folks with a POSIX ‘date’ command can find the week number with [5]: $ date +%V There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway. The 8am Pacific meeting gets the odd slot because it's Europe-friendly and lots of folks will be in Europe on 2017-03-29 for KubeCon [6]. I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). Future bumps to meeting.ics should bump LAST-MODIFIED [7] or DTSTAMP [8] for any altered components. We can't use DTSTAMP in the VEVENT because VEVENTs require DTSTAMP [9]. The timezone entry is based on the America/New_York example from [10]. Figuring out a single RRULE to cover both meeting times was beyond my abilities, and while RFC 2445 allowed multiple RRULEs in a single VEVENT [11,12], RFC 5545 does not [13]. Something like: RRULE:FREQ=YEARLY;BYDAY=WE;BYHOUR=8,17;BYSETPOS=1,4,5,8,9,... should be legal (at least for 2017), but Google Calendar [14] doesn't seem to respect BYHOUR expansion, and ICAL.js [15] doesn't seem to respect the BYSETPOS limit, so I gave it up and went with two events. To stick strictly to the ISO weeks we could use: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=13,15,17,19,21,23,25,27,29,31,33,35, 37,39,41,43,45,47,49,51 and: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=14,16,18,20,22,24,26,28,30,32,34,36, 38,40,42,44,46,48,50,52 but that's tedious to type, and folks probably don't care all that much about ISO weeks. I've gone with WEEKLY and INTERVAL=2 to give us something that might survive the end of the year. The ICS was validated with [16]. The CRLF line endings are intentional [17], and the .gitattributes entry ensures we keep them. The committed files will still have LF endings, which can confuse 'git diff ...', but you can use --ignore-space-at-eol to see what really changed. [1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 08:37:55 -0700 Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com> [2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 18:33:34 +0100 Message-ID: <CAPWU_0rByhFp=jQQ6cvagHJuYmeTvN7T1zAW+oZR3=F1W8b_rw@mail.gmail.com> [3]: opencontainers#719 (review) [4]: http://doodle.com/poll/zu664785gb59pwkg [5]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html [6]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2017/opencontainers.2017-03-22-21.00.log.html [7]: https://tools.ietf.org/html/rfc5545#section-3.8.7.3 [8]: https://tools.ietf.org/html/rfc5545#section-3.8.7.2 [9]: https://tools.ietf.org/html/rfc5545#section-3.6.1 [10]: https://tools.ietf.org/html/rfc5545#page-69 [11]: https://tools.ietf.org/html/rfc2445#section-4.6.1 [12]: https://tools.ietf.org/html/rfc2445#section-4.8.5.4 [13]: https://tools.ietf.org/html/rfc5545#appendix-A.1 [14]: https://calendar.google.com/ [15]: http://mozilla-comm.github.io/ical.js/ [16]: https://icalendar.org/validator.html [17]: https://tools.ietf.org/html/rfc5545#section-3.1 Signed-off-by: W. Trevor King <wking@tremily.us>
|
Naw, two |
wking
added a commit
to wking/image-spec
that referenced
this pull request
Mar 29, 2017
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]: > summarizing the discussion, how about we just alternative the time like > Jonathan discussed? > > I believe that's the only fair thing to do and it's reassuring to hear from > people like Phil who would be able to make the time along with others. > > I'm fine with the current time (1000AEST/1500PST/0000CET) and then > 0400AEST/0900PST/1800CET The 8am Pacific time ended up working out better than 9am for Jonathan and Samuel [2,3], so I've used that instead of 9am. The 8am slot was confirmed as the most popular slot in a Doodle poll [4], with the following folks approving that slot: * David Lyle * George Lestaris * Jonathan Boulle * Julz * Michael Crosby * Mike Brown * Mrunal Patel * Phil Estes * Rob Dolin * Samuel Ortiz * Stephen Day * Stephen Walli * Vincent Batts * W. Trevor King Removing those folks, the second most popular slot is 5pm Pacific, with the following folks approving that slot: * Aleksa Sarai * Keyang Xie * Lei Jitang * Ma Shimiao * Qiang Huang Stephen and Mrunal approved both slots, and since they frequently anchor the runtime and image conversations respectively, there should be sufficient continuity between the two meetings. The only person voting in the Doodle poll who didn't approve either slot is Tianon. Folks with a POSIX ‘date’ command can find the week number with [5]: $ date +%V There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway. The 8am Pacific meeting gets the odd slot because it's Europe-friendly and lots of folks will be in Europe on 2017-03-29 for KubeCon [6]. I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). Future bumps to meeting.ics should bump LAST-MODIFIED [7] or DTSTAMP [8] for any altered components. We can't use DTSTAMP in the VEVENT because VEVENTs require DTSTAMP [9]. The timezone entry is based on the America/New_York example from [10]. Figuring out a single RRULE to cover both meeting times was beyond my abilities, and while RFC 2445 allowed multiple RRULEs in a single VEVENT [11,12], RFC 5545 does not [13]. Something like: RRULE:FREQ=YEARLY;BYDAY=WE;BYHOUR=8,17;BYSETPOS=1,4,5,8,9,... should be legal (at least for 2017), but Google Calendar [14] doesn't seem to respect BYHOUR expansion, and ICAL.js [15] doesn't seem to respect the BYSETPOS limit, so I gave it up and went with two events. To stick strictly to the ISO weeks we could use: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=13,15,17,19,21,23,25,27,29,31,33,35, 37,39,41,43,45,47,49,51 and: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=14,16,18,20,22,24,26,28,30,32,34,36, 38,40,42,44,46,48,50,52 but that's tedious to type, and folks probably don't care all that much about ISO weeks. I've gone with WEEKLY and INTERVAL=2 to give us something that might survive the end of the year. The ICS was validated with [16]. The CRLF line endings are intentional [17], and the .gitattributes entry ensures we keep them. The committed files will still have LF endings, which can confuse 'git diff ...', but you can use --ignore-space-at-eol to see what really changed. [1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 08:37:55 -0700 Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com> [2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 18:33:34 +0100 Message-ID: <CAPWU_0rByhFp=jQQ6cvagHJuYmeTvN7T1zAW+oZR3=F1W8b_rw@mail.gmail.com> [3]: opencontainers/runtime-spec#719 (review) [4]: http://doodle.com/poll/zu664785gb59pwkg [5]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html [6]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2017/opencontainers.2017-03-22-21.00.log.html [7]: https://tools.ietf.org/html/rfc5545#section-3.8.7.3 [8]: https://tools.ietf.org/html/rfc5545#section-3.8.7.2 [9]: https://tools.ietf.org/html/rfc5545#section-3.6.1 [10]: https://tools.ietf.org/html/rfc5545#page-69 [11]: https://tools.ietf.org/html/rfc2445#section-4.6.1 [12]: https://tools.ietf.org/html/rfc2445#section-4.8.5.4 [13]: https://tools.ietf.org/html/rfc5545#appendix-A.1 [14]: https://calendar.google.com/ [15]: http://mozilla-comm.github.io/ical.js/ [16]: https://icalendar.org/validator.html [17]: https://tools.ietf.org/html/rfc5545#section-3.1 Signed-off-by: W. Trevor King <wking@tremily.us>
wking
added a commit
to wking/image-spec
that referenced
this pull request
Apr 3, 2017
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]: > summarizing the discussion, how about we just alternative the time like > Jonathan discussed? > > I believe that's the only fair thing to do and it's reassuring to hear from > people like Phil who would be able to make the time along with others. > > I'm fine with the current time (1000AEST/1500PST/0000CET) and then > 0400AEST/0900PST/1800CET The 8am Pacific time ended up working out better than 9am for Jonathan and Samuel [2,3], so I've used that instead of 9am. The 8am slot was confirmed as the most popular slot in a Doodle poll [4], with the following folks approving that slot: * David Lyle * George Lestaris * Jonathan Boulle * Julz * Michael Crosby * Mike Brown * Mrunal Patel * Phil Estes * Rob Dolin * Samuel Ortiz * Stephen Day * Stephen Walli * Vincent Batts * W. Trevor King Removing those folks, the second most popular slot is 5pm Pacific, with the following folks approving that slot: * Aleksa Sarai * Keyang Xie * Lei Jitang * Ma Shimiao * Qiang Huang Stephen and Mrunal approved both slots, and since they frequently anchor the runtime and image conversations respectively, there should be sufficient continuity between the two meetings. The only person voting in the Doodle poll who didn't approve either slot is Tianon. Folks with a POSIX ‘date’ command can find the week number with [5]: $ date +%V There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway. The 8am Pacific meeting gets the odd slot because it's Europe-friendly and lots of folks will be in Europe on 2017-03-29 for KubeCon [6]. I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). Future bumps to meeting.ics should bump LAST-MODIFIED [7] or DTSTAMP [8] for any altered components. We can't use DTSTAMP in the VEVENT because VEVENTs require DTSTAMP [9]. The timezone entry is based on the America/New_York example from [10]. Figuring out a single RRULE to cover both meeting times was beyond my abilities, and while RFC 2445 allowed multiple RRULEs in a single VEVENT [11,12], RFC 5545 does not [13]. Something like: RRULE:FREQ=YEARLY;BYDAY=WE;BYHOUR=8,17;BYSETPOS=1,4,5,8,9,... should be legal (at least for 2017), but Google Calendar [14] doesn't seem to respect BYHOUR expansion, and ICAL.js [15] doesn't seem to respect the BYSETPOS limit, so I gave it up and went with two events. To stick strictly to the ISO weeks we could use: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=13,15,17,19,21,23,25,27,29,31,33,35, 37,39,41,43,45,47,49,51 and: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=14,16,18,20,22,24,26,28,30,32,34,36, 38,40,42,44,46,48,50,52 but that's tedious to type, and folks probably don't care all that much about ISO weeks. I've gone with WEEKLY and INTERVAL=2 to give us something that might survive the end of the year. The ICS was validated with [16]. The CRLF line endings are intentional [17], and the .gitattributes entry ensures we keep them. The committed files will still have LF endings, which can confuse 'git diff ...', but you can use --ignore-space-at-eol to see what really changed. [1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 08:37:55 -0700 Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com> [2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 18:33:34 +0100 Message-ID: <CAPWU_0rByhFp=jQQ6cvagHJuYmeTvN7T1zAW+oZR3=F1W8b_rw@mail.gmail.com> [3]: opencontainers/runtime-spec#719 (review) [4]: http://doodle.com/poll/zu664785gb59pwkg [5]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html [6]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2017/opencontainers.2017-03-22-21.00.log.html [7]: https://tools.ietf.org/html/rfc5545#section-3.8.7.3 [8]: https://tools.ietf.org/html/rfc5545#section-3.8.7.2 [9]: https://tools.ietf.org/html/rfc5545#section-3.6.1 [10]: https://tools.ietf.org/html/rfc5545#page-69 [11]: https://tools.ietf.org/html/rfc2445#section-4.6.1 [12]: https://tools.ietf.org/html/rfc2445#section-4.8.5.4 [13]: https://tools.ietf.org/html/rfc5545#appendix-A.1 [14]: https://calendar.google.com/ [15]: http://mozilla-comm.github.io/ical.js/ [16]: https://icalendar.org/validator.html [17]: https://tools.ietf.org/html/rfc5545#section-3.1 Signed-off-by: W. Trevor King <wking@tremily.us>
wking
added a commit
to wking/image-spec
that referenced
this pull request
Apr 3, 2017
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote [1]: > summarizing the discussion, how about we just alternative the time like > Jonathan discussed? > > I believe that's the only fair thing to do and it's reassuring to hear from > people like Phil who would be able to make the time along with others. > > I'm fine with the current time (1000AEST/1500PST/0000CET) and then > 0400AEST/0900PST/1800CET The 8am Pacific time ended up working out better than 9am for Jonathan and Samuel [2,3], so I've used that instead of 9am. The 8am slot was confirmed as the most popular slot in a Doodle poll [4], with the following folks approving that slot: * David Lyle * George Lestaris * Jonathan Boulle * Julz * Michael Crosby * Mike Brown * Mrunal Patel * Phil Estes * Rob Dolin * Samuel Ortiz * Stephen Day * Stephen Walli * Vincent Batts * W. Trevor King Removing those folks, the second most popular slot is 5pm Pacific, with the following folks approving that slot: * Aleksa Sarai * Keyang Xie * Lei Jitang * Ma Shimiao * Qiang Huang Stephen and Mrunal approved both slots, and since they frequently anchor the runtime and image conversations respectively, there should be sufficient continuity between the two meetings. The only person voting in the Doodle poll who didn't approve either slot is Tianon. Folks with a POSIX ‘date’ command can find the week number with [5]: $ date +%V There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway. The 8am Pacific meeting gets the odd slot because it's Europe-friendly and lots of folks will be in Europe on 2017-03-29 for KubeCon [6]. I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). Future bumps to meeting.ics should bump LAST-MODIFIED [7] or DTSTAMP [8] for any altered components. We can't use DTSTAMP in the VEVENT because VEVENTs require DTSTAMP [9]. The timezone entry is based on the America/New_York example from [10]. Figuring out a single RRULE to cover both meeting times was beyond my abilities, and while RFC 2445 allowed multiple RRULEs in a single VEVENT [11,12], RFC 5545 does not [13]. Something like: RRULE:FREQ=YEARLY;BYDAY=WE;BYHOUR=8,17;BYSETPOS=1,4,5,8,9,... should be legal (at least for 2017), but Google Calendar [14] doesn't seem to respect BYHOUR expansion, and ICAL.js [15] doesn't seem to respect the BYSETPOS limit, so I gave it up and went with two events. To stick strictly to the ISO weeks we could use: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=13,15,17,19,21,23,25,27,29,31,33,35, 37,39,41,43,45,47,49,51 and: RRULE:FREQ=YEARLY;BYDAY=WE;BYWEEKNO=14,16,18,20,22,24,26,28,30,32,34,36, 38,40,42,44,46,48,50,52 but that's tedious to type, and folks probably don't care all that much about ISO weeks. I've gone with WEEKLY and INTERVAL=2 to give us something that might survive the end of the year. The ICS was validated with [16]. The CRLF line endings are intentional [17], and the .gitattributes entry ensures we keep them. The committed files will still have LF endings, which can confuse 'git diff ...', but you can use --ignore-space-at-eol to see what really changed. [1]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/mh7FYse2BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 08:37:55 -0700 Message-ID: <CAJg1wMTCGEFRuKoKBEbUPdho82TVH8sPZdGORK_NA2vCNe+w9w@mail.gmail.com> [2]: https://groups.google.com/a/opencontainers.org/d/msg/dev/p0mTOspVgd0/ULXnARy9BAAJ Subject: Re: Moving the OCI Call (again) Date: Thu, 9 Mar 2017 18:33:34 +0100 Message-ID: <CAPWU_0rByhFp=jQQ6cvagHJuYmeTvN7T1zAW+oZR3=F1W8b_rw@mail.gmail.com> [3]: opencontainers/runtime-spec#719 (review) [4]: http://doodle.com/poll/zu664785gb59pwkg [5]: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/date.html [6]: http://ircbot.wl.linuxfoundation.org/meetings/opencontainers/2017/opencontainers.2017-03-22-21.00.log.html [7]: https://tools.ietf.org/html/rfc5545#section-3.8.7.3 [8]: https://tools.ietf.org/html/rfc5545#section-3.8.7.2 [9]: https://tools.ietf.org/html/rfc5545#section-3.6.1 [10]: https://tools.ietf.org/html/rfc5545#page-69 [11]: https://tools.ietf.org/html/rfc2445#section-4.6.1 [12]: https://tools.ietf.org/html/rfc2445#section-4.8.5.4 [13]: https://tools.ietf.org/html/rfc5545#appendix-A.1 [14]: https://calendar.google.com/ [15]: http://mozilla-comm.github.io/ical.js/ [16]: https://icalendar.org/validator.html [17]: https://tools.ietf.org/html/rfc5545#section-3.1 Signed-off-by: W. Trevor King <wking@tremily.us>
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.
On Thu, Mar 09, 2017 at 08:37:55AM -0700, Chris Aniszczyk wrote:
Folks with a POSIX
datecommand can find the week number with:That means that next week will be an odd week with the 2pm PDT meeting (because the US goes into daylight savings time this weekend), which is 2016-03-15 21:00 UTC.
There may be some doubling up around the end of the year, but we're usually canceling meetings around then anyway.
I'd be happier with meeting times anchored to UTC to make life easier for folks outside of the US, but one change at a time ;). And I think UTC-anchored times have been rejected before, but I haven't dug up a reference for that.