...
To use this time optimally, we will gather candidate discussion topics before and at the start of the meeting, then do a prioritization, and then have time-boxed discussions on the high-priority topics.
| Priority | Candidate Discussion Topic | Requestor | More Details; Others can chime in here to modify scope, show support or not, etc. | Notes: |
|---|---|---|---|---|
| 1 | Test Suite Revamp : What do we need to do finish this off. | Balwinder Singh (thank you, thank you) is leading this critical Epic to define a test suite with mostly ultra-low-res grids to get both improved code coverage and faster test throughput. What can the team do to finish this off? | ||
| 2 | How to best support Critical Path Team and Coupled Sim Group? | Michael Deakin (Unlicensed), Jon Wolfe: What should the rest of the SE/CPL + Perf groups know to better support ACME scientists? | ||
| 3 | Is there a better way to solicit/determine requirements for CIME and associated infrastructure? | Philip Jones, Patrick Worley (Unlicensed) (in absentia) | In the recent past, some capabilities have been (inadvertently?) dropped. Related to testing too. | |
| 4 | How can we provide a mechanism for work to move forward without requiring a CIME mod to propagate into the repo? | Philip Jones, Patrick Worley (Unlicensed) (in absentia) | As CIME has become more opaque, it is more difficult to make quick/simple workarounds to keep simulations going while the final fix propagates through the system. Makes James Foucar a single point of failure. | |
| 5 | Upcoming Issues to be ready for: | Andy Salinger | Things we need to be ready for:
|