[J3] (SC22WG5.6210) Re: (SC22WG5.6208) Re: (SC22WG5.6204) [EXTERNAL] Re: RE: [ukfortran] October meeting visa invitation letter

[Ondřej Čertík]

Hi Bill,

I tried to keep my answer as short as possible:

> > Bryce, thank you for this detailed explanation how C++ does it. That's precisely what I am trying to get the Fortran Committee to eventually do also. But step by step in an evolutionary matter, so we first created the J3 GitHub repository, tried it for a few papers, it was a success, then we'll try for more papers, until we get there.
> 
> And where is “there”?  discussing and submitting all the papers on GitHub? 

The goal (i.e. "there") that I am proposing:

* Keep using https://j3-fortran.org/ as the primary (final) place to upload each paper, we discuss, vote in person, the same as now. Committee members who only have time to do that will only do that. They don't have to work between meetings, they just have to show up at the J3 meeting (in Vegas).

* Each paper is tracked at GitHub, from the initial idea to all the papers the idea generates, and discussed with the wide Fortran community.  The community collaborates on papers, that eventually get submitted to https://j3-fortran.org/. Committee members who have the time participate and help track papers. Those who don't have time don't participate.

* For those members that simply don't have the time to discuss ahead of time at GitHub would simply show up at the J3 meeting in Vegas, as they do now. The J3 / WG5 leadership would ensure that those members are welcomed and encouraged to revisit any discussion that might have happened at GitHub before. Those members can still discuss (and shot down) papers as they can now. Those members will not lose anything.

* But all the people who cannot participate in Vegas will gain an (almost) equal place at the table. It's a win / win situation.

If you are busy, you do not need to participate at GitHub. But you should still not be against people who have the time to participate there and you should be encouraging them to participate. 

The goal should be to include everyone who wants to help. Both people who have busy day jobs as well as people who have more time. Remember that there are a lot of people who want to help (and are already helping at GitHub), but cannot come to a week long meeting (for financial or time reasons). At the same time there are many experts at the Committee who have a very busy day job and don't have time to work between meetings. We should include all.

> > * we will have to build a community again there --- it was a *lot* of work that I and others had to put into the J3 GitHub site. Somebody will have to put in the same amount of work to make it a success.
> 
> No.  You just put a message on the current GitHub saying that the 
> project has moved, and click here to go there.  Same community. No new 
> building.  Just one click. 

Unfortunately this move would almost for sure reduce our momentum. Some people would move, but not all. 
I expect to lose lots (but not all) of the smaller contributions from new people that we currently have at GitHub. In the best case scenario we can keep the momentum, but I doubt it. Our goal should be to keep our momentum at maximum.

Ondrej