License the logo under Creative Commons?

[lidel]

There probably should be a LICENSE file in this repository (with, for example CC BY-SA 4.0), so that community projects such as ipfs-chrome-extension / ipfs-firefox-addon can safely reuse it :gift:

Or maybe just add it at the end of README.md, for exampe:

### License

<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/80x15.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.

renders as:

License

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

[jbenet]

Good point! Wonder if it should just be CC-Attribution. (For ex the golang gopher is). Ideally would use a license that would make it able to be copied and derived, but not used to evoke our support of things without our permission. (In spirit of a BSD license almost)

— Sent from Mailbox

On Mon, Mar 30, 2015 at 1:01 AM, Marcin Rataj notifications@github.com wrote:

There probably should be a LICENSE file in this repository (with, for example CC BY-SA 4.0), so that community projects such as ipfs-chrome-extension / ipfs-firefox-addon can safely reuse it :gift: Or maybe just add it at the end of README.md, for exampe:

### License
<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/80x15.png" /></a><br />This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.

renders as:

License

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Reply to this email directly or view it on GitHub: https://github.com/ipfs/logo/issues/1

[lidel]

CC-Attribution(-SA) should be fine.

Otherwise it is a slippery-slope and you end up in “freezing logo” to be used only with unaltered codebase, like in case of Firefox:

The name "Mozilla Firefox" is a registered trademark; along with the official Firefox logo, it may only be used under certain terms and conditions. Anyone may redistribute the official binaries in unmodified form and use the Firefox name and branding for such distribution, but restrictions are placed on distributions which modify the underlying source code.

Mozilla has placed the Firefox logo files under open-source licenses, but its trademark guidelines do not allow displaying altered or similar logos in contexts where trademark law applies. – https://en.wikipedia.org/wiki/Firefox#Trademark_and_logo

That is why Debian renamed Firefox to Iceweasel. :confused:

[Mithgol]

Remember that the “-SA” (“share-alike”) part of CC-BY-SA means that you cannot distribute a derivative work under a license other than CC-BY-SA (or a compatible license such as CC-BY-SA-ND). See CC-BY-SA 3.0 Legal Code, section 4b.

I am not a lawyer, but I think that such licensing makes the use of CC-BY-SA-licensed IPFS logo in CC0-licensed IPFS addon for Firefox questionable.

[lidel]

Note that CC0 is not a license per se: it is a legal tool for waiving as many rights as legally possible, worldwide (FSF recommends CC0 as the preferred method of releasing software into the public domain).

According to Creative Commons FAQ it is perfectly fine to remix CC-BY-SA with CC0/PD, as long as credit is given where credit is due:

• Can I combine material that uses different Creative Commons licenses into my work?

I updated LICENSE section to emphasize that the Logo is licensed separately under CC-BY-SA.

[jbenet]

thanks! closing this.