[J3] Numbering scheme of J3 meetings

Bill Long longb at cray.com
Mon Oct 7 17:38:35 EDT 2019

I suspect the main reason we number the meeting consecutively is that we’ve always done it that was and people are comfortable with the scheme.  And it’s easy to keep track of how many meetings you’ve attended  (for HR reports, for example). And the meeting folder naming is really simple, However, there are practical reasons as well.  INCITS has rules regarding trial meetings and  regular attendance (two out of three consecutive meetings, etc).  If the meetings are numbered consecutively, it is really easy to tell if someone is in violation of the membership attendance rules. Note that the current pattern of 3 meetings each year has not always been the case.   Something like 19.218, 19.219, 19.220, 20,221, … might be an option to consider, but I suspect the simplest option is to do nothing. 


> On Oct 1, 2019, at 2:27 PM, Vipul Parekh via J3 <j3 at mailman.j3-fortran.org> wrote:
> Is there a particular reason for sequential numbering for J3 meetings?
> Do the current numbers e..g, m219 and m220 hold a particular (and
> perhaps sacrosanct) significance?
> Why not number them 19.2, 19.3 (or 19-1, 19-3; or 2019.2, 2019.3;
> etc.), meaning something mnemonic to make it easier to recall and
> relate to the meetings in a given year?
> Same with papers: why 19-227.txt as the next likely paper for the
> upcoming m220 as a continuation of the numbering from prior 2019
> meetings?  Why not 19.3-8.txt to signify 8th paper at the 3rd J3
> meeting in 2019, or some such relatable scheme?
> Vipul Parekh

Bill Long                                                                       longb at cray.com
Principal Engineer, Fortran Technical Support &   voice:  651-605-9024
Bioinformatics Software Development                      fax:  651-605-9143
Cray, a Hewlett Packard Enterprise company/ 2131 Lindau Lane/  Suite 1000/  Bloomington, MN  55425

More information about the J3 mailing list