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 -
          Alex Earl made changes -
          Assignee Original: Alex Earl [ slide_o_mix ]
          Alex Earl made changes -
          Component/s Original: email-ext [ 15538 ]
          Mark Waite made changes -
          Component/s Original: git-client [ 17423 ]
          Mark Waite made changes -
          Component/s Original: git [ 15543 ]
          ikedam made changes -
          Component/s Original: parameterized-trigger [ 15592 ]
          Steven G Brown made changes -
          Component/s Original: timestamper [ 15749 ]
          Jenkins IRC Bot made changes -
          Component/s Original: maven2 [ 15487 ]
          Alex Earl made changes -
          Component/s Original: token-macro-plugin [ 15832 ]
          Tom Van Eyck made changes -
          Component/s New: build-name-setter-plugin [ 15902 ]
          Tom Van Eyck made changes -
          Description Original: 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
          New: 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

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

              Created:
              Updated:
              Resolved: