Since CEOS is in the process of implementing digital object identifiers (DOI) for documents and repos like the EO glossary and this governance repo probably qualify as formal documents (and it's possible that other software repos will as well), it might be helpful to provide some guidelines under which a DOI should be assigned to a repo.
Since CEOS has selected Zenodo as its platform for DOI generation, the mechanics of DOI assignment to a repo should be fairly straightforward:
https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content
Since CEOS is in the process of implementing digital object identifiers (DOI) for documents and repos like the EO glossary and this governance repo probably qualify as formal documents (and it's possible that other software repos will as well), it might be helpful to provide some guidelines under which a DOI should be assigned to a repo.
Since CEOS has selected Zenodo as its platform for DOI generation, the mechanics of DOI assignment to a repo should be fairly straightforward:
https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content