This is a subjective question, but I feel that when the only thing in
src/main is src/main/resources/index.jelly the wrapper should be
licensed the same way as the library being wrapped, because our own
contribution to production code is de minimis. It seems strange to use
a different license when our unique contribution is just build/test
code. In cases where our contribution to src/main is nontrivial then I
am fine with applying our own MIT license to the plugin.

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjqrkUMMeCyb662wYdSsBiA1YQv0npYvCUUr2dk0ufkU8A%40mail.gmail.com.

Reply via email to