search

vermaseren / form

The FORM project for symbolic manipulation of very big expressions
GNU General Public License v3.0
1.13k stars 135 forks source link

FORM DOI? #229

Open tueda opened 7 years ago

tueda commented 7 years ago

In future we could have a DOI for FORM?

https://guides.github.com/activities/citable-code/

See also a talk in ACAT 2017:

https://indico.cern.ch/event/567550/contributions/2696191/

vermaseren commented 7 years ago

Hi Takahiro,

Looks very interesting. We can do this when you are back.

Also this JOSS journal looks good.

Cheers

Jos

On 25 aug. 2017, at 20:50, Takahiro Ueda notifications@github.com wrote:

In future we could have a DOI for FORM?

https://guides.github.com/activities/citable-code/ https://guides.github.com/activities/citable-code/ See also a talk in ACAT 2017:

https://indico.cern.ch/event/567550/contributions/2696191/ https://indico.cern.ch/event/567550/contributions/2696191/ — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/229, or mute the thread https://github.com/notifications/unsubscribe-auth/AFLxEqvSBDjycZ4_HNpZgnI20XEz59c5ks5sbxeJgaJpZM4PDCWb.

benruijl commented 6 years ago

Jos, could you please register the DOI by following the instructions in Takahiro's link? Takahiro and I cannot do that ourselves (and we need it for our proceedings).

vermaseren commented 6 years ago

I am trying to make this DOI, but I get an error message when confirming my email account.

Like this

× https://zenodo.org/confirm/WyIzODE5MSIsImY3MjYyMzQ1NzI4N2EyZTRlNjAyZjVmZWZlM2NiNDRkIl0.DOTOwA.NiPbOy6Rv9VskM-cXEca9hb5Ck4#Thank you. Your email has been confirmed. Home https://zenodo.org/ Change password Internal server error Error identifier: 64ac747b40754c448038871d39b66d63

On 8 nov. 2017, at 16:21, Ben Ruijl notifications@github.com wrote:

On the one hand it says that it has been confirmed, but when I go to my profile it says it hasn’t.

Jos

Jos, could you please register the DOI by following the instructions in Takahiro's link? Takahiro and I cannot do that ourselves (and we need it for our proceedings).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/229#issuecomment-342850243, or mute the thread https://github.com/notifications/unsubscribe-auth/AFLxElnJF-MeLrQEz8Z8VwBl994PBGIfks5s0ccKgaJpZM4PDCWb.

vermaseren commented 6 years ago

OK, you may call me stupid, but I follow the instructions and it does not work. Probably I miss something, but I do not see what.

Cheers

Jos

On 8 nov. 2017, at 18:26, Jos Vermaseren t68@nikhef.nl wrote:

I am trying to make this DOI, but I get an error message when confirming my email account.

Like this

× https://zenodo.org/confirm/WyIzODE5MSIsImY3MjYyMzQ1NzI4N2EyZTRlNjAyZjVmZWZlM2NiNDRkIl0.DOTOwA.NiPbOy6Rv9VskM-cXEca9hb5Ck4#Thank you. Your email has been confirmed. Home https://zenodo.org/ Change password Internal server error Error identifier: 64ac747b40754c448038871d39b66d63

On 8 nov. 2017, at 16:21, Ben Ruijl <notifications@github.com mailto:notifications@github.com> wrote:

On the one hand it says that it has been confirmed, but when I go to my profile it says it hasn’t.

Jos

Jos, could you please register the DOI by following the instructions in Takahiro's link? Takahiro and I cannot do that ourselves (and we need it for our proceedings).

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/229#issuecomment-342850243, or mute the thread https://github.com/notifications/unsubscribe-auth/AFLxElnJF-MeLrQEz8Z8VwBl994PBGIfks5s0ccKgaJpZM4PDCWb.

tueda commented 6 years ago

The tag should be v4.2.1 (or v4.3.0), not 4.2.0.0, if you really want to make a minor release, right?

vermaseren commented 6 years ago

My idea was that 4.2.0.0 is not a real release and hence 4.2.1 would put it put of the books by the time we have something real.

But I got nothing to work.

Jos

On 8 nov. 2017, at 18:37, Takahiro Ueda notifications@github.com wrote:

The tag should be v4.2.1 (or v4.3.0), not 4.2.0.0, if you really want to make a minor release, right?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/229#issuecomment-342895035, or mute the thread https://github.com/notifications/unsubscribe-auth/AFLxEhB6fjGAL9yQRD6R3uTI9F6lRS8Jks5s0ebOgaJpZM4PDCWb.

tueda commented 6 years ago

When you push a tag to the Github, automatically it does mean a real release. Actually, we now have

FORM 4.2.0 (Oct 26 2017, 4.2.0.0) 64-bits        Run: Wed Nov  8 17:29:44 2017

in https://travis-ci.org/vermaseren/form/jobs/299215545.

tueda commented 6 years ago

Well, if you don't get anything to work, maybe we could remove the release 4.2.0.0 (with breaking the repository history a bit), before someone tries to pull or updates the FORM version in Wikipedia to 4.2.0.0...

tueda commented 6 years ago

When you push a tag to the Github, automatically it does mean a real release.

I'm a bit confused. I think the tag 4.2.0.0 should be filtered out from the version determination and the version must be still 4.2.0 (from the tag v4.2.0)... https://github.com/vermaseren/form/blob/954024f163e8d702e1f28c1dd99846c08b0333f8/scripts/git-version-gen.sh#L101

vermaseren commented 6 years ago

OK, Should I try to remove it (it did not work after all), or can you do that? (with less chance of errors).

Jos

On 8 nov. 2017, at 18:53, Takahiro Ueda notifications@github.com wrote:

When you push a tag to the Github, automatically it does mean a real release.

I'm a bit confused. I think the tag 4.2.0.0 should be filtered out from the version determination and the version must be still 4.2.0 (from the tag v4.2.0)... https://github.com/vermaseren/form/blob/954024f163e8d702e1f28c1dd99846c08b0333f8/scripts/git-version-gen.sh#L101 https://github.com/vermaseren/form/blob/954024f163e8d702e1f28c1dd99846c08b0333f8/scripts/git-version-gen.sh#L101 — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/229#issuecomment-342899789, or mute the thread https://github.com/notifications/unsubscribe-auth/AFLxEocY36PMy3FOIhNbAqXIdUMsSJn9ks5s0eqIgaJpZM4PDCWb.

tueda commented 6 years ago

OK. (Oct 26 2017, 4.2.0.0) means that just git describe gives the latest tag name 4.2.0.0, and this is not necessarily the recognized version number.

tueda commented 6 years ago

@vermaseren I will try to remove it.

vermaseren commented 6 years ago

Thanks

Jos

On 8 nov. 2017, at 18:58, Takahiro Ueda notifications@github.com wrote:

@vermaseren https://github.com/vermaseren I will try to remove it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/229#issuecomment-342901391, or mute the thread https://github.com/notifications/unsubscribe-auth/AFLxEscqGeswKv1d2jG5w8SGY4gil0UXks5s0eu6gaJpZM4PDCWb.

tueda commented 6 years ago

I have deleted the release page and corresponding tag for 4.2.0.0.

tueda commented 6 years ago

If we'd like to get a DOI via a release on GitHub, maybe DOI acquisition could be postponed to a patch release containing the current unreleased fixes. Maybe it is good to have such a release before developing/merging the diagrams branch, because it may take a long time. Hopefully at some point in this year or early next year? I think it will be very great if we could also fix some very severe bugs like #14 and #95 in the release.