summaryrefslogtreecommitdiff
path: root/minidebconfwomen2014_entry.txt
blob: a4c80747d0c84bb49afe8bb426f3c8b4222d9f47 (plain)
  1. I've been asked to make - or rather to participate in making - a logo for the upcoming "Debian Mini Conf Barcelona March 2014". I said I could spend about eight hours a week on the task, but two weeks have already flewn by. I have a vague idea about a MirĂ³'ish typograhy, primary colored paint spots, one of them being the swirl, and the female gender sign.
  2. I was sketching on the idea this morning, and I think it could work. Talking with my boyfriend about it, I realised I'm on the wrong path. Not with the idea, but with the whole approach, acting as if I was ordered to finish a task, instead of participating with my mind, not only with my design skills, but with all of me.
  3. He asked the obvious questions a designer should ask: Why a logo? It's not a DebConf. It's not necessary to brand the event. There already is a logo for Debian Women. Nobody is coming because of a logo or staying home if there is none. It's a nice to have.
  4. Being a graphic designer I default into saying that visual identity design is necessary always and everywhere. Well, it shouldn't always be the case. It might be a waste of resources.
  5. Sure, recently I declared that I want to do some work for Debian. But designing an event logo really was not what I had in mind. On the other hand, it would be really nice to have done it, as my 'debut' in the organisation. Especially when I am giving my talk "Graphic design with Debian". But then again -