name: Badge Muse description: You submitted an idea for a new badge for Fedora Badges
attachment <img alt="badgemuse.png" src="//issue/raw/files/fc35a02a9e8fbdda997d0bd4e8f95c68aa41c6643cb82028cb75ef14fb9d7d2a-badgemuse.png" />
attachment <img alt="badgemuse.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/fc35a02a9e8fbdda997d0bd4e8f95c68aa41c6643cb82028cb75ef14fb9d7d2a-badgemuse.png" />
attachment badgemuse.svg
nice! the 'thought bubble badge' looks a bit small to me, but i can see it can't easily be made any bigger.
do we want to have separate badges for 'proposed' and 'accepted'? or just make it an 'accepted' badge? or only have 'proposed'?
It will be much easier to code if we just make it for "participating in the discussion of new badges".
I was thinking you could use the 'creator:' field of the badge yaml to identify people who've had badges accepted?
Added the badge: https://badges.fedoraproject.org/badge/badge-muse-badge-ideas-i
Here's the rule: http://infrastructure.fedoraproject.org/infra/badges/rules/badge-muse-01.yml
reopening - artwork too large
badge muse 110px <img alt="badge-muse.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/b051f56dbf7b6cbd3e7417698e4af0e5f148aef5a80314faa83337516c1ecc33-badge-muse.png" />
badge muse 110px <img alt="badge-muse.png" src="//issue/raw/files/b051f56dbf7b6cbd3e7417698e4af0e5f148aef5a80314faa83337516c1ecc33-badge-muse.png" />
badge muse 256px <img alt="badge-muse.2.png" src="https://pagure.io/Fedora-Badges/issue/raw/files/215fbe9da14936c7b0a704ec5f22063bd18504683184cb97960545bbb259a608-badge-muse.2.png" />
badge muse 256px <img alt="badge-muse.2.png" src="//issue/raw/files/215fbe9da14936c7b0a704ec5f22063bd18504683184cb97960545bbb259a608-badge-muse.2.png" />
Here's artwork that's size-corrected!
[[Image(badge-muse.png)]] [[Image(badge-muse.2.png)]]
yikes, we really need to set up that separate trac for bugs in badges, tracking them here doesn't really work :( but a messy ticket beats no ticket, keeping it open for now.
I proposed an extension of this series as #75.
Set triaged to 'yes' for all tickets, as I've hit them all already.
Use the new bug ticket type.
blank keywords on bugfix bugs now we have a ticket type
This was pushed out a long time ago. Closing!
https://badges.fedoraproject.org/badge/badge-muse-badge-ideas-i
Metadata Update from @ralph: - Issue assigned to duffy
I'm not sure if this still works...
trigger: all: - topic: trac.ticket.new
@rhea, please file a bug.
Metadata Update from @mleonova: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None (was: 0) - Custom field has_complete_yaml reset (from Approved (badges admins only)) - 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 adjusted to on (was: 1) - Issue close_status updated to: None (was: Pushed)
I think this was originally going to be a series of badges, but we only have one. Could we add maybe one or two more? For if you propose 5 or 10 badges?
Metadata Update from @computerkid: - 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) - Issue status updated to: Open (was: Closed)
Metadata Update from @computerkid: - Custom field artwork adjusted to has_concept (was: None) - Custom field concept_review_passed adjusted to passed (was: None) - Custom field has_complete_yaml reset (from false) - Custom field has_description adjusted to on (was: false) - Custom field has_name adjusted to on (was: false) - Custom field needs_manual_award adjusted to on (was: false)
@computerkid hmmm is there an SVG for this one in the badges repo? If so can you drop the file here please :) if not, I might be able to dig it out of some mass badge file I had. Or we could revamp the artwork entirely!!
Metadata Update from @riecatnor: - Custom field has_complete_yaml reset (from false)
I couldn't find one, sorry. If it's in there is must be VERY misnamed, I tried all different combinations of what it should be called.
Metadata Update from @computerkid: - Custom field has_complete_yaml reset (from false)
Login to comment on this ticket.