-
Notifications
You must be signed in to change notification settings - Fork 29
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
zenodo: more author metadata, and ccp-petmr community #391
Conversation
@KrisThielemans regarding
|
Codecov Report
@@ Coverage Diff @@
## master #391 +/- ##
=======================================
Coverage 50.05% 50.05%
=======================================
Files 2 2
Lines 1720 1720
=======================================
Hits 861 861
Misses 859 859 Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #391 +/- ##
==========================================
- Coverage 50.64% 50.17% -0.48%
==========================================
Files 2 2
Lines 1629 1720 +91
==========================================
+ Hits 825 863 +38
- Misses 804 857 +53
Continue to review full report at Codecov.
|
Unrelated, but how did Johannes get an 'X' in his ORCID? I checked and it links correctly. |
lol I noticed that |
response from Zenodo support:
|
Currently, our license still has to be GPL 3 due to use of FFTW. can we say something like "GPL 3, but most parts also licensed as Apache 2.0"? |
@casperdcl I actually cannot see |
no but we can leave it as the default (Other - Open)
good point, neither can I when I access the API. Sent a follow-up to Zenodo. They must have some weird caching issues. |
NB: You might have to accept #392 before this PR |
Good spot, done. |
@paskino you may want to check this file to find out author details |
Follow-up from Zenodo:
|
Some quick edits on a cluster or another computer perhaps? I've had similar experiences when making edits on the cluster and no email was set, GitHub doesn't associate the commits with my account. You can modify these with |
my first thought was that github is a bit silly but I then realised that the commiter email is probably the only way they can do this. After all, you can have lots of local commits made by lots of different people, which then one github user pushes. Those commits should not be assigned to the github user of course. Therefore, github has to look at git content, which stores We cannot fix this as it'd mean invalidating all commits since then (replacing them with new ones), so we'll live with it. Moral of the store: be careful how you do your @casperdcl please thank your zenodo contact. Very helpful! |
added my orcid and changed UCL to full name
Apache-2.0Other (for now, until GPL from FFTW is removed)