== Badge Description == Title: Chemnitzer Linux-Tage 2016 Attendee Caption: You visited the Fedora booth at Chemnitzer Linux-Tage 2016
== Activities == This badge is associated with the Chemnitzer Linux-Tage 2016. Various Fedora Ambassadors will be attending the conference. More details about Fedora's participation are on the wiki: https://fedoraproject.org/wiki/Chemnitzer_Linuxtage_2016
== Who gets badge == Visitors to the booth/table are eligible to earn the badge.
== Why get badge == Earning the badge is primarily as a motivator to register an FAS account.
== When get badge == March 19th - 20th (days of Chemnitzer Linux-Tage 2016).
== How get badge == Scan QR code to add badge to FAS account.
== Artwork concepts == Let's adopt the tux from https://chemnitzer.linux-tage.de/2016/en/presse/downloads or https://chemnitzer.linux-tage.de/2016/en/ - or alternatively the typical "Chemnitzer Linux-Tage" phrase from the logo? Given I'm not a designer, I've not really a clue what's possible. I am up to better suggestions through.
Great! That's why I'm thinking about to join the event, personally.
About design of badge: Maybe for inspiration, look also to
https://idw-online.de/de/image?id=85252&size=screen
I don't want to be a devil's advocate here, but given the number of Fedora contributors coming, I think this badge is unnecessary.
We are basically creating a badge for ourselves, similarly to https://badges.fedoraproject.org/badge/froscon-2015-attendee or https://badges.fedoraproject.org/badge/pycon-2014-attendee
We can just get a booth badge and be happy https://badges.fedoraproject.org/badge/the-panda-is-in
I'd argue keep the event badges Fedora events only (+ some huge things, like FOSDEM, which already has some tradition here on Badges).
If we really want CLT badge, I'd suggest make just one, keep the year out of it and reuse it each year.
Replying to [comment:4 churchyard]:
That's indeed a valid argument in general, I took the idea from ticket #429 - which would suffer the same issue then (there are IMHO not really more Fedora contributors).
Nevertheless, I would like to see a badge - if possible - because I think it's nice for (new) contributors, and we gained some contributors in the past during CLT, and some are AFAIK still active.
Interesting, I didn't get this badge for CLT last year then.
That sounds like a possible way to go :)
Maybe Joerg or Fabian can also comment on this and share their opinions?
Replying to [comment:5 robert]:
as i do not participate in collecting badges, i am maybe not the right person to comment ...
in general i think it worth having a badge to reuse every year for CLT, it would still be a rare badge to get ;)
in last years we always got new contributors ... and it would add to our story by asking them why they have not earned their badge yet ... as always more in a funny way ...
Well, I personally don't really care about the badges otherwise I would send 20 emails to get the promised badge for the participation in the Python 3 Porting FAD ;-)
But while looking at the Badges website I think that we should have a CLT badge. The reason is simple it's the biggest Open Source Event in Germany and it couldn't harm to have to tell a story as jsimon already mentioned.
attachment clt.svg
attachment <img alt="clt.png" src="//issue/raw/files/524d3b84ce69cad06aee642b9dcb7646e4ed866729d3f0c393ffde27d25fbd89-clt.png" />
attachment <img alt="clt.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/524d3b84ce69cad06aee642b9dcb7646e4ed866729d3f0c393ffde27d25fbd89-clt.png" />
What about this? [[Image(clt.png)]]
The background feels to dark and it's hard to see the penguin form distance. Otherwise it looks good me (not a design team member).
I like robyduck's proposal! But churchyard might be right...especially when zooming out. Could it help to maybe just take the upper part of the penguin (like above the belly)? Anyway, I'm not clued in badge designing...
attachment clt2.svg
attachment <img alt="clt2.png" src="//issue/raw/files/cec7777044d7fdcb1ee7f2fd09866cc4d91f984a7168a398b2f3eab616eefd62-clt2.png" />
attachment <img alt="clt2.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/cec7777044d7fdcb1ee7f2fd09866cc4d91f984a7168a398b2f3eab616eefd62-clt2.png" />
What about this?
[[Image(clt2.png)]]
attachment <img alt="clt1.png" src="//issue/raw/files/4ecb7db54b5b16cc412d9af84d4610de833e238703663484bc693e172603c8d4-clt1.png" />
attachment <img alt="clt1.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/4ecb7db54b5b16cc412d9af84d4610de833e238703663484bc693e172603c8d4-clt1.png" />
So here is a new logo and another BG. [[Image(clt1.png)]]
attachment clt1.svg
I like it (both by the way), but could somebody from the design team let us know whether they would be suitable or if there's a general issue with the layout or whatever?
I think the one with the gray gradient background looks great (and has the needed contrast)
Triaging ticket, appears ready for review to me!
CCing members of the Design Team so they can help give a lookover of the badge to see if it's ready to push out in the current form.
I think this one is the best. All in all, looks great! Cheers!
[[Image(https://fedorahosted.org/fedora-badges/raw-attachment/ticket/430/clt1.png)]]
Seeing as this is approved by the design team, I'll push it out asap (if no one else is working on that already).
I just pushed it.
URL is https://badges.fedoraproject.org/badge/chemnitzer-linux-tage-2016 (I didn't realize until after I pushed it that it was not intended to be year-specific). I have updated the name and description, but we can't update the URL of the badge.
Can you please e-mail me the PDF with QR code and URL? I will print it and bring it with me to CLT.
Replying to [comment:21 churchyard]:
Can you please e-mail me the PDF with QR code and URL? I will print it and bring it with me to CLT. If you were given permissions to award the badge, you should have an option to create a QR code with an expiration and also get the URL to grant the badge from the [https://badges.fedoraproject.org/badge/chemnitzer-linux-tage-2016 badge page]. If not, nb or threebean will have to grant you the permissions. :)
I have it now. Thanks.
Metadata Update from @robert: - Issue assigned to robyduck
Log in to comment on this ticket.