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

Relicense the project from GPL to BSD #23

Closed
DarkDrek opened this issue Aug 9, 2016 · 16 comments
Closed

Relicense the project from GPL to BSD #23

DarkDrek opened this issue Aug 9, 2016 · 16 comments
Assignees
Milestone

Comments

@DarkDrek
Copy link

DarkDrek commented Aug 9, 2016

Using this library would force me to provide the source code of my application as well.
Could you provide this library under the same license as the official PHP Tracking API? Link

@julienmoumne
Copy link
Member

This project should definitely have the same license as the php one. Thanks for spotting this.

@julienmoumne julienmoumne self-assigned this Aug 11, 2016
@mattab
Copy link
Member

mattab commented Sep 27, 2016

Consider the project is under MIT or BSD license and you can freely use & redistribute it. we'll change the license as soon as possible, cc @julienmoumne

@reinholdaudials
Copy link

+1

@julienmoumne
Copy link
Member

julienmoumne commented Nov 8, 2016

We actually need to contact all the contributors to ask for their permission.

Is there a particular process by which we should collect their consent or would a simple e-mail suffice?

Also, do note the GPL restriction you mentioned only applies if you propagate and convey your code to parties you do not control.

As in most cases, if you are simply using this library on your own servers, the restriction does not apply. This is a common misconception.

See Basic Permissions, second paragraph.

@mattab
Copy link
Member

mattab commented Nov 8, 2016

@julienmoumne think use case "I'm building a game and doing game analytics with Piwik". or "Building an app and doing app analytics with Piwik". Both would be publish/distributed on Google/Apple app stores. For this use case it was a little mistake we picked the GPL license for this SDK in the early days (and I missed this fact during early review), as the GPL license for a SDK prevents the SDK users from bundling their app along with the SDK and sell it/distribute it to others. (or their app would have to be GPL too since it's linked to the SDK and GPL applies). I consider it a simple mistake that we can easily correct by changing license to similar license as Java/PHP/iOS/Android SDKs 👍 (I'd say we can change the license without hearing back from all other 3 contributors since you contributed almost everything and other contribs are minor..)

@opcon
Copy link
Contributor

opcon commented Nov 8, 2016

I agree with changing the license from GPL, as @mattab said it means I can't legally distribute my game using Piwik Analytics.

@julienmoumne
Copy link
Member

I will ask contributors to give their consent by commenting in this issue.

In the mean time, as mentioned in my previous comment, if you are using the library on your own servers you are fine.

@mattab
Copy link
Member

mattab commented Nov 9, 2016

Awesome thanks @julienmoumne 👍

@robocoder
Copy link

Yes, IMO the GPL for the dotnet tracking library would encumber any app that is distributed with it. The LGPL might be a good middle ground as it would require distributors to open source their changes to the library. But whether you choose to relicense as BSD, MIT, or some other liberal license, you will need the approval of its contributors.

@robocoder
Copy link

For relicensing, getting the approval of contributors is required because the Piwik project doesn't use a formal copyright transfer for contributions.

You don't need approval for trivial contributions, or contributions that are no longer in the current code base.

@tetsuo13
Copy link
Contributor

tetsuo13 commented Nov 9, 2016

👍

@fushnisoft
Copy link
Contributor

Fine with me! 👍

@evilham
Copy link

evilham commented Jan 11, 2017

TL;DR: Make it clear which license the project is changing to! Don't use PHP License but MIT or BSD instead.

While I'm glad to see someone already brought this up and developers seem to agree there is a licensing issue, I don't see it moving forward in a nice direction, so my two cents (btw: IANAL!):

Some contributors are "agreeing" to the general idea of changing the license away from GPL, that's nice, but it is not clear what they are agreeing to change it to.

From reading the thread, I think the current proposal is changing to PHP license, which I don't think is such a good choice: PHP License is way too PHP specific. Article 4 even says:

software may not be called "PHP", nor may "PHP" appear in their name,

(Which, for example, means RALPHPHOTO would not be an allowed name)

In any case, the PHP License is over complicated for this library, as mentioned by others MIT or BSD would be a better fit. As an example, piwik-php-tracker uses BSD.

@robocoder
Copy link

Since the "+1's" don't specifically vote in favor of a specific license, we should formalize the proposal. Therefore...

The proposal is to change this project's license to BSD. Re-licensing under a BSD license would be consistent with the other official Piwik trackers. The call is now out for the following contributors to please vote either for/:+1: or against/:-1: the proposal.

Contributor
@julienmoumne
@tetsuo13
@fushnisoft
@opcon
@tsteur
@ptr1120
@mironych

@julienmoumne
Copy link
Member

julienmoumne commented Mar 5, 2017

Sorry for the state changes. I misclicked while working on the issue.

@julienmoumne
Copy link
Member

fixed in 4883823

@julienmoumne julienmoumne changed the title GPL is too restrictive Relicense the project from GPL to BSD Mar 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants