Adding some workflows for monthly builds of the paper.

Adding some notes here for context (close if you all have reached a consensus already)

What was done in the past for ISS

• NCAR Technical Note - unclear what the terms are here at least at first glance

What other groups do

Project Pythia

• Apache 2.0 license in the template (commonly used for software at NSF NCAR/UCAR) - https://github.com/ProjectPythia/cookbook-template/blob/main/LICENSE
• More here in the citation info: https://projectpythia.org/cookbook-template/notebooks/how-to-cite.html

US-RSE notebook conference proceedings

• Doesn’t have a license in the template - https://github.com/USRSE/jupyter-notebook-templates/tree/reproducible-publication
• Leaves notebook repos with the original owner (doesn’t attempt to aggregate)

SciPy proceedings (papers, posters, and slides - not notebooks or code)

• Open access with CC BY license and DOIs
  https://github.com/scipy-conference/scipy_proceedings?tab=readme-ov-file#open-access-for-an-open-community

Earthcube notebook conference proceedings

• No license in templates - https://github.com/earthcube/NotebookTemplates
• CC license in Zenodo metadata, but individual and varying licenses in the compiled notebooks - https://github.com/earthcube2022/ec22_book/blob/master/.zenodo.json

Recommendation from the 2024 SEA ISS discussion today.

I want to test on creating issue as the template mentioned from my repository. Did you receive the issue that I just created from my repository?

Since the update of sphinx pythia theme the page build has changed and possibly fail.

From 01-24-2023 meeting: Adding some general guidelines for where to host data.