Quilkin logo and Quilly the mascot

[markmandel]

Includes the original AI files (they also open in Inkscape for editing), and some PNG exports of both the white log and Quilly on transparent backgrounds.

Updated the README to also include both.

[quilkin-bot]

Build Succeeded 🥳

Build Id: 79b9bac1-67b0-4654-93cf-c19c1b0be0c3

To build this version:

git fetch git@github.com:googleforgames/quilkin.git pull/289/head:pr_289 && git checkout pr_289
cargo build

[XAMPPRocky]

LGTM! There are a couple of things, but I'm fine with this as-is.

• Should this be under docs or under something like assets? I feel like the latter might be more obvious for people to find.
• Should these AI files be in Git LFS? They're not likely to change much but they do add a lot to the repo.

[markmandel]

Should this be under docs or under something like assets? I feel like the latter might be more obvious for people to find.

🤔 Hmnnn. I am liking the idea of assets, but was thinking of not wanting to expand the top level folders too much, and I figure we'll primarily be using assets in this folder in our documentation? Some follow on thoughts:

• docs/assets/logos (if we want to keep things in the docs folder)
• assets/logos (if we want to go assets as top level, in case we get other asset types)

Thoughts?

Should these AI files be in Git LFS? They're not likely to change much but they do add a lot to the repo.

🤷🏻 it's 4Mb?

[XAMPPRocky]

🤷🏻 it's 4Mb?

Right, that might not seem like a lot, but relatively just adding it doubles the clone size of repository. The current size-pack for the repository is 4.95 MiB.

[quilkin-bot]

Build Succeeded 🥳

Build Id: df36dbe0-bdb5-456e-a50b-fac7591f8a55

To build this version:

git fetch git@github.com:googleforgames/quilkin.git pull/289/head:pr_289 && git checkout pr_289
cargo build

[markmandel]

Right, that might not seem like a lot, but relatively just adding it doubles the clone size of repository. The current size-pack for the repository is 4.95 MiB.

Seems like more trouble than it's worth to setup and maintain Git LFS for a few MB? As well as the extra complexity for maintainers? We can always revisit if we end up with lot more binary files.

Sounds like there aren't many strong opinions about the changes above - so if not, I'll merge as is.

[XAMPPRocky]

Nope, LGTM.