Closed armaneshaghi closed 9 years ago
Not sure if we should do this or go for a proper publication in JSS or similar. Brian--do you have thoughts?
On 11 February 2015 at 09:44, Arman Eshaghi notifications@github.com wrote:
We could get a DOI for ANTsR and make the whole software citable https://zenodo.org. Objections?
— Reply to this email directly or view it on GitHub https://github.com/stnava/ANTsR/issues/11.
i would prefer to try http://www.jstatsoft.org/
brian
On Wed, Feb 11, 2015 at 9:50 AM, bkandel notifications@github.com wrote:
Not sure if we should do this or go for a proper publication in JSS or similar. Brian--do you have thoughts?
On 11 February 2015 at 09:44, Arman Eshaghi notifications@github.com wrote:
We could get a DOI for ANTsR and make the whole software citable https://zenodo.org. Objections?
— Reply to this email directly or view it on GitHub https://github.com/stnava/ANTsR/issues/11.
— Reply to this email directly or view it on GitHub https://github.com/stnava/ANTsR/issues/11#issuecomment-73892903.
That would be excellent...
Just to add that jss can take a while if you want something in the interim I have used zenodo.org.
Sent from my iPad
On 11 Feb 2015, at 06:44, Arman Eshaghi notifications@github.com wrote:
We could get a DOI for ANTsR and make the whole software citable. Objections?
— Reply to this email directly or view it on GitHub.
interesting comments here: http://robjhyndman.com/hyndsight/jss-rpackages/
another fantastic reference: http://www.sciencedirect.com/science/article/pii/S0167947308001606
My inclination is that it's worth it to do it "properly" and get it up to JSS standards, and then have one unambiguous place to cite, even if it takes a few months more to get out. We've invested enough time in this package that it's worth it to do the "advertising"/taking credit properly.
On 11 February 2015 at 15:58, stnava notifications@github.com wrote:
interesting comments here: http://robjhyndman.com/hyndsight/jss-rpackages/
— Reply to this email directly or view it on GitHub https://github.com/stnava/ANTsR/issues/11#issuecomment-73963364.
agreed ... and it's good to know, now, what the "beyond cran" standards of jss are ....
brian
On Wed, Feb 11, 2015 at 4:04 PM, bkandel notifications@github.com wrote:
My inclination is that it's worth it to do it "properly" and get it up to JSS standards, and then have one unambiguous place to cite, even if it takes a few months more to get out. We've invested enough time in this package that it's worth it to do the "advertising"/taking credit properly.
On 11 February 2015 at 15:58, stnava notifications@github.com wrote:
interesting comments here: http://robjhyndman.com/hyndsight/jss-rpackages/
— Reply to this email directly or view it on GitHub https://github.com/stnava/ANTsR/issues/11#issuecomment-73963364.
— Reply to this email directly or view it on GitHub https://github.com/stnava/ANTsR/issues/11#issuecomment-73964460.
nice blog post for JSS standards, definitely worth the time, I'm sure we will all be learning lots of things in the process (as I have already learned a lot). Am happy to work on this even if it takes a year or so
On Thu, Feb 12, 2015 at 12:34 AM, bkandel notifications@github.com wrote:
My inclination is that it's worth it to do it "properly" and get it up to JSS standards, and then have one unambiguous place to cite, even if it takes a few months more to get out. We've invested enough time in this package that it's worth it to do the "advertising"/taking credit properly.
On 11 February 2015 at 15:58, stnava notifications@github.com wrote:
interesting comments here: http://robjhyndman.com/hyndsight/jss-rpackages/
Reply to this email directly or view it on GitHub https://github.com/stnava/ANTsR/issues/11#issuecomment-73963364.
Reply to this email directly or view it on GitHub https://github.com/stnava/ANTsR/issues/11#issuecomment-73964460.
We could get a DOI for ANTsR and make the whole software citable. Objections?
Step by step guide:
https://guides.github.com/activities/citable-code/