Badge description (like "You added a co-maintainer to a package. BFF!"): You visited the Fedora table at SouthEast LinuxFest (SELF) 2018!
Help the badges team understand what this idea is all about. If this badge is awarded for certain kinds of activities:
1) What are those activities? Awarded to those who visited the Fedora table at Southeast Linuxfest 2018
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?) Attendees at the 2018 Southeast Linuxfest
3) Why are they doing them (is this a means to a different end?) They came to Southeast Linuxfest 2018 and wanted to learn more about Fedora
4) When do they do them (every day? once a year?) Southeast Linuxfest 2018 is June 8-10, 2018
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?) Scan the QR code, visit a link, or have a Fedora table staffer award the badge manually.
Lastly, do you have any ideas for artwork concepts? SVG and PNG attached
<img alt="events-self-2018.png" src="/fedora-badges/issue/raw/c1c895ead6375271a8f98d77500dedaa3cdac1395669ab98b889ac4ff9b22e0d-events-self-2018.png" /> <img alt="events-self-2018.svg" src="/fedora-badges/issue/raw/3914162a442ebf931759c77cd8299b79546ed15274189b6c0fd8cf196bad21e9-events-self-2018.svg" />
@imabug I like this, although I'm wondering why use the yellow background when it has been grey in the past. I'm not opposed to it, though.
Metadata Update from @nb: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None
@nb 2018 is the 10th Southeast Linuxfest, so I thought it deserved something with a brighter background
@imabug thank you for working on this badge! The yellow colour is lovely! Unfortunately, there is two issues if we approve this as is. One, other event badges will then request to have a unique background, and this one will be the arguing point. We try to keep the uniform background to help keep consistency and an overall aesthetic between all the badges of the same "category" of badge. Second issue is it will stick out quite sorely among all the other event badges, and not in a great way.
Please make a version with a grey background similar to other event badges. Thanks again!!
@riecatnor Sure, no problem. I'll submit a new version when I get a chance to work on it.
Attached are the PNG and SVG files for the SELF 2018 badge going back to the gray background.
<img alt="events-self-2018.png" src="/fedora-badges/issue/raw/files/775d4c000b18c7e0dc5c7a6ebe21b7968b05617706da5d8a8e1bd65604a06548-events-self-2018.png" /><img alt="events-self-2018.svg" src="/fedora-badges/issue/raw/files/5f1bdb6cebae336eae7764234486b0e28d7eff74e2f20da2d48485273464b202-events-self-2018.svg" />
Hi @imabug ! The badge looks great! Please check the size though - png should be 256x256px at 96 dpi when you export the whole page.
Metadata Update from @mleonova: - Issue assigned to imabug - Issue tagged with: artwork-easy, event
Ok, let's try these
<img alt="events-self-2018.png" src="/fedora-badges/issue/raw/files/175e69a45329efc823a8267bcf643b3bae1d015bf7a05bb8e2b36acc15b87230-events-self-2018.png" /><img alt="events-self-2018.svg" src="/fedora-badges/issue/raw/files/5c91d35453f61448e5ef157889ae0579f0b3c02dabf6f2851f8332b0a2dc3e02-events-self-2018.svg" />
@imabug awesome! All good to go!
Metadata Update from @mleonova: - Custom field artwork adjusted to approved (was: None)
Metadata Update from @mleonova: - Issue tagged with: ready to push
I've pushed this badge here: https://badges.fedoraproject.org/badge/self-2018
@award3535 @imabug who needs access to generate QR codes?
I've pushed this badge here: https://badges.fedoraproject.org/badge/self-2018 @award3535 @imabug who needs access to generate QR codes?
I think @nb has done it in the past
@bex I will do it.
@nb please confirm you can award the badge so we can close this ticket. @imabug thank you!
Metadata Update from @riecatnor: - Issue tagged with: artwork-approved
@bex @nb @imabug can this ticket be closed? please update! thanks
@bex I can take care of it. Closing ticket.
Metadata Update from @nb: - Issue close_status updated to: pushed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.