Re: [Tools-discuss] Important dates in upcoming.ics

Robert Sparks <rjsparks@nostrum.com> Wed, 03 February 2021 17:28 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1794B3A0C06; Wed, 3 Feb 2021 09:28:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.281
X-Spam-Level:
X-Spam-Status: No, score=-1.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EfmafPI0Srz1; Wed, 3 Feb 2021 09:28:17 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A7803A09B5; Wed, 3 Feb 2021 09:28:17 -0800 (PST)
Received: from unformal.localdomain ([47.186.1.92]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 113HSD0T091278 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 3 Feb 2021 11:28:13 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1612373294; bh=+hB+DMHjbofsQy9I3RNKCNmEfffz/1cWd0zbUBI2Ylw=; h=To:References:From:Subject:Date:In-Reply-To; b=sr7QJDEGreSJQMc1s668TUhq64lSkvPFE2nnWKNr7/sGF420je5JYlgK1LZTgx+u0 bgp7LSvEZM3qM4w5MarvwTzZKtEN5ReWG+nMbsvUCTSUfP6D/b+BXbk0ClJmc6WLPS 4RHYP4PmxpUuuwJmpuPVAKTUyIRr9Z42UNhOlvA4=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.1.92] claimed to be unformal.localdomain
To: Michael Richardson <mcr+ietf@sandelman.ca>, tools-discuss <tools-discuss@ietf.org>, Lars Eggert <lars@eggert.org>, Greg Wood <ghwood@ietf.org>
References: <7da79bcd-2931-4a0e-8f7e-3ba528fea0cc@nostrum.com> <20268.1612372060@localhost>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <cac83fb6-2cbd-5037-e6d7-623d4e2c30b1@nostrum.com>
Date: Wed, 03 Feb 2021 11:28:08 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <20268.1612372060@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/1MCzxP_Fpkm85h5stUiV7Ps8LCY>
Subject: Re: [Tools-discuss] Important dates in upcoming.ics
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2021 17:28:19 -0000

On 2/3/21 11:07 AM, Michael Richardson wrote:
> Robert Sparks <rjsparks@nostrum.com> wrote:
>      > All, and particularly Michael, who IIRC made the original request:
>
>      > The upcoming meetings ics calendar currently includes meeting important
>      > dates (but the page does not show them). Lars points out that this is
>      > both inconsistent, and redundant with the separate important dates ics
>      > calendar we have.
>
> I'm okay with important dates being elsewhere.
> What feed is that page?  https://www.ietf.org/how/meetings/ does not mention
> it.  I get to https://datatracker.ietf.org/meeting/important-dates/
> only by going into a specific meeting.

You found where the link is homed: 
https://datatracker.ietf.org/meeting/important-dates/

https://datatracker/meeting will always have a link to that page.

Greg - consider adding a link to 
https://datatracker.ietf.org/meeting/important-dates/ at 
https://www.ietf.org/how/meetings/


>
> I think that ultimately my original complaint was that the upcoming included
> the *meeting* things, which was redundant with having the meeting calendar loaded.
> I think that this has been fixed now.
Yes
>
> The primary utility I have with upcoming.ics is that it tells me (in various
> roles), when there are other (virtual) interim meetings.
>
> I would like it if the upcoming.ics included the IESG Telechats and other
> related things (LLC board, RTG area meetings, etc.).

We could add these other things, but I think we would then need to add 
filters so people could select the information that they really want.

I understand the general deconflicting use case.

It will likely be a stretch to get LLC board meetings and the like into 
the datatracker - those are maintained in other systems.

Area meetings on the other hand should just be interims - are they not 
being organized that way?

>   Again, the goal is
> either de-conflicting, or at least, consciously knowing about double bookings.
>
>      > Would it be reasonable to remove the important dates from the
>      > upcoming.ics calendar?
>
> YES.
>
>      > (Also note that the way these important dates are currently being
>      > represented in both of the above .ics files is not right - it fails to
>      > display in calendar.app, and causes other calendaring systems to assert
>      > that the whole day is "Busy" - see
>      > https://trac.tools.ietf.org/tools/ietfdb/ticket/3161).
>
> Oh.  That's really bad.
> I guess that's because they are not associated with a specific time.
> Maybe for some things, like Draft Deadline, a 5 minute event at 23:55:00
> would work.  That would also establish the deadline into the right time zone.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
>             Sandelman Software Works Inc, Ottawa and Worldwide