#638 DevConf.US Attendee badge
Closed: pushed a year ago Opened a year ago by langdon.

Badge description (like "You added a co-maintainer to a package. BFF!"):

Apologies on this being rather last minute, I didn't think of it til I saw the Flock badge. Is there any chance we could get a DevConf.US Attendee and Speaker badges based on the DevConf.CZ ones? The conference start on Aug. 17, so it is a bit of a rush.

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?
Attending or speaking at DevConf.US

2) Who is doing them (are they packagers? translators? newcomers? veterans?
users? sponsors?)
See above

3) Why are they doing them (is this a means to a different end?)
n/a

4) When do they do them (every day? once a year?)
once (actually, some of the speakers are doing more than one talk, not sure if that might be fun as a riser)

5) How do they do them (by talking in IRC? by running commands in the console?
by using a web interface?)

Attending or speaking at the conference

Lastly, do you have any ideas for artwork concepts?

I think this could be basically a clone of the DevConf.CZ badge. Maybe like this: https://devconf.info/ (the us one). Assets here: https://github.com/devconfcz/devconfcz/tree/master/icon/us


For 2018 DevConf CZ we didn't do a speaker badge. I'd argue not to do it for DevConf US either and only have one badge.

https://pagure.io/fedora-badges/issue/593

Metadata Update from @churchyard:
- Custom field artwork adjusted to None
- Custom field concept_review_passed adjusted to None

a year ago

@churchyard agreed. Let's keep this consistent.

Metadata Update from @mleonova:
- Issue assigned to mleonova

a year ago

@churchyard yup, but I had to put the year somewhere - so I took the devconf.cz badge and modified the color slightly.

woohoo.. What do I do next?

You say that you like it ;)

Metadata Update from @mleonova:
- Issue tagged with: artwork-approved, artwork-easy, event, ready to push

a year ago

Metadata Update from @bex:
- Issue close_status updated to: pushed
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata
Attachments 1
Attached a year ago View Comment