Fedora Badges August 2014

badges@lists.stg.fedoraproject.org

5 participants
28 discussions

Re: [badges] [fedora-badges] #290: APAC badge dancer
by fedora-badges 21 Aug '14

21 Aug '14

#290: APAC badge dancer -------------------------------------+------------------------------------- Reporter: | Owner: botreynisa | Status: Type: New badge | new idea | Resolution: Priority: minor | Has a name: Keywords: | 0 Has a description: 0 | Concept approved (reviewers only): Artwork status: None | 0 External requirements: | Badge definition status: Triaged (triagers only): 0 | None | Manually awarded: | 0 -------------------------------------+------------------------------------- Comment (by riecatnor): [[Image(FAD_phnompenh.png)]] Here is a first draft of the badge.. I tried my hardest to make sure that I was including all of the traditional elements of this costume, let me know if I missed anything! Any other suggestions are also welcome :) -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/290#comment:2> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 0

Re: [badges] [fedora-badges] #276: "You can pry it from my cold, dead hands" badge has bogus trigger
by fedora-badges 21 Aug '14

21 Aug '14

#276: "You can pry it from my cold, dead hands" badge has bogus trigger -------------------------------------+------------------------------------- Reporter: sinic | Owner: Type: Bug | Status: report | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: None | Concept approved (reviewers only): External requirements: | 0 Triaged (triagers only): 0 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+------------------------------------- Comment (by sinic): Am I correct in assuming that there's no way to provide karma to updates once a version of Fedora is EOL? Then it should be sufficient to decrement the rule's version string (and change the comment, of course). I can remove it from https://fedoraproject.org/wiki/End_of_life_SOP#Badges_tasks and add it to fedora-releases.txt in the infrastructure documents, sure. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/276#comment:3> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 0

Re: [badges] [fedora-badges] #37: Apex
by fedora-badges 21 Aug '14

21 Aug '14

#37: Apex -------------------------------------+------------------------------------- Reporter: ralph | Owner: Type: New badge | Status: idea | closed Priority: minor | Resolution: Keywords: | pushed Has a description: 1 | Has a name: Artwork status: Approved | 1 (design team members only) | Concept approved (reviewers only): External requirements: fedmsg | 0 for fpl status (wiki page | Badge definition status: scrape?) | None Triaged (triagers only): 1 | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by ralph): * status: reopened => closed * resolution: => pushed Comment: 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. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/37#comment:16> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Fedora Badges August 2014