From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Thu May 21 15:52:49 2020 Return-Path: X-Original-To: sc22wg5-dom9 Delivered-To: sc22wg5-dom9@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 47AEE9DB116; Thu, 21 May 2020 15:52:49 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id B68F5356E3F for ; Thu, 21 May 2020 15:52:48 +0200 (CEST) Received: by mail-oi1-f176.google.com with SMTP id z9so1406402oid.2 for ; Thu, 21 May 2020 06:52:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stevelionel.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=DhGt6tYh4IlNspSyh4gtajLFKyla9TSjuxQ5A4Ncodo=; b=jf88RoSQDMzmxQwSm32VZ7CXJYzdgirOIhP4+dDv7ptucDVF/ra4TIrEhM5bSjSWqr iScCAotsaiaBs8e229e48MLv3awK6sMth6Yv8GOw6VANkw8PtGZ8fHB3qoREzSfyqM04 8fXhSv9wrCqhWvRBKmMM8n9qUk/iyj1j0AKFA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=DhGt6tYh4IlNspSyh4gtajLFKyla9TSjuxQ5A4Ncodo=; b=MeuGearXeQFV28010Vv+7YsEv+wvElke3ZO6mM0AOZdafS9guVUViISjfaNCmsZlU7 BdRLh9VubtbsVTFymkk71CGmky0HL4tPW3gKrDpl0zm5YJI93Cc1vCQQghdkVtQild1x uehK1mqA+xxYn4dICx1jUYwAx7jOLUZ33QKTfkddRR3M8Gn9dZ6sKHcRqgZFvl2l9Pzc UxSW9CdQusrAzK+JtL6gtvFvB0UWdTwUZPg2KV8nrd96L23x/1cy3mxzqL5RDJ6d+m2d XNqEvWkCq+9kzPCvxLjtM9K5iYm1MzNHq0+WVON9OFk6tVZYubuMwN8ZjetsY4NrKKh0 aE1Q== X-Gm-Message-State: AOAM532oTT4aPCIibjU2xQiALbnpm2ISsknQYmrEn+B+L1UqM2woscGs Wtmr8vuV2ebAnB+9CdL5gvEx7vi0yw/m/87K4H3LLGb7G0o= X-Google-Smtp-Source: ABdhPJxtrNMHekSw8Mxu4zgT/sLniZzNbF9uqXZDpdqZUjjNvy4B3CpmHlZSJaj0qsKfYIwY5i/m4B2n4VLdSFJ8YZ0= X-Received: by 2002:aca:4b0f:: with SMTP id y15mr6406820oia.114.1590069166826; Thu, 21 May 2020 06:52:46 -0700 (PDT) MIME-Version: 1.0 References: <20200521055603.56E7E358784@www.open-std.org> In-Reply-To: <20200521055603.56E7E358784@www.open-std.org> From: Steve Lionel Date: Thu, 21 May 2020 09:52:35 -0400 Message-ID: Subject: Re: [J3] (SC22WG5.6216) All face to face INCITS or US-hosted ISO meetings cancelled for the rest of 2020 To: WG5 Content-Type: multipart/alternative; boundary="000000000000db7b2205a628d3aa" Sender: owner-sc22wg5@open-std.org Precedence: bulk --000000000000db7b2205a628d3aa Content-Type: text/plain; charset="UTF-8" On Thu, May 21, 2020 at 1:56 AM Bryce Adelstein Lelbach aka wash via J3 < j3@mailman.j3-fortran.org> wrote: > > INCITS has cancelled all face to face meetings of INCITS committees and US > hosted ISO meetings for the rest of the year. Just wanted to give y'all a > heads up as I didn't see a post to your mailing lists about this yet. > This came out just yesterday afternoon, my time. I immediately wrote to Dan Nagle and the J3 subgroup heads to get some initial thoughts on how J3 and WG5 should handle this. I haven't heard from Dan yet, but did get some ideas from others. From the WG5 side, which is where I could make a decision, my inclination is to just cancel the WG5 meeting for 2020. WG5 doesn't have any real business at this time - we've already agreed on the 202X work list, aren't discussing 202Y proposals yet, and don't have a corrigendum to discuss. So even a virtual WG5 meeting seems less useful at this time. Our 2021 meeting is scheduled for late June in Manchester, UK, and I very much hope the world will be in a place by then where we can do that. When WG5 and J3 meet together, the WG5 members are very helpful in contributing to J3's work on technical papers, but that can still happen. There's already been a lot of discussion on the J3 email list about providing J3 an online space for discussing/developing the technical work. The idea I have is to set up a discussion board on the J3 website for J3 (and WG5) members to do the work that usually happens in subgroup meetings. My hope is that we can transition to doing more of this work between meetings than we have been in the recent past, but this can't be a complete substitute for the personal interactions we get when we meet physically - I hope we can get back to that next year. It is clear that the pandemic is going to affect the 202X schedule, but how much it does so greatly depends on how well we shift into working online. This is going to be a major change for many of you, but I have confidence that we can pull this off. It's not my decision to make about what to do regarding J3's meeting - look to hear from Dan about that. WG5 members (which of course includes J3) - does it seem reasonable to just cancel the 2020 WG5 meeting? J3 work can continue online and WG5 folk are welcome to participate as usual. You can reply directly to me in email, or to the group, but if you reply to the list *please make sure you do so to the WG5 list and not J3*. Thanks. Steve WG5 Convenor --000000000000db7b2205a628d3aa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, May 21, 2020 at 1:56 AM Bryce Ade= lstein Lelbach aka wash via J3 <j3@mailman.j3-fortran.org> wrote:
=
INCITS has cancelled all face to face meetings of INC= ITS committees and US hosted ISO meetings for the rest of the year. Just wa= nted to give y'all a heads up as I didn't see a post to your mailin= g lists about this yet.

This ca= me out just yesterday afternoon, my time. I immediately wrote to Dan Nagle = and the J3 subgroup heads to get some initial thoughts on how J3 and WG5 sh= ould handle this. I haven't heard from Dan yet, but did get some ideas = from others.

From the WG5 side, which is where I c= ould make a decision, my inclination is to just cancel the WG5 meeting for = 2020. WG5 doesn't have any real business at this time - we've alrea= dy agreed on the 202X work list, aren't discussing 202Y proposals yet, = and don't have a corrigendum to discuss. So even a virtual WG5 meeting = seems less useful at this time. Our 2021 meeting is scheduled for late June= in Manchester, UK, and I very much hope the world will be in a place by th= en where we can do that.

When WG5 and J3 meet toge= ther, the WG5 members are very helpful in contributing to J3's work on = technical papers, but that can still happen. There's already been a lot= of discussion on the J3 email list about providing J3 an online space for = discussing/developing the technical work. The idea I have is to set up a di= scussion board on the J3 website for J3 (and WG5) members to do the work th= at usually happens in subgroup meetings. My hope is that we can transition = to doing more of this work between meetings than we have been in the recent= past, but this can't be a complete substitute for the personal interac= tions we get when we meet physically - I hope we can get back to that next = year.

It is clear that the pandemic is going to af= fect the 202X schedule, but how much it does so greatly depends on how well= we shift into working online. This is going to be a major change for many = of you, but I have confidence that we can pull this off.

It's not my decision to make about what to do regarding J3's= meeting - look to hear from Dan about that.=C2=A0

WG5 members (which of course includes J3) - does it seem reasonable to jus= t cancel the 2020 WG5 meeting? J3 work can continue online and WG5 folk are= welcome to participate as usual. You can reply directly to me in email, or= to the group, but if you reply to the list please make sure you do so t= o the WG5 list and not J3. Thanks.

Steve <<= a href=3D"mailto:steve@stevelionel.com">steve@stevelionel.com>
=
WG5 Convenor
--000000000000db7b2205a628d3aa--