= Badge Description =
= Understanding badge =
1) What are those activities?
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
3) Why are they doing them (is this a means to a different end?)
4) When do they do them (every day? once a year?)
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
= Artwork concepts =
Depending on how things go, I might design this badge if a design team member is not
Fixing the description…
The number of such requests are increasing which is really good but how can other people know that there really was Fedora table present at that conference?
Replying to [comment:2 pnemade]:
The Fedora Ambassadors of North America approved this event as a sponsor in our [https://meetbot.fedoraproject.org/sresults?group_id=famna&type=team weekly meetings]. You can find the [https://fedorahosted.org/famna/ticket/139 ticket] in our Trac as well as the [https://fedoraproject.org/wiki/Bitcamp_Spring_2016 wiki page] documenting the event.
For future reference, any event that Fedora Ambassadors are attending ''should'' have this information present somewhere to verify that the event is happening and that Fedora has a role in the event. Categorizing wiki pages with the [https://fedoraproject.org/wiki/Category:Events Events] category helps with this.
Bitcamp campfire logo bitcamp-logo.svg
Bitcamp official text bitcamp-logo-text-orange.svg
= Proposed artwork =
Here is my first proposed badge artwork of the Bitcamp 2016 Attendee badge. Marking the artwork status as proposed and CCing some members of the Design Team for feedback! The event is this weekend, so any quick review / help is appreciated on this one!
[[Image(https://fedorahosted.org/fedora-badges/raw-attachment/ticket/444/events-brickhack-2016.png)]]
As an afterthought, I would like to add some kind of distinguishment for the year (i.e. "2016"), but I'm not quite sure how to work that into this design…
Hey! One thing right away - word bitcamp is hard to read, can we make it white? And try adding 2016 to different parts of badge, see if anything looks good. Crazy idea - maybe write bitcamp on one log and 2016 on the other.. or vice versa. or just 2016 on the log. something of sorts.
Hope this helps ;)
Justin,
Maybe Fedora on the long log and in the upper right section of the underside log 2016 ? or Just ''' '16 '''
Replying to [comment:6 mleonova]:
Replying to [comment:7 corey84]:
Okay, here's the latest revision of the badge that I have! How does this look for a revision?
[[Image(https://fedorahosted.org/fedora-badges/raw-attachment/ticket/444/events-bitcamp-2016.png)]]
Looks great! Just move the 6 a bit closer to 1 and the whole thing a tinsy bit to the left and we're good =)
Slightly modified SVG version of badge events-bitcamp-2016.svg
Okay, shifted it over a little bit! Going to CC some sysadmin members to push this badge so we can get it ready in time for Bitcamp.
Seems like my last upload didn't actually shift the '16, this should do it <img alt="events-bitcamp-2016.png" src="//issue/raw/files/ab2c47defd3c840bec1fe860cda352232626302ef851a09bc3a19191f78b0b82-events-bitcamp-2016.png" />
Seems like my last upload didn't actually shift the '16, this should do it <img alt="events-bitcamp-2016.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/ab2c47defd3c840bec1fe860cda352232626302ef851a09bc3a19191f78b0b82-events-bitcamp-2016.png" />
Pushed.
Metadata Update from @jflory7: - Issue assigned to jflory7
Login to comment on this ticket.