search

IGITUGraz / spore-nest-module

Synaptic Plasticity with Online Reinforcement learning
https://igitugraz.github.io/spore-nest-module/
GNU General Public License v2.0
25 stars 11 forks source link

Make SPORE citable #14

Closed mhoff closed 6 years ago

mhoff commented 7 years ago

As of this tutorial, GitHub repositories can be turned into DOI references using zenodo.

For this, I think the repository owner (IGITUGraz) has to allow zenodo to access its data.

@anandtrex Could you give that a look? If so, I would also like to assist you in this.

anandtrex commented 7 years ago

I have given Zenodo access to this repository. Now if you create a new release on github it should automatically assign a DOI according to their documentation.

mhoff commented 7 years ago

Good. Seems like we all can access the zenodo interface with our individual accounts as we are members of the organization.

Do we have to recreate 2.12.0 now? Can we even recreate a release (for the same commit) without breaking something (like rendering the old URL invalid)?

kappeld commented 7 years ago

No. Please don't create a new release for the same commit. This really would not make sense and is just confusing. If there is no alternative solution, we can just make a 2.12.1 with some bug fixes later next week or so (I already found some small bugs but I have to test my fixes before I commit).

mhoff commented 7 years ago

I was only considering deleting & creating again the exact release we had before to trigger the web-hook. As a release is essentially context information for an existing tag, this might be possible without any interference. However, I did not find any statements proving this hypothesis. Hence, I would agree to play safe and wait for 2.12.1.

kappeld commented 7 years ago

A NEST 2.12.1 release seems to be on its way according to: https://github.com/nest/nest-simulator/pull/739#pullrequestreview-42235591

I guess we best wait until this release is out and then issue our corresponding 2.12.1 to stay in synch with the version number of NEST.

mhoff commented 6 years ago

Just for future reference: NEST decided to skip 2.12.1 and to create a proper 2.14.0 release before NEST 3.0.

I just checked the Zenodo page and it seems like we are indeed all set up to create a release (at least in terms of this issue).

Closing the issue.