#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
#303: Speak up series continued -------------------------------------+------------------------------------- Reporter: gnokii | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: Proposed | Concept approved (reviewers only): External requirements: | 0 Triaged (triagers only): 0 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by riecatnor):
[[Image(speak-up-ii.png)]] [[Image(speak-up-ii_v2.png)]] [[Image(speak-up-ii_v3.png)]] I am leaning towards version 3.. thoughts?
#303: Speak up series continued -------------------------------------+------------------------------------- Reporter: gnokii | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: Proposed | Concept approved (reviewers only): External requirements: | 0 Triaged (triagers only): 0 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by churchyard):
Version 3, +1.
#303: Speak up series continued -------------------------------------+------------------------------------- Reporter: gnokii | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: Proposed | Concept approved (reviewers only): External requirements: | 0 Triaged (triagers only): 0 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by duffy):
Hey, I actually think 1 maybe fits the style the best (specifically because the numbers are bold / large and have the outline. My suggestion would be to either modify 1 so the panda is smaller and pushed down to make room for the numbers to not go up ontop of the colored border (we don't normally do that, we usually only bleed out to the inner white border right?) Or, alternatively, modify 3 so that the '25' in the bubble is stylized the way it is in 1. What do you think?
#303: Speak up series continued -------------------------------------+------------------------------------- Reporter: gnokii | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: Proposed | Concept approved (reviewers only): External requirements: | 0 Triaged (triagers only): 0 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by gnokii):
like this above?
#303: Speak up series continued -------------------------------------+------------------------------------- Reporter: gnokii | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: Approved | Concept approved (reviewers only): (design team members only) | 0 External requirements: | Badge definition status: Triaged (triagers only): 0 | None | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by duffy):
* has_artwork: Proposed => Approved (design team members only)
Comment:
sure, v3 works! setting to approved
#303: Speak up series continued -------------------------------------+------------------------------------- Reporter: gnokii | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: Approved | Concept approved (reviewers only): (design team members only) | 0 External requirements: | Badge definition status: Triaged (triagers only): 0 | None | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by ralph):
I'm really sorry, but I don't know how to implement this one without some hacking on the fedbadges backend.
#303: Speak up series continued -------------------------------------+------------------------------------- Reporter: gnokii | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: Approved | Concept approved (reviewers only): (design team members only) | 0 External requirements: | Badge definition status: Triaged (triagers only): 0 | Not yet possible | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by gnokii):
* has_complete_yaml: None => Not yet possible
#303: Speak up series continued -------------------------------------+------------------------------------- Reporter: gnokii | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: Approved | Concept approved (reviewers only): (design team members only) | 0 External requirements: | Badge definition status: Triaged (triagers only): 0 | Not yet possible | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by ralph):
I want to elaborate on what the problem is (the limitation to the way the fedbadges backend is coded).
Here's the current IRC badge: https://git.fedorahosted.org/cgit/badges.git/tree/rules/irc-speak-up.yml
The 'recipient' at the bottom is the list of people in ``msg.attendees`` -- that's a list of people.
For an example of a badge that counts some number of events in history, see this badge: https://git.fedorahosted.org/cgit/badges.git/tree/rules/badger-03.yml
See the 'criteria->datanommer->filter->users' entry? That only works because the incoming message is only associated with *one* user: ``msg.user.username``. The IRC messages, on the other hand, are associated with multiple user names: ``msg.attendees``. That datanommer interface would need to be expanded to somehow handle a list of people intelligently.
We would probably need some kind of loop, so that you can check if each of the people in the meeting should be given the badge.. not just the whole set as a group. (one person might have attended 10000 meetings, while another in the same meeting might only have ever attended 3...)
#303: Speak up series continued -------------------------------------+------------------------------------- Reporter: gnokii | Owner: Type: New badge | Status: idea | new Priority: minor | Resolution: Keywords: | Has a name: Has a description: 0 | 0 Artwork status: Approved | Concept approved (reviewers only): (design team members only) | 0 External requirements: | Badge definition status: Triaged (triagers only): 0 | Not yet possible | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by jflory7):
Thanks for adding this info in, Ralph. So it wouldn't be a straightforward way to implement this badge.
I'm going to "import" Ticket #443 and subsequently close it as a duplicate.
= Badge Description =
* '''Name''': Speak Up! {II,III,IV} * ''NOTE'': Speak Up! exists, as defined [https://infrastructure.fedoraproject.org/infra/badges/rules/irc-speak- up.yml here] * '''Description''': * II: Participated in 10 IRC meetings. * III: Participated in 100 IRC meetings. * IV: Participated in 1000 IRC meetings. A true Fedora veteran!
= Understanding badge =
1) What are those activities?
* '''Users are granted badge for participating in meetings consecutively (thereby building habits and encouraging positive contributions to sub- projects)'''
2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
* '''Just about any active contributor!
3) Why are they doing them (is this a means to a different end?)
* '''To work through issues, tasks, and reach goals as a team in meeting slots'''
4) When do they do them (every day? once a year?)
* '''Weekly or fortnightly (usually)'''
5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
* '''Talking in IRC during a Meetbot meeting'''
= Artwork concepts =
* Slight redesign of the [https://badges.fedoraproject.org/badge/speak-up! existing badge] with room to place a number for the number of meetings you've attended (would require changing artwork of original badge too)
badges@lists.stg.fedoraproject.org