Hello. JENKINS-21270 points plugins without license information: https://issues.jenkins-ci.org/browse/JENKINS-21270
Parameterized-trigger-plugin is also pointed. As I was just planning to make its new release merging some pull requests, I'm going to add a license notice to that if I can. Please let me know how can I decide its license. What is required to put it under MIT license? Does it require agreements by someone? It contains no LICENSE file. Some of files contain license notices in their header comments, but many of them including core logic files contain no license notices. As parameterized-trigger-plugin is contributed by many developers, I'm not sure who is responsible for its license... Does anyone know how to do in that case? * Plugins hosted in Jenkins repository without any license notice can be treated under MIT License ? * Requires an agreement of the developer originally developed that plugin? * Requires agreements of all developers contributed that plugin? * No one can decide its license ? (It should be left without license notice?) Regards, Ikedam -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
