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

zenodo: more author metadata, and ccp-petmr community #391

Merged
merged 8 commits into from
Aug 29, 2019
Merged

Conversation

casperdcl
Copy link
Member

@casperdcl casperdcl commented May 22, 2019

@casperdcl
Copy link
Member Author

casperdcl commented May 22, 2019

@KrisThielemans regarding foobar2016 previously appearing in Zenodo:

  1. it's no longer an issue if we're specifying authors in a metadata file
  2. apparently it's likely because a contributor used to have that username
  3. author lists are generated based on https://github.com/CCPPETMR/SIRF/graphs/contributors

@casperdcl casperdcl self-assigned this May 22, 2019
@casperdcl casperdcl added this to the v2.0 milestone May 22, 2019
@codecov
Copy link

codecov bot commented May 22, 2019

Codecov Report

Merging #391 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ea4a56f...0314fff. Read the comment docs.

@codecov
Copy link

codecov bot commented May 22, 2019

Codecov Report

Merging #391 into master will decrease coverage by 0.47%.
The diff coverage is n/a.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
src/xGadgetron/pGadgetron/Gadgetron.py 47.13% <0%> (-0.89%) ⬇️
src/xSTIR/pSTIR/STIR.py 52.83% <0%> (-0.09%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8ff0bea...f124e74. Read the comment docs.

@ashgillman
Copy link
Member

Unrelated, but how did Johannes get an 'X' in his ORCID? I checked and it links correctly.

@casperdcl
Copy link
Member Author

lol I noticed that

@casperdcl
Copy link
Member Author

casperdcl commented May 23, 2019

response from Zenodo support:

You can see the code that does the extraction here: https://github.com/inveniosoftware/invenio-github/blob/master/invenio_github/utils.py#L80-L108 

I've tried to debug it, and I've traced the foobar2016 to this GitHub API response:

https://api.github.com/repos/CCPPETMR/SIRF/stats/contributors
(https://developer.github.com/v3/repos/#list-contributors)
forbar2016 is listed there as having 3 contributions to the project

How the user ended up there I didn't have time to look into yet.

@KrisThielemans
Copy link
Member

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"?

@KrisThielemans
Copy link
Member

@casperdcl I actually cannot see foobar2016 on our list of contributors. (Indeed, that user has no contributions to any repo anywhere). mystery.

@casperdcl
Copy link
Member Author

can we say something like "GPL 3, but most parts also licensed as Apache 2.0"?

no but we can leave it as the default (Other - Open)

I actually cannot see foobar2016 on our list of contributors

good point, neither can I when I access the API. Sent a follow-up to Zenodo. They must have some weird caching issues.

casperdcl added a commit that referenced this pull request May 23, 2019
@ashgillman
Copy link
Member

NB: You might have to accept #392 before this PR

@rijobro
Copy link
Contributor

rijobro commented May 24, 2019

NB: You might have to accept #392 before this PR

Good spot, done.

@casperdcl
Copy link
Member Author

@paskino you may want to check this file to find out author details

@casperdcl
Copy link
Member Author

Follow-up from Zenodo:

I apologise, I sent the wrong [...] URL. The URL is https://api.github.com/repos/CCPPETMR/SIRF/contributors (without stats) [...] which includes foobar2016.

[...] you can see the commits here:
https://api.github.com/repos/CCPPETMR/SIRF/commits?author=foobar2016
Specifically [...]:
ddc363c
18b7e18
819d8a1
[...] authored by:
Evgueni Ovtchinnikov <me@example.com>

Why GitHub is associating the GitHub user foobar2016 with Evgueni Ovtchinnikov <me@example.com>, I don't know. Perhaps because of the email address "me@example.com" being used?

@ashgillman
Copy link
Member

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
git config --global user.email "me@example.com" and also user.name.

@KrisThielemans
Copy link
Member

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 user.email and user.name for each commit. Makes sense.

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 git config!

@casperdcl please thank your zenodo contact. Very helpful!

@KrisThielemans KrisThielemans modified the milestones: v2.0, v2.1 Jun 18, 2019
@casperdcl casperdcl merged commit f124e74 into master Aug 29, 2019
@casperdcl casperdcl deleted the zenodo branch August 29, 2019 15:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants