#21 Old Yeller badge
Closed: Pushed None Opened 5 years ago by adamwill.

New badge idea: a badge for retiring a package, the Old Yeller badge. (I'll try and use the badge builder to come up with yml for this one).


Partial badge file - missing an image and the precise trigger right now
old-yeller.yml

Partial badge file - missing an image and the precise trigger right now
old-yeller.yml

Updating the yml file with the criteria. Same as those proposed for the Hatchling badge (https://fedorahosted.org/fedora-badges/ticket/43 ). I think we can still use package owner as a proxy for 'person retiring the package' and it should be correct in most cases, but it might be good to check that with People In The Know. I think the only people who will be retiring packages are their owners and a bot for retiring long-term orphans, but IMBW. I guess this will give credit 'unfairly' to people who just orphan their packages and leave them for others to clean up, but I'm not sure if we can fix that.

Updating the yml file with the criteria. Same as those proposed for the Hatchling badge (https://fedorahosted.org/fedora-badges/ticket/43 ). I think we can still use package owner as a proxy for 'person retiring the package' and it should be correct in most cases, but it might be good to check that with People In The Know. I think the only people who will be retiring packages are their owners and a bot for retiring long-term orphans, but IMBW. I guess this will give credit 'unfairly' to people who just orphan their packages and leave them for others to clean up, but I'm not sure if we can fix that.

updated yaml file with criteria (still no artwork)
pkgdb-old-yeller.yml

updated yaml file with criteria (still no artwork)
pkgdb-old-yeller.yml

Artwork concept: may be tricky to do this one tastefully =) Perhaps just a tombstone for a package, however that could be represented? A nice dog with a halo? Definitely no gore or shotguns :)

Artwork concept: may be tricky to do this one tastefully =) Perhaps just a tombstone for a package, however that could be represented? A nice dog with a halo? Definitely no gore or shotguns :)

Moar art added. Package image, instead of Panda Image.

Moar art added. Package image, instead of Panda Image.

I LOVE that art. But I think we want the SVG as well as / instead of the PNG? Can you add it? Thanks!

I LOVE that art. But I think we want the SVG as well as / instead of the PNG? Can you add it? Thanks!

updated yaml file with fix to the criteria and line wrapping fix
pkgdb-old-yeller.2.yml

updated yaml file with fix to the criteria and line wrapping fix
pkgdb-old-yeller.2.yml

Would this become a counting badge series, all the way up to serial killer?

Would this become a counting badge series, all the way up to serial killer?

Set triaged to 'yes' for all tickets, as I've hit them all already.

Set triaged to 'yes' for all tickets, as I've hit them all already.

just put types back in, we'll try and handle bugs here too, no new trac.

just put types back in, we'll try and handle bugs here too, no new trac.

notting: it could be. I'm not a huge serial badge fan myself, but I dunno. I mean to bring up the question of when to do serial badges when i finally get around to starting a badge policy discussion.

notting: it could be. I'm not a huge serial badge fan myself, but I dunno. I mean to bring up the question of when to do serial badges when i finally get around to starting a badge policy discussion.

Hm, I think the recipient and the user for the datanommer criteria query should be %(msg.agent) instead of %(msg.package_listing.owner).

Usually in fedmsg messages, if an "agent" field is present, its there because there are multiple users involved and we needed a way to demarcate the "doer" of the action. Here, the one retiring the package should be the recipient, not the old owner (which is usually "orphan" anyways).

Hm, I think the recipient and the user for the datanommer criteria query should be %(msg.agent) instead of %(msg.package_listing.owner).

Usually in fedmsg messages, if an "agent" field is present, its there because there are multiple users involved and we needed a way to demarcate the "doer" of the action. Here, the one retiring the package should be the recipient, not the old owner (which is usually "orphan" anyways).

updated yaml which awards the badge to the right person and not 'orphan', thanks threebean for the catch
pkgdb-old-yeller.3.yml

updated yaml which awards the badge to the right person and not 'orphan', thanks threebean for the catch
pkgdb-old-yeller.3.yml

Here's decause's .svg - can someone from the design team use it to fix the pngs like ryanlerch mentions in #22?

https://raw.github.com/FOSSRIT/badges/master/art/src/fedora/oldyeller.svg

Here's decause's .svg - can someone from the design team use it to fix the pngs like ryanlerch mentions in #22?

https://raw.github.com/FOSSRIT/badges/master/art/src/fedora/oldyeller.svg

old yeller with padding (256)
old-yeller.png

old yeller with padding (256)
old-yeller.png

here u go :)

[[Image(old-yeller.png)]]

here u go :)

[[Image(old-yeller.png)]]

Reopening - this appears to have not been awarded since it's been activated - is something wrong in the yaml?

(The inverse of this for unretiring a package appears to have the same problem.)

Reopening - this appears to have not been awarded since it's been activated - is something wrong in the yaml?

(The inverse of this for unretiring a package appears to have the same problem.)

I noticed the same as notting. I retired a package on Sept 16 (ql23xx-firmware) and nobody has gotten the Old Yeller badge.

I noticed the same as notting. I retired a package on Sept 16 (ql23xx-firmware) and nobody has gotten the Old Yeller badge.

Replying to [comment:25 notting]:

Reopening - this appears to have not been awarded since it's been activated - is something wrong in the yaml?

(The inverse of this for unretiring a package appears to have the same problem.)

Applies to me, too. Just orpahned a pkg and no award.

Replying to [comment:25 notting]:

Reopening - this appears to have not been awarded since it's been activated - is something wrong in the yaml?

(The inverse of this for unretiring a package appears to have the same problem.)

Applies to me, too. Just orpahned a pkg and no award.

Reopening as this badge was awarded at "2014-05-07" for the last time, which is quite an usually long time for not getting any award, isn't it?
[https://bugzilla.redhat.com/show_bug.cgi?id=1114952#c8 A few days a ago], I retired a package, but got no badge for it.

Reopening as this badge was awarded at "2014-05-07" for the last time, which is quite an usually long time for not getting any award, isn't it?
[https://bugzilla.redhat.com/show_bug.cgi?id=1114952#c8 A few days a ago], I retired a package, but got no badge for it.

Indeed. If you look at the history of pkgdb.package.retire messages in datagrepper, you see that the last message of that type was published 2 months ago:

https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.pkgdb.package.retire

That is right about the time that we switched over to pkgdb2 -- the message/type/content must have changed.

Indeed. If you look at the history of pkgdb.package.retire messages in datagrepper, you see that the last message of that type was published 2 months ago:

https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.pkgdb.package.retire

That is right about the time that we switched over to pkgdb2 -- the message/type/content must have changed.

OK, this change to the badges rules should fix it. Please re-open if you notice any further problems:

https://git.fedorahosted.org/cgit/badges.git/commit/?id=0bff549c851a7aa66285ee4009dd23a2cd37fa64

OK, this change to the badges rules should fix it. Please re-open if you notice any further problems:

https://git.fedorahosted.org/cgit/badges.git/commit/?id=0bff549c851a7aa66285ee4009dd23a2cd37fa64

Metadata Update from @adamwill:
- Issue assigned to decause

2 years ago

It seems that this badge has stopped being awarded. I sent liborigin2 to its grave a few days ago and I was anxiously waiting for the badge, but then I noticed that the last time anyone got it was in July of 2017. There have been plenty of retirements since then, so my guess is that it needs some tweaking again.

As was mentioned in the past, "Phoenix Down", the badge for unretiring packages, also hasn't been awarded in 4 years (missing that one as well!).

Login to comment on this ticket.

Metadata
Attachments 6
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment