Repository navigation
Delete codemeta.json in favor of CITATION.cff - #1772
Conversation
|
Thank you for contributing to PlasmaPy! The project's future depends deeply on contributors like you, so we deeply appreciate it! 🌱 The following checklist will be used by the code reviewer to help guide the code review process.
|
Codecov ReportBase: 98.36% // Head: 98.36% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #1772 +/- ##
=======================================
Coverage 98.36% 98.36%
=======================================
Files 86 86
Lines 8176 8176
=======================================
Hits 8042 8042
Misses 134 134 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
To make sure it gets included in distributions. I think. (MANIFEST.in files confuse me.)
codemeta.jsoncodemeta.json in favor of CITATION.cff
StanczakDominik
left a comment
There was a problem hiding this comment.
Lovely addition-to-deletion ratio <3
|
If we eventually consider going back to
We probably shouldn't switch again unless we have a good reason to (e.g., a need for fields in CodeMeta that ∄ in CFF or that CodeMeta becomes much more widely used than CFF). |
Right now, we use both
codemeta.jsonandCITATION.cffto include metadata for our project. While CodeMeta and Citation File Format each have useful fields that the other one does not have, it'll be a pain to keep both up-to-date...in particular because the bulk of the information (i.e., the author list) will be duplicated in both. Thinking about the tradeoffs between the two of them,CITATION.cffhas better integration with GitHub and Zenodo, and thus would end up making our lives easier.We could eventually go back to
codemeta.json, especially since there are tools that will do the conversion from CodeMeta → CFF, though I had trouble finding ones that went CFF → CodeMeta and covered all of the fields that we needed and were out of beta.(I do really like the CodeMeta format though, but alas!)