Trademark committee approval for logo

[jasongrout]

Having a unified and consistent branding across Jupyter projects is important to protecting the Jupyter trademark and responding to logo modification requests from outside Jupyter. When a project modifies the Jupyter logo, I think it is important to get approval from the trademark committee (email an approval request to [email protected]) for several reasons:

1. Modifying the Jupyter logo is nominally against the Jupyter branding guidelines, so should be approved by the committee administering trademark issues
2. Approval can be granted, of course, but even if approval is granted, the trademark committee should be keeping track of the different modifications we have across Jupyter to make better informed decisions about future modification requests

Disclaimer: I serve on the Jupyter trademark committee

[welcome]

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.

You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

[jtpio]

Thanks @jasongrout for bringing this up 👍

Does this mean every project that is considered to be accepted as a Jupyter sub-project, should submit a request for approval, regardless of whether the logo is similar to the existing Jupyter logo?

If so, maybe we could then update the list of items mentioned in https://github.com/jupyter/governance/blob/master/newsubprojects.md#criteria-for-official-subprojects, to not forget that step?

[jtpio]

For reference if anyone is interested, the new logo, added in #131, was designed as follows:

• Search for "retro" on Google Image

• Create the "sun" with a similar style as the ones on the screenshot above
• Add 3 "moons" around it, as an "easter-egg" this is somehow related to Jupyter
• Write RetroLab below it

[jtpio]

Closing as this repository and RetroLab itself will soon be archived and deprecated: #356