Update codemeta.json for version 0.4.0 and related release guide instructions #902
Conversation
This field is might not be able to be updated before the release is uploaded to PyPI or Zenodo. The DOI makes it findable enough anyway.
Codecov Report
@@ Coverage Diff @@
## master #902 +/- ##
=======================================
Coverage 96.21% 96.21%
=======================================
Files 60 60
Lines 5414 5414
=======================================
Hits 5209 5209
Misses 205 205 Continue to review full report at Codecov.
|
- Add newer versions of Python - Remove google group as email address of developers
|
So I guess |
codemeta.json
Outdated
| "@type": "SoftwareSourceCode", | ||
| "license": "https://spdx.org/licenses/BSD-2-Clause-Patent", | ||
| "codeRepository": "https://github.com/PlasmaPy/plasmapy", | ||
| "contIntegration": "https://dev.azure.com/plasmapy/PlasmaPy/_build/results?buildId=1733&view=results", |
There was a problem hiding this comment.
Do we want this to point to that particular build (PR 900)?
There was a problem hiding this comment.
And this, my friend, is why we do code review!
| "identifier": "http://doi.org/10.5281/zenodo.4037407", | ||
| "description": "An open source Python package for plasma research and education", | ||
| "applicationCategory": "Plasma Physics", | ||
| "developmentStatus": "wip", |
Co-authored-by: Dominik Stańczak <[email protected]>
If I'm remembering correctly, Cross-reference: #628, zenodo/zenodo#1504, codemeta/codemeta#213 |
Codemeta is an emerging open metadata standard for storing information about software packages. This PR updates our
codemeta.jsonfile to be consistent with our version 0.4.0 release, and also adds the author list. I'm hoping this will (eventually) alleviate some of the tedious aspects of uploading releases to Zenodo.One continual worry though is that we have some of the same data in different places that will need to be updated simultaneously during releases. I'm wondering if we could generate the author list that goes in the documentation from
codemeta.json, or do other similar things. But, that's for another day (or more likely, for another year).