2019 12 04

2019-12-06 meeting minutes

Attendees:

• Jeff Squyres
• Puri Bangalore
• Martin Rüefenacht

Big topics from today

Jeff/Martin immediate action items

• Jeff to git merge everything back to feat-modern-lang-bindings
• Jeff to fix "make clean" in tools chapter
• Martin+Jeff to finish Pythonizing by Sat evening
• Martin+Jeff to make a pass through of all KINDs with a giant grep/sed:
  • SMALLFOO: "int" size (1 binding)
  • POLYFOO: will be embiggened (2 bindings)
  • FOO: "big" size (1 binding)
• Martin will document how to use the regression tool on the wiki.

Puri action items

Work on embiggening the collectives chapter.

Work on the same branch as pythonizing.

Puri will put the word "BIG" (in all caps) as the first word of each of his embiggening commits so that we can tell them apart from pythonizing commits.

This way, we can rebase / reorder all the embiggening commits and eventually put them on their own branch. But for now, the pythonizing branch is still changing, so it's easier for us all to work together on the same branch.

Sidenote: Let's also try to embiggen pt2pt (Jeff will try to do this in ABQ). That way, in ABQ, we can show both pt2pt and collectives chapters as PDFs.

Martin suggests:

• Interactively convert a Sessions / Partitioned Communication API - show them how it's done
• Suggest that you write the pythonized ones today and comment them out in LaTeX

ABQ planning

Goal: show a "perfect" pythonized document to the Forum next week

• We need to get an "approval" process for acceptable changes vs. v3.1 (e.g., "~" moving, etc.)
• ...put JSON of acceptable changes in git?
  • Martin will play a little bit to try to make a stable output...? Perhaps use OrderedDictionary and make a "false" version of everything first that goes into git.

Points to bring up to the Forum next week:

• Pythonizing plan:

  • You got a perfect 4.0 doc today
  • Chapter authors verify vs. 3.1
  • All feedback due T-3 weeks before Feb meeting (so we have time to fix!)
  • Vote on errata in Feb meeting
  • All future PRs will need to have Pythonized bindings (including v4.0.x bindings!)
    • I'm looking at you, sessions / partitioned communications
    • All existing PRs will likely need to be updated

• Embiggening plan:

  • Text should be all done here in ABQ.
  • Bindings will be done for Feb/Portland.