Hey Maria, I can testify :)
Cheers, Max On 23.04.20 20:49, María Cruz wrote: > Hi everyone! > It is amazing to see how this process developed to collaboratively > create Apache Beam's mascot. Thank you to everyone who got involved! > I would like to write a blogpost for the Beam website, and I wanted to > ask you: would anyone like to offer their testimony about the process of > creating the Beam mascot, and what this means to you? Everyone's > testimony is welcome! If you witnessed the development of a mascot for > another open source project, even better =) > > Please feel free to express interest on this thread, and I'll reach out > to you off-list. > > Thanks, > > María > > On Fri, Apr 17, 2020 at 6:19 AM Jeff Klukas <[email protected] > <mailto:[email protected]>> wrote: > > I personally like the sound of "Datum" as a name. I also like the > idea of not assigning them a gender. > > As a counterpoint on the naming side, one of the slide decks > provided while iterating on the design mentions: > > > Mascot can change colors when it is “full of data” or has a “batch > of data” to process. Yellow is supercharged and ready to process! > > Based on that, I'd argue that the mascot maps to the concept of a > bundle in the beam execution model and we should consider a name > that's a play on "bundle" or perhaps a play on "checkpoint". > > On Thu, Apr 16, 2020 at 3:44 PM Julian Bruno <[email protected] > <mailto:[email protected]>> wrote: > > Hi all, > > While working on the design of our Mascot > Some ideas showed up and I wish to share them. > In regard to Alex Van Boxel's question about the name of our Mascot. > > I was thinking about this yesterday night and feel it could be a > great idea to name the Mascot "*Data*" or "*Datum*". Both names > sound cute and make sense to me. I prefer the later. Datum means > a single piece of information. The Mascot is the first piece of > information and its job is to collect batches of data and > process it. Datum is in charge of linking information together. > > In addition, our Mascot should have no gender. Rendering it > accessible to all users. > > Beam as a name for the mascot is pretty straight forward but I > think there are many things carrying that same name already. > > What do you think? > > Looking forward to hearing your feedback. Names are important > and I feel it can expand the personality and create a cool > background for our Mascot. > > Cheers! > > Julian > > On Mon, Apr 13, 2020, 3:40 PM Kyle Weaver <[email protected] > <mailto:[email protected]>> wrote: > > Beam Firefly is fine with me (I guess people tend to forget > mascot names anyway). But if anyone comes up with something > particularly cute/clever we can consider it. > > On Mon, Apr 13, 2020 at 6:33 PM Aizhamal Nurmamat kyzy > <[email protected] <mailto:[email protected]>> wrote: > > @Alex, Beam Firefly? > > On Thu, Apr 9, 2020 at 10:57 PM Alex Van Boxel > <[email protected] <mailto:[email protected]>> wrote: > > We forgot something.... > > ... > > ... > > it/she/he needs a *name*! > > > _/ > _/ Alex Van Boxel > > > On Fri, Apr 10, 2020 at 6:19 AM Kenneth Knowles > <[email protected] <mailto:[email protected]>> wrote: > > Looking forward to the guide. I enjoy doing > (bad) drawings as a way to relax. And I want > them to be properly on brand :-) > > Kenn > > On Thu, Apr 9, 2020 at 10:35 AM Maximilian > Michels <[email protected] <mailto:[email protected]>> > wrote: > > Awesome. What a milestone! The mascot is a > real eye catcher. Thank you > Julian and Aizhamal for making it happen. > > On 06.04.20 22:05, Aizhamal Nurmamat kyzy wrote: > > I am happy to announce that this vote has > passed, with 13 approving +1 > > votes, 5 of which are binding PMC votes. > > > > We have the final design for the Beam > Firefly! Yahoo! > > > > Everyone have a great week! > > > > > > > > On Mon, Apr 6, 2020 at 9:57 AM David > Morávek <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>>> wrote: > > > > +1 (non-binding) > > > > On Mon, Apr 6, 2020 at 12:51 PM Reza > Rokni <[email protected] <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>>> wrote: > > > > +1(non-binding) > > > > On Mon, Apr 6, 2020 at 5:24 PM > Alexey Romanenko > > <[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>> wrote: > > > > +1 (non-binding). > > > > > On 3 Apr 2020, at 14:53, > Maximilian Michels > > <[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>> wrote: > > > > > > +1 (binding) > > > > > > On 03.04.20 10:33, Jan > Lukavský wrote: > > >> +1 (non-binding). > > >> > > >> On 4/2/20 9:24 PM, Austin > Bennett wrote: > > >>> +1 (nonbinding) > > >>> > > >>> On Thu, Apr 2, 2020 at > 12:10 PM Luke Cwik > > <[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > > >>> <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>>> wrote: > > >>> > > >>> +1 (binding) > > >>> > > >>> On Thu, Apr 2, 2020 at > 11:54 AM Pablo Estrada > > <[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > > >>> > <mailto:[email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>>>> wrote: > > >>> > > >>> +1! (binding) > > >>> > > >>> On Thu, Apr 2, 2020 > at 11:19 AM Alex Van Boxel > > >>> <[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>>> wrote: > > >>> > > >>> Thanks for > clearing this up Aizhamal. > > >>> > > >>> +1 (non binding) > > >>> > > >>> _/ > > >>> _/ Alex Van Boxel > > >>> > > >>> > > >>> On Thu, Apr 2, > 2020 at 8:14 PM Aizhamal > > Nurmamat kyzy > > >>> > <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>>>> wrote: > > >>> > > >>> Good point, > Alex. Actually Julian and I > > have talked > > >>> about > producing this kind of guide. It > > will be > > >>> delivered > as an additional contribution > > in the follow > > >>> up. We > think this will be a derivative of > > the original > > >>> design, and > be done after the original is > > officially > > >>> accepted. > > >>> > > >>> With this > vote, we want to accept the > > Firefly donation > > >>> as designed > [1], and let Julian produce other > > >>> artifacts > using the official Beam mascot > > later on. > > >>> > > >>> [1] > > > > https://docs.google.com/document/d/1zK8Cm8lwZ3ALVFpD1aY7TLCVNwlyTS3PXxTV2qQCAbk/edit?usp=sharing > > >>> > > >>> > > >>> On Thu, Apr > 2, 2020 at 10:37 AM Alex Van > > Boxel > > >>> > <[email protected] <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>>>> wrote: > > >>> > > >>> I don't > want to be a spoiler... but > > this vote > > >>> feels > like a final deliverable... but > > without a > > >>> style > guide as Kenn originally > > suggested most of > > >>> use > will not be able to adapt the > > design. This > > >>> would > include: > > >>> > > >>> * > frontal view > > >>> * > side view > > >>> * > back view > > >>> > > >>> > actually different posses so we can > > mix and match. > > >>> Without > this it will never reach the > > potential of > > >>> the Go > gopher or gRPC Pancakes. > > >>> > > >>> Note > this is *not* a negative vote > > but I'm afraid > > >>> that > the use without a guide will be > > fairly > > >>> limited > as most of use are not > > designers. Just a > > >>> concern. > > >>> > > >>> _/ > > >>> _/ Alex > Van Boxel > > >>> > > >>> > > >>> On Thu, > Apr 2, 2020 at 7:27 PM Andrew > > Pilloud > > >>> > <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>>>> > > >>> wrote: > > >>> > > >>> +1, > Accept the donation of the > > Firefly design > > >>> as > Beam Mascot > > >>> > > >>> On > Thu, Apr 2, 2020 at 10:19 AM > > Julian Bruno > > >>> > <[email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>> > > >>> > <mailto:[email protected] > <mailto:[email protected]> > > <mailto:[email protected] > <mailto:[email protected]>>>> wrote: > > >>> > > >>> > Hello Apache Beam Community, > > >>> > > >>> > Please vote on the acceptance > > of the final > > >>> > design of the Firefly as > > Beam's mascot > > >>> > [1]. Please share your input > > no later than > > >>> > Monday, April 6, at noon > > Pacific Time. > > >>> > > >>> > > >>> > [ ] +1, Accept the donation > > of the Firefly > > >>> > design as Beam Mascot > > >>> > > >>> > [ ] -1, Decline the donation > > of the > > >>> > Firefly design as Beam Mascot > > >>> > > >>> > > >>> > Vote is adopted by at least 3 > > PMC +1 > > >>> > approval votes, with no PMC > > -1 disapproval > > >>> > > >>> > votes. Non-PMC votes are > > still encouraged. > > >>> > > >>> > PMC voters, please help by > > indicating your > > >>> > vote as "(binding)" > > >>> > > >>> > > >>> > The vote and input phase will > > be open > > >>> > until Monday, April 6, at 12 > > pm Pacific Time. > > >>> > > >>> > > >>> > Thank you very much for your > > feedback and > > >>> > ideas, > > >>> > > >>> > Julian > > >>> > > >>> > > >>> [1] > > >>> > > > > https://docs.google.com/document/d/1zK8Cm8lwZ3ALVFpD1aY7TLCVNwlyTS3PXxTV2qQCAbk/edit?usp=sharing > > > > > >>> > > >>> -- > > >>> > Julian Bruno // Visual Artist > > & Graphic > > >>> > Designer > > >>> > (510) 367-0551 <tel:(510)%20367-0551> > > <tel:(510)%20367-0551> > <tel:(510)%20367-0551> / > > >>> > SF Bay Area, CA > > >>> > www.instagram.com/julbro.art > <http://www.instagram.com/julbro.art> > > > <http://www.instagram.com/julbro.art> > > >>> > > > <http://www.instagram.com/julbro.art> > > >>> > > >
