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

Usage of GPL license #4

Open
christianneu opened this issue May 21, 2021 · 4 comments
Open

Usage of GPL license #4

christianneu opened this issue May 21, 2021 · 4 comments

Comments

@christianneu
Copy link

christianneu commented May 21, 2021

From a project usage perspective the question would be if the repository should make use of a GPL 3.0 license?

As an alternative I would propose to change the license to APACHE 2.0 or BSD-2-Clause as most of the relative repositories make use of these: https://github.com/ehn-digital-green-development?q=hcert

@gunnarif
Copy link
Collaborator

I changed it to the "EUROPEAN UNION PUBLIC LICENCE v. 1.2", the same license the Base45Encoding implementation is under.
I'm honestly not sure what is the best choice is here.
Maybe @gabywh can have a say in this.
Also, the current implementation is far behind the latest pull request.

@christianneu
Copy link
Author

Any update on this?

My proposal would be to streamline the org to Apache 2.0 license to be equivalent to the repositories of https://github.com/eu-digital-green-certificates and to be more open for the usage.

@gabywh
Copy link
Contributor

gabywh commented Jun 2, 2021

I would hesitate making the whole org Apache 2.0, since this takes away individual original author's freedom to choose something different.
EUPL or Apache 2.0 seems to be used in practice for these kinds of things - so I would prefer to leave the choice to the original author with a possible hint/help to choose either EUPL or Apache 2.0 if really no preference - and I see EUPL chosen. If that's fine with the original author, it's fine with me.

@gabywh
Copy link
Contributor

gabywh commented Jun 14, 2021

hcert-dotnet now Apache 2.0, right? If so, this issue can be closed I think?

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

3 participants