Derivative work relicensing

[Leonardo Brito]

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.

I tried to search on https://customelements.io/ , but only found code with the original license unmodified. So I'm stucked with this.

Thanks.

[Daniel Llewellyn]

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

[Leonardo Brito]

Thanks Daniel,

I really don't want to change any licensing terms, they're all MIT licensed. My concern is just not addressing the fact that I changed the code and thus release the software as Google or The Polymer Authors.

I'll follow the Apache 2.0 guideline and put a Derivative Work Notice above the original copyright.

Anyway it would be nice to see such guideline at the LICENSE file.

Leonardo Xavier de Brito