https://github.com/CCPPETMR/SIRF/pull/391
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
@KrisThielemans regarding foobar2016
previously appearing in Zenodo:
Merging #391 into master will not change coverage.
The diff coverage isn/a
.
@@ 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.
Merging #391 into master will not change coverage.
The diff coverage isn/a
.
@@ 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.
—
@ashgillman pushed 1 commit.
—
You are receiving this because you are subscribed to this thread.
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:
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 projectHow the user ended up there I didn't have time to look into yet.
@KrisThielemans pushed 1 commit.
—
You are receiving this because you are subscribed to this thread.
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 foobar2016
on our list of contributors. (Indeed, that user has no contributions to any repo anywhere). mystery.
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 pushed 1 commit.
—
You are receiving this because you are subscribed to this thread.
@ashgillman pushed 1 commit.
—
You are receiving this because you are subscribed to this thread.
NB: You might have to accept #392 before this PR
@paskino you may want to check this file to find out author details
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 <m...@example.com>Why GitHub is associating the GitHub user
foobar2016
with Evgueni Ovtchinnikov <m...@example.com>, I don't know. Perhaps because of the email address "m...@example.com" being used?
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 "m...@example.com"
and also user.name
.
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!
@casperdcl pushed 1 commit.
—
You are receiving this because you are subscribed to this thread.
Merged #391 into master.