Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

do we still need codemeta.json? #127

Closed
jspaaks opened this issue Apr 13, 2021 · 3 comments
Closed

do we still need codemeta.json? #127

jspaaks opened this issue Apr 13, 2021 · 3 comments
Assignees
@jspaaks
Labels
template Related to the template itself, as opposed to the generated code

Comments

@jspaaks
Copy link

jspaaks commented Apr 13, 2021

We have the CITATION.cff, and it may be difficult to keep codemeta up to date with CITATION.cff and .zenodo.json (the consistency of the latter two is ensured by the workflow that PR #123 adds)
@fdiblen fdiblen added this to the 0.3.0 milestone Apr 13, 2021
@fdiblen
Copy link
Member

fdiblen commented Apr 13, 2021

We decided to keep CITATION.cff only.

@jspaaks
Copy link
Author

jspaaks commented Apr 13, 2021

and .zenodo.json

@jspaaks jspaaks self-assigned this Apr 13, 2021
@jspaaks jspaaks mentioned this issue Apr 13, 2021
Merged
@jspaaks jspaaks added the template Related to the template itself, as opposed to the generated code label Apr 14, 2021
@jspaaks
Copy link
Author

jspaaks commented Apr 14, 2021

PR was merged, closing

@jspaaks jspaaks closed this as completed Apr 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jspaaks jspaaks

Labels
template Related to the template itself, as opposed to the generated code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fdiblen @jspaaks