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.

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

Project Licence #4

Open
mjakeman opened this issue Dec 25, 2021 · 1 comment
Open

Project Licence #4

mjakeman opened this issue Dec 25, 2021 · 1 comment
Labels
question Further information is requested
Milestone

Comments

@mjakeman
Copy link
Owner

While the application itself is likely to be GPL-3.0 by the time of the first release, I'd like to allow use of the text engine under a more permissive license.

The two main contenders for licensing are:

  • LGPL-3.0: Can use the library for any type of application, as long as the end user has the freedom to re-link with a modified version of the library. Source code must be provided.
  • MPL-2.0: Basically the above, with an exception for static linking.

Given that we're based on glib, which itself is LGPL, I'm not sure there's all that much benefit to using MPL-2.0. An additional upside of LGPL is we could then reuse code from GTK and/or Lasem.

@mjakeman mjakeman added this to the v0.1.0 milestone Dec 25, 2021
@mjakeman mjakeman added the question Further information is requested label Dec 25, 2021
@mjakeman
Copy link
Owner Author

mjakeman commented Feb 5, 2022

The text engine component of bluetype has been split-off into mjakeman/text-engine, which is available under the MIT licence. Going forward, bluetype will likely be GPL3+.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant