Just to throw another proposal out there and inspire some debate, here's a similar-but-different idea (inspired by John + some sketches I found on google):
*~~ See attachment, inlined image is too large for the mailing list ~~* This one's definitely more fun, my only concern is that it doesn't really scale well. At the lower end of sizes the otters will be pretty difficult to see; and I had to stretch out the Kafka circles even at the larger end just to fit them through. But maybe with a cleaner drawing and some color it'll still look good and be recognizable + distinct enough when small. Any thoughts? Any binding and/or non-binding votes? On Sun, Mar 8, 2020 at 1:00 AM Sophie Blee-Goldman <sop...@confluent.io> wrote: > Seems the mailing list may have filtered the inlined prototype logo, > attaching it here instead > > On Sat, Mar 7, 2020 at 11:54 PM Sophie Blee-Goldman <sop...@confluent.io> > wrote: > >> Matthias makes a good point about being careful not to position Streams as >> outside of Apache Kafka. One obvious thing we could do it just include >> the >> Kafka logo as-is in the Streams logo, somehow. >> >> I have some unqualified opinions on what that might look like: >> A good logo is simple and clean, so incorporating the Kafka logo as a >> minor >> detail within a more complicated image is probably not the best way to get >> the quick and easy comprehension/recognition that we're going for. >> >> That said I'd throw out the idea of just attaching something to the Kafka >> logo, >> perhaps a stream-dwelling animal, perhaps a (river) otter? It could be >> "swimming" left of the Kafka logo, with its head touching the upper >> circle and >> its tail touching the bottom one. Like Streams, it starts with Kafka and >> ends >> with Kafka (ie reading input topics and writing to output topics). >> >> Without further ado, here's my very rough prototype for the Kafka Streams >> logo: >> >> [image: image.png] >> Obviously the real thing would be colored and presumably done by someone >> with actual artist talent/experience (or at least photoshop ability). >> >> Thoughts? >> >> On Sat, Mar 7, 2020, 1:08 PM Matthias J. Sax <mj...@apache.org> wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA512 >>> >>> Boyang, >>> >>> thanks for starting this discussion. I like the idea in general >>> however we need to be a little careful IMHO -- as you mentioned Kafka >>> is one project and thus we should avoid the impression that Kafka >>> Streams is not part of Apache Kafka. >>> >>> Besides this, many projects use animals that are often very adorable. >>> Maybe we could find a cute Streams related mascot? :) >>> >>> I would love to hear opinions especially from the PMC if having a logo >>> for Kafka Streams is a viable thing to do. >>> >>> >>> - -Matthias >>> >>> On 3/3/20 1:01 AM, Patrik Kleindl wrote: >>> > Hi Boyang Great idea, that would help in some discussions. To throw >>> > in a first idea: https://imgur.com/a/UowXaMk best regards Patrik >>> > >>> > On Mon, 2 Mar 2020 at 18:23, Boyang Chen >>> > <reluctanthero...@gmail.com> wrote: >>> > >>> >> Hey Apache Kafka committers and community folks, >>> >> >>> >> over the years Kafka Streams has been widely adopted and tons of >>> >> blog posts and tech talks have been trying to introduce it to >>> >> people with need of stream processing. As it is part of Apache >>> >> Kafka project, there is always an awkward situation where Kafka >>> >> Streams could not be campaigned as a standalone streaming engine, >>> >> and makes people confused about its relation to Kafka. >>> >> >>> >> So, do we want to introduce a customized logo just for Streams? >>> >> The immediate benefit is when people are making technical >>> >> decisions, we could list Streams as a logo just like Flink and >>> >> Spark Streaming, instead of putting Kafka logo there as it is not >>> >> literally a legitimate comparison between processing framework >>> >> and messaging system. Should we do a KIP for this? >>> >> >>> >> Boyang >>> >> >>> > >>> -----BEGIN PGP SIGNATURE----- >>> >>> iQIzBAEBCgAdFiEEI8mthP+5zxXZZdDSO4miYXKq/OgFAl5kDVQACgkQO4miYXKq >>> /Og2Hg/+IOjjz3yrvHOz/p/Qbi9hXDK+GZT6Ixzk2HrrpMiLAAZs6WrNGQMwwI6a >>> qrPdMRLKA45F53wwMXBqhLYe0O0vOIRSur3pef8UuTVEkbFstY6dNzduPjTXK4vV >>> Ahzb+pu1lZsF+n2DbMuXWvkmvMAsSrKQXbH58rA7I4qx7Zr6g1a/KL2b2oOoo3kI >>> 4x3PJfG6oLSnQHwkJxmM79ZjM7MLZh0d8cRqb7Oudy5MJiMzHY+Rm5aTu4nhPgRr >>> cLxA8kz1PbGPboxjD9/ZGuZJMWfVnvY1wJcOp5UnOUs4kX5uYDyWw1sKIn3DcnW8 >>> YVzoto0syCHTAdbl89H2fxhJbtVp8JSxbBx9AW8mdgLOLsYRZGHZ1cbdJ3h4NkeE >>> xTPTuTptQbhdcjbSVX6F0q+h1hiPCU5PKqcR12zGVTBI4rOGkhPIhDdnIti5Qp2e >>> MQ1Urh/tWCfwiJZbOyjZ9Tz/2vbUBB4kzUI9DxwWpD15jgMuN3JfqFwcwSIm7NrY >>> jHcM3UB2QlUt+uymU78xjy6er2AFiGrfL7UXeFHzzVIWBU3fdw4wqpuIuWjFhL3t >>> NWnAvamXOc7kfE4VXQ8igoRUVDZ8xCCqNvVoaJZ1cWboY/Cfk+4sgd9QnDMZN9jU >>> bzRpghQp3R93Vp5FH4L9z478uuh8DFM2/+6pqqapd9efydGtKrU= >>> =OFBs >>> -----END PGP SIGNATURE----- >>> >>