Jenkins plugin development open source license requirement

[Michael McGreevey]

My question is about the 2nd bullet item below (found on page:  https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins):

Specify an open source license for your code (most plugins use MIT)

• The Jenkins project does not host closed-source plugins
• All of the dependencies of your plugin must also be open source-licensed
• You should specify the license in the plugin metadata (e.g. pom.xml), but ideally also in a LICENSE file in the root of your repository
  

My plugin has a dependency that has an open source MIT license, is that sufficient or do I also have to open source the code in this dependency?

Thank you!

[Mark Waite]

If the dependency has an MIT license, that is sufficient.  No need to include the source code from the dependency.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b33ddaac-3f50-4396-8a50-451337cd025a%40googlegroups.com.

--

Thanks!

Mark Waite

[Oleg Nenashev]

My plugin has a dependency that has an open source MIT license, is that sufficient or do I also have to open source the code in this dependency?

To clarify this question... Is the code under the MIT license is available somewhere? Or is it a private-source code licensed under the MIT License? If the answer to the second question is "yes", it does not make much sense to me though it does not seem to be explicitly prohibited by the license terms. IANAL, other license explicitly include the source code availability clause.

Personally I would consider a plugins as closed source if any of its dependencies is closed source, regardless of the license.

BR, Oleg

 

On Tuesday, September 17, 2019 at 12:32:44 AM UTC+2, Mark Waite wrote:

If the dependency has an MIT license, that is sufficient.  No need to include the source code from the dependency.

On Mon, Sep 16, 2019 at 10:48 AM Michael McGreevey <michaelm...@gmail.com> wrote:

My question is about the 2nd bullet item below (found on page:  https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins):

Specify an open source license for your code (most plugins use MIT)

• The Jenkins project does not host closed-source plugins
• All of the dependencies of your plugin must also be open source-licensed
• You should specify the license in the plugin metadata (e.g. pom.xml), but ideally also in a LICENSE file in the root of your repository
  

My plugin has a dependency that has an open source MIT license, is that sufficient or do I also have to open source the code in this dependency?

Thank you!

--
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 jenkin...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b33ddaac-3f50-4396-8a50-451337cd025a%40googlegroups.com.

--

Thanks!

Mark Waite