Skip to content
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

meeting: Add UberConference information #757

Merged
merged 1 commit into from
Apr 6, 2017

Conversation

wking
Copy link
Contributor

@wking wking commented Apr 5, 2017

And bump DTSTAMP for the touched VEVENTS.

This is less DRY, but makes life easier for folks pulling up the calendar a minute before the meeting, since they don't have to click through to the README section. Also requested by @vbatts ;).

The LOCATION entry seems like a reasonable location for the conference-call page, so I've used that. Note that the URI there is a text value; LOCATION supports URIs in ALTREP, but the UberConference page isn't an “alternate text representation for the property value”. The URI in DESCRIPTION is a fallback for clients that don't support/display LOCATION (I'm not sure if any exist, but it's easy to play it safe). I couldn't find a more structured location for the phone number, unless we also wanted to put that in LOCATION.

The ICS was validated here.

And bump DTSTAMP for the touched VEVENTS.

This is less DRY, but makes life easier for folks pulling up the
calendar a minute before the meeting, since they don't have to click
through to the README section.  Also requested by Vincent [1] ;).

The LOCATION entry [2] seems like a reasonable location for the
conference-call page, so I've used that.  Note that the URI there is a
text value; LOCATION supports URIs in ALTREP [2], but the
UberConference page isn't an "alternate text representation for the
property value" [3].  The URI in DESCRIPTION is a fallback for clients
that don't support/display LOCATION (I'm not sure if any exist, but
it's easy to play it safe).  I couldn't find a more structured
location for the phone number, unless we also wanted to put that in
LOCATION.

The ICS was validated with [4].

[1]: http://ircbot.wl.linuxfoundation.org/eavesdrop/%23opencontainers/%23opencontainers.2017-04-05.log.html#t2017-04-05T17:55:25
[2]: https://tools.ietf.org/html/rfc5545#section-3.8.1.7
[3]: https://tools.ietf.org/html/rfc5545#section-3.2.1
[4]: https://icalendar.org/validator.html

Signed-off-by: W. Trevor King <[email protected]>
@wking
Copy link
Contributor Author

wking commented Apr 5, 2017

And it seems like Google Calendar will display the LOCATION but not the DESCRIPTION (see here and here), so I think we need to keep both to support them.

@vbatts
Copy link
Member

vbatts commented Apr 5, 2017

and since i've linked straight to raw file on master it ought to just update ;-)
LGTM

Approved with PullApprove

@mrunalp
Copy link
Contributor

mrunalp commented Apr 6, 2017

LGTM

Approved with PullApprove

@mrunalp mrunalp merged commit 0946333 into opencontainers:master Apr 6, 2017
@wking wking deleted the ics-uberconf-link branch April 7, 2017 18:13
@vbatts vbatts mentioned this pull request Jul 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants