licensing related stuff #1
Comments
|
Hello,
I am considering changing the license to CC0. Would that work for you?
Best,
Froyo
On Sat, Jan 29, 2022 at 12:37 PM urbec-guest ***@***.***> wrote:
Hi,
while packaging fantasma for Debian,
I stumbled over two minor licensing related things.
1. The glyphs file does not have fsType [1] set,
what makes fontmake default to setting it to "edit only"
when generating the otf/ttf, what contradicts with the license choice
of GPL-3 + font exception
and makes our rather picky linting tool complaining :)
Attached a patch [2] to set the value to "installable embedding".
[1] https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype
[2] (
https://github.com/froyotam/Fantasma/files/7964601/0001-Explicitly-setting-fsType-value-to-0-installable-emb.txt
)
1. The fonts exception to GPL-3 was added after release 1.0 -
would it be possible to make another release
that includes the font exception?
—
Reply to this email directly, view it on GitHub
<#1>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOBDNVK66AWPK633R6445SDUYRF2NANCNFSM5NDJW3WQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Froyo Tam
froyotam.info
818.671.8925
|
As GPL-3+FE would have already worked well If you would consider making a release with either the new license Thanks for your reply :) |
|
Just had a convo with the people who made the posters as well,
They are all fine with me changing the license to CC0.
Once I change the license.txt, what other steps would I need to take?
Best,
Froyo
…On Sat, Jan 29, 2022 at 1:14 PM urbec-guest ***@***.***> wrote:
Hello, I am considering changing the license to CC0.
Would that work for you? Best, Froyo
As GPL-3+FE would have already worked well
and CC0 is even far more permissive, yes that would work indeed :)
(though I assume it would not affect the posters as for those their
Authors would need to agree to the change, but I did not put those into the
package anyway)
If you would consider making a release with either the new license
(or the font exception if you decide to stay with GPL)
I would just wait for that one.
Thanks for your reply :)
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOBDNVLFJX4CYPN3NW625W3UYRKDFANCNFSM5NDJW3WQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
--
Froyo Tam
froyotam.info
818.671.8925
|
Basically just add a second release tag to git (the current one is 1.0 |
|
Just updated the release to 1.1.
https://github.com/froyotam/Fantasma/tree/1.1
Let me know if there's anything else I would need to do!
Best,
Froyo
…On Sat, Jan 29, 2022 at 1:38 PM urbec-guest ***@***.***> wrote:
Once I change the license.txt, what other steps would I need to take?
Basically just add a second release tag to git (the current one is 1.0
so probably 2.0 or 1.1)
(The patch I attached basically just makes it explicit, that nothing about
embedding is forbidden, though of course it's just an offer :))
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOBDNVIH3JR4XG546AJ7RR3UYRM7FANCNFSM5NDJW3WQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
--
Froyo Tam
froyotam.info
818.671.8925
|
No, all is fine. Thanks :) |
|
Awesome!
Glad the licensing issue is resolved. Marking the issue as closed.
Best,
Froyo
On Sat, Jan 29, 2022 at 2:16 PM urbec-guest ***@***.***> wrote:
Let me know if there's anything else I would need to do!
No, all is fine.
Thanks :)
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOBDNVIAGXZDNJCEPTWR5QLUYRRKDANCNFSM5NDJW3WQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
--
Froyo Tam
froyotam.info
818.671.8925
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
while packaging fantasma for Debian,
I stumbled over two minor licensing related things.
what makes fontmake default to setting it to "edit only"
when generating the otf/ttf, what contradicts with the license choice
of GPL-3 + font exception
and makes our rather picky linting tool complaining :)
Attached a patch [2] to set the value to "installable embedding".
[1] https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype
[2] (https://github.com/froyotam/Fantasma/files/7964601/0001-Explicitly-setting-fsType-value-to-0-installable-emb.txt)
would it be possible to make another release
that includes the font exception?
The text was updated successfully, but these errors were encountered: