kframework / k-legacy

The K tools (deprecated, see README)
http://kframework.org
Other
146 stars 61 forks source link

LICENSE.md too complicated and hard to maintain #1136

Open grosu opened 9 years ago

grosu commented 9 years ago

Do we really need to list all those software at the bottom of the LICENSE.md page? Some of those are probably part of K modules that have either disappeared or will disappear from the kernel. Also, we say:

The K software contains code written by third parties. Such software will have its own individual
LICENSE file in the directory in which it appears.

So then, why bother listing all the following on the main License page?


The following pieces of software have additional or alternate copyrights, licenses, and/or restrictions:

Maude (http://maude.cs.uiuc.edu) is licensed under the GPL license.

Stratego (http://strategoxt.org) is licensed under the LGPL license.

Xstream (http://xstream.codehaus.org/) is licensed under the BSD license.

XML Pull (http://www.xmlpull.org) API is free.

Xpp3 (http://www.extreme.indiana.edu/xgws/xsoap/xpp) is licensed under Indiana University Extreme! Lab Software License.

KXML2 (http://kxml.sourceforge.net/kxml2/) is licensed under the BSD license.

SSCTarjan (https://github.com/indy256/codelibrary) is licensed under the Unlicense. Alphanum (http://www.davekoelle.com/alphanum.html) is licensed under the LGPL license.


I would indeed make sure that the licenses of these software are included in the directories where they are used, and then replace the last section of the K License with the following simpler paragraph:

The K software may contain code written by third parties. Such software will have its
own individual LICENSE file in the directory in which it appears.  The disclaimer of
warranty in the University of Illinois Open Source License applies to all code in the K
Distribution, and nothing in any of the other licenses gives permission to use the names
of the institutions or companies forming the K Team to endorse or promote products
derived from this Software.

Since we are at this, I would also change the paragraph above,

Neither the names of the K Team, the University of Illinois at Urbana-Champaign, the
University Alexandru-Ioan Cuza, nor the names of its contributors may be used to
endorse or promote products derived from this Software without specific prior written
permission.

which does not mention RV anyway, as follows:

Neither of the names of the institutions or companies forming the K Team, nor the
names of its contributors may be used to endorse or promote products derived from
this Software without specific prior written permission.

@dwightguth feel free to change the above however you wish to make it all sound good.

dwightguth commented 9 years ago

Oncall should probably go through this and update the license so that we are complying with all the open source licenses that we import in this project. Basically that means picking through every transitive dependency and making sure that LICENSE.md contains any information which the license in question requires us to replicate.