Organization-specific code

[HendrikTolman-NOAA]

Many of our community maintain code inside the WW3 repository. Simplifying the core WW4 repository would benefit from separating organization-specific code in separate repositories. The disadvantage of this is that individual organizations will not have a “one-stop-shop”. How should we approach organization-specific code in WW4?

[JessicaMeixner-NOAA]

Some examples from other repositories:
https://github.com/CICE-Consortium/CICE/tree/main/cicecore and https://github.com/mom-ocean/MOM6/tree/main/config_src/drivers

have code sectioned off into separate folders.

So this could potentially be that separate folders could be used for example:

└── src
    ├── ww4_core
    ├── ww4_utils 
    └── ww4_progs
    └── external_drivers
        └── nuopc
        └── oasis

External drivers would potentially need to have a different testing strategy because of the required external dependency, but I'd suggest trying to have that live within the code. That being said I think things like the, OASIS, ESMF or other components, etc should not live in the WW4 repository or it's tests.

[JessicaMeixner-NOAA]

Some of the switches within the code itself in WW3 -- we should work to not have to have those (ie where we have NCO switches, etc).