Spack: Relicense Spack from LGPL-2.1 to MIT/Apache-2.0

Created on 31 Aug 2018 · 39Comments · Source: spack/spack

Summary

We are working to change the license for Spack from the current LGPL-2.1 license , to a dual license under the widely-accepted and common MIT License and the Apache License, version 2.0, so that users may choose the appropriate license for them.

Why MIT / Apache-2.0?

We want to make this change so that Spack can be used as widely as possible. At many organizations, it is difficult or cumbersome to use LGPL-licensed packages, but a number of those organizations have expressed interest in contributing to Spack. The Apache 2.0 license contains important protection against patent aggression, but it is not compatible with the GPL, version 2. The MIT license allows Spack to be integrated with GPLv2 projects. We believe that this combination will appeal to the broadest possible base of users and contributors, and that it will enable us to grow the Spack community most effectively.

What do contributors need to do?

We are asking for permission from all contributors to change the Spack license from LGPL-2.1 to a dual MIT/Apache 2.0 license for their past contribution(s).

If you agree to have all the code that you have contributed to Spack be relicensed in this way, please copy the message below, fill in the blanks with the email addresses you used to contribute to Spack, and paste it either:

into a comment on Spack issue https://github.com/spack/spack/issues/9137, or
into an email to [email protected]

A note on emails: You only need to post emails that appear in the Spack history. To get these, clone https://github.com/spack/spack.git and use git log to see what emails you should use. For example, Todd Gamblin appears in the logs in the following ways:

$ git clone https://github.com/spack/spack.git
$ cd spack
$ git log --format='"%an" %ae' | grep -i Gamblin | sort | uniq
"George Todd Gamblin" [email protected]
"Todd Gamblin" [email protected]
"Todd Gamblin" [email protected]

You may want to search for your name and <your github username>@noreply.github.com, and any other names you've used. We just need enough to associate your consent with your contributions.

Here is the message text:

My name is _________________________, and I am a contributor to Spack. I have used or may have used the following email address(es): ______________________________. I consent to change the current license contained in the License file at https://github.com/spack/spack/blob/develop/LICENSE from the LGPL-2.1 license to the MIT License and Apache License 2.0 with respect to all of my contributions to Spack.

By granting this permission, you are confirming that you have the right to make your contribution(s) to Spack and to grant this permission, and that if you made your contribution(s) in the course of your employment, that such contributions and consent have been authorized by your employer.

If we do not hear from you, we will assume that you do not consent to the relicensing and we will not relicense your contribution(s).

Discussion

If you have any questions or concerns, please raise them by commenting on issue #9145. We have made a separate issue to avoid notification spam for participants. We will try our best to respond promptly!

We are grateful to all the contributors who have contributed to Spack and look forward to their help and support in this effort!

Thanks!

relicense

Source

tgamblin

🎉1

Most helpful comment

Hi all, here is an update on the state of Spack relicensing:

We have all the consents we need to relicense the entire Spack core (134 consents!)
We have consents covering *2,815 out of 2,877 packages (333 consents!)*

So, we're nearly done. Thanks to everyone who has commented or emailed so far! I initially had doubts whether we'd be able to do this at all, but with your help we've been able to get nearly all of the consents in what I think is a remarkably short period of time.

At this point, we are going to go forward with relicensing the core and most of the packages. You should expect that to happen in the next couple of weeks. We will change the LICENSE and COPYRIGHT files, as well as file headers for all the files we have consent for. We will also change the CONTRIBUTING file to indicate the new license for inbound code.

If you have not commented or emailed yet, but you intend to, please do so as soon as you can. We would like to include as many packages as possible in the switchover, so see the top this page (https://github.com/spack/spack/issues/9144) for instructions. We will initially leave LGPL packages in the repo, but eventually we will either remove or rewrite them so that Spack is 100% Apache2/MIT.

Thanks again for helping this tedious process go so smoothly, and thanks to everyone for your many contributions to Spack!

If your name is in the list below, we still need consent for your contributions to the packages listed:

[ ] @AP97 (farmhash)
[x] @YtterbiJum (tmux)
[x] @adamqc (petsc)
[x] @alcharal (abyss)
[x] @bilke
[x] @christianbaensch (suite-sparse)
[x] @clementval (claw)
[x] @DDevHan (canu, pacvim)
[x] @disheng222 (sz)
[x] @edoapra (nwchem)
[x] @f-sim (fenics)
[x] @g-mathias (libmatheval)
[x] @glentner (hadoop)
[x] @isu-rassilon (gapfiller)
[x] @iulian787 (cgm, meshkit, moab, netgen, oce)
[x] @jack-morrison (gdb, hadoop)
[x] @jasonfenglu (py-yt, py-h5py)
[x] @jimmy04500 (charmpp)
[ ] @jlingema
[x] @jmjwozniak (adlbx, exmcutils, stc, turbine)
[x] @kylefernandes (intel-daal, intel-ipp, intel-mkl, intel-mpi, intel-parallel-studio, intel)
[x] @mdevlin1 (libxsmm, libxstream, hmmer)
[x] @mikedep333 (gcc)
[x] @moxcodes
[ ] @peetsv / @23skdu (dialign-tx, igv, lftp, nextflow, perl-file-copy-recursive, perl-xml-libxml, py-cnvkit, py-crossmap, py-pybedtools, py-pyfaidx, py-pysam, py-pyvcf, py-vmd-python, r-cghflasso, r-dismo, r-proc, r-spatial, r-utf8, rsync, sniffles, vardictjava, viennarna)
[x] @rajeeja (meshkit)
[x] @raznikk (bamtools)
[x] @rbrts (py-ase, visit)
[x] @rice31 (py-pyyaml)
[x] @simonflood (ants, hmmer, trinity)
[x] @thecorkscrew (c-lime)
[x] @TheQueasle
[x] @ursache (plumed)
[x] @zepx (glog)

tgamblin on 3 Oct 2018

👍5 🎉3