[fedora-badges] #319: A badge for FAD attendees
by fedora-badges
#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
8 years, 9 months
[fedora-badges] #311: Badget for multiple security updates via bodhi
by fedora-badges
#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
8 years, 9 months
[fedora-badges] #318: Badge for Fedora 21 Release Party Owners: "Let's have a party"
by fedora-badges
#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
8 years, 10 months
[fedora-badges] #308: shellshocked
by fedora-badges
#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
9 years
[fedora-badges] #331: Country in FAS
by fedora-badges
#331: Country in FAS
-------------------------------------+-------------------------------------
Reporter: | Owner:
fale | 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:
Adding (or having) the country declared in FAS
Badge description (like "You added a co-maintainer to a package. BFF!"):
You pinned your country!
Anything else we need to know:
This information should be easily foundable in FAS :)
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/331>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
9 years, 1 month
[fedora-badges] #328: Cookie Badge
by fedora-badges
#328: Cookie Badge
-------------------------------------+-------------------------------------
Reporter: | Owner:
duffy | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: Concept
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:
So here's the idea. The FPL has the FPL blessing, right? But, someone did
something really helpful and awesome for me today, with no expectation of
getting anything in return. This person really made my life easier. And I
really wish I could give him something as a token of my appreciation.
So my thought here - maybe everyone in the Fedora project gets an amount
of cookie badges that they can hand out as thank yous to others in the
project as they're getting things done and helping each other out. You
can't award one to yourself, only others. Maybe you get one cookie for
every 5 badges you have earned, so folks get a number of cookies
proportional to their achievements in the system, and if they run out they
can replenish their cookies by earning more badges.
If a user earns more than one cookie badge, they can stack up the way the
series badges stack. so you could get a 1 cookie badge, 10 cookie badge,
25 cookie badge, 50 cookie badge, and a 100+ cookie badge. Beyond that, I
think maybe you've got enough cookies :)
Badge description (like "You added a co-maintainer to a package. BFF!"):
1 - "You've been given a cookie for helping someone out. Thanks!"
10 - "Ten people think you're great, because they've given you cookies.
Yummy!"
25 - "Mmmmm.... cookies. You've helped out 25 Fedorans! Go you!"
50 - "50 Fedorans have recognized your achievements by giving you
cookies."
100+ - "You have helped so many Fedorans you've got over 100 cookies.
Don't eat them all at once!"
Anything else we need to know:
The dark side has cookies too, but ours are more better.
Each level could feature a different type of cookie - chocolate chip,
oatmeal, snickerdoodle, etc
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/328>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
9 years, 1 month
[fedora-badges] #293: Badge for sending patch to a list
by fedora-badges
#293: Badge for sending patch to a list
-------------------------------------+-------------------------------------
Reporter: | Owner:
elad | 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: Sending a patch to a fedora mailing
list
Badge description: You sent a patch to a Fedora mailing list!
Anything else we need to know: It's considered a rare event in Fedora to
have patches sent to (most) public lists. We usually use bugzilla and
such, and mailing lists are full of people arguing minor details. Today, a
rare event happened and stickster sent a patch to the desktop list. I feel
this rare event should be awarded with a special badge :)
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/293>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
9 years, 1 month
[fedora-badges] #313: Blocker/Freeze exception granted
by fedora-badges
#313: Blocker/Freeze exception granted
-------------------------------------+-------------------------------------
Reporter: | Owner:
twaugh | 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:
A proposal you made for a blocker or freeze exception bug was granted.
Badge description (like "You added a co-maintainer to a package. BFF!"):
"Just in time! You proposed a blocker/freeze exception bug and it was
approved!"
Anything else we need to know:
Should link with https://qa.fedoraproject.org/blockerbugs
Would be nice to award a badge to the person who reported the bug as well.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/313>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
9 years, 3 months
[fedora-badges] #317: LinuxCon 2014 Düsseldorf Attendant
by fedora-badges
#317: LinuxCon 2014 Düsseldorf Attendant
-------------------------------------+-------------------------------------
Reporter: | Owner:
heffer | Status: new
Type: | Keywords: linuxcon
New badge idea | event 2014
Priority: | Has a description: 0
minor | Artwork status: None
Has a name: | External requirements:
0 | Triaged (triagers only): 0
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
What the badge should be granted for: Attendance at LinuxCon 2014 in
Düsseldorf
Badge description: Attended LinuxCon 2014 in Düsseldorf
Anything else we need to know: You rock!
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/317>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
9 years, 3 months
[fedora-badges] #324: new badge: Uh, try this instead
by fedora-badges
#324: new badge: Uh, try this instead
-------------------------------------+-------------------------------------
Reporter: | Owner:
tomspur | 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: editing an update and replacing one
build with a newer one
Badge description (like "You added a co-maintainer to a package. BFF!"):
"You replaced one build in an update. Hope not it's fixed!"
Anything else we need to know:
I was recently replacing one build in one of my updates with a newer one
and was watching `fedmsg`. I _think_ there is no msg sent yet, that you
removed on build from the update. Or did I just miss it?
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/324>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
9 years, 3 months