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.

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

Add a CITATION.cff file #448

Open
gregcorbett opened this issue Mar 31, 2023 · 4 comments
Open

Add a CITATION.cff file #448

gregcorbett opened this issue Mar 31, 2023 · 4 comments
Labels
enhancement good first issue Issues that require "minimal" knowledge of the codebase hackathon Issues that could be solved within a day

Comments

@gregcorbett
Copy link
Member

Add this may also be a timely oppurtunity to remove authorship info from individual files, and let the CITATION.cff file and commit history provide that info.

@gregcorbett gregcorbett added enhancement good first issue Issues that require "minimal" knowledge of the codebase hackathon Issues that could be solved within a day labels Mar 31, 2023
@GRyall
Copy link
Contributor

GRyall commented Mar 31, 2023

good in theory - but the commit history does not cover all authorship. GocDB was previously maintained on SVN and the history from then was not imported. I agree we do not need it on every file, but we should acknowledge authorship that predates the use of git.

@davidmeredith
Copy link
Contributor

good in theory - but the commit history does not cover all authorship. GocDB was previously maintained on SVN and the history from then was not imported. I agree we do not need it on every file, but we should acknowledge authorship that predates the use of git.

Thank you George for your consideration !

@GRyall
Copy link
Contributor

GRyall commented Apr 11, 2023

Long time no see @davidmeredith - I hadn't realised you also haunt the GOCDB repo like me!

@tofu-rocketry
Copy link
Member

Authorship info in individual files is a terrible way to track it. In many cases, the files have been subsequently edited without the headers being changed so the info is incomplete and therefore wrong.

Also bear in mind that the vast majority of work on GOCDB has been carried out during paid employment of UKRI and its predecessors, so individual authorship in those cases is a nice-to-note, not a legal necessity. The only non-UKRI staff contributions will have been after the code was added to Git, won't they?

So, I say, go for it. We can create a list of historic (i.e. pre-git) contributors separately to the actual code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement good first issue Issues that require "minimal" knowledge of the codebase hackathon Issues that could be solved within a day
Projects
None yet
Development

No branches or pull requests

4 participants