Re: [libreplanet-discuss] Code license principles in academic publications?

[Pen-Yuan Hsing]

On 08/06/17 06:30, amunizp wrote:
> El 7 de junio de 2017 21:02:46 GMT+01:00, Pen-Yuan Hsing 
> <penyuanhsing@gmail.com> escribió:
> > Dear libreplanet-discuss,
> >
> > I have been asked to comment on a draft article about best
> > practices/principles in publishing academic computer code (e.g.
> > scientific R scripts, Python code, etc.).
> >
> > Though the article is supposed to be short, I think a huge glaring
> > problem in this draft is that software licenses are not mentioned AT
> > ALL.
> >
> > Obviously one comment I'll add is that it is crucial for code to be
> > free
> > (as in freedom) and that a license needs to be attached to its
> > publication.
> >
> > That said, I'm just wondering if anyone has already written about this
> > and if I can refer to it? Ideally something that lays out the basic
> > steps of attaching a software license?
> >
> > Sorry I've only got about 32 hours to respond, so would really
> > appreciate any of your suggestions!
> >
> > _______________________________________________
> > libreplanet-discuss mailing list
> > libreplanet-discuss@libreplanet.org
> > https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
>
> One thing to look out for, I guess, is what licence is the journal released 
> under. It cc-by-sa 4.0 I think you will have the journal to back you up.
>
> Normally code (and data) should be attached to paper. But in the past this has 
> not been done and only nice reviewers such as your self has asked for it. So 
> thank you.

Thanks Andres for your encouragement. I indeed try to "spread the word" 
as much as I can in academic circles. Unfortunately you'll be surprised 
at the resistance to free software even in academia... The concerns are 
sometimes different, but the proprietary result is sadly the same.

I've tried to address them as much as I can in my comments. We'll see 
what they say!