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

          [JENKINS-21270] Add licenses to jenkins core and plugins

          Tom Van Eyck created issue -

          license should be set in maven pom.xml

          Nicolas De Loof added a comment - license should be set in maven pom.xml

          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?

          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?

          Alex Earl added a comment -

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

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

          Alex Earl added a comment -

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

          Alex Earl added a comment - Other plugin owners would need to be assigned so they see this.
          Alex Earl made changes -
          Assignee Original: Alex Earl [ slide_o_mix ]

          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

          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

          Alex Earl added a comment -

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

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

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

              Created:
              Updated:
              Resolved: