From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Fri Jan 1 22:23:45 2021 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 ED911358AAC; Fri, 1 Jan 2021 22:23:44 +0100 (CET) Delivered-To: sc22wg5@open-std.org Received: from mail-qt1-f181.google.com (mail-qt1-f181.google.com [209.85.160.181]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id 8D23B356671 for ; Fri, 1 Jan 2021 22:23:44 +0100 (CET) Received: by mail-qt1-f181.google.com with SMTP id y15so14801969qtv.5 for ; Fri, 01 Jan 2021 13:23:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stevelionel.com; s=google; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=45P5j72elOsHcAfG/vu8H+ksqkyC8IXXVTzrMmhlW2o=; b=1sewHeTIHNM9ApoPkMp8XvNQxbWftcxfGAYeoGkcEHGts0V46lVDlX672ITd/c3Ibw DtyJFcEdM3j51PexFSGsYdN5PBVTDqHD9wrpJrwlYOwi2VZ5ZwZw7M4PM5kMQknEuKks 5YuGiPU4XKVNhOdTysV79WXa/tTUNb5LpBlD4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=45P5j72elOsHcAfG/vu8H+ksqkyC8IXXVTzrMmhlW2o=; b=lMdYCPcq8nqp5VdAhP/LMqGk3UOjlUMed9BFvrAU54LzJ4ZytpmU9YZ75wZbytMIE1 OVISAcI00Bal+HaH2idPC5MwZZSatTL5P4XaZIY1/+3i9CvgOL4YeYf/RfdivWRxX0xw qY6VLNd9LW08uayhVl3wNhSsKYf2oFVK3HgQxpU7ZEMOkYZyqUku/5sqEWLwW7MSk5xc uoeOWJoo+RQN7a3hCBFICgehAciQpRTbaslWpAIgJA8D7zVnvcCapgYRGsGZa0Ds46vM DxSveCNBx96MjxcY+sS4veA+syhOBaTn3cZN6k6vJJOwjIaDYoXon/qH/i+WWb68jTb9 dCzg== X-Gm-Message-State: AOAM530YkhGoaPG+QBQ0ZIPUWfUrM5D9aGnnG2uFn1bKtXv0v7946/Jd qnnmqwZGPyK8yblpR1PIEQigEGrx+nUKeYz6 X-Google-Smtp-Source: ABdhPJzzuIyaAPzE88hbPi0YWGRBI16uKp1gUQvLzZggA+SU2l7XxEpXfzZbMEu5p9G4dMcddf5j8A== X-Received: by 2002:a05:622a:1c3:: with SMTP id t3mr63153322qtw.378.1609536222490; Fri, 01 Jan 2021 13:23:42 -0800 (PST) Received: from [192.168.1.38] ([71.169.142.206]) by smtp.gmail.com with ESMTPSA id z26sm31050595qki.40.2021.01.01.13.23.41 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 01 Jan 2021 13:23:41 -0800 (PST) To: WG5 List From: Steve Lionel Subject: June 2021 meeting X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <7559a032-8e52-afbd-4684-f80c15d8b1ef@stevelionel.com> Date: Fri, 1 Jan 2021 16:23:40 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 Content-Type: text/html; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: owner-sc22wg5@open-std.org Precedence: bulk

Well, we made it through 2020, though, sadly, almost two million around the globe didn't due to the coronavirus. Here's hoping that things start to improve in 2021.

Unfortunately, it seems that the world situation won't improve enough for us to still hold the 2021 WG5 meeting in Manchester, England, as planned. I've discussed this with Nathan (remember that Arm was to be the host for this meeting) and he agrees that assuming everyone will be able to travel to the UK for June is unreasonable. ISO rules require 16 week notice for meetings, which is almost upon us. Therefore, I have decided that the 2021 meeting will be virtual, held over Zoom. J3 did this for the October 2020 meeting and it worked remarkably well - J3 will be doing it again for February.

WG5, though, poses a higher obstacle regarding time zones. The October meeting went from 1700-2000 Eastern time, which was 0600-0900 (the next day) for Malcolm in Tokyo, and 2100-0000 for the couple of UK folk who joined. If we picked the same times, that would be even an hour later for Germany. The October J3 meeting was held over three days (Monday-Wednesday), and we ran out of time. A poll I ran in the J3 forum had four days of three hours each as the most popular option. I welcome comments, especially from UK/Europe members, on timing.

We still have five 202X work items to complete, and I would like to spend a bit of time discussing 202Y ideas. To see some that have been kicked around, take a look at Issues · j3-fortran/fortran_proposals (github.com) I'll remind everyone that we won't have the luxury of going off during the day during the meeting to write papers and that we really need to at least draft proposals before we start. The J3 forum (J3 Work Items - Index page (j3-fortran.org)) has topics for each work item and discussions can take place there. The Generics subgroup has been having their own meetings to work on proposals for 202Y. We will be able to have "breakout rooms" in Zoom (Nathan has generously offered to host the Zoom meetings for June), but again, time zones may be problematic.

For 2022, I'm going to cross my fingers and plan on getting back to physical meetings, though there will be virtual participation. Sidd has offered to host at UCAR in Boulder (taking over from Dan, who retired.)

Thanks to all for your efforts. I am convinced we can get 202X done in 2022. Let's make it happen.

Steve