The documentation could be a website, or a PDF or similar document. We should assess the likely longevity of the source and make a decision if we need to make a copy and host it ourselves.
It is also likely that the documentation would need updating. We shouldn't let that process stop us from recommending the documentation as-is: we can note caveats about what is covered in the documentation, and what might be missing.
This issue has been created to try and make sure this process does happen.
In the process of updating the ACCESS-OM2 model run instructions it became apparent that we should make an effort to identify some good (authoritative?) documentation for the model components .
The documentation could be a website, or a PDF or similar document. We should assess the likely longevity of the source and make a decision if we need to make a copy and host it ourselves.
It is also likely that the documentation would need updating. We shouldn't let that process stop us from recommending the documentation as-is: we can note caveats about what is covered in the documentation, and what might be missing.
This issue has been created to try and make sure this process does happen.