Re: [fedora-badges] #288: Killing Bugs
by fedora-badges
#288: Killing Bugs
-------------------------------------+-------------------------------------
Reporter: amsharma | Owner:
Type: New badge | dabzse
idea | Status:
Priority: minor | assigned
Keywords: | Resolution:
Has a description: 1 | Has a name:
Artwork status: None | 1
External requirements: | Concept approved (reviewers only):
Triaged (triagers only): 0 | 0
| Badge definition status:
| Partial
| Manually awarded:
| 0
-------------------------------------+-------------------------------------
Changes (by dabzse):
* owner: => dabzse
* status: new => assigned
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/288#comment:4>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 9 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, 9 months
[fedora-badges] #411: Requesting badge for Fedoa Globalization FAD attendees
by fedora-badges
#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
7 years, 9 months
[fedora-badges] #418: Council member badge
by fedora-badges
#418: Council member badge
-------------------------------------+-------------------------------------
Reporter: | Owner:
robyduck | Status: new
Type: | Keywords:
New badge idea | Has a description: 1
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: |
0 |
-------------------------------------+-------------------------------------
What the badge should be granted for: Former and current Council Members
Badge description (like "You added a co-maintainer to a package. BFF!"):
This Badge should be granted to all former and current council members as
recognition of their hard work.
"You have been a member of the Fedora Council!"
Anything else we need to know: There is no council FAS group AFAIK, but we
could award them manually if nothing else helps.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/418>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 9 months
[fedora-badges] #441: Hot Topic - Badge series for mailing list posts
by fedora-badges
#441: Hot Topic - Badge series for mailing list posts
-------------------------------------+-------------------------------------
Reporter: | Owner:
jflory7 | Status: new
Type: | Keywords:
New badge idea | Has a description: 1
Priority: | Artwork status: None
minor | External requirements:
Has a name: | Triaged (triagers only): 1
1 |
Concept approved (reviewers only): |
1 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
= Badge Description =
* '''Name''': Hot Topic {I,II,III,IV}
* '''Description''':
* I: Congratulations, you made your first post on a Fedora mailing list!
* II: You've made 10 posts on Fedora mailing lists.
* III: You've made 100 posts on Fedora mailing lists.
* IV: You've made 1000 posts on Fedora mailing lists. You're a mailing
list master!
= Understanding badge =
1) What are those activities?
* '''Users are granted badge for mailing list activity (now possible with
the advent of Mailman3 + Hyperkitty'''
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
* '''Any and all contributors (depends on list)'''
3) Why are they doing them (is this a means to a different end?)
* '''Making posts to mailing lists'''
4) When do they do them (every day? once a year?)
* '''Hourly, daily, weekly, monthly, annually… etc.'''
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
* '''Sending email to a list you are subscribed to'''
= Artwork concepts =
* A panda and a badger tossing a paper airplane between each other
* A {panda,badger} holding a sealed envelope
* [Pre-existing artwork] {Panda,badger} sitting at computer looking at
screen, with screen saying something like, "You have mail!"
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/441>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 9 months
[fedora-badges] #442: Licensed to Push - Get added as a contributor to Pagure repositories
by fedora-badges
#442: Licensed to Push - Get added as a contributor to Pagure repositories
-------------------------------------+-------------------------------------
Reporter: | Owner:
jflory7 | Status: new
Type: | Keywords:
New badge idea | Has a description: 1
Priority: | Artwork status: Concept
minor | External requirements:
Has a name: | Triaged (triagers only): 1
1 |
Concept approved (reviewers only): |
0 |
Badge definition status: |
None |
Manually awarded: |
0 |
-------------------------------------+-------------------------------------
= Badge Description =
* '''Name''': Licensed to Push {I,II,III,IV}
* '''Description''':
* I: Congratulations, you were added as a contributor to your first
repository on Fedora Pagure (pagure.io)!
* II: You've been added as a contributor to 10 repositories on Fedora
Pagure (pagure.io).
* III: You've been added as a contributor to 25 repositories on Fedora
Pagure (pagure.io).
* IV: You've been added as a contributor to 100 repositories on Fedora
Pagure (pagure.io). With great power comes great responsibility...
= Understanding badge =
1) What are those activities?
* '''Users are granted badge for being added as a contributor to a
respository on Pagure, Fedora's git hosting service'''
2) Who is doing them (are they packagers? translators? newcomers?
veterans? users? sponsors?)
* '''Packagers, developers, maintainers, etc.'''
3) Why are they doing them (is this a means to a different end?)
* '''Adding more contributors to a repo to help with development of a
project (usually as a permanent member of the project / repo)'''
4) When do they do them (every day? once a year?)
* '''Once per repository (although a user could be removed and added to
the same repo again, should be taken into consideration)'''
5) How do they do them (by talking in IRC? by running commands in the
console? by using a web interface?)
* '''Another repository admin / owner is adding them as a contributor'''
= Artwork concepts =
* <optimistic>In spirit of the badge name and its [http://ecx.images-
amazon.com/images/I/51j-SggaWSL.jpg inspiration], some sort of snap of the
tail end of a plane with a number for the repositories added to (e.g. 1,
10, 25, 100)</optimistic>
* {Panda,badger} standing, holding a rectangular-shaped card (like a
license…) with the number of repositories they are added to on it
* Some kind of combination of keys (e.g. Crypto Panda / Badger) mixed with
Pagure logo
= Other discussion =
As of the moment, I don't know if there is a fedmsg hook in place to
automate this badge series. If there is, this ticket's concept can be
marked as "approved". If not, this ticket should be closed and the badge
definition status set to "not yet possible".
Note, this ticket is similar to #434.
I am CCing robyduck and pingou to help advise on this one in terms of
whether it is possible.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/442>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 9 months
[fedora-badges] #471: The Flock 2016 Organizer Badge is miscategorized
by fedora-badges
#471: The Flock 2016 Organizer Badge is miscategorized
-------------------------------------+-------------------------------------
Reporter: | Owner:
bex | Status: new
Type: | Keywords:
Bug report | 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 |
-------------------------------------+-------------------------------------
Problem:The flock 2016 organizer badge should be categorized as an Event
Badge, like the 2015 one was. It is currently uncategorized.
--
Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/471>
fedora-badges <https://badges.fedoraproject.org>
A place to collect and debate badge ideas for the Fedora Badges app
7 years, 9 months