Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Relicensing Permission #1570

Closed
samth opened this issue Jan 10, 2017 · 336 comments
Closed

Relicensing Permission #1570

samth opened this issue Jan 10, 2017 · 336 comments
Assignees
@samth

Comments

@samth
Copy link
Sponsor Member

samth commented Jan 10, 2017 •
edited
Loading

We (the core team) are planning to relicense Racket and its standard
libraries under a permissive license (MIT and Apache v2). Since Racket
contains contributions from hundreds of people, we need permission
from people who have contributed. If you've contributed code or
documentation to Racket at any point, we would like to get your
permission. You can do that by replying to me by email, or at this
GitHub issue: #1570

Why switch from the LGPL?

First, making Racket available under a more permissive license will
allow Racket to be used in more contexts and by more people -- one of
our most important goals. In particular, some organizations cannot use
GPL-variant licenses, including the LGPL as used by Racket.

Second, the LGPL is tricky to apply to Racket. The Racket compiler
combines the program and the standard library via cross-module
inlining, as well as inserting the results of macro expansion into the
resulting compiled output. This makes it unclear if the entire
resulting program is a derived work of the standard library. Also, the
mechanisms for linking in Racket can make shipping Racket executables
that comply with the license difficult, as described in the license
page.

Third, the LGPL version 2 which we use does not provide patent
protection, and the LGPL v3 which does has other issues.

What license are we switching to?

We plan to switch to dual-license under the Apache License, version 2 and the MIT license. The MIT license is extremely permissive
and compatible with almost everything, while the Apache license has
patent protection and is compatible with other software already
distributed under the Apache license. This is also the combination
chosen by the Rust project.

What repositories does this cover?

We plan to relicense the code distributed with the Racket distribution. That includes everything depended upon by the main-distribution package. Generally, anything in the racket organization on GitHub is included in this.

When will this change happen?

In the near term, we only plan to release the Racket code under a
different license. Because the C code is linked with multiple existing
libraries that are licensed under the LGPL (such as Lightning and
GMP), the C code in Racket will continue to be distributed under the
LGPL v2.

However, we plan to make this change eventually for all code, so we
are asking for all past and future contributions to be licensed
under the new pair of licenses.

I hope to complete the process for the Racket code in the next two
release cycles (six months).

How are you collecting permission?

Either via email to me (samth@racket-lang.org) or at this GitHub
issue.

Please tell me any names and any email addresses that you may have
contributed to Racket (or PLT Scheme) under.

What if I don't agree?

We hope that everyone will agree, but we can't be sure of it, nor can
we guarantee that we will be able to contact everyone. For people who
do not respond to direct contact, we will treat that as agreement in
most cases. If you explicitly do not agree, we will try to work
something out so that the re-licensing can go forward while respecting
your copyright.

What if I think we should do something different?

Please, let us know. We are not lawyers, and we're happy to hear
suggestions for other ways we can accomplish the goals mentioned
above.
@samth samth changed the title License Relicensing Permission Jan 10, 2017
@samth
Copy link
Sponsor Member Author

samth commented Jan 10, 2017

I, Sam Tobin-Hochstadt, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses samth@ccs.neu.edu, samth@racket-lang.org, samth@cs.indiana.edu, samth@indiana.edu, sam@alumni.uchicago.edu, sam@uchicago.edu

@jeapostrophe
Copy link
Collaborator

I, Jay McCarthy, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses jay.mccarthy@gmail.com, jay@cs.brown.edu, jay@cs.byu.edu, jay@kenyamountain.com, jay@racket-lang.org, jay@plt-scheme.org

@sstrickl
Copy link
Contributor

I, Stevie Strickland, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses sstrickl@ccs.neu.edu, sstrickl@racket-lang.org, sstrickl@plt-scheme.org. (I believe these are all the email addresses with which I've contributed to Racket, if others are found let me know and I'll give permissions for those commits as well.)

@florence
Copy link
Contributor

I, Spencer Florence, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses florence@ccs.neu.edu, spencer@florence.io

@nadeemabdulhamid
Copy link
Contributor

