#303 Speak up series continued
Opened 5 years ago by gnokii. Modified 2 years ago

continue the Speak Up! IRC meeting series

25 participations
50 participations


[[Image(speak-up-ii.png)]]
[[Image(speak-up-ii_v2.png)]]
[[Image(speak-up-ii_v3.png)]]
I am leaning towards version 3.. thoughts?

[[Image(speak-up-ii.png)]]
[[Image(speak-up-ii_v2.png)]]
[[Image(speak-up-ii_v3.png)]]
I am leaning towards version 3.. thoughts?

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?

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?

sure, v3 works! setting to approved

sure, v3 works! setting to approved

I'm really sorry, but I don't know how to implement this one without some hacking on the fedbadges backend.

I'm really sorry, but I don't know how to implement this one without some hacking on the fedbadges backend.

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...)

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...)

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 =

= 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 =

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 =

= 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 =

Metadata Update from @riecatnor:
- Custom field artwork adjusted to approved
- Custom field concept_review_passed adjusted to None (was: 0)
- Custom field has_complete_yaml reset (from Not yet possible)
- Custom field has_description reset (from 0)
- Custom field has_name reset (from 0)
- Custom field needs_manual_award reset (from 0)
- Custom field triaged reset (from 0)
- Issue close_status updated to: None

2 years ago

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)
- Issue tagged with: artwork-approved, community

2 years ago

Metadata Update from @sayanchowdhury:
- Custom field has_complete_yaml reset (from false)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)
- Issue tagged with: not-yet-possible

2 years ago

@jflory7 do you know if this badge is possible yet? thanks!

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)

2 years ago

Login to comment on this ticket.

Metadata
Attachments 10
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment
Attached 5 years ago View Comment