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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to