@rjsparks@nostrum.com changed status from new to accepted

@rjsparks@nostrum.com commented

The important dates are there by request.
Changing the availability of them seems reasonable.
Should availability for the sessions on that calendar change?

@lars@eggert.org commented

The important dates are there by request.

Request by whom and why? We have an "important dates" iCal at webcal://datatracker.ietf.org/meeting/important-dates.ics linked from https://datatracker.ietf.org/meeting/important-dates/. Important dates are not interim meetings.

I would not change the availability of sessions.

@rjsparks@nostrum.com commented

Upcoming meetings includes full IETF meetings, not just interims.
IIRC Micheal Richardson put in the original request for important dates to appear in this calendar.

(They are clearly not being included correctly though, as you demonstrated with Calendar.app's behavior out of band).

@lars@eggert.org commented

Maybe we should involve Michael in this discussion. Given that we have a separate iCal for "important dates", I don't understand why we need to replicate those in a calendar that otherwise only has actual meetings.

@rjsparks@nostrum.com commented

On the issue with Calendar.app not displaying all day events correctly:

The culprit is how we're building DESCRIPTION for the meeting and all the important dates - we are not folding lines correctly. Calendar.app is mostly forgiving, but something about this particular one causes it to give up (quietly) on the rest of the file:

BEGIN:VEVENT
UID:ietf-110-opensched-2020-12-07
SUMMARY:IETF 110: Scheduling Opens
CLASS:PUBLIC
DTSTART;VALUE=DATE:20201207
DTSTAMP:20210202T191034Z
DESCRIPTION:Working Group and BOF scheduling begins
To request a Working Group session, use the IETF Meeting Session Request Tool:
https://datatracker.ietf.org/secr/sreq/
If you are working on a BoF request, it is highly recommended to tell the IESG
now by sending an email to iesg@ietf.org to get advance help with the request.
END:VEVENT 

The right thing to do is fold correctly, and we already have code to do that.

We also should use

TRANSP:TRANSPARENT

on the important dates so they do not appear as busy.

@rjsparks@nostrum.com commented

Per discussion on tools-discuss (see the thread at https://mailarchive.ietf.org/arch/msg/tools-discuss/bjwiiLgQEB1lTTyPVlfHSSAlh6s/), we'll drop important dates from this ics feed. They will still be available from their own feed at the important dates page.

@rjsparks@nostrum.com commented

Just to make it easier to find later - the most recent decision to keep the important dates in upcoming.ics was in the last meeting improvement contract and the current implementation came in from that work. See the last section of https://www.ietf.org/media/documents/IETF_MeetingApp_RFP_02-28-19.pdf.

As noted above, we're changing that decision.

@rjsparks@nostrum.com changed status from accepted to closed

@rjsparks@nostrum.com changed resolution from `` to fixed

@rjsparks@nostrum.com commented

fixed in 7620642