badges-team July 2016

badges@lists.fedoraproject.org

3 participants
82 discussions

[fedora-badges] #455: Fedora @ Red Hat Summit 2016
by fedora-badges 12 Aug '16

12 Aug '16

#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

1 14

[fedora-badges] #456: Flock badges 2016
by fedora-badges 10 Aug '16

10 Aug '16

#456: Flock badges 2016 -------------------------------------+------------------------------------- Reporter: | Owner: gnokii | 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 | -------------------------------------+------------------------------------- Similar to #366 we need: *flock organizer *flock attendee *flock speaker *party badge -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/456> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 10

[fedora-badges] #348: Badge for release engineering members
by fedora-badges 09 Aug '16

09 Aug '16

#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

1 8

[fedora-badges] #432: I've been there
by fedora-badges 04 Aug '16

04 Aug '16

#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

1 1

[fedora-badges] #402: Badge for Fedora 23 Release Party Owners: "Let's have a party"
by fedora-badges 02 Aug '16

02 Aug '16

#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

1 3

[fedora-badges] #411: Requesting badge for Fedoa Globalization FAD attendees
by fedora-badges 02 Aug '16

02 Aug '16

#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

1 6

[fedora-badges] #418: Council member badge
by fedora-badges 02 Aug '16

02 Aug '16

#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

1 5

[fedora-badges] #441: Hot Topic - Badge series for mailing list posts
by fedora-badges 02 Aug '16

02 Aug '16

#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

1 6

[fedora-badges] #442: Licensed to Push - Get added as a contributor to Pagure repositories
by fedora-badges 02 Aug '16

02 Aug '16

#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

1 10

[fedora-badges] #471: The Flock 2016 Organizer Badge is miscategorized
by fedora-badges 01 Aug '16

01 Aug '16

#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

1 2

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

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