search

GOCDB / gocdb

Grid Operations Configuration Management Database. A Repository, Portal and REST style API for managing Grid and Cloud topology objects including; projects, administrative domains, sites, services, service-endpoints, service-groups, downtimes, users, roles and business rules.
Apache License 2.0
12 stars 28 forks source link

Add a CITATION.cff file #448

Open gregcorbett opened 1 year ago

gregcorbett commented 1 year ago

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.

GRyall commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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

tofu-rocketry commented 1 year ago

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.