Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Make sure all science capability you want to preserve is tested. 
    1. run_acme script, for example.
    2. You can't have the assumption that infrastructure doesn't change
  2. Slack messaging service is very valuable for informal communications: Chat for ACME
  3. CMDV Software: Please consider investing time in the SE Learning initiative of Mike Heroux and sub-component test of Anshu Dubey.
  4. SE Team scope: have no expectation that we know anything about climate
  5. Documentation on software and best coding practices is on our roadmap.Not "Unit testing" but "sub-component testing".   Have some volunteers, would like more.

Highlights of meeting:

  1. Good revamp of SE roadmap
  2. CIME 5 complete rewrite is HUGE step forward for our infrastructure
    1. Python
    2. Deep expertise
  3. CIME Collaboration with CSEG going very well: win-win
  4. First JIRA Deep dive meeting made encouraging progress

...