See also [https://fedorahosted.org/fedora-badges/ticket/46 ticket 46]?

See also [https://fedorahosted.org/fedora-badges/ticket/46 ticket 46]?

ryanlerch from #46 suggests "Title: "Na, na, na, na, na, na, Leader!"" - http://www.youtube.com/watch?v=7fnmhj58o0k .

I don't think we have an easy way to do this with fedmsg at present, so setting external requirement field: we'd need some kind of icky wiki page scraping to capture it, I think.

ryanlerch from #46 suggests "Title: "Na, na, na, na, na, na, Leader!"" - http://www.youtube.com/watch?v=7fnmhj58o0k .

I don't think we have an easy way to do this with fedmsg at present, so setting external requirement field: we'd need some kind of icky wiki page scraping to capture it, I think.

See also: #58. That's a slightly wider 'retired from a leadership position' proposal.

See also: #58. That's a slightly wider 'retired from a leadership position' proposal.

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.

FYI, I submitted this one at https://fedoraproject.org/wiki/Open_Badges#Badge_Ideas as "Commander-in-Chief" back in March.

FYI, I submitted this one at https://fedoraproject.org/wiki/Open_Badges#Badge_Ideas as "Commander-in-Chief" back in March.

[[Image(apex.svg)]]

[[Image(apex.svg)]]

attachment
apex.svg

attachment
apex.svg

fabulous!!

fabulous!!

attachment

attachment

Pushed! https://badges.fedoraproject.org/badge/apex

Pushed! https://badges.fedoraproject.org/badge/apex

I also updated the wiki page of FPL succession tasks so that hopefully future FPLs will get the badge too - https://fedoraproject.org/wiki/FPL_succession_tasks

We'll do it manually.

I also updated the wiki page of FPL succession tasks so that hopefully future FPLs will get the badge too - https://fedoraproject.org/wiki/FPL_succession_tasks

We'll do it manually.

Hey, I have an idea that's less susceptible to wiki scraping issues. But if this is not easily achievable, please re-close this bug and consider it a non-issue. The 'chair' alias in SMTP is set up to hold only the FPL's account name -- would this be sourceable for a badge when a puppet change is made to the aliases?

Hey, I have an idea that's less susceptible to wiki scraping issues. But if this is not easily achievable, please re-close this bug and consider it a non-issue. The 'chair' alias in SMTP is set up to hold only the FPL's account name -- would this be sourceable for a badge when a puppet change is made to the aliases?

Yeah, but for such a rare event, it may not be worth investing the time in automation here. If the automation fails, we won't know for the next N years (when the FPL changes next) and then we'll have to notice and spend time figuring out why it didn't work (did we migrate from puppet to ansible in the meantime? did we migrate from ansible to saltstack?)

Having a badges admin manually award the badge to the next FPL once every so many years seems like less work in the long run.

Yeah, but for such a rare event, it may not be worth investing the time in automation here. If the automation fails, we won't know for the next N years (when the FPL changes next) and then we'll have to notice and spend time figuring out why it didn't work (did we migrate from puppet to ansible in the meantime? did we migrate from ansible to saltstack?)

Having a badges admin manually award the badge to the next FPL once every so many years seems like less work in the long run.