Re: [matplotlib-devel] getting a DOI for v1.4.0

[Thomas C. <tca...@gm...>]

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" <nj...@po...> wrote:

> On Sun, Aug 24, 2014 at 2:42 AM, Thomas Caswell <tca...@gm...>
> 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
>