Menu
▾
▴
matplotlib-devel
|
From: Thomas C. <tca...@gm...> - 2014-08-24 01:42:22
|
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 tca...@gm... |
|
From: Benjamin R. <ben...@ou...> - 2014-08-24 17:50:09
|
+1 On Sat, Aug 23, 2014 at 9:42 PM, 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. > > Any other thoughts? > > Tom > > -- > Thomas Caswell > tca...@gm... > > > ------------------------------------------------------------------------------ > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
|
From: Yaron de L. <jd...@gm...> - 2014-08-25 05:39:57
|
+1 from me too On 24 August 2014 20:49, Benjamin Root <ben...@ou...> wrote: > +1 > > > On Sat, Aug 23, 2014 at 9:42 PM, 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. >> >> Any other thoughts? >> >> Tom >> >> -- >> Thomas Caswell >> tca...@gm... >> >> >> ------------------------------------------------------------------------------ >> Slashdot TV. >> Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/ >> _______________________________________________ >> Matplotlib-devel mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> > > > > ------------------------------------------------------------------------------ > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > |
|
From: Tobias S. <tob...@gm...> - 2014-08-26 20:07:02
|
Hi Thomas! Can you send out the DOI once you have it? -Tobias |
|
From: Thomas C. <tca...@gm...> - 2014-08-26 21:01:25
|
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 > |
|
From: Benjamin R. <ben...@ou...> - 2014-08-26 21:09:21
|
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 <tca...@gm...> 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" <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 >> > > > ------------------------------------------------------------------------------ > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > |
|
From: Thomas C. <tca...@gm...> - 2014-08-26 21:23:15
|
https://zenodo.org/record/11451#.U_z6ckREvfQ 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...@ou...> 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 <tca...@gm...> 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" <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 >> >> >> >> ------------------------------------------------------------------------------ >> Slashdot TV. >> Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/ >> _______________________________________________ >> Matplotlib-devel mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> > -- Thomas Caswell tca...@gm... |
|
From: Nathaniel S. <nj...@po...> - 2014-08-26 21:59:25
|
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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X