We (CCT Data Science) typically like to archive code on Zenodo at the close of a project to get a DOI. Zenodo DOIs are versioned though, and we don't necessarily need to wait until the end. Having a DOI also makes it easy to reference in code-availability statements and the like. I suggest we get an initial DOI for this code even if we end up continuing work here (i.e. rather than starting a new repo(s) for additional work in EcosystemEcologyLab/AZ-AGB-trend#3, #30, etc.). What do you think @KristinaRiemer, @davidjpmoore ?
We (CCT Data Science) typically like to archive code on Zenodo at the close of a project to get a DOI. Zenodo DOIs are versioned though, and we don't necessarily need to wait until the end. Having a DOI also makes it easy to reference in code-availability statements and the like. I suggest we get an initial DOI for this code even if we end up continuing work here (i.e. rather than starting a new repo(s) for additional work in EcosystemEcologyLab/AZ-AGB-trend#3, #30, etc.). What do you think @KristinaRiemer, @davidjpmoore ?