(j3.2006) CD ballot
Tue Mar 14 14:13:53 EDT 2017
In general, this seems OK.
If Lorri has to generate a file by the 28th, we need to have the final content a couple of days before. To have the final content agreed upon, we need to start the agreement process several days before that.
If the intent is to vote ?yes, with comments?, then all we need are SOME comments. I would suggest that we agree to a relatively small set of technical comments for the ballot. Particularly internal contradictions if there are any. We don?t need to have every comment included in the ballot. If we tried that we would devolve into holding the meeting online and all the votes in the beginning of April rather than in June. Purely editorial stuff can just be in meeting papers for m213. Ditto for a lot of minor quibbles. Or suggestions about rearranging subclauses. For the ballot we need to focus on actual technical errors.
On Mar 14, 2017, at 11:56 AM, Dan Nagle <danlnagle at me.com> wrote:
> I'm negotiating with Debbie to get our deadline extended
> from April 21 to April 28. I'm arguing that the CD is a large
> and complex document.
> The difficulty here is that INCITS is insisting that
> all responses be in a .doc file they provide.
> I know some of our members cannot process such files.
> INCITS doesn't seem to care.
> I propose that we resolve a set of comments, agreed by all
> via email, and the submit one ballot, with all our comments.
> That way, we can comport with INCITS silliness, and only one
> person (hi, Lorri!) needs to process .doc files.
> Other thoughts?
> Dan Nagle
> J3 mailing list
> J3 at mailman.j3-fortran.org
Bill Long longb at cray.com
Fortran Technical Support & voice: 651-605-9024
Bioinformatics Software Development fax: 651-605-9142
Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101
More information about the J3