#846 DevConf.US Attendee Badge
Closed: pushed a year ago by gui1ty. Opened 2 years ago by maxamillion.

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

Apologies on this being last minute, I didn't realize nobody had requested it before hand. Is there any chance we could get a DevConf.US Attendee and Speaker badges based on the DevConf.CZ ones? The conference started today Sep 2, 2021, 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

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?

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

Attached the proposed SVG


Metadata Update from @smeragoel:
- Custom field artwork adjusted to None
- Custom field concept_review_passed adjusted to None
- Issue tagged with: artwork - needed, category - event, difficulty - easy, good first issue, outreachy-2022

2 years ago

Hello! Can i please be assigned this issue? :) thank you

Metadata Update from @smeragoel:
- Issue assigned to harshita12

2 years ago

Hello @harshita12! You can start working on this. Let me know if you have any questions. Happy designing!

Metadata Update from @smeragoel:
- Assignee reset

2 years ago

Unfortunately we missed that this event passed :( but there will be a DevConf.US in 2022- so someone will need to update the art work to use "2022"

https://www.devconf.info/us/

@smeragoel can this issue be assigned to me please?

@smeragoel I would like to work on this issue. Thank you.

Unfortunately we missed that this event passed :( but there will be a DevConf.US in 2022- so someone will need to update the art work to use "2022"

https://www.devconf.info/us/

I have worked on the badge for 2022
please have a look

HI @booky you're welcome to submit something for this ticket

Hi @madhavidayma thanks for starting work on this task. I would suggest reviewing some of the How to Design a Fedora Badge docs [0] and also some of the videos we have on youtube [1] for this. Its important to use the badge templates provided. Since this is a badge we have created in years past, all that is needed here is to update the year, and upload the new svg & png. You can find the correct file in the previous ticket [2].

[0] https://docs.fedoraproject.org/en-US/badges/design-badges/
[1] https://www.youtube.com/results?search_query=fedora+badges
[2] https://pagure.io/fedora-badges/issue/638#comment-525802

Hello @riecatnor @smeragoel I would be working on this issue. Thank you

Hello @riecatnor and @smeragoel, I would like to be assigned to this issue, please. Thank you!

Hi folks! Leaving one comment for both submissions to save scrolling space on the ticket ;)

@ifeanyinoel this looks great! The only change needed is to re-export the PNG at 256x256 pixels- if you are using inkscape it will be 96dpi. Thanks!

@madhavidayma getting closer! Make sure you have the comfortaa typeface installed:
https://fontlibrary.org/en/search?query=comfortaa
The only change needed from the last design is the year, and it should look exactly the same but with the year "2022" Thanks!

Kindly have a look at this :) @riecatnor @smeragoel. Waiting for the review. I also have an idea that whether I should put the US flag on the badge somewhere if it's fine.

DevconfusAttendee2022.svg

Hi folks! A note for everyone: the output for this badge should look exactly like the previous badge with only the date changed. Based on that please revisit your designs. Here is the previous badge:
https://badges.fedoraproject.org/badge/devconf.us-attendee-2018

@ifeanyinoel nice work, you are pretty much there with this latest design. I noticed the "2022" is a bit higher and doesn't looked centered. You will need to move it down just a bit :) thanks!

Hi @riecatnor @smeragoel!
Tried my hand at this issue as well!
I have kept the design exactly same as the 2018 one, and swapped the text with 2022. Please have a look, thank you so much :)
issue-846.png

Hi, sorry, just a little update. I realised the text size was such that the two 2's (haha) at either ends ended up looking a bit wonky. Tried to fix those as best as I could, attaching the png and svg files here, please have another look. Thanks!

issue-846.svgissue-846.png

oops, I forgot to tag you for review, @riecatnor, @smeragoel, just realised!

Hello @ifeanyinoel @zohamid! Thank you for your work. Your designs are identical, and I think it's ready to push.

For whoever pushes the badge, please use the files in this comment: https://pagure.io/fedora-badges/issue/846#comment-792400

A big thank you to everyone else also for contributing to this issue!

Metadata Update from @smeragoel:
- Issue tagged with: ready to push

2 years ago

Metadata Update from @smeragoel:
- Issue untagged with: artwork - needed

2 years ago

Metadata Update from @smeragoel:
- Issue untagged with: D: easy, good first issue, outreachy-2023

a year ago

@maxamillion, since this badge will be awarded retrospectively, do you have a list of attendees?

Metadata Update from @gui1ty:
- Issue assigned to gui1ty

a year ago

Badge has been pushed and authorization given to @maxamillion. Let me know if you've got a list of users that should be awarded this badge and I can take care of it.

https://badges.fedoraproject.org/badge/devconf.us-attendee-2022

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

a year ago

Login to comment on this ticket.

Metadata
Attachments 18
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment
Attached 2 years ago View Comment