Hi all - The CF Governance Panel discussed DOIs during our last meeting. Mainly for reasons of greatly simplified future access/maintenance, we believe CF should use the GitHub/Zenodo integration to create a CF DOI(s). Here is a summary of the discussion:
> The CF DOI discussion focused on the possible mechanisms for minting CF DOIs: > 1) the use of GitHub/Zenodo integration, or 2) a particular institution's DOI > minting capabilities. We settled on using GitHub/Zenodo because of the > greatly simplified future maintenance (it would use existing CF GitHub > permissions). It also minimizes any appearance or implication that the DOI > minting institution in any way "owns" CF. The main down side of using the > GitHub/Zenodo approach is that we lose control over the DOI landing page. > However, maintainability and simply having a DOI that can be cited were seen > as much more important than the details of the landing page If there is further discussion, please comment on this issue. If there are no objections, we can start/continue planning for implementation. -- Reply to this email directly or view it on GitHub: https://urldefense.us/v3/__https://github.com/cf-convention/cf-conventions/issues/127*issuecomment-1085035774__;Iw!!G2kpM7uM-TzIFchu!grWhUbCVzp6DPAbjyI0c3ZRG_1spyIfHholttpu62tjtY7SnzzD0GEPSYBoHh-_mtmVNV2uD2-U$ You are receiving this because you commented. Message ID: <cf-convention/cf-conventions/issues/127/[email protected]> This list forwards relevant notifications from Github. It is distinct from [email protected], although if you do nothing, a subscription to the UCAR list will result in a subscription to this list. To unsubscribe from this list only, send a message to [email protected].
