The ocean model grid generator subproject

[ngs333]

Enhancing NCTools with the Ocean Model Grid Generator subproject.

This is some of the decisions and issues so far.

I) The subproject will be a fork of Nikis Zadehs own repository (https://github.com/nikizadehgfdl/ocean_model_grid_generator) and the fork will be under the github NOAA-GFDL organization (https://github.com/NOAA-GFDL).

II) Updating the fork from the upstream.
a) It is possible to do this manually or with a github action. Advantages and disadvantages?

III) Nikis existing project under NOAA-GFDL.
Coincidentally, a fork already exists (https://github.com/nikizadehgfdl/ocean_model_grid_generator/network/members)
It is possible to use this fork if the user permissions are appropriate, or we can create another (preferably deleting this fork first to reuse the default name)

IV) Clone location in NCTools
The location of the clone can be the github default, which is
a directory with the name of the repository (ocean_model_grid_generator)
placed immediately under the FRE-NCtools main directory. An alternative is to
have one extra subdirectory under NCTools and the grid generator and future subprojects are placed there.

V) Installations at GFDL managed sites.
Is it desired that the executable of the ocean model grid generator project be installed at the GFDL managed sites along with NCTools apps or binaries? Which are installed, for example, under /home/fms/local/opt/fre-nctools/bronx-18).

[ngs333]

Update from meeting on 7/20 Rusty and Miguel.
IV) Clone location in NCTools
The preferred location of the OMGR its own directory under FRE-NCTools/tools
V) We should treat is as a regular NCTools tool as much as possible ( See IV), including for installation and testing, etc)
II)Updating the fork from upstream
See if triggered updates are possible.
I) Seth U. and Tara will have ability to change ownership, members, etc. Verify or experiment.