Closed danielleberre closed 6 years ago
I'm fine with the change.
On Oct 10, 2017, at 11:38 AM, Daniel Le Berre notifications@github.com wrote:
One user of the plugin would like to contribute to the plugin but cannot due to the current license of the project conflicting with his employer IP policy.
We initially used LGPL for the plugin because it is the license used by the majority of the sonar plugins.
We welcome contributions from the community and as such are willing to change the current license to Apache 2.0.
Changing the license of the plugin requires all committers of the project to agree with that change.
@dthagard @bobintornado @Tvli @mariusstaicu would you agree to change the license of the project to Apache 2.0
The change of license would apply in the next release (1.3).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Sure, I agree
I agree.
@Tvli @mariusstaicu it would be nice if we could have your input on that subject.
@znerd @maclav3 @Kernle32DLL would you agree ?
I agree.
@thibaultfalque I agree
I'm ok with this, sorry for the delay
@Tvli @mariusstaicu It would be nice if we could have your feedback on that issue.
Hi @danielleberre Sorry about the long delay, missed this message completely... I agree with this change.
Well, it looks like all code contributors agreed with the change (@mariusstaicu contributed a script on the README page).
So next release 1.3 will be provided under the Apache 2.0 license.
We have to check how to do this properly: released code must stay forever under LGPL 3.0 license, I guess it can be done using an LGPL_3_0 tag on the branches. Need to think about it.
Thanks for your feedback. I am closing the issue now.
One user of the plugin would like to contribute to the plugin but cannot due to the current license of the project conflicting with his employer IP policy.
We initially used LGPL for the plugin because it is the license used by the majority of the sonar plugins.
We welcome contributions from the community and as such are willing to change the current license to Apache 2.0.
Changing the license of the plugin requires all committers of the project to agree with that change.
@dthagard @bobintornado @Tvli @mariusstaicu would you agree to change the license of the project to Apache 2.0?
The change of license would apply in the next release (1.3).