badges-team August 2016

badges@lists.fedoraproject.org

5 participants
78 discussions

badges Calling All Fedora Badgers
by Ralph Bean 09 Apr '17

09 Apr '17

Hi all, I got to thinking about how to actually use this list (it has seen zero real usage since its creation) and here's what I came up with: what if we directed the trac instance at https://fedorahosted.org/fedora-badges/ to send emails here everytime there was a new ticket or an update on an existing ticket? Currently, I'm the only one that is notified of activity there and keeping me as a bottleneck there is a bad idea longer-term. On the other hand, this would generate a lot of traffic here (maybe too much). I'm leaning towards doing it. Does anyone want to weigh in? Any objections?

5 5

[fedora-badges] #333: Oh, wait!
by fedora-badges 01 Mar '17

01 Mar '17

#333: Oh, wait! -------------------------------------+------------------------------------- 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 | -------------------------------------+------------------------------------- What the badge should be granted for: Canceling a Koji build Badge description (like "You added a co-maintainer to a package. BFF!"): You have cancelled a running Koji build -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/333> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 6

[fedora-badges] #424: You helped get NodeJS 4 into Fedora
by fedora-badges 16 Jan '17

16 Jan '17

#424: You helped get NodeJS 4 into Fedora -------------------------------------+------------------------------------- Reporter: | Owner: jsmith | 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 helped get NodeJS 4 into Fedora. Thanks! 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? Helping out with the effort to get NodeJS 4.x (and it's long list of dependencies) into Fedora 24. 2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?) Packagers 3) Why are they doing them (is this a means to a different end?) As part of the NodeJS feature. 4) When do they do them (every day? once a year?) It's a one-time effort to get NodeJS 4.x into Fedora 5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?) By building, updating, and reviewing packages. The badge would likely be awarded manually by the feature owners. Lastly, do you have any ideas for artwork concepts? The NodeJS logo typically includes a hexagon and a muted (almost sage?) green color. The badge might include a green hexagon with "4" or "4.x" in the middle, or maybe just a green hexagon on a package box. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/424> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 18

[fedora-badges] #470: Request a badge for localization members l10n
by fedora-badges 16 Jan '17

16 Jan '17

#470: Request a badge for localization members l10n -------------------------------------+------------------------------------- Reporter: | Owner: fredlima | Status: new Type: | Keywords: l10n, New badge idea | zanata 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 | -------------------------------------+------------------------------------- Badge description (like "You added a co-maintainer to a package. BFF!"): L10n new members of a language team in zanata. After the new member have his subscription approved on a language team on zanata, I think he deserves a badge 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? translating Fedora websites, packages, spins to other language than english 2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?) translators 3) Why are they doing them (is this a means to a different end?) they brings fedora to another languages 4) When do they do them (every day? once a year?) every time a new member has subscription approved on one language team in zanata 5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?) using web interface zanata Lastly, do you have any ideas for artwork concepts? a dictionary -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/470> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 27

[fedora-badges] #464: CommOps Onboarding Series Badge
by fedora-badges 12 Jan '17

12 Jan '17

#464: CommOps Onboarding Series Badge -------------------------------------+------------------------------------- Reporter: | Owner: skamath skamath | 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!"): 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? This badge is to be awarded to those who completes / have completed the Onboarding Series of Commops. 2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?) This badge targets the new-comers 3) Why are they doing them (is this a means to a different end?) This will help keep track of the Onboarding series and this badge, if implemented can be a nice reward for it. 4) When do they do them (every day? once a year?) They do it once. 5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?) This badge is dependent on other badges / activities like : * Creating a FAS Account and signing the FPCA ( [https://badges.fedoraproject.org/badge/involvement Involvement badge] ) * Sending an introductory email to the [https://admin.fedoraproject.org/mailman/listinfo/CommOps CommOps Mailing Lists] * Attending a commops meeting * Getting sponsored to the [https://admin.fedoraproject.org/accounts/group/view/commops CommOps group] * Editing wiki-pages ( [https://badges.fedoraproject.org/badge/junior- editor Junior Editor] ) / blogs / fed-mag articles If the user completes the above-mentioned activities, this badge is to be rewarded. 6) Lastly, do you have any ideas for artwork concepts? Not yet. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/464> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 7

[fedora-badges] #361: Badge Request: Fedora Atomic
by fedora-badges 09 Jan '17

09 Jan '17

#361: Badge Request: Fedora Atomic -------------------------------------+------------------------------------- Reporter: | Owner: jzb | 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 | -------------------------------------+------------------------------------- A lot of folks have contributed work to enable the Fedora Atomic Host from the Fedora Cloud edition. I'd like to have a badge that we can award to people who've made contributions that have helped make it happen and work on continued improvement. I'm thinking something like "Atomizer" or "Fedora Atomic Scientist" -- would like to stay away from any "splitting the atom" metaphors. :-) I can provide SVGs of the Project Atomic logo if that would be helpful. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/361> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 28

[fedora-badges] #412: Side by side
by fedora-badges 04 Jan '17

04 Jan '17

#412: Side by side -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | 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: | Partial | Manually awarded: | 0 | -------------------------------------+------------------------------------- Badge description (like "You added a co-maintainer to a package. BFF!"): You've built a package in a side tag. 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? Trigger a build of any package in any side tag in Koji. 2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?) Packagers. 3) Why are they doing them (is this a means to a different end?) When a new version of important lib is released. 4) When do they do them (every day? once a year?) Side tags in Koji only happen when certain stack needs a rebuild. This is not very often, usually a few times a year. 5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?) By using fedpkg. Lastly, do you have any ideas for artwork concepts? Some characters (badgers or pandas) standing side by side. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/412> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 19

[fedora-badges] #475: Fedora 25 Release Party Attendee
by fedora-badges 17 Dec '16

17 Dec '16

#475: Fedora 25 Release Party Attendee -------------------------------------+------------------------------------- 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: | Not yet possible | Manually awarded: | 1 | -------------------------------------+------------------------------------- = Metadata = * '''Badge Name''': Fedora 25 Release Partygoer * '''Badge Description''': Attended a local release party to celebrate the launch of Fedora 25! = Artwork ideas = One thing to note is distinguishing between the [https://fedorahosted.org /fedora-badges/attachment/ticket/452/release_party_24.png badge] for release party organizers. It may be helpful to come up with ways to keep the same theme between the two but separate them in another way (sort of similar to Flock attendee vs. organizer badges). 1. One panda with a party hat on, with the number of the release 2. Cake with the release number on it 3. Ball drop-esque tower, with the release number on the ball (as it "descends" down) = Understanding badge = 1. '''What activities''': Awarded to those who attend a release event but aren't necessarily organizing it 2. '''Who does it''': Newcomers to the project who may not have a FAS account yet (but this may encourage them to get one), or current contributors who may be nearby the area for a party 3. '''Why''': Gives some kind of "achievement" for going to a party and participating in the event, like a milestone that could be shown or displayed later on 4. '''When''': Once a release, when an attendee could make it a local release party happening in their area 5. '''How''': Scanning the QR code at the party or getting the link at the event To expand on this badge idea a little more, it would be helpful to have this from a community metrics perspective. This specific badge idea popped up at the CommOps workshop at Flock. For this badge, we would be able to have all party organizers have the QR code at their event. After release parties wind down, we could look at the dates where the badge was claimed and associate the dates with specific events. It would be possible to evaluate the impact the event had towards bringing more interested people into Fedora (e.g. did someone already have a FAS account before the event? Or did they make one there? Did they become more active in the project after the event? etc.). This would also be useful to compare against other events to see where we are having more of an impact. bee2502 may be able to expand on this too if there's any angle that I missed. Going to CC some designers to this ticket too since the ticket should be triaged / pending designer feedback now. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/475> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 28

[fedora-badges] #298: Badges (graphics) have no license
by fedora-badges 01 Dec '16

01 Dec '16

#298: Badges (graphics) have no license -------------------------------------+------------------------------------- Reporter: | Owner: churchyard | 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 | -------------------------------------+------------------------------------- When I visit badges.fedoraproject.org, there is no clear information about the content license, such as, but not limited to, badge designs. From my POV that means badges are CC BY-SA 3.0 Unported, because of FPCA. If that being true, I would suggest adding this information to the footer of the page and also tracking the author of the graphics in YAML and displaying it on badge details page. -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/298> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 2

[fedora-badges] #389: Missing apostrophe in Sistine Badgers (Badge Artist IV) description
by fedora-badges 01 Dec '16

01 Dec '16

#389: Missing apostrophe in Sistine Badgers (Badge Artist IV) description -------------------------------------+------------------------------------- Reporter: | Owner: jwakely | Status: new Type: | Keywords: Bug report | Has a description: 0 Priority: | Artwork status: None trivial | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- "You have been putting in work, and Rafaels angels know it! You designed 25 badges." That should be ** Rafael's ** -- Ticket URL: <https://fedorahosted.org/fedora-badges/ticket/389> fedora-badges <https://badges.fedoraproject.org> A place to collect and debate badge ideas for the Fedora Badges app

1 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

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