I, Nadeem Abdul Hamid, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses nadeem@acm.org, nhamid@berry.edu.

@jbclements
Copy link
Collaborator

jbclements commented Jan 10, 2017 via email

@tonyg
Copy link
Member

tonyg commented Jan 10, 2017

Ugh. I object to the term "permissive licence": a better term is "user-hostile licence". You can probably infer lots of other reckons from just that, so I'll leave it there. That said, this is a drop in the bucket as far as times being generally tough for end-users of software, and not a hill I'd choose to die on; therefore:

I, Tony Garnock-Jones, give permission to license my contributions to Racket under MIT/Apache 2. I've used or may have used the email addresses tonyg@ccs.neu.edu, tonygarnockjones@gmail.com and tonyg@leastfixedpoint.com. Like Stevie says, there may be others; let me know if I've missed any, and I'll give permission for those commits too.

What is the scope of the permission you are requesting? I assume, in the permission statement I make just above, that it is only meant to cover (portions of) the code in the main "racket" git repo (and its git history). Is anything further intended for inclusion? I'm probably happy to extend my statement accordingly if so, but please do let us all know specifically what the scope is to be.

@samth
Copy link
Sponsor Member Author

samth commented Jan 10, 2017

@tonyg This is intended to cover all the code currently in the racket organization, or any other repository that's a dependency of the main-distribution Racket package. I'll clarify this in the issue.

@bennn
Copy link
Contributor

bennn commented Jan 10, 2017 •
edited
Loading

I, Ben Greenman, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses benjaminlgreenman@gmail.com, types@ccs.neu.edu

MIT:

Copyright 2014–2017 Ben Greenman Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Apache 2

Copyright 2014–2017 Ben Greenman Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License.  You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  See the License for the specific language governing permissions and limitations under the License.

@stamourv
Copy link
Contributor

I, Vincent St-Amour, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses stamourv@racket-lang.org stamourv@ccs.neu.edu

@mfelleisen
Copy link
Collaborator

I, Matthias Felleisen, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses matthias@cs.rice.edu, matthias@rice.edu,, matthias@racket-lang.org, matthias@plt-scheme.org, matthias@ccs.neu.edu.

@mflatt
Copy link
Member

mflatt commented Jan 10, 2017

I, Matthew Flatt, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses mflatt@racket-lang.org, mflatt@plt-scheme.org, mflatt@cs.utah.edu, matthew.flatt@gmail.com

@samth
Copy link
Sponsor Member Author

samth commented Jan 11, 2017 •
edited
Loading

The following people have contributed on GitHub to some of the Racket repositories.

@alehed
@mafagafogigante
@jackfirth
@khinsen
@acarrico
@bluerider
@e45lee
@cordarei
@BartAdv
@hoelzro
@bon
@Metaxal
@jamessan
@davidtpierson
@kimmyg
@filonenko-mikhail
@jcwhittier
@arkadini
@RayRacine
@jaor
@shofetim
@4z3
@jacones
@ds26gte
@pnwamk
@btlachance
@miraleung
@projanen
@lyons
@LeiWangHoward
@david-vanderson
@lvilnis
@schuster
@cky
@frenchy64
@gcr
@offby1
@jsmaniac
@simmone
@mordae
@telephil
@jkominek
@philnguyen
@RenaissanceBug
@calvis

@samth
Copy link
Sponsor Member Author

samth commented Jan 11, 2017

Also these people:

@dfeltey
@wilbowma
@sctb
@rhcarvalho
@dvanhorn
@SamB
@greghendershott
@juanfra684
@gmarceau
@mbutterick
@97jaz
@AlexKnauth
@lexi-lambda
@soegaard
@sbloch
@LeifAndersen
@Zoetermeer
@ntoronto
@paddymahoney
@dyoo
@jspiro
@maxsnew
@bdj
@stchang
@bfetscher
@ghcooper
@gus-massa
@kathryngray
@carl-eastlund
@clklein
@mikesperber
@kazzmir
@tewk
@takikawa
@rmculpepper
@rfindler
@elibarzilay

@97jaz
Copy link
Contributor

