-
Notifications
You must be signed in to change notification settings - Fork 28
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
Unify AGL&AGLFN, glyphNameFormatter and GlyphsInfo licenses #5
Comments
This was referenced Sep 25, 2019
@twardoch Given the minimal changes, your suggestion works for this repository. |
@cjchapman please could you make this change? Or would you prefer a PR to make it? :) |
@davelab6 – please go ahead and submit a PR for the change. You can mark me for review (@cjchapman is no longer at Adobe). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I’d like to propose that AGL&AGLFN, glyphNameFormatter and GlyphsInfo adopt the same license text, the "BSD 3-Clause Revised License", unified in the way that I’m proposing below.
AGLFN
Currently, https://github.com/adobe-type-tools/agl-aglfn/blob/master/aglfn.txt is licensed under the "BSD 3-Clause Revised License" as follows (it mentions "Adobe" explicitly in the 3rd clause):
glyphNameFormatter
Currently, https://github.com/LettError/glyphNameFormatter is licensed also under the "BSD 3-Clause Revised License". Virtually identical to Adobe’s, but uses the generic "copyright holder" in 3rd clause.
GlyphsInfo
Currently, https://github.com/schriftgestalt/GlyphsInfo is licensed under the "MIT License":
Suggestion
If possible, I’d like to suggest that all three projects change their license as follows:
Then followed by this identical text:
Effectively:
We’d gain from this that all three projects would have an identical license, so any composite data made from those projects could simply be credited as:
plus potential additional contributors, followed by the same text.
I think this would simplify things a lot.
The text was updated successfully, but these errors were encountered: