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

join-pluging missing licensing information

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      There's no LICENSE.txt or similar file at the top-level of the GitHub project, nor is there a <license> entry in the pom.xml

      Without either, the code is unusable.

        Attachments

          Activity

          Hide
          mdonohue mdonohue added a comment -

          https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin

          "If nothing is defined, your code will be assumed to fall under the MIT license terms."

          Show
          mdonohue mdonohue added a comment - https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin "If nothing is defined, your code will be assumed to fall under the MIT license terms."
          Hide
          trims Erik Trimble added a comment - - edited

          That link isn't good enough, mainly because it's never referenced in the plugin documentation, nor in the GitHub repo anywhere. That's a pretty obscure place, especially since it's not something that any end-user is going to look. It's also not legally binding, which is the concern here - code has to be explicitly licensed, not by inference.

          really, this is simple. Add the following to the pom.xml file:

              <licenses>
                <license>
                  <name>The MIT license</name>
                  <url>http://www.opensource.org/licenses/mit-license.php</url>
                  <distribution>repo</distribution>
                </license>
              </licenses>
          

          Or, heck, just check-in the LICENSE.txt file obtained from one of the other plugins.

          E.g. https://github.com/jenkinsci/backup-plugin/blob/backup-1.6.1/LICENSE.txt

          Show
          trims Erik Trimble added a comment - - edited That link isn't good enough, mainly because it's never referenced in the plugin documentation, nor in the GitHub repo anywhere. That's a pretty obscure place, especially since it's not something that any end-user is going to look. It's also not legally binding, which is the concern here - code has to be explicitly licensed, not by inference. really, this is simple. Add the following to the pom.xml file: <licenses> <license> <name>The MIT license</name> <url>http: //www.opensource.org/licenses/mit-license.php</url> <distribution>repo</distribution> </license> </licenses> Or, heck, just check-in the LICENSE.txt file obtained from one of the other plugins. E.g. https://github.com/jenkinsci/backup-plugin/blob/backup-1.6.1/LICENSE.txt
          Hide
          mdonohue mdonohue added a comment -

          Guess you'll have to make the risk decision here.

          Show
          mdonohue mdonohue added a comment - Guess you'll have to make the risk decision here.
          Hide
          trims Erik Trimble added a comment -

          Why? It's a one-line fix. And it's simply reasonable code distribution protocol.

          I just don't have the commit rights, or I'd do it myself.

          Show
          trims Erik Trimble added a comment - Why? It's a one-line fix. And it's simply reasonable code distribution protocol. I just don't have the commit rights, or I'd do it myself.
          Hide
          mdonohue mdonohue added a comment -

          Saying something is "unusable" is a bit extreme. I added an explicit MIT license to the pom.xml file just now.

          Show
          mdonohue mdonohue added a comment - Saying something is "unusable" is a bit extreme. I added an explicit MIT license to the pom.xml file just now.

            People

            Assignee:
            mdonohue mdonohue
            Reporter:
            trims Erik Trimble
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: