Excellent - I was hoping for GPLv2 but MIT should streamline being able to
push patches back!
BTW - the pom.xml still references LGPL v3
<licenses>
<license>
<name>LGPL 3</name>
<url>http://www.gnu.org/licenses/lgpl.html</url>
<distribution>repo</distribution>
</license>
</licenses>
On Wednesday, 21 August 2013 07:14:42 UTC+1, nicolas de loof wrote:
>
> The plugin was initially created under AGPL, but I got approval to
> relicense it under MIT.
>
> https://github.com/jenkinsci/build-flow-plugin/commit/022b40b86383ef678184bf6fe6497be033254555
>
>
> 2013/8/20 teilo <[email protected] <javascript:>>
>
>> Hi Nicolas/Cloudbees/other buildflow contributors.
>>
>> Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3
>> (jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3.
>>
>> Is this just an oversight when the plugin was re-licensed - or is this
>> really a mix?
>>
>> (also any chance of changing it to something without the GPL v3 patent
>> issues to make it more company friendly - even if it is dual licenced with
>> the Jenkins enterprise plugins) I don't ask for much do I ;-)
>>
>> /James
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