97jaz commented Jan 11, 2017

I, Jon Zeppieri (@97jaz), give permission to license my contributions to Racket under MIT/Apache 2. I've used the email address zeppieri@gmail.com.

@kazzmir
Copy link
Contributor

kazzmir commented Jan 11, 2017

I, Jon Rafkind, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses jon@rafkind.com, rafkind@cs.utah.edu, rafkind@racket-lang.org

@gcr
Copy link
Contributor

gcr commented Jan 11, 2017 •
edited
Loading

I, @gcr, give permission to license my contributions to Racket under MIT/Apache 2. I've used gcr@sneakygcr.net.

@shofetim
Copy link
Contributor

I, Jordan Schatz, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses jordan@noionlabs.com, shofetim@gmail.com & white.armor@gmail.com

@hoelzro
Copy link
Contributor

hoelzro commented Jan 11, 2017

I, Rob Hoelz (@hoelzro), give permission to license my contributions to Racket under MIT/Apache 2. I've used rob AT hoelz.ro.

@jkominek
Copy link
Contributor

I, Jay Kominek, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email address kominek@gmail.com

@jcwhittier
Copy link
Contributor

I, J.C. Whittier (@jcwhittier), give permission to license my contributions to Racket under MIT/Apache 2.

@RenaissanceBug
Copy link
Contributor

I, Jordan Johnson (@RenaissanceBug), give permission to license my contributions to Racket under MIT/Apache 2. I've used the email address accounts@fellowhuman.com.

@pnwamk
Copy link
Member

pnwamk commented Jan 11, 2017 •
edited
Loading

I, Andrew M. Kent (@pnwamk), give permission to license my contributions to Racket under MIT/Apache 2. I may have used the following email addresses while contributing: pnwamk@gmail.com, andmkent@iu.edu, andmkent@indiana.edu, sgtamk@gmail.com, andmkent@racket-lang.org

@lexi-lambda
Copy link
Member

lexi-lambda commented Jan 11, 2017 •
edited
Loading

I, Alexis King, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses lexi.lambda@gmail.com and jaking@cj.com.

@wargrey
Copy link
Contributor

wargrey commented Jan 11, 2017

I, WarGrey Ju(@wargrey), give permission to license my contributions to Racket under MIT/Apache 2. I've used the email address: juzhenliang@gmail.com.

@jaor
Copy link
Contributor

jaor commented Jan 11, 2017

I, Jose Antonio Ortega Ruiz (@jaor) give permission to license my contributions to Racket under MIT/Apache 2. I've used the email address jao@gnu.org.

@AlexKnauth
Copy link
Member

I, Alexander Knauth, give permission to license my contributions to Racket under MIT and Apache 2. I've used alexander at knauth dot org.

@samth
Copy link
Sponsor Member Author

samth commented Nov 4, 2019 •
edited
Loading

We're still looking for signoffs from the following people:

@jshelley-xx
@weskerfoot
@bon
@dbenoit17
@earldean
@tkoehlmann
@JohnCGriffin
@jeanniet13
@hopkinsr
@markfarrell
@mkeyhani

@weskerfoot
Copy link

I Wesley Kerfoot, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email address wjak56@gmail.com

@samth samth mentioned this issue Nov 4, 2019
Merged
@earldean
Copy link

earldean commented Nov 5, 2019 •
edited
Loading

I, Earl Dean, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email addresses earldean@me.com.

@jshelley-xx
Copy link

jshelley-xx commented Nov 5, 2019 via email

@samth samth mentioned this issue Nov 7, 2019
Merged
@otherjoel
Copy link
Sponsor Contributor

I, Joel Dueck, give permission to license my contributions to Racket under MIT/Apache 2. I've used the email address joel@jdueck.net .

@samth
Copy link
Sponsor Member Author

samth commented Nov 18, 2019

This is now done. Thanks to everyone who helped and to everyone who gave permission. See the LICENSE file in this repository or the blog post at https://blog.racket-lang.org/2019/11/completing-racket-s-relicensing-effort.html for more details.

@mordae
Copy link
Contributor

