[fedora-badges] #364: Busy Badger
by fedora-badges
#364: Busy Badger
-------------------------------------+-------------------------------------
Reporter: | Owner:
riecatnor | 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:
Updating tickets on the fedora-badges trac 1, 10, 25, 50, 100, 250 times
Possible concepts: Badger building a badge, sticky note with 'update'
written, incomplete badge with sticky note on it, adding more sticky notes
for each badge in the series, badge blueprint with added notes for each
badge in series.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/364>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 5 months
[fedora-badges] #381: Heroes of Fedora Badges
by fedora-badges
#381: Heroes of Fedora Badges
-------------------------------------+-------------------------------------
Reporter: | Owner:
roshi | 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 |
-------------------------------------+-------------------------------------
The Fedora QA team publishes contributor stats [0] for each release (and
each milestone), and I think it'd be great if we could give badges out to
people based on our stats. I had a couple ideas for this:
- Placing Top 3 in any of the following:
- Release Validation
- Updates Testing
- Bug reports filed
- Holding a position from milestone to milestone
- Gaining a position (moving from 2nd to 1st) between milestones
- Being in the top three for all milestones
- Not being in the list and then taking one of the top three slots for
another milestone
- Getting a mention in the stats at all
I can try to think of names for all of these badges if it seems like a
good idea. This would be a manual process (for now, at least) that would
require me to send a list of names and badges - but I think it'd be good
to tie in with the Heroes of Fedora posts.
[0] https://roshi.fedorapeople.org/heroes-of-fedora-hof-
fedora-22-part-1.html
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/381>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 5 months
[fedora-badges] #393: Metabadges
by fedora-badges
#393: Metabadges
-------------------------------------+-------------------------------------
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 |
-------------------------------------+-------------------------------------
So I got this idea about Metabadges, thet you would get for collecting
badges.
The idea is that we would tag all our badges with what's on them (panda,
badges, snake, transport device, etc...) (I'm willing to do that). And
users could get badges for collecting X badges with certain thing on it.
This would require us to expose tags in Tahrir API which we currently
don't do; also in the fedmsg (which currently we probably also don't do,
but I'm not sure).
My ideas:
* Metapanda
* Metabadger
* Metasnake
* Metanumber (for badges with numbers on them)
* Metatransport
* Metawrite (for badges with things you can write with)
* Metahat (for badges with characters with something on their heads)
The exact numbers would a little less than maximum of badges we currently
have with that thing, that would get counted after the badges are tagged.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/393>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 5 months
[fedora-badges] #363: Holiday Maker
by fedora-badges
#363: Holiday Maker
-------------------------------------+-------------------------------------
Reporter: | Owner:
isimluk | Status: new
Type: | Keywords: relax
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 |
-------------------------------------+-------------------------------------
Alternative name: Camper Badge.
Criteria: Did not receive any badge in 2 months.
Rationale: Firstly, it is beneficial for one's mental health to relax for
a while. Secondly, it is also good for Fedora to remind its contributors,
that it has already been a while since their last contribution.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/363>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 7 months
[fedora-badges] #378: Bit from the core
by fedora-badges
#378: Bit from the core
-------------------------------------+-------------------------------------
Reporter: | Owner:
mattdm | 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:
Any change which either
a) reduces the number of packages installed in Fedora Cloud base
(generally, by reducing dependencies), or
b) otherwise shrinks the total compressed image size by at least 1MB
(subpackaging, better compression, just removing stuff, etc.)
Badge description (like "You added a co-maintainer to a package. BFF!"):
"You reduced the size of the Fedora Cloud image"
Anything else we need to know:
I think Kushal can track this semi-automatically (possibly using tunir).
At least, can track the size and package set, and award manually when
deserved.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/378>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 8 months
[fedora-badges] #348: Badge for release engineering members
by fedora-badges
#348: Badge for release engineering members
-------------------------------------+-------------------------------------
Reporter: | Owner:
till | 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: Membership of sysadmin-releng
Badge description (like "You added a co-maintainer to a package. BFF!"):
You keep Fedora rolling as part of the release engineering team.
Anything else we need to know:
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/348>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 8 months
[fedora-badges] #402: Badge for Fedora 23 Release Party Owners: "Let's have a party"
by fedora-badges
#402: Badge for Fedora 23 Release Party Owners: "Let's have a party"
-------------------------------------+-------------------------------------
Reporter: | Owner:
gnokii | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: Proposed
minor | External requirements:
Has a name: | Triaged (triagers only): 0
1 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
1 |
-------------------------------------+-------------------------------------
similar to #189 and #318
This badges continues existing badge for Release Party Owners. This time
for Fedora 23.
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.
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/402>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 8 months
[fedora-badges] #380: Fedora tagger
by fedora-badges
#380: Fedora tagger
-------------------------------------+-------------------------------------
Reporter: | Owner: espasmo
espasmo | 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 |
-------------------------------------+-------------------------------------
Badges for the top 10 in fedora tagger
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/380>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 8 months
[fedora-badges] #349: Badge for reporting security issues in Fedora Infrastructure
by fedora-badges
#349: Badge for reporting security issues in Fedora Infrastructure
-------------------------------------+-------------------------------------
Reporter: | Owner:
till | 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: Reporting a security issue in Fedora
Infrastructure
Badge description (like "You added a co-maintainer to a package. BFF!"):
You kept Fedora secure by reporting a security issue in Fedora's
infrastructure
Anything else we need to know:
This could also be mentioned on any pages where it is documented how to
report security issues in Fedora (I hope there are some) to motivate
people to report issues like there are bug bountys in other projects.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/349>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 11 months
[fedora-badges] #303: Speak up series continued
by fedora-badges
#303: Speak up series continued
-------------------------------------+-------------------------------------
Reporter: | Owner:
gnokii | Status: new
Type: | Keywords:
New badge idea | Has a description: 0
Priority: | Artwork status: Proposed
minor | External requirements:
Has a name: | Triaged (triagers only): 0
0 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
continue the Speak Up! IRC meeting series
25 participations
50 participations
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/303>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 11 months