From owner-sc22wg5+sc22wg5-dom9=www.open-std.org@open-std.org Thu May 21 20:01:45 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 C38A89DB116; Thu, 21 May 2020 20:01:45 +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 6B628356E3F for ; Thu, 21 May 2020 20:01:44 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 084295C00FB for ; Thu, 21 May 2020 14:01:43 -0400 (EDT) Received: from imap21 ([10.202.2.71]) by compute1.internal (MEProxy); Thu, 21 May 2020 14:01:43 -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:content-transfer-encoding; s=fm3; bh=LzUEj vD7Zkx177o9rTkYtcg6mmbvxgr1kXXkq1evHSU=; b=bHs79jfxLTZ/tzIv2B1vd NkykgDm5t3HbHBKjGhKhPfC5hjrbeH/LmG9OVn+G8Ua6/bNrVkhcdJYPUjCox2T8 NPBHcHTSNT7+7b8f8hN0AftGy57CX0PrXLGY789m4whEJikgH5FjbWfmI6JSx9SL 6vPyd3YNXHJPITwtwWL41k4Eg2Ut6IIIaI8Aumay1Ae4fSG+LSxXnG/rwBorvFGE m5Ee4QQR2cMWQkM9cJzxDVIN3AHMG6YiTHiN2WX+yj4o2va4VTBa/zIUsvCXHFb9 HFRc8zwWd0qgTAzyRLRfF52AopcdS9rHoUH1DdSN0J+Cxf8qt2oWoIoOnvNlZfZe g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding: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=LzUEjvD7Zkx177o9rTkYtcg6mmbvxgr1kXXkq1evH SU=; b=hrLXSKhZdCPf2VejCB96PPnVoDWpz1a0CV1dJacaSICUt+m1rjdxF/NOd MiVMVfaLyaS7KFjB6TnnMP4FoqisvE6Y8aSYQePv+zhBbVAZnH7isE2ZS9LNB9c1 S4+kIUE46uwVqElEJY20s6fKvW8+s1d8J3+namuMVR+D3VTJfftI9iTh6ifDXueR dWrUFxHxiBec738UL2cl8YSaBz1vAsRMXYTbr5h8EiWB5CDYmetjkxypBepsUHbP 8H3/Oze2B48bEV583wccV8KE480jsyfDUuJbNU9tDbQ/xUDkoyw/kHgpJ8KhGEI8 33Tg4VEQ7PXo90iA1qUYiU3/fltcw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudduuddgudduvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgse htqhertderreejnecuhfhrohhmpefqnhgurhgvjhgpvegvrhhtvohkuceoohhnughrvghj segtvghrthhikhdruhhsqeenucggtffrrghtthgvrhhnpeehvdeuvdejfeevheevvdevie fgtdeileefleeggffgieduledvjeeifedvieduffenucffohhmrghinhepghhithhhuhgs rdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epohhnughrvghjsegtvghrthhikhdruhhs X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 5FE5F66007E; Thu, 21 May 2020 14:01:42 -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: <3ac2acc9-30e5-4567-81f5-f5df53c9fc42@www.fastmail.com> In-Reply-To: <20200521173040.0B114358727@www.open-std.org> References: <20200521055603.56E7E358784@www.open-std.org> <20200521135249.65B5A358727@www.open-std.org> <20200521150210.517593581D2@www.open-std.org> <20200521173040.0B114358727@www.open-std.org> Date: Thu, 21 May 2020 12:01:21 -0600 From: =?UTF-8?Q?Ond=C5=99ej_=C4=8Cert=C3=ADk?= To: "WG5 List" Subject: =?UTF-8?Q?Re:_[J3]_(SC22WG5.6219)_Re:_All_face_to_face_INCITS_or_US-host?= =?UTF-8?Q?ed_ISO_meetings_cancelled_for_the_rest_of_2020?= Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable Sender: owner-sc22wg5@open-std.org Precedence: bulk Hi Steve, On Thu, May 21, 2020, at 11:30 AM, Steve Lionel via J3 wrote: > On 5/21/2020 11:01 AM, Ond=C5=99ej =C4=8Cert=C3=ADk via J3 wrote: > > 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. > There is no prescribed length. A virtual meeting would benefit by bein= g=20 > shorter, but the only way we can make that work is if the time-consumi= ng=20 > development of papers by J3 subgroups happens mostly before the meetin= g=20 > so that the virtual meeting can focus on voting and adjustments to spe= cs=20 > and syntax. > > 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. > We have a fair bit left to do on 202X - that is the top priority. If w= e=20 > can make significant progress on full papers (specs/syntax/edits) for=20= > the remaining work list items, we will still be on track for publicati= on=20 > in 2022. Here is the summary of the work list for 202X that Zach put together (th= ank you!): https://github.com/j3-fortran/fortran_proposals/issues/162#issuecomment-= 593671596 With links to specific issues for each item if they exist (they then con= tain links to the submitted papers). There is not that many proposals that still need to be written for 202X.= Let's try to get it done as a community before our next J3 or WG5 meeti= ng, so that we can spend the meeting on voting and adjustments to specs = and syntax. Ondrej