...
Planned ocean developments should be communicated to the Omega group leadership
Ecosystem projects that need features before the delivery of Omega should develop in fortran and utilize MPAS-Ocean
All ecosystem features must be developed as ‘stealth features’, which means they go into the code as off and the model must be shown as BFB with the current code.
Ecosystem project teams must follow full procedure for stealth features defined hereE3SM Code Review and New Feature Process (documentation and testing)
Design doc required
For all features a 10-year fully coupled simulation is required
For features that change the climate when enabled, a 100-year coupled run is required.
The E3SM project will be responsible for the final merge to E3SM master, however, ecosystem projects are responsible for creating bug fix PRs for features not officially supported by the E3SM project.
Longer term developments should move to C++
Possibility to develop ecosystem wide hackathons to train up staff in C++/YAKL
The same comment about being a stealth feature applies to C++ developments
The default position of the E3SM project will be to not officially support new ecosystem developments.
This means that there will be no guarantee from the E3SM project that new code developments will be compatible with the E3SM code long term.
The E3SM project may decided to officially support new features at its discretion.
Only features officially supported by the E3SM project will be ported to Omega
...