[
https://issues.apache.org/jira/browse/AVRO-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764756#comment-17764756
]
Emma Kellam commented on AVRO-3554:
-----------------------------------
Thank you for your feedback everyone, it's been very helpful and is much
appreciated! :D Also thank you for posting the screenshots of the previous
designs Oscar! I can now attach files directly to comments so I'll do that from
now on.
Martin, taking another look at it I can see how you could associate the blobs
with data loss (especially in design V4), although that wasn't my original
intention! You're right that the blobs covey speed, but I also meant for them
to represent 'flow' and 'transformation', which were some keywords I picked up
on in the original mailing list discussion. They are also meant to abstractly
represent data serialization, where bytes of data, the blobs, reform together
to form a cohesive whole again, the airplane (looking at the designs again this
might be better conveyed in the V9 design because of the orientation)
Ryan, I agree with your observations as well! I'm partial to the pigeon, but I
feel that the simpler design of the airplanes matches other ASF project icons
and will be more flexible overall :)
I've made some final logo drafts to add to the bucket for consideration which
I'll post below!
I added V9 back to this sheet for comparison purposes as I also think it's the
best plane look. In design V10 I adjusted the base of the airplane and the
overall angle so it matches the changes that were made to the V9 design, the
only difference between them being the blocky/pixelated tail.
Design V11 is based on design V4 with some minor adjustments to the blobby tail
so it matches the new upward orientation a little bit better. Design V12 is the
same as V11 except with the blocky/pixelated tail instead of the blobs.
My gut feeling is that the final decision will most likely be between V9 and
V11 (with V3 as a possible third contender), but I wanted to open the floor to
another round of discussion to see if any other options are speaking to y'all
before we do a final vote on the mailing list! :D
Thanks again!
!Apache-Avro-Logo-Revisions-V2.png!
> Create original art for the Avro logo
> -------------------------------------
>
> Key: AVRO-3554
> URL: https://issues.apache.org/jira/browse/AVRO-3554
> Project: Apache Avro
> Issue Type: Improvement
> Reporter: Ryan Skraba
> Assignee: Emma Kellam
> Priority: Major
> Fix For: 1.12.0
>
> Attachments: Apache-Avro-Logo-Ideas.pdf, Apache-Avro-Logo-Ideas.png,
> Apache-Avro-Logo-Revisions-V1.pdf, Apache-Avro-Logo-Revisions-V2.png,
> Apache-Avro-Logos-1.png, Apache-Avro-Logos-2.png, OldAsmLogo.png, cuttlefish
> oscar 2.svg, cuttlefish oscar.svg
>
>
> There was a quick discussion with Apache Trademarks along the lines "If it
> ever came to a legal challenge, would we care enough to defend our usage? If
> not, changing it discreetly and voluntarily is the best route."
> The result: we _must_ change our logo this year to some original art.
>
> Criteria for a new logo, as discussed on the mailing list:
> [https://lists.apache.org/thread/m5w7fmkjnrl8m4hlbw8xhzr4v69xg3ml]:
> Must:
> * be unique and not similar to anything “out there”
> * be available in a vector format (SVG) so it can be scaled with full
> accuracy
> Should:
> * show either something of the name (like Beam, Airflow, Ant, Drill) or what
> it does (like Mahout, Bookkeeper, Ratis, Pulsar)
> * have 2 variants: Square/Circle (social media, favicon, etc) and rectangle
> (top banner)
> Could:
> * have the banner logo be the compact logo with the name attached, or more
> elaborate
> Would:
> * have limited colors; at most 5-10 (so like Iceberg, not like Flex with the
> gradients)
>
> _To allow sufficient artistic freedom, we should limit new requirements.
> Instead, please add ideas in the comments._
>
> See [https://www.apache.org/logos/] for many examples
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
