From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Thu May 21 17:02:10 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 3EB0C35711D; Thu, 21 May 2020 17:02:10 +0200 (CEST) Delivered-To: sc22wg5@open-std.org Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by www.open-std.org (Postfix) with ESMTP id E21DB356E3F for ; Thu, 21 May 2020 17:02:05 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 988265C009F for ; Thu, 21 May 2020 11:02:02 -0400 (EDT) Received: from imap21 ([10.202.2.71]) by compute1.internal (MEProxy); Thu, 21 May 2020 11:02:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=certik.us; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=XdI2uAmPhqRKa95ecWEcXxZKEAobelU 32X7FQ3ZxZ1g=; b=uWAzFMDlLR/1zHvI/S++1Megsrz1IJ1cuxh0r7AtPbteOin tH7j1XrTJCs9l2by/K3JsKj0MVEtvG637pZrnV/n3sH5rfBJjrbaVrxsjWYH3Lbb /r43ZiOk04HcuQmdbapi5miw+7N66YGGQimB8nEtnbAAPZLjxK7SQG2SfXsZqXcL b5anO326vTXTEL0kUbnke1EeyTCOpupfF54kUwF6Lb22AdX1TtkJVkvXdfNxw40B R8k5KyRwtIoPVPYJhF3bMVJ1uyGCdiHFj+ngn2r2+VaVyNnSXIdxM/8lA+zVDkmC jDtIzOk7c3dTFiwb9IRqk8t/wNAEBeqrPMLaB1Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=XdI2uA mPhqRKa95ecWEcXxZKEAobelU32X7FQ3ZxZ1g=; b=vMraHYLvnGAGMfZwICOqX1 X18ZQal/vV9NZFm+3EA+wl/5y0yX6h1Ez4vKG+jZwMeACyfRXiny0pq8yWXfoKSE MJ/l258K8XN9W3Ez8uN8BroHKRrCDvvWXJss8iXw4nCkhgF3KrmIEtOTLjF16C0e B/tRHEajCca00Gvf7m7hHAkRoqp95U0Bz9tm3eQfGeyCEXaC2F2hcSj9FJkNEIlS ufO0uFaREMYRzc2vPR6bEASTk3FPA2AygaLWSgjN9m2FN/UDRBTDyc19/eDTCoHq aoFWI1d38QqGHsnm3qn5ru3tZd0fG+5qhH/jJOoZfgWh4VCDySJnBzglbpbzM2rA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudduuddgkeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderreejnecuhfhrohhmpefqnhgurhgvjhgpvegvrhhtvohkuceoohhnughrvghjsegt vghrthhikhdruhhsqeenucggtffrrghtthgvrhhnpeegudduhfeukeduhfejkeefteegte etheettdeiiefhjefgteetffehheefhfeghfenucffohhmrghinhepghhithhhuhgsrdgt ohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepoh hnughrvghjsegtvghrthhikhdruhhs X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 194D1660081; Thu, 21 May 2020 11:02:02 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.3.0-dev0-487-g38013f6-fm-20200519.001-g38013f6c Mime-Version: 1.0 Message-Id: <99be54c6-811a-4932-a58b-64e8d8dcf65c@www.fastmail.com> In-Reply-To: <20200521135249.65B5A358727@www.open-std.org> References: <20200521055603.56E7E358784@www.open-std.org> <20200521135249.65B5A358727@www.open-std.org> Date: Thu, 21 May 2020 09:01:22 -0600 From: =?UTF-8?Q?Ond=C5=99ej_=C4=8Cert=C3=ADk?= To: "WG5 List" Subject: =?UTF-8?Q?Re:_[J3]_(SC22WG5.6217)_All_face_to_face_INCITS_or_US-hosted_I?= =?UTF-8?Q?SO_meetings_cancelled_for_the_rest_of_2020?= Content-Type: text/plain Sender: owner-sc22wg5@open-std.org Precedence: bulk Hi Steve and others, On Thu, May 21, 2020, at 7:52 AM, Steve Lionel via J3 wrote: > On Thu, May 21, 2020 at 1:56 AM Bryce Adelstein Lelbach aka wash via J3 > 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. I would suggest to keep the (virtual) meeting, it can be shorter if needed. If it is held, does it have to be 5 days long? I didn't see this specified in the ISO rules, but maybe I missed it. If it is true that "WG5 doesn't have any real business at this time", then I suggest we use the effort to either help the 202X standard out of the way sooner, or start tackling proposals for 202Y. In particular, the most requested difficult problems seem to be: * generic programming * exceptions * GPU support An alternative solution is to just held the J3 (virtual) meeting, but invite all WG5 members to participate. > 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. Steve and I discussed this privately and it seems we we agreed on the general framework how this can work. There are two distinct issues: 1. Moving the work of the Committee itself online. This must follow the ISO rules and it must restrict the discussion to committee members. There are multiple ways to do that, from a private GitHub or GitLab repository, to some other private forum such as Discourse or phpBB. Or even just an email on a private mailinglist. This is what Steve's paragraph above suggests. 2. Involving the community. This is what the "incubator repository" (https://github.com/j3-fortran/fortran_proposals) is for. I do advocate the committee members to *optionally* use it and to discuss as much as they are able and really to embrace it as a tool to develop proposals together with the community. This is distinct from 1. and is not supposed to replace 1, but rather complement it --- to feed into 1. We need both 1. and 2. We might disagree on the extent to which the community should be involved, in other words how much work will be done using the 1. versus 2. approach, but we made huge progress on figuring this out and agreeing that we need both 1. and 2., and I suggest we simply start doing it and figure out and adjust the details as we go. Ondrej