[J3] (SC22WG5.6205) RE: [EXTERNAL] RE: [ukfortran] October meeting visa invitation letter

Gary Klimowicz gklimowicz at nvidia.com
Thu Apr 30 19:58:46 EDT 2020

I did not know of all this. This is impressive.

Thanks, Bryce.

-----Original Message-----
From: J3 <j3-bounces at mailman.j3-fortran.org> On Behalf Of Bryce Adelstein Lelbach aka wash via J3
Sent: Thursday, April 30, 2020 4:54 PM
To: van.snyder at jpl.nasa.gov; General J3 interest list <j3 at mailman.j3-fortran.org>
Cc: Bryce Adelstein Lelbach aka wash <brycelelbach at gmail.com>; sc22wg5 <sc22wg5 at open-std.org>
Subject: [J3] (SC22WG5.6204) [EXTERNAL] Re: RE: [ukfortran] October meeting visa invitation letter

External email: Use caution opening links or attachments

There are plenty of ISO and INCITS working groups that conduct
business on GitHub.

For ISO WG21 and INCITS PL22.16 (C++), we have mailing lists, and we
make extension use of GitHub.


Every paper is tracked by a GitHub issue:


Using wg21.link, our lookup service, you can easily get a paper and
locate the GitHub issue and status for a paper:

http://wg21.link/P1255 <- link to the latest revision of the paper
http://wg21.link/P1255R1 <- link to revision 1 of the paper
http://wg21.link/P1255/github <- GitHub issue and current status for a paper

As you can see from the last link, the GitHub issue for each paper
includes a comment with a summary of each discussion of said paper,
including poll results and the guidance to authors. The GitHub issue
tracks the progress of the paper, from initial incubation, through
design review groups, through wording review groups, and ending with
the issue being closed after a pull request has been made to the
sources for the standard applying the change.

National Body comments are processed on GitHub:


Issues are tracked via GitHub:


The Latex sources for the standard are on GitHub:


The Project Editor and his assistants manage changes to the standard
via pull requests:


Major editing projects are tracked via GitHub projects:


Subgroup agendas for face to face meetings are created using GitHub projects:


ISO WG21/INCITS PL22.16 is about 1 order of magnitude larger than
WG5/J3; we have about ~250 people from ~15 national bodies and ~25
active study groups at each of our face to face meetings. We have
people from all sorts of backgrounds, organizations, and countries,
with all sorts of different requirements. Some people can't or won't
use any Google services; some people disable Javascript in their web
browser. These limitations have not prevented us from making use of
organizational tools. The number of such individuals is small, so
we're able to make accomodations, and not everyone has to use or have
access to everything. Some people just participate via the mailing
list, some people just participate at face to face meetings, some
people just participate on GitHub or Slack. The only people who need
to have access to and use all of the different services are the
officers and leadership.

On Wed, Apr 29, 2020 at 11:00 AM Van Snyder via J3
<j3 at mailman.j3-fortran.org> wrote:
> On Wed, 2020-04-29 at 15:10 +0000, Bill Long via J3 wrote:
> > some people have an aversion to, and concerns about,  products from
> > Microsoft (of which GitHub is one, and Skype another).   Google and
> > Facebook have acquired tarnished reputations  as well.  And don’t get
> > the cyber security folks started about ZOOM.
> I believe IEEE P1722 did everything via a-mail. I believe they did not
> have any face-to-face meetings. Ultimately, formal "motions" were
> circulated, which contained edits. These were passed (or rejected) with
> formal e-mail ballots.
> I haven't asked my contacts in WG9 and ARG, but it seems the Ada
> committees do a lot of work via e-mail.  They have a yearly meeting,
> usually in conjunction with Ada Europe and the Conference on Software
> Reliability, about three days total. I don't know for sure, but based on
> the number of different names I see in e-mail traffic, I think WG9 has
> more members than WG5.
> Not to say the WG5 and J3 could switch to that mode tomorrow, or that we
> would find it useful to move rapidly in that direction, but some people
> have made it work.
> At least we ought to try to get more done via e-mail between meetings,
> especially so that we don't get ambushed on Friday after working all
> week on a project.

Bryce Adelstein Lelbach aka wash
US Programming Language Standards (PL22) Chair
ISO C++ Library Evolution Chair
CppCon and C++Now Program Chair
CUDA Core C++ Libraries (Thrust, CUB, libcu++) Lead @ NVIDIA

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

More information about the J3 mailing list