-
Notifications
You must be signed in to change notification settings - Fork 165
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
Change license from GPL-2 to something more permissive #308
Comments
12 tasks
The |
andreasabel
added a commit
that referenced
this issue
Nov 23, 2020
The license is found in the LICENSE file.
andreasabel
added a commit
that referenced
this issue
Nov 23, 2020
Also add command-line options --help and --license. The latter prints the license text, which is verbatim the content of the LICENSE file.
andreasabel
added a commit
that referenced
this issue
Nov 23, 2020
Also: new option --license to print the LICENSE text.
andreasabel
added a commit
that referenced
this issue
Nov 23, 2020
andreasabel
added a commit
that referenced
this issue
Nov 23, 2020
andreasabel
added a commit
that referenced
this issue
Nov 24, 2020
2.9.0 has been released under BSD 3-clause. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BNFC currently is licensed under GPL-2 which is a bit strict and excludes e.g. industrial users from using the sample grammars (and even the
bnfc
tool) in closed-source projects.The following list serves to organize the process and can be extended with new information.
TODO:
* Decide whom to send this email (even 1-patch contributors? --- some did not even leave their real name).
* For git developers, https://github.com/BNFC/bnfc/blob/master/.mailmap might help.
* Collect emails of older developers.
The text was updated successfully, but these errors were encountered: