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

Choosing a license: Permissive vs Restrictive #10

Open
coolharsh55 opened this issue Jul 22, 2022 · 1 comment
Open

Choosing a license: Permissive vs Restrictive #10

coolharsh55 opened this issue Jul 22, 2022 · 1 comment

Comments

@coolharsh55
Copy link

coolharsh55 commented Jul 22, 2022

tldr; implications of license used (GPL v3) may restrict adoption and use in typical use-cases; a more permissive license such as GPL v2 or Apache 2.0 may be better

Hi. Use of GPL v3 as the License will require published Apps to be published with their source made available (AFAIK), which is typically not the norm since most apps are not open-sourced. Since the aim of this work is to encourage better handling of (personal) data in the interests of data protection and privacy, a license that facilitates integration more easily would result in more adoption and use.

Ideally, if there is a need to nudge sharing back improvements, the GPL v2 may be a more palatable option; or if the intention is to have this work be used as widely as possible, the Apache 2.0 license may be suitable (and is the more preferred option for such work since its easier to figure out implications of reuse).

@kasnder
Copy link
Member

kasnder commented Jul 22, 2022

Good question about license! The reason why I picked a restrictive license is for now that the project is still pretty early in development, and I'm not quite sure yet where it's headed. But if this project should become more suitable for production, I completely agree that another license might be more appropriate!

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