Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21270

Add licenses to jenkins core and plugins

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hi all,

      we use Jenkins and quite a few of its plugins in our organization. Due to legal reasons we are required to keep track of which licenses any software we use falls under. Generally this is pretty easy.

      However, I'd estimate that less than half of the Jenkins core and plugin components that we use has clear license info (e.g. a license file in a github repo or a license mentioned on http://maven-repository.com). Would it be possible to have a look at this? Or is there perhaps an implicit license that applies when no license is specified?

      The following plugins are ones that I'm having trouble finding a license for:

      ruby-runtime plugin https://github.com/jenkinsci/ruby-runtime-plugin
      git plugin https://github.com/jenkinsci/git-plugin
      email-ext plugin https://github.com/jenkinsci/email-ext-plugin
      rvm plugin https://github.com/jenkinsci/rvm-plugin
      github api plugin https://github.com/jenkinsci/github-api-plugin
      git client plugin https://github.com/jenkinsci/git-client-plugin
      html publisher plugin https://github.com/jenkinsci/htmlpublisher-plugin
      maven project plugin https://github.com/jenkinsci/maven-plugin/tree/master
      multijob plugin https://github.com/jenkinsci/tikal-multijob-plugin
      parameterized trigger plugin https://github.com/jenkinsci/parameterized-trigger-plugin
      timestamper plugin https://github.com/jenkinsci/timestamper-plugin
      token macro plugin https://github.com/jenkinsci/token-macro-plugin
      build name setter plugin https://github.com/jenkinsci/build-name-setter-plugin

      What would be the correct way to go about collecting license information for these? I've opened a few pull requests on github with licensing info for these, but was told that writing a JIRA ticket like this might yield better results.

      Many thanks,
      Tom

        Attachments

          Activity

          vaneyckt Tom Van Eyck created issue -
          Hide
          ndeloof Nicolas De Loof added a comment -

          license should be set in maven pom.xml

          Show
          ndeloof Nicolas De Loof added a comment - license should be set in maven pom.xml
          Hide
          slide_o_mix Alex Earl added a comment -

          It can be assumed that all code falls within that license then, correct? Can you post an example in this ticket for those of us who are not Maven people? Also, what is the generally liked license for Jenkins? MIT? Apache 2?

          Show
          slide_o_mix Alex Earl added a comment - It can be assumed that all code falls within that license then, correct? Can you post an example in this ticket for those of us who are not Maven people? Also, what is the generally liked license for Jenkins? MIT? Apache 2?
          Hide
          slide_o_mix Alex Earl added a comment -

          I added the license to the email-ext plugin pom.xml

          Show
          slide_o_mix Alex Earl added a comment - I added the license to the email-ext plugin pom.xml
          Hide
          slide_o_mix Alex Earl added a comment -

          Other plugin owners would need to be assigned so they see this.

          Show
          slide_o_mix Alex Earl added a comment - Other plugin owners would need to be assigned so they see this.
          slide_o_mix Alex Earl made changes -
          Field Original Value New Value
          Assignee Alex Earl [ slide_o_mix ]
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          BTW, there's a note on this topic on Jenkins Governance Page:

          The Jenkins project uses the MIT license as the primary license of choice, for the code that we develop. Unless otherwise stated, all the code is under the MIT license.

          The core is entirely in the MIT license, so is the most infrastructure code (that runs the project itself), and many plugins. We encourage hosted plugins to use the same MIT license, to simplify the story for users, but plugins are free to choose their own licenses, so long as it’s a OSI-approved open-source license.

          This is not to be confused with proprietary plugins — we recognize and encourage plugins that people write on their own for their internal use, without ever making the source code available.

          https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document

          Show
          oleg_nenashev Oleg Nenashev added a comment - BTW, there's a note on this topic on Jenkins Governance Page: The Jenkins project uses the MIT license as the primary license of choice, for the code that we develop. Unless otherwise stated, all the code is under the MIT license. The core is entirely in the MIT license, so is the most infrastructure code (that runs the project itself), and many plugins. We encourage hosted plugins to use the same MIT license, to simplify the story for users, but plugins are free to choose their own licenses, so long as it’s a OSI-approved open-source license. This is not to be confused with proprietary plugins — we recognize and encourage plugins that people write on their own for their internal use, without ever making the source code available. https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document
          Hide
          slide_o_mix Alex Earl added a comment -

          Removing email-ext as I have added the MIT license to the pom

          Show
          slide_o_mix Alex Earl added a comment - Removing email-ext as I have added the MIT license to the pom
          slide_o_mix Alex Earl made changes -
          Component/s email-ext [ 15538 ]
          markewaite Mark Waite made changes -
          Component/s git-client [ 17423 ]
          markewaite Mark Waite made changes -
          Component/s git [ 15543 ]
          Hide
          markewaite Mark Waite added a comment -

          Removed git-plugin and git-client-plugin after confirming that both those plugins include a license section in their pom.xml.

          Show
          markewaite Mark Waite added a comment - Removed git-plugin and git-client-plugin after confirming that both those plugins include a license section in their pom.xml.
          Hide
          ikedam ikedam added a comment -

          Parameterized trigger added a license notice in 2.23 (will be available in a day).
          Removed parameterized-trigger from components.

          Show
          ikedam ikedam added a comment - Parameterized trigger added a license notice in 2.23 (will be available in a day). Removed parameterized-trigger from components.
          ikedam ikedam made changes -
          Component/s parameterized-trigger [ 15592 ]
          Hide
          stevengbrown Steven G Brown added a comment -

          Removed timestamper, which now has a license section in the POM.

          Show
          stevengbrown Steven G Brown added a comment - Removed timestamper, which now has a license section in the POM.
          stevengbrown Steven G Brown made changes -
          Component/s timestamper [ 15749 ]
          ircbot Jenkins IRC Bot made changes -
          Component/s maven2 [ 15487 ]
          Hide
          slide_o_mix Alex Earl added a comment -

          Removing token-macro-plugin, it has the license info in the pom file.

          Show
          slide_o_mix Alex Earl added a comment - Removing token-macro-plugin, it has the license info in the pom file.
          slide_o_mix Alex Earl made changes -
          Component/s token-macro-plugin [ 15832 ]
          vaneyckt Tom Van Eyck made changes -
          Component/s build-name-setter-plugin [ 15902 ]
          vaneyckt Tom Van Eyck made changes -
          Description Hi all,

          we use Jenkins and quite a few of its plugins in our organization. Due to legal reasons we are required to keep track of which licenses any software we use falls under. Generally this is pretty easy.

          However, I'd estimate that less than half of the Jenkins core and plugin components that we use has clear license info (e.g. a license file in a github repo or a license mentioned on http://maven-repository.com). Would it be possible to have a look at this? Or is there perhaps an implicit license that applies when no license is specified?

          The following plugins are ones that I'm having trouble finding a license for:

          ruby-runtime plugin https://github.com/jenkinsci/ruby-runtime-plugin
          git plugin https://github.com/jenkinsci/git-plugin
          email-ext plugin https://github.com/jenkinsci/email-ext-plugin
          rvm plugin https://github.com/jenkinsci/rvm-plugin
          github api plugin https://github.com/jenkinsci/github-api-plugin
          git client plugin https://github.com/jenkinsci/git-client-plugin
          html publisher plugin https://github.com/jenkinsci/htmlpublisher-plugin
          maven project plugin https://github.com/jenkinsci/maven-plugin/tree/master
          multijob plugin https://github.com/jenkinsci/tikal-multijob-plugin
          parameterized trigger plugin https://github.com/jenkinsci/parameterized-trigger-plugin
          timestamper plugin https://github.com/jenkinsci/timestamper-plugin
          token macro plugin https://github.com/jenkinsci/token-macro-plugin

          What would be the correct way to go about collecting license information for these? I've opened a few pull requests on github with licensing info for these, but was told that writing a JIRA ticket like this might yield better results.

          Many thanks,
          Tom
          Hi all,

          we use Jenkins and quite a few of its plugins in our organization. Due to legal reasons we are required to keep track of which licenses any software we use falls under. Generally this is pretty easy.

          However, I'd estimate that less than half of the Jenkins core and plugin components that we use has clear license info (e.g. a license file in a github repo or a license mentioned on http://maven-repository.com). Would it be possible to have a look at this? Or is there perhaps an implicit license that applies when no license is specified?

          The following plugins are ones that I'm having trouble finding a license for:

          ruby-runtime plugin https://github.com/jenkinsci/ruby-runtime-plugin
          git plugin https://github.com/jenkinsci/git-plugin
          email-ext plugin https://github.com/jenkinsci/email-ext-plugin
          rvm plugin https://github.com/jenkinsci/rvm-plugin
          github api plugin https://github.com/jenkinsci/github-api-plugin
          git client plugin https://github.com/jenkinsci/git-client-plugin
          html publisher plugin https://github.com/jenkinsci/htmlpublisher-plugin
          maven project plugin https://github.com/jenkinsci/maven-plugin/tree/master
          multijob plugin https://github.com/jenkinsci/tikal-multijob-plugin
          parameterized trigger plugin https://github.com/jenkinsci/parameterized-trigger-plugin
          timestamper plugin https://github.com/jenkinsci/timestamper-plugin
          token macro plugin https://github.com/jenkinsci/token-macro-plugin
          build name setter plugin https://github.com/jenkinsci/build-name-setter-plugin

          What would be the correct way to go about collecting license information for these? I've opened a few pull requests on github with licensing info for these, but was told that writing a JIRA ticket like this might yield better results.

          Many thanks,
          Tom
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -
          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: ikedam Path: pom.xml http://jenkins-ci.org/commit/groovy-postbuild-plugin/7b5378c805cb81b115705a4fbd263e806424aa99 Log: Merge pull request #23 from vaneyckt/master JENKINS-21270 add MIT license Compare: https://github.com/jenkinsci/groovy-postbuild-plugin/compare/9c365546b196...7b5378c805cb
          Hide
          le0 Lev Mishin added a comment -

          All of the plugins you mentioned have a MIT license references in the pom.xml or MIT license text in the repository root

          All plugins and Jenkins use MIT license

          Show
          le0 Lev Mishin added a comment - All of the plugins you mentioned have a MIT license references in the pom.xml or MIT license text in the repository root All plugins and Jenkins use MIT license
          le0 Lev Mishin made changes -
          Assignee Lev Mishin [ le0 ]
          le0 Lev Mishin made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          le0 Lev Mishin made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 153133 ] JNJira + In-Review [ 207303 ]

            People

            • Assignee:
              le0 Lev Mishin
              Reporter:
              vaneyckt Tom Van Eyck
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: