On 30/06/2015 14:26, Leonardo Brito wrote: > Is there a guide for relicensing customized components? I made some > components based on the gold-zip-input and I'm trying to update the > license as it state clearly that Google or Polymer authors names should > not be used to endorse any derivative work.
Bearing in-mind that IANAL: Even if you "re-license" a component, you still need to abide by all the terms of the component's original license agreement. This means that you will likely be required to include all copyright notices from the original component such as the google or polymer copyrights, and if the original license requires that neither google nor polymer be used to endorse the work then you need to include those restrictions on your derivative work. You cannot remove terms and conditions unless they are explicitly stated to be removable in derivative works. This means that you cannot for example take a GPL project and release your derivative under a different license because the GPL restrictions require that derivatives be licensed under the same terms as the original. The restrictions of the GPL applied to the original project are transferred to derivative works. For MIT or BSD licensed projects, which are more liberal in their allowances, you are still required to maintain the original copyright and restrictions on endorsements even if you release your derivative under a different license, be that proprietary or open source. This means you need to include those same restrictions into whichever terms your derivative work is released under. HTH, Daniel Llewellyn Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" 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/polymer-dev/5592CE7B.7010705%40bowlhat.net. For more options, visit https://groups.google.com/d/optout.
