getting a DOI for v1.4.0

Hey all,

Github has made it possible to get a DOI for a release (
https://guides.github.com/activities/citable-code/ ).

I am inclined to do this for 1.4.0. I think doing this is a good
first step towards being good (leading?) citizens in the reproducible
science community.

Any other thoughts?

Tom

···

--
Thomas Caswell
tcaswell@...149...

+1

···

On Sat, Aug 23, 2014 at 9:42 PM, Thomas Caswell <tcaswell@…149…> wrote:

Hey all,

Github has made it possible to get a DOI for a release (

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

I am inclined to do this for 1.4.0. I think doing this is a good

first step towards being good (leading?) citizens in the reproducible

science community.

Any other thoughts?

Tom

Thomas Caswell

tcaswell@…149…


Slashdot TV.

Video for Nerds. Stuff that matters.

http://tv.slashdot.org/


Matplotlib-devel mailing list

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

+1 from me too

···

On 24 August 2014 20:49, Benjamin Root <ben.root@…553…> wrote:

+1


Slashdot TV.

Video for Nerds. Stuff that matters.

http://tv.slashdot.org/


Matplotlib-devel mailing list

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On Sat, Aug 23, 2014 at 9:42 PM, Thomas Caswell <tcaswell@…149…> wrote:

Hey all,

Github has made it possible to get a DOI for a release (

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

I am inclined to do this for 1.4.0. I think doing this is a good

first step towards being good (leading?) citizens in the reproducible

science community.

Any other thoughts?

Tom

Thomas Caswell

tcaswell@…149…


Slashdot TV.

Video for Nerds. Stuff that matters.

http://tv.slashdot.org/


Matplotlib-devel mailing list

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

FYI, since I just spent half an hour figuring this out:

To use the Zenodo magic DOI feature you have to:

1) Attach Zenodo to the repository like it says in the tutorial.

2) Create a "release" on github, which is *not* the same as a tag,
even though the github UI claims that they are identical. See all of
these releases that are listed on your github releases page?
    https://github.com/matplotlib/matplotlib/releases
None of them are actually releases in the sense that Zenodo wants.

Here's an example of what it looks like after you've made Zenodo happy:
    https://github.com/pydata/patsy/releases

The trick is to click "draft a new release", and then type in the name
of your existing tag. You can add some release notes if desired, which
will be copied to the archived Zenodo page, which will look like this:
   https://zenodo.org/record/11445
(The text "See release notes: <url>" is what I typed into the Github
release description box.) And then click "Publish release" obviously.
This will convert your existing release tag into an *extra-special*
release tag, which AFAICT works the same as before except that (a) it
gets snazzier graphics in the github UI, and (b) Zenodo will archive
it.

-n

···

On Sun, Aug 24, 2014 at 2:42 AM, Thomas Caswell <tcaswell@...149...> wrote:

Hey all,

Github has made it possible to get a DOI for a release (
https://guides.github.com/activities/citable-code/ ).

I am inclined to do this for 1.4.0. I think doing this is a good
first step towards being good (leading?) citizens in the reproducible
science community.

--
Nathaniel J. Smith
Postdoctoral researcher - Informatics - University of Edinburgh
http://vorpus.org

Thanks! This hasn’t been done yet because I was confused by zenodo and hadn’t taken the tune to sort this out.

Tom

···

On Aug 26, 2014 4:54 PM, “Nathaniel Smith” <njs@…503…> wrote:

On Sun, Aug 24, 2014 at 2:42 AM, Thomas Caswell <tcaswell@…149…> wrote:

Hey all,

Github has made it possible to get a DOI for a release (

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

I am inclined to do this for 1.4.0. I think doing this is a good

first step towards being good (leading?) citizens in the reproducible

science community.

FYI, since I just spent half an hour figuring this out:

To use the Zenodo magic DOI feature you have to:

  1. Attach Zenodo to the repository like it says in the tutorial.

  2. Create a “release” on github, which is not the same as a tag,

even though the github UI claims that they are identical. See all of

these releases that are listed on your github releases page?

[https://github.com/matplotlib/matplotlib/releases](https://github.com/matplotlib/matplotlib/releases)

None of them are actually releases in the sense that Zenodo wants.

Here’s an example of what it looks like after you’ve made Zenodo happy:

[https://github.com/pydata/patsy/releases](https://github.com/pydata/patsy/releases)

The trick is to click “draft a new release”, and then type in the name

of your existing tag. You can add some release notes if desired, which

will be copied to the archived Zenodo page, which will look like this:

https://zenodo.org/record/11445

(The text "See release notes: " is what I typed into the Github

release description box.) And then click “Publish release” obviously.

This will convert your existing release tag into an extra-special

release tag, which AFAICT works the same as before except that (a) it

gets snazzier graphics in the github UI, and (b) Zenodo will archive

it.

-n

Nathaniel J. Smith

Postdoctoral researcher - Informatics - University of Edinburgh

http://vorpus.org

In case you weren’t already thinking of this, we might want to update this page:
http://matplotlib.org/citing.html

···

On Tue, Aug 26, 2014 at 5:01 PM, Thomas Caswell <tcaswell@…149…> wrote:

Thanks! This hasn’t been done yet because I was confused by zenodo and hadn’t taken the tune to sort this out.

Tom

On Aug 26, 2014 4:54 PM, “Nathaniel Smith” <njs@…503…> wrote:

On Sun, Aug 24, 2014 at 2:42 AM, Thomas Caswell <tcaswell@…149…> wrote:

Hey all,

Github has made it possible to get a DOI for a release (

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

I am inclined to do this for 1.4.0. I think doing this is a good

first step towards being good (leading?) citizens in the reproducible

science community.

FYI, since I just spent half an hour figuring this out:

To use the Zenodo magic DOI feature you have to:

  1. Attach Zenodo to the repository like it says in the tutorial.

  2. Create a “release” on github, which is not the same as a tag,

even though the github UI claims that they are identical. See all of

these releases that are listed on your github releases page?

[https://github.com/matplotlib/matplotlib/releases](https://github.com/matplotlib/matplotlib/releases)

None of them are actually releases in the sense that Zenodo wants.

Here’s an example of what it looks like after you’ve made Zenodo happy:

[https://github.com/pydata/patsy/releases](https://github.com/pydata/patsy/releases)

The trick is to click “draft a new release”, and then type in the name

of your existing tag. You can add some release notes if desired, which

will be copied to the archived Zenodo page, which will look like this:

https://zenodo.org/record/11445

(The text "See release notes: " is what I typed into the Github

release description box.) And then click “Publish release” obviously.

This will convert your existing release tag into an extra-special

release tag, which AFAICT works the same as before except that (a) it

gets snazzier graphics in the github UI, and (b) Zenodo will archive

it.

-n

Nathaniel J. Smith

Postdoctoral researcher - Informatics - University of Edinburgh

http://vorpus.org


Slashdot TV.

Video for Nerds. Stuff that matters.

http://tv.slashdot.org/


Matplotlib-devel mailing list

Matplotlib-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

And yes, I will create an issue for updating the citation page.

Tom

···

On Tue, Aug 26, 2014 at 5:08 PM, Benjamin Root <ben.root@...553...> wrote:

In case you weren't already thinking of this, we might want to update this
page:
http://matplotlib.org/citing.html

On Tue, Aug 26, 2014 at 5:01 PM, Thomas Caswell <tcaswell@...149...> wrote:

Thanks! This hasn't been done yet because I was confused by zenodo and
hadn't taken the tune to sort this out.

Tom

On Aug 26, 2014 4:54 PM, "Nathaniel Smith" <njs@...503...> wrote:

On Sun, Aug 24, 2014 at 2:42 AM, Thomas Caswell <tcaswell@...149...> >>> wrote:
> Hey all,
>
> Github has made it possible to get a DOI for a release (
> https://guides.github.com/activities/citable-code/ ).
>
> I am inclined to do this for 1.4.0. I think doing this is a good
> first step towards being good (leading?) citizens in the reproducible
> science community.

FYI, since I just spent half an hour figuring this out:

To use the Zenodo magic DOI feature you have to:

1) Attach Zenodo to the repository like it says in the tutorial.

2) Create a "release" on github, which is *not* the same as a tag,
even though the github UI claims that they are identical. See all of
these releases that are listed on your github releases page?
    https://github.com/matplotlib/matplotlib/releases
None of them are actually releases in the sense that Zenodo wants.

Here's an example of what it looks like after you've made Zenodo happy:
    https://github.com/pydata/patsy/releases

The trick is to click "draft a new release", and then type in the name
of your existing tag. You can add some release notes if desired, which
will be copied to the archived Zenodo page, which will look like this:
   https://zenodo.org/record/11445
(The text "See release notes: <url>" is what I typed into the Github
release description box.) And then click "Publish release" obviously.
This will convert your existing release tag into an *extra-special*
release tag, which AFAICT works the same as before except that (a) it
gets snazzier graphics in the github UI, and (b) Zenodo will archive
it.

-n

--
Nathaniel J. Smith
Postdoctoral researcher - Informatics - University of Edinburgh
http://vorpus.org

------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

--
Thomas Caswell
tcaswell@...149...