[Mesa-users] Licensing for a GitHub repo of small MESA extensions
aaron.dotter at gmail.com
Fri Oct 20 11:29:36 EDT 2017
Thanks for wanting to share your code and for thinking about the best way
to do it. mesa-users doesn't have many lawyers among the subscribers (that
I know of!) so you may not get a conclusive answer.
MESA is under LGPL v2.1 and there are some GNU-centric thoughts about
various open-source licenses here:
On Fri, Oct 20, 2017 at 11:20 AM, Warrick Ball <wball at bison.ph.bham.ac.uk>
> Hi everyone,
> I've been sitting on a bunch of minor modifications I've made to my
> versions of MESA and, in the spirit of MESA, I ought to make them
> available. I've set up a GitHub repo for the files with small
> modifications and was intending to distribute them as the minimum files
> that have to be replaced in a MESA work folder (or, later, the trunk) for
> my changes to function.
> I was about to select a licence and realised that I might need to be
> careful about which I select. I will be uploading modified versions of
> some MESA source files (e.g. stuff in $MESA_DIR/star/astero/work and more
> later) so some of that code is really the work of the MESA devs.
> I would instinctively go with the MIT Licence but thought I should check
> among the community, council and devs what the right thing to do is.
> PS: If you need an example to make things clearer, one change I once
> implemented was a way for the `from_file` search option in the astero
> module to restart from a file. My plan was to upload a few modified
> Fortran files from star/astero/src and a modified makefile to compile them
> in the work folder. (The compiling thing just involves pointing to the
> modified files in the work folder rather than those in the trunk.)
> Warrick Ball
> Postdoc, School of Physics and Astronomy
> University of Birmingham, Edgbaston, Birmingham B15 2TT
> wball at bison.ph.bham.ac.uk
> +44 (0)121 414 4552
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mesa-users