JOSE review (@mjanuario)

[JessicaBolin]

Hi @JessicaBolin ,

Nice work on the workshop materials. I've completed my review for now, and any unchecked items on my checklist indicate a need for additional work. Feel free to refer to my own repo for examples of how I addressed software release, archiving, and other publication requirements: https://github.com/mjanuario/evolved

To summarize the main points:

• Create a formal release of the workshop. The repository should include a GitHub release (e.g., using the Releases feature): https://github.com/JessicaBolin/esmRworkshop_notes/releases
• Archive the workshop in a permanent repository. JOSE’s policy is not 100% clear if this is a must, but here is github’s instruction on how to do it as linked in JOSE site: https://guides.github.com/activities/citable-code/ . I archived mine using Zenodo, which is free to the point I remember.
• State the target audience in the "Statement of Need" section. This would help communicate more clearly who the workshop is intended for. A short sentence is enough for me.
• Reference issues I've found and should flag for the editor:
* I could not find the reference for Halpin et al. (2014).
* Kellie, D., & Westgate appears to be a website post rather than a formal publication. I'm not sure whether JOSE accepts this type of source as a reference, so I will flag it for the editor to consider.

Originally posted by @mjanuario in #377

[JessicaBolin]

Thank you for your thoughtful comments and suggestions. We've addressed each comment below in bold italicized text. Please let us know if anything requires clarification.

Create a formal release of the workshop. The repository should include a GitHub release (e.g., using the Releases feature): https://github.com/JessicaBolin/esmRworkshop_notes/releases

• Agreed, this is a great suggestion. We've created a Github release here: https://github.com/JessicaBolin/esmRworkshop_notes/releases/tag/v1.0.1

Archive the workshop in a permanent repository. JOSE’s policy is not 100% clear if this is a must, but here is github’s instruction on how to do it as linked in JOSE site: https://guides.github.com/activities/citable-code/ . I archived mine using Zenodo, which is free to the point I remember.

• Thank you for providing the instructions and your example repo! We’ve now archived the workshop using Zenodo: https://zenodo.org/records/21249373.

State the target audience in the "Statement of Need" section. This would help communicate more clearly who the workshop is intended for. A short sentence is enough for me.

• Agreed and the other reviewer also raised this point. We have incorporated the following sentence into the statement of need section: "This workshop is designed for marine ecologists with basic or no prior experience in climate modeling who want to incorporate Earth System Model outputs into their own ecological research using R, and no prior experience with climate modeling, Earth System Models, or Bash/shell scripting is assumed."

Reference issues I've found and should flag for the editor:
I could not find the reference for Halpin et al. (2014).
Kellie, D., & Westgate appears to be a website post rather than a formal publication. I'm not sure whether JOSE accepts this type of source as a reference, so I will flag it for the editor to consider.

• We have removed both of these references from the paper.

[mjanuario]

Good job @JessicaBolin and co-authors!