Missing Zenodo community and Codemeta informations for ESCAPE

In order to complete the on-boarding of gammapy on the ESCAPE platform several actions are required :

• edit the Zenodo entry to add it on ESCAPE 2020 community see https://escape2020.pages.in2p3.fr/wp3/ossr-pages/page/contribute/publish_overview/ : “Edit your project on Zenodo. Under “Communities” search for “ESCAPE 2020” and add it. Save the record. This will trigger the curation process to the OSSR.” Who can do this ? @Bultako, @adonath, @registerrier, @bkhelifi

• on zenodo the codemeta.json should be also uploaded outside of the zip file as in this example: https://zenodo.org/record/5972794#.YinUQhPMI6h

• the codemeta.jon should include informations about funder and funding grant as in the example below (from https://zenodo.org/record/5972794#.YinUQhPMI6h)

  "funder":[
    {
      "@type": "Organization",
      "name": "European Commission",
      "@id": "https://doi.org/10.13039/501100000780"
    }
  ],
  "funding": "824064",

could this be also included to the CITATION.cff or have to be added after conversion to codemeta.json ?

• the validity of the .json file should be verified with the eossr codemeta validator: https://escape2020.pages.in2p3.fr/wp3/eossr/docstring_sources/eossr_cli/eossr-metadata-validator.html could this be added to the workflow of #3833 ?

[vuillaut]

gammapy is now fully onboarded

[vuillaut]

In order to complete the on-boarding of gammapy on the ESCAPE platform several actions are required :

• on zenodo the codemeta.json should be also uploaded outside of the zip file as in this example: https://zenodo.org/record/5972794#.YinUQhPMI6h

This is not necessary anymore. Just add a codemeta.json to your repository and continue with the GitHub-Zenodo integration as usual.