README: Document the alternate-week meeting times#627
Closed
wking wants to merge 1 commit intoopencontainers:masterfrom
Closed
README: Document the alternate-week meeting times#627wking wants to merge 1 commit intoopencontainers:masterfrom
wking wants to merge 1 commit intoopencontainers:masterfrom
Conversation
Member
|
Cherry pick indeed, it references the runtime-spec ;-) |
wking
force-pushed
the
alternating-meetings
branch
2 times, most recently
from
06877c3 to
3f7694b
Compare
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>
Contributor
Author
|
On Mon, Apr 03, 2017 at 04:30:32PM -0700, Vincent Batts wrote:
Cherry pick indeed, it references the runtime-spec ;-)
|
Contributor
Author
|
On Mon, Apr 03, 2017 at 04:56:56PM -0700, W. Trevor King wrote:
I updated the meeting.ics entries…
Thinking this over a bit more, I'm not quite sure how we want to
handle the iCalendar file. PRODID is supposed to be globally unique
[1], and I'm currently using the same PRODID for both runtime-spec and
in this PR. Do we expect folks to track both of these iCalendar files
at the same time? Will they want to see a single OCI meeting, or
separate (overlapping) meetings for runtime-spec and image-spec? I
think the best route forward as long as there's a shared meeting is
keep the ICS in a shared location (project-template? Outside of
version control on www.opencontainers.org? In runtime-spec?) and have
other projects link to it there. If/when we split into image- and
runtime-specific meetings, we can fork that central iCalendar file
into spec-specific ones. Thoughts?
[1]: https://tools.ietf.org/html/rfc5545#section-3.7.3
|
Member
|
closing for now as this is too variadic. perhaps the meetings should just be in a wiki or something more flexible |
Contributor
Author
|
On Fri, May 19, 2017 at 10:56:58AM -0700, v1.0.0.batts wrote:
closing for now as this is too variadic.
Hopefully the timing will settle down again soon.
perhaps the meetings should just be in a wiki or something more
flexible
There is already an entry in [1], although that's stale with the 17:00
reference. However, entries in the image-spec repo itself show
clearly that the image-spec maintainers have approved a given time.
That's harder to establish with an open wiki or an opencontainers.org
entry.
And as it stands, the image-spec master is a stale reference to
“always 14:00 Pacific” [2]. If the image-spec maintainers aren't
interested in keeping that up to date, they should replace the current
reference with a punt to somewhere…
[1]: https://www.opencontainers.org/community
[2]: https://github.com/opencontainers/image-spec/blob/5ebcc54f1725d37e8a8dbdebe1931df46d486736/README.md#weekly-call
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cherry-pick opencontainers/runtime-spec#740 over now that it has landed (and still ~45 minutes before today's meeting starts ;).