Licensing
#755
Replies: 1 comment 1 reply
-
Hi Liam,
Thanks for raising this. A while back, it was one FOSSA flag that was an
invalid match to an otf font. I raised this with FOSSA but they were
reluctant to change it. So I kinda mentally switched off to the widget. It
concerns me for sure and I'll look at removing or replacing license clashes.
That being said, for a tool like this, it feels like a more restrictive
license would benefit the project and include a clause that the templates
and runtime are excempt. I want to do the right thing by everyone else and
also myself. Am open to suggestions on how to achieve that.
Cheers,
…-Lea.
On Mon, 12 Jul 2021, 07:50 Liam Bigelow, ***@***.***> wrote:
Hi Lea! 🙂
Just a query on where the licensing will end up. Right now the project is
labeled as MIT, but it looks like there are a range of incompatible
licenses within, at least as far as
<https://app.fossa.io/projects/git%2Bgithub.com%2Fwailsapp%2Fwails?ref=badge_shield>
is concerned. I don't know if that's an accurate summary of the distributed
code, however.
What are the longer-term plans here?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#755>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAO2SYCS3Q4N3WVUXCJ326DTXIGZJANCNFSM5AFV3C2Q>
.
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Lea! 🙂
Just a query on where the licensing will end up. Right now the project is labeled as MIT, but it looks like there are a range of incompatible licenses within, at least as far as is concerned. I don't know if that's an accurate summary of the distributed code, however.
What are the longer-term plans here?
Beta Was this translation helpful? Give feedback.
All reactions