#438: 3D Printing SIG Member
-------------------------------------+-------------------------------------
Reporter: | Owner:
churchyard | 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: |
Partial |
Manually awarded: |
1 |
-------------------------------------+-------------------------------------
Badge description: You're a member of the 3D Printing Special Interest
Group
For the members of https://fedoraproject.org/wiki/SIGs/3DPrinting (would
be manually awarded by me)
Lastly, do you have any ideas for artwork concepts?
Yes, attached.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/438>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#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
#451: Kernel Tester VI and more
-------------------------------------+-------------------------------------
Reporter: | Owner:
cialu | Status: new
Type: | Keywords: kernel
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: Completed run of the kernel
regression test suite
Badge description: You have regression tested your kernel
Anything else we need to know:
Why did Kernel Tester Badge stop at level V aka 50 runs of the kernel
regression test suite?
Maybe we could do more badges of this series, about 100, 200, 500 runs?
Original discussion:
https://fedorahosted.org/fedora-badges/ticket/155
Actual badges:
https://badges.fedoraproject.org/explore
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/451>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#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
#455: Fedora @ Red Hat Summit 2016
-------------------------------------+-------------------------------------
Reporter: | Owner: spot
spot | Status: new
Type: | Keywords:
New badge idea | Has a description: 1
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: |
0 |
-------------------------------------+-------------------------------------
Badge description (like "You added a co-maintainer to a package. BFF!"):
You visited Fedora at the Red Hat Summit in 2016!
This is a new version of the previously approved 2015 badge:
https://fedorahosted.org/fedora-badges/ticket/372
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/455>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#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
#432: I've been there
-------------------------------------+-------------------------------------
Reporter: | Owner:
churchyard | Status: new
Type: | Keywords: event
New badge idea | Has a description: 1
Priority: | Artwork status: Concept
minor | External requirements:
Has a name: | Triaged (triagers only): 0
1 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
Partial |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
Badge description: You've visited a Fedora booth at an event.
1) What are those activities?
Visiting Fedora booth at a conference/meetup/etc.
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
Anyone, but the main target here are newcomers.
3) Why are they doing them (is this a means to a different end?)
They want to get some swag. Now thay can also have a badge.
4) When do they do them (every day? once a year?)
Once per an event.
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
By showing up in person.
I think we don't have the time and energy to create badges for all
conferences where Fedora has a presence. On the other hand, I'm now on
PyCon SK and lot of new potential contributors are showing up and asking
interesting questions. If we could award them a badge, we can then see if
they become active lately or not. (See
https://networksfordata.wordpress.com/2016/03/08/fedora-at-fosdem/) My
idea here is that we will have a general badge for events without a
specific badge. We would need to protect the URL somehow (i.e. creating a
specific URL before an event and disabling it after).
Artwork ideas:
* an actual booth similar to https://badges.fedoraproject.org/badge/the-
panda-is-in but with a badger standing outside the booth
* a hand with a smartphone scanning a QR code (a bit meta)
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/432>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
#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
#411: Requesting badge for Fedoa Globalization FAD attendees
-------------------------------------+-------------------------------------
Reporter: | Owner:
pravins | 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 |
-------------------------------------+-------------------------------------
Badge description (like "You added a co-maintainer to a package. BFF!"):
You done great work at G11N FAD 2016
Help the badges team understand what this idea is all about. If this
badge is awarded for certain kinds of activities:
1) What are those activities?
Languages Fedora support.
Brainstorm on new G11N architecture i.e. management of localization files.
Review of Zanata feedback survey.
Forming Governing body for G11N.
Important bug-fixing for input methods.
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
packagers, translators and couple of newcomers.
3) Why are they doing them (is this a means to a different end?)
To make Fedora a suitable project for users with different regional
language requirement.
4) When do they do them (every day? once a year?)
Every day.
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
Talking on IRC, Using Zanata web interface. Packaging and contributing to
upstream.
Lastly, do you have any ideas for artwork concepts?
This is happening in Tokyo, Japan. Badge with Fedora written in Japanese +
FAD in Latin will be nice i think.
May be some temple in Tokyo. Or City picture will be nice.
I will ask someone to provide text on Fedora written in Japanese.
Event dates: 1st to 3rd Nov. Happening at Tokyo, Japan. We have few new
participants to Fedora, it will be great and motivating for them, it they
get this badge. Apologies for being bit late on this request.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/411>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app