Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

put the logo on #7

Closed
wants to merge 2 commits into from
Closed

put the logo on #7

wants to merge 2 commits into from

Conversation

@edunham
Copy link
Contributor

edunham commented Nov 10, 2015

Review on Reviewable

@edunham
Copy link
Contributor Author

edunham commented Nov 10, 2015

or could a decision get made in servo/servo#3893 and use that logo instead?

@metajack
Copy link
Contributor

metajack commented Nov 10, 2015

I have someone working on a real logo from #3893, but it probably wont' be ready for several more weeks. Proceed with the doge for now :)

@mbrubeck
Copy link
Contributor

mbrubeck commented Nov 10, 2015

I think this should wait until an official logo is chosen in #3893. The doge logo is fine for developer builds and inside jokes, but for more prominent public use we should make sure we don't run afoul of the Rust trademark policy:

Using the Rust trademarks within another trademark requires written permission from the Rust core team except as described above.

and the Mozilla Trademark policy:

There is one additional broad category of things you can't do with Mozilla's Marks. Produce modified versions of them.

Since both Servo and the Rust trademarks are owned by Mozilla, we potentially could get permission to do this. But there's also a question of ownership of the doge image, and of whether it's a good idea to set an example that other Rust projects can't follow.

@larsbergstrom
Copy link

larsbergstrom commented Nov 11, 2015

I'll send mail to the Rust core team.

I would prefer that we explicitly not look too official, especially in our alpha releases. Before we start making Servo look like a real product, we should engage deeply with Firefox program management. There is a huge risk in devaluing the brand and confusing our userbase (plus annoying off the Firefox team!) if we push too hard too fast with Servo-as-product.

I've been through that experience before (on VS) and it was a PR nightmare plus a huge morale killer when our incubation project leaked and was mistaken by the press to be the Next Big Thing and devalued the imminent upcoming releases from the product org.

@edunham
Copy link
Contributor Author

edunham commented Nov 11, 2015

Would it be an acceptable compromise to use a doge meme without the Rust logo, such as this?

servodogememe

@Manishearth
Copy link
Member

Manishearth commented Nov 11, 2015

Such r, many +

@larsbergstrom
Copy link

larsbergstrom commented Nov 11, 2015

The Rust core team has provided written approval of our Servo-doge-Rust logo usage.

@edunham
Copy link
Contributor Author

edunham commented Nov 11, 2015

@larsbergstrom Thank you for getting permission -- that logo usage also means that @bors-servo is in the clear.

Your point about getting taken seriously by developers and the media before we're ready is compelling, though. I've pushed an even less polished-looking doge so that people would look even sillier for taking the site seriously.

@edunham
Copy link
Contributor Author

edunham commented Nov 11, 2015

In the meantime, an actual screenshot was PR'd. Merged it, since it carries useful information about Servo's ability to render things rather than a questionably copyright-infringing meme.

@edunham edunham closed this Nov 11, 2015
@edunham edunham deleted the edunham:doge branch Nov 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

5 participants
You can’t perform that action at this time.