badges-team January 2015

badges@lists.fedoraproject.org

1 participants
78 discussions

[fedora-badges] #296: Get ready!
by fedora-badges 07 Aug '15

07 Aug '15

#296: Get ready! -------------------------------------+------------------------------------- Reporter: | Owner: jreznik | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None minor | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: attending Fedora release readiness meeting as an active participant (Alpha, Beta, Final) Badge description (like "You added a co-maintainer to a package. BFF!"): Something like "Ship it! We're ready for the another awesome release." Anything else we need to know: could be granted manually, I can prepare the list or automatically if possible when someone writes 1+ lines during the meeting (Meetbot is present)/chair (I'll make sure participant get chair). Credits for the idea: robyduck -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/296> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 8

[fedora-badges] #326: Fedora PA Member
by fedora-badges 28 Jul '15

28 Jul '15

#326: Fedora PA Member -------------------------------------+------------------------------------- Reporter: | Owner: blackfile | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None minor | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: People applicants to Group Fedora Panama should be based in Panama. Badge description (like "You added a co-maintainer to a package. BFF!"): you're accepted as a member in the Group Fedora Panama Anything else we need to know: -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/326> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 16

[fedora-badges] #335: DevConf.cz 2015
by fedora-badges 21 Jul '15

21 Jul '15

#335: DevConf.cz 2015 -------------------------------------+------------------------------------- Reporter: | Owner: eischmann | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None major | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: for attending DevConf.cz 2015, we will have a QR code at the Fedora booth. Badge description (like "You added a co-maintainer to a package. BFF!"): You attended DevConf.cz 2015. Anything else we need to know: I would use the same artwork as last year, just changing the year. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/335> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 13

[fedora-badges] #337: AppStream font metainfo file contribution badge
by fedora-badges 21 Jul '15

21 Jul '15

#337: AppStream font metainfo file contribution badge -------------------------------------+------------------------------------- Reporter: | Owner: pnemade | Status: new Type: | Keywords: appdata New badge idea | Has a description: 0 Priority: | Artwork status: None minor | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: Those who are adding AppStream metainfo files in fonts packages. As we have this work already done for the required fonts packages, I think I cannot ask for automatic badge award based on git commit message. So, this need to be manually awarded. We can also use this badge for future metainfo file contribution in fonts packages. On 16th October 2014, on fonts list we received email https://lists.fedoraproject.org/pipermail/fonts/2014-October/001747.html which asked to help by adding appdata files in fonts packages. People maintaining fonts packages then started working on this. Then Richard sent an email on devel list https://lists.fedoraproject.org/pipermail/devel/2014-October/203394.html and created google spreadsheet https://docs.google.com/spreadsheets/d/1o2sPWF7PEe6BKnBeZUI23m51nfFHUMx61IR… to avoid people working on the same font package. We then collectively finished this work, announced that in https://lists.fedoraproject.org/pipermail/devel/2014-November/204497.html and its documented in that spreadsheet. Badge description (like "You added a co-maintainer to a package. BFF!"): You're an AppStream font metainfo contributor! Anything else we need to know: This idea is the outcome of private email discussion about https://fedorahosted.org/fedora-badges/ticket/272 -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/337> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 5

[fedora-badges] #330: FAD Rheinland 2014 Attendee
by fedora-badges 21 Jul '15

21 Jul '15

#330: FAD Rheinland 2014 Attendee -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None minor | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: Attending http://fedoraproject.org/wiki/FAD_Rheinland_2014 Badge description (like "You added a co-maintainer to a package. BFF!"): Now we are talking business Anything else we need to know: This years https://badges.fedoraproject.org/badge/fad-rheinfelden-2013-attendee - but the design cannot be reused. I have no idea for the artwork yet. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/330> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 5

[fedora-badges] #319: A badge for FAD attendees
by fedora-badges 21 Jul '15

21 Jul '15

#319: A badge for FAD attendees -------------------------------------+------------------------------------- Reporter: | Owner: pjp | Status: new Type: | Keywords: FAD New badge idea | Has a description: 0 Priority: | Artwork status: None major | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: We plan to host a Fedora Activity Day(FAD) on 1 Nov 2014. Could we have a badge for the attendees as a token for their participation? -> https://fedoraproject.org/wiki/FAD_Pune_Security_1 Badge description (like "You added a co-maintainer to a package. BFF!"): Ummn -> "FAD Pune, 01 Nov 2014." Anything else we need to know: The theme for this FAD is Security. It would be great if the badge design could show that security aspect somehow. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/319> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 2

[fedora-badges] #311: Badget for multiple security updates via bodhi
by fedora-badges 21 Jul '15

21 Jul '15

#311: Badget for multiple security updates via bodhi -------------------------------------+------------------------------------- Reporter: | Owner: robert | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None minor | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: If somebody submits a single security update (s)he receives "white hat". But what if somebody submits 10, 50 or 100 security updates? Badge description (like "You added a co-maintainer to a package. BFF!"): (sorry, I do not have any good idea) Anything else we need to know: The basic idea behind is outlined, there is likely enough people in Fedora who submitted more than just one security update. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/311> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 1

[fedora-badges] #318: Badge for Fedora 21 Release Party Owners: "Let's have a party"
by fedora-badges 27 Jun '15

27 Jun '15

#318: Badge for Fedora 21 Release Party Owners: "Let's have a party" -------------------------------------+------------------------------------- Reporter: | Owner: robyduck | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None minor | External requirements: Has a name: | Triaged (triagers only): 0 1 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 1 | -------------------------------------+------------------------------------- This badges continues existing badge #189 for Release Party Owners. This time for Fedora 21! What the badge should be granted for: FAmSCo want to give all Release Party organizers a release specific badge. Badge description (like "You added a co-maintainer to a package. BFF!"): Everyone who organizes a Release Party should get a release specific badge. Release Parties take place immediately after a new version of Fedora gets released. Anything else we need to know: Although the owners will be known about 1-2 months afte GA release, it will not be possible to assign the badge automatically, IMHO. Therefore they have to be assigned manually, following a list FAmSCo will be able to pass at some point to the Infra team. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/318> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 20

[fedora-badges] #341: Fedora 22 Change Accepted
by fedora-badges 02 Jun '15

02 Jun '15

#341: Fedora 22 Change Accepted -------------------------------------+------------------------------------- Reporter: | Owner: ralph | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None major | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- This is a followup to ticket #297 and ticket #1. Badge description (like "You added a co-maintainer to a package. BFF!"): "You got a "Change" accepted into the Fedora 20 Change list" Anything else we need to know: http://fedoraproject.org/wiki/Releases/22/ChangeSet here are name of people submitted change proposal in F22 -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/341> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 7

[fedora-badges] #308: shellshocked
by fedora-badges 29 Apr '15

29 Apr '15

#308: shellshocked -------------------------------------+------------------------------------- Reporter: | Owner: mattdm | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None major | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- What the badge should be granted for: Helping build, test, document, or push the fix for CVE-2014-6271 (and followups). Badge description: "You helped us bash the shellshocked bug." Anything else we need to know: Like: https://badges.fedoraproject.org/badge/heartbleed-buster -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/308> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 39

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

[MOVED TO DISCOURSE] Fedora Badges - https://discussion.fedoraproject.org/tag/badges-team January 2015