mordae commented Nov 18, 2019 •
edited
Loading

Late to the party.
I, Jan Hamal Dvořák (formerly Jan Dvořák), give permission to license my contributions to Racket under MIT/Apache 2. I might have used the email addresses mordae@anilinux.org, mordae@mordae.eu and jan.dvorak@techlib.cz.

@alshopov
Copy link
Contributor

alshopov commented Nov 18, 2019 via email

@samth
Copy link
Sponsor Member Author

samth commented Nov 18, 2019

@alshopov

The git history in the string-constants repository is complete, even though it's truncated in this repository.

The original author of the Russian & Ukranian translation is Sergey Semerikov, email semerikov@gmail.com. The original author of the Korean translation is Jae sung Chung. I've emailed both of them, but haven't heard back. The original authors of the Spanish and Dutch translations are unknown -- the commits were done by @rfindler but he doesn't have the emails from then.

My current plan was to maintain the LGPL for those four files, and any new translations based on those files. An alternative would be to re-do the work by those committers, but that would likely require a full re-translation for each of those languages. That seems impractical for these languages since most of those have seen few contributions other than the original author. If, however, you want to do this for one of those languages I'd be very happy about that.

@ssemerikov
Copy link

  1. I, Sergey Semerikov, give permission to license my contributions to Racket under MIT/Apache.
  2. I've used the email addresses semerikov@gmail.com.

samth added a commit to racket/string-constants that referenced this issue Jan 14, 2020
@samth
Sergey Smerikov replied giving permission.
4e84272 
See racket/racket#1570.
@xxxserxxx xxxserxxx mentioned this issue Feb 15, 2020
Closed
@sirinath sirinath mentioned this issue Feb 19, 2020
Closed
@donm donm mentioned this issue Apr 13, 2020
Closed
@abattery
Copy link

I Jae Sung Chung, give permission to license my contributions to Racket
under MIT/Apache 2. I've used the email addresses abattery@gmail.com

@jieungkim
Copy link

I Jieung Kim, give permission to license my contributions to Racket
under MIT/Apache 2. I've used the email addresses je1004k@gmail.com

@samth
Copy link
Sponsor Member Author

samth commented May 26, 2020

Thank you, @abattery and @jieungkim. Are you the only two contributors to the Racket Korean translation?

mfelleisen pushed a commit to racket/racket-lang-org that referenced this issue May 28, 2020
@samth @mfelleisen
Blog post on new license.
f9e34f8 
Closes racket/racket#1570.
@willghatch willghatch mentioned this issue Mar 9, 2021
Closed
@woodrush woodrush mentioned this issue Jan 16, 2022
Open
samth added a commit to samth/math that referenced this issue May 31, 2022
@samth
Correct license information.
b544bd8 
The code in these packages was intended to be relicensed in 2019
with the rest of Racket (see racket/racket#1570). However, these
files were not changed due to an oversight.

Also, mention the dependence of "math-lib" on two LGPL libraries
which are distributed separately.

Also, correct the discussion about the license of some old Fortran
code.
@samth samth mentioned this issue May 31, 2022
Merged
samth added a commit to samth/math that referenced this issue Jun 7, 2022
@samth
Correct license information.
be009ac 
The code in these packages was intended to be relicensed in 2019
with the rest of Racket (see racket/racket#1570). However, these
files were not changed due to an oversight.

Also, mention the dependence of "math-lib" on two LGPL libraries
which are distributed separately.

Also, correct the discussion about the license of some old Fortran
code.
samth added a commit to racket/math that referenced this issue Jun 7, 2022
@samth
Correct license information.
19dfe71 
The code in these packages was intended to be relicensed in 2019
with the rest of Racket (see racket/racket#1570). However, these
files were not changed due to an oversight.

Also, mention the dependence of "math-lib" on two LGPL libraries
which are distributed separately.

Also, correct the discussion about the license of some old Fortran
code.
@eudoxia0 eudoxia0 mentioned this issue Feb 7, 2023
Closed
@LiberalArtist LiberalArtist mentioned this issue Mar 25, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@samth samth

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests