What the badge should be granted for: Badge description (like "You added a co-maintainer to a package. BFF!"):Volunteering at a Fedora Event
Volunteered at a Fedora Conference (Once) Volunteered at a Fedora Conference (Three) Volunteered at a Fedora Conference (Five) Volunteered at a Fedora Conference (Ten) Volunteered at a Fedora Conference (Twenty)
Possible artwork concept: Badger with a name tag
A mock up of a badge
mock up Fedora_Event_Volunteer.svg
Great start!
I think the concept works- though the panda head has gotten a little distorted. I think the panda head from this ticket would work perfectly for this https://fedorahosted.org/fedora-badges/ticket/246 You can find the svg there. Make sure to hold down control and then drag to scale proportionally.
Hi all. Is this badge proposal a duplicate of "[https://badges.fedoraproject.org/badge/the-panda-is-in The Panda Is In]"?
https://badges.fedoraproject.org/badge/the-panda-is-in https://fedorahosted.org/fedora-badges/ticket/250
Is this proposal maybe extending that badge into a series beyond just one?
Metadata Update from @riecatnor: - Issue assigned to vhloche
@jflory7, I would agree that is an extension to that badge... I think the best plan of action would be to add numbers into the composition of that badge. I like the numbering progression. Adding tags :)
Metadata Update from @riecatnor: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None (was: 0) - Custom field has_complete_yaml reset (from None) - Custom field has_description reset (from 0) - Custom field has_name reset (from 0) - Custom field needs_manual_award reset (from 0) - Custom field triaged reset (from 0) - Issue close_status updated to: None
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false) - Issue tagged with: artwork-easy, artwork-needed, event
Metadata Update from @riecatnor: - Custom field artwork adjusted to needed (was: None) - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false)
@riecatnor please review, workshop-flock-2017
@veon looks great! Thanks for your work - setting to approved
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false)
Metadata Update from @riecatnor: - Custom field artwork adjusted to approved (was: needed) - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false)
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false) - Issue untagged with: artwork-needed - Issue tagged with: artwork-approved
@jflory7 Any idea on how to implement the badge? I am currently clueless.
Metadata Update from @sayanchowdhury: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false)
@sayanchowdhury manual. Currently I award the-panda-is-in when an event owner gives me a list of people who have helped with that event..
Metadata Update from @nb: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false)
@nb Okay, then I will push this badge and give the permissions to you to award the badges.
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false) - Issue tagged with: ready to push
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false) - Issue untagged with: difficulty - easy
Is this badge still relevant? Do we need to push this badge?
Maybe @riecatnor can give a better input, but I think this badge is still relevant, not for Fedora Conference per se, but any Fedora event that is organised, so I think we can push it.
Metadata Update from @smeragoel: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false)
Hello @riecatnor is this issue open to work on?
Hello @smeragoel @riecatnor I am not sure if this ticket is open to work on, but just in any case it is, here is the design I came up with
Hi @booky thank you for the work, but this badge artwork is approved already. Please find another ticket to work on, thank you!
Issue tagged with: AW: needed
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false) - Custom field has_description reset (from false) - Custom field has_name reset (from false) - Custom field needs_manual_award reset (from false) - Custom field triaged reset (from false) - Issue untagged with: AW: needed
This repository has moved over to Fedora Forge. All issue tickets have been transferred in there.
Metadata Update from @t0xic0der: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)