Change license to Apache 2.0.
Mailing list discussion was here: https://groups.google.com/forum/#!topic/redo-list/wLMZMxtn4wo Several more contributors replied to me personally to say that they don't have a problem with the change (and several consider the change to be an improvement). The overwhelming majority of everything in the redo repo was written by me, so I have the right to change the license unilaterally anyway, subject to a few rules. Since the new license actually removes licensing/usage restrictions for everyone, this should be no problem.
This commit is contained in:
parent
3b305edc7e
commit
4008ce4a91
3 changed files with 224 additions and 484 deletions
|
|
@ -1,10 +1,14 @@
|
|||
# License
|
||||
|
||||
My version of redo was written without ever seeing redo code by Bernstein or
|
||||
Grosskurth, so I own the entire copyright. It's distributed under the GNU
|
||||
LGPL version 2. You can find a copy of it in the file called LICENSE.
|
||||
Grosskurth, so I own the entire copyright. It's distributed under the terms
|
||||
of the [Apache License 2.0](https://www.apache.org/licenses/LICENSE-2.0),
|
||||
which you can find in the file called
|
||||
[LICENSE](https://github.com/apenwarr/redo/tree/master/LICENSE). (Previous
|
||||
versions of redo were distributed under the GNU LGPL, but this [changed in
|
||||
2018](https://groups.google.com/forum/#!topic/redo-list/wLMZMxtn4wo).)
|
||||
|
||||
minimal/do is in the public domain so that it's even easier
|
||||
minimal/do is in the public domain so that it's as easy as possible
|
||||
to include inside your own projects for people who don't
|
||||
have a copy of redo.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue