#669 Request for a new badge to contributors, to be awarded for participating in Fedora I18N bug triage activity.
Opened 2 years ago by bbarve. Modified a year ago

Badge description (like "You added a co-maintainer to a package. BFF!"):
- Thank you for your contribution to the Fedora I18N bug triage activity.

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?
- I18N bug triage activity for Fedora is carried out by contributors to check the bug list for I18N bugs and close/carry forward them as applicable for every Fedora release.. A wiki page (example - https://fedoraproject.org/wiki/QA/F28_I18N_Bug_Triage )is created for this bug triage activity where bugs are divided into slots of 5 or 6 depending on the total number. Then contributors triage slots/individual bugs on the applicable fedora release. We want to present a badge each for the top 3 contributors.

2) Who is doing them (are they packagers? translators? newcomers? veterans?
users? sponsors?)
- This event is open for all community members including developers, QA, L10N folks and other users of Fedora.

3) Why are they doing them (is this a means to a different end?)
- The bug triage activity is a part of Fedora I18N QA activities for better defect management.

4) When do they do them (every day? once a year?)
- For each Fedora release. Twice a year.

5) How do they do them (by talking in IRC? by running commands in the console?
by using a web interface?)
- Triaging by checking bugs on the applicable Fedora version and updating the BZ accordingly. Communication happens over bugzilla, IRC channels, emails etc.

Lastly, do you have any ideas for artwork concepts?
- None from my side at the moment. This is first time I'm proposing such thing.

Metadata Update from @bbarve:
- Issue private status set to: False (was: True)

2 years ago

Metadata Update from @jflory7:
- Custom field artwork adjusted to needed
- Custom field concept_review_passed adjusted to passed
- Custom field needs_manual_award adjusted to on
- Custom field triaged adjusted to on
- Issue priority set to: minor (3-4 weeks)
- Issue tagged with: artwork - needed, category - event, difficulty - intermediate

2 years ago

@jflory7 any chance to get this moving?

@gnokii @duffy can you all assist here?

sorry I just came back after 6hrs without electricity but I wondering what this is:


@gnokii This badge is for i18n but its for bug triaging activity. Each release we close number of bug as End of Life cycle.

To make sure, we are not loosing important bugs, we do bug triage activity. https://fedoraproject.org/wiki/QA/F28_I18N_Bug_Triage

maybe debug the translation team first, just a few things

*after 4 years coordinating the khmer team I am still not sponsor for the cvsl10n group, each time I have somebody I have to convince this person to write to the maling list and then its a lucky game somebody feels responsible to add then this person. You might ask @mattdm but it is this way, then people who already do translation being asked to add themself to zanata and such nonsense. And this is not an exception my own request for german took more then a year and did happen only after the change to fab and I told him directly

*looking back how much fight it was to found the khmer group and adding it to zanata and so on, there should be an easier way to do this and this must be organized. So far I really hesitating to add kuy even there are requests here for starting it.

*I find it strange that the belorussian translation of Fedora is discussed on a mailing list of debian

  • more as strange I find that the only existing structure is flsc and this page was changed last time 2012

and there are more such things.

@gnokii replied on trans list for this issue, lets follow up on list.

@mleonova @riecatnor @nb @jflory7 @churchyard what do you all think about this as a separate badge? Personally I am mixed. I see a clean difference between this activity and testing. It isn't clear to me how this will be awarded - what are the criteria. @pravins can you expand on that?

I also wonder if we need a general bug triage badge instead.

depends on the criteria (I don't get them either)

Criteria for this issue:
1. In I18n bug triage, we divides bug list into slots i.e. 5 bugs in 1 slot. The person who complete one slot get the badge.
Fedora 24: https://fedoraproject.org/wiki/QA/F24_I18N_Bug_Triage
Fedora 26 : https://fedoraproject.org/wiki/QA/F26_I18N_Bug_Triage

For this case, we can award badge manually by checking. Bit easy.

Thinking on broader audience and all Fedora team.
Can we make some automated way, Rule can be:
1. Any Fedora contributor who moves EOL cycle bugs by testing to current release version will get the badge. (It might be already there) - I dont think this is blocker for this ticket.

The original comment said "We want to present a badge each for the top 3 contributors." - how do I understand this part?

The original comment said "We want to present a badge each for the top 3 contributors." - how do I understand this part?

May be we can change that. Would be good to present badge for all those who contribute for this activity.

Hi, so any updates further on this? Anything else required from my side?

@churchyard This statement should be
"You have triaged 5 or more bugs of Fedora 29 release".

Originally we created this ticket for Fedora 28 bug triaging activity but nothing happened. We are on the way for Fedora 29 bug triaging activity now. Any chance to make this badge reality? :)

I won't be able to dedicate my time to this badge, sorry.

Hi all! Reviewing this issue. I think a badge for bug triage events found be a cool idea! Instead of making it a yearly/release based badge, I propose we create a series with the count. Thoughts on that?

Artwork concept for badge: panda with a bug catching net and bugs around

Metadata Update from @riecatnor:
- Issue tagged with: outreachy-2020

a year ago

Hi @riecatnor I would like to take this up!

Metadata Update from @riecatnor:
- Issue assigned to grlwholifts

a year ago

Hi @grlwholifts works for me, I assigned you to the issue :) let me know if you have questions.

Hi @riecatnor how does this look? also, could you specify the content to be written on this badge? Is this going to be issued per release or for the number of bugs triaged or both?


Hi @grlwholifts, this is a great start :) a couple things that need to be accounted for to fit the guidelines.

  • Keep it simple, there are too many elements going on.
  • Make sure any text or any other artwork is legible at a small size. (your bugs are illegible, as well as text i18n, bug triage)
  • Text should mainly be used for numbering, or releases. I think for this because it will be used for multiple releases, it should be 1, 5, 10, 25, 50, 100, 150, 200, 250. This is most likely the only text you will need, as their is text accompanying the artwork on the website.
  • I would suggest bringing the panda to the foreground and cropping it's lower body out. Make one or two bugs bigger, and put a couple in the background smaller.

Looking forward to the next draft :) thank you!

Hi @riecatnor, i took care of the points you mentioned. I have some questions:
- the color of 1 as purple or any other color you would like to mention? I tried the red from the bug, but it didn't quite match and was popping out a lot. IMO, purple looks decent, however, we can try orange. also, will we require an outline of darker color around it?
- size of 1 as small or big?
- the gradient for net as light grey or dark grey?
- the background as pink or beige?
- color of bug as red or light pink?

Let me know if they work!



Hi @grlwholifts this is an improvement :D

A couple thoughts:

  • right now the "1" is taking over the design, I think it is more secondary to the content of the design
  • the light pink bugs are hard to see
  • the red are ok. we do have a red in the extended palette, but its not something we use a lot. Maybe try green for the bugs?
  • what about a green panda too??
  • for the net, take a look here: https://badges.fedoraproject.org/badge/commis-cookbook-i


Login to comment on this ticket.