[J3] (SC22WG5.6284) SC22 Resolutions

[Steve Lionel]

The ISO JTC1/SC22 Plenary just ended, and there were several resolutions 
that affect WG5.

There was a long discussion about in-person WG meetings. WG14 (C) and 
WG21 (C++) have a problem in that they have made financial commitments 
to hotels two years out, and they wanted "air cover" from SC22 to allow 
them to cancel without penalty. Initially the proposal was to ban 
physical meetings entirely through 2023 with SC22 revisiting that at its 
next plenary (August 2021). I objected that this would block WG5 from 
holding its next meeting in June 2021, even if it seemed safe to do so, 
and I suggested adding a "more than X attendees" qualifier to the 
resolution (WG14/WG21 meetings are usually in excess of 250 attendees!) 
This was accepted, and the resolution now states:

    *Resolution 20-06: Face-to-face Meetings*
    JTC 1/SC 22 resolves to prohibit face-to-face meetings for JTC 1/SC
    22 Working Group meetings where the expected face-to-face attendance
    exceeds 100 attendees until further notice. This will provide JTC
    1/SC 22 WGs with sufficient lead time for face-to-face meeting
    planning. This will be revisited at the next JTC 1/SC 22 plenary.

This works for us. Obviously we'll have to see what the pandemic 
situation is in early 2021, but we have the flexibility - unless ISO 
JTC1 or all of ISO extends the current restrictions (that go only three 
months out, a big problem for WG14/WG21).

Next was:

    *Resolution 20-07: Face-to-face Meetings Provisions*
    JTC 1/SC 22 Working Group meetings being held face-to-face shall
    provide the facilities to allow for full remote participation, which
    includes voting.  This will be revisited at the next JTC 1/SC 22
    plenary.

Generally WG5 hosts have teleconferencing equipment that will allow us 
to do this, but we're going to have to change our procedures to enable 
"full remote participation" if the meeting is held partly in-person. I 
picked up some useful tips during the SC22 Plenary, which was entirely 
virtual.

At some point, J3 will also need to address this - our current 
arrangements don't work even for in-person meetings (too small) and we 
have no teleconferencing equipment. The October 2020 meeting is already 
entirely virtual and I suspect February 2021 will be as well. J3 needs 
to start preparing now for virtual attendance.

A third resolution affecting us was:

    *Resolution 20-03: Project Source Files *
    In order to ensure that all working groups are able to continue
    standards development and not have a single point of failure, JTC
    1/SC 22 directs that all of its WGs shall have a recent copy of the
    project source file(s) for each project on ISO Documents.

The prime motivation for this was WG4 (COBOL), where the project editor 
died unexpectedly last November. That committee had a hard time 
reconstructing the work, thus the new requirement that up-to-date 
document sources be uploaded to the ISO Documents web site. Malcolm has 
been uploading his SVN repository bundles to the Edit subfolder on the 
J3 site, and I'll copy that to ISO Documents. *Malcolm*, would you 
please also upload to Edits your latest repository of F202X work when 
you have the next draft? I'll copy it to ISO Documents then.

Another item of interest is that Dan's WG23 chapter on vulnerabilities 
for Fortran was upgraded from a Preliminary Work Item to an Active Project.

Lastly, David Keaton was renominated as SC22 chair and I was renominated 
as WG5 Convenor. This then goes to ISO JTC1 for a country vote.

Steve

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20200901/f32db84b/attachment.htm>