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

Licencing? #7

Closed
broomfn opened this issue Jan 11, 2022 · 6 comments
Closed

Licencing? #7

broomfn opened this issue Jan 11, 2022 · 6 comments

Comments

@broomfn
Copy link

broomfn commented Jan 11, 2022

Hi,

This looks like a fantastic library, but the AGPL licence seems a little prescriptive, correct me if I'm wrong, but If I include your npm package I would need to open source the rest of my Ionic mobile application?

Thanks

Neil

@riderx
Copy link
Collaborator

riderx commented Jan 20, 2022

Hey @broomfn thanks for the feedback, i understand your issue.
I use AGPL as explained here : https://opensource.com/article/17/1/providing-corresponding-source-agplv3-license

What is often misunderstood is that the source code requirement in AGPLv3 Section 13 is triggered only
where the AGPLv3 software has been modified by "you" (for example, the entity providing the network service). 
My interpretation is that, so long as "you" do not modify the AGPLv3 code, the license should not be read as
requiring access to the Corresponding Source in the manner prescribed by Section 13. As I see it, many 
unmodified and standard deployments of software modules under AGPL simply do not trigger Section 13, 
although making the source code available
even if not required under the license is a good idea.

Include it in your project don't force you to open source it.
this is only needed if you modify capacitor-updater

@riderx riderx closed this as completed Jan 20, 2022
@broomfn
Copy link
Author

broomfn commented Jan 20, 2022

@riderx Many thanks for the clarification.

I know from the past there have been many arguments as to what defines a derived work, so just wanted to be clear before we use it, if you're happy we don't need to open source our entire project that's good enough for me.

@riderx
Copy link
Collaborator

riderx commented Jan 20, 2022

Yes of course, it's a long debate, i should have writed it, on the repo, i know that unclear for some people

@riderx
Copy link
Collaborator

riderx commented Jun 1, 2022

the question came back again yesterday and someone talked about LGPL-3, who look a good alternative too
but some other article confirms my choice too: https://medium.com/swlh/understanding-the-agpl-the-most-misunderstood-license-86fd1fe91275
So i tried to get some advice on the internet :
https://twitter.com/martindonadieu/status/1531950286201290753?s=20&t=oKSANxsFJO9oaT5881iTTQ
Without much success, i will find someone to fix the question forever.

@riderx
Copy link
Collaborator

riderx commented Jun 1, 2022

After some conversation in the discord and the Discover of this:
https://opensource.stackexchange.com/questions/6879/may-i-use-agpl-license-in-a-desktop-application-without-providing-the-source-cod
It seems pretty obvious now AGPL3 is not what i think, so i migrated to LGPL3

@riderx
Copy link
Collaborator

riderx commented Mar 4, 2023

After other feedback from users MPL seems better designed for plugin code:
https://fossa.com/blog/open-source-software-licenses-101-mozilla-public-license-2-0/

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

No branches or pull requests

2 participants