Creating a Codemeta JSON file #676
Conversation
I put some of the data for funding agencies in a little ahead of time, but decided to do it now since I was able to look things up. The NASA HDEE and NSF CSSI proposals are currently pending. I started working on PlasmaPy through a DOE grant, and also did some work through an internal Smithsonian Institution grant.
namurphy
added
status: nearing completion
Availability
needs changelog entry
|
The codemeta standard is still relatively new and will probably evolve, so we should make sure to check before each release to make sure the standard hasn't changed. We might want to add a separate issue to add in all of the contributors. Hopefully, metadata in codemeta.json will be able to be read in by Zenodo to autofill a bunch of the things, like the list of contributors. |
| "isAccessibleForFree": true, | ||
| "issueTracker": "https://github.com/PlasmaPy/plasmapy/issues", | ||
| "readme": "https://github.com/PlasmaPy/PlasmaPy/blob/master/README.md", | ||
| "developmentStatus": "WIP", |
There was a problem hiding this comment.
| "developmentStatus": "WIP", | |
| "developmentStatus": "The WIPpest", |
I added a bit about Codemeta, made a few changes about the Zenodo procedure, and made some formatting changes.
Codecov Report
@@ Coverage Diff @@
## master #676 +/- ##
=======================================
Coverage 95.03% 95.03%
=======================================
Files 58 58
Lines 4674 4674
=======================================
Hits 4442 4442
Misses 232 232Continue to review full report at Codecov.
|
|
Ok, I think that's all that I wanted to include with this one. If it looks good, we can do a squash merge whenever. |
This PR adds a codemeta JSON file that contains the metadata for our project. I created this initially with their online tool (which I had to use Chrome for instead of Firefox; see codemeta/codemeta.github.io#18), and added terms from the codemeta schema to my heart's content. Things I still need to do are:
Closes #622.