#662 Badge for Fedora 30 Internationalization test day participants
Closed: fixed 2 years ago by sayanchowdhury. Opened 2 years ago by pnemade.

Badge description (like "You added a co-maintainer to a package. BFF!"):
"You helped to test Fedora 30 i18n features"

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?
Testing Fedora 30 for i18n test day.

2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)
It can be anyone but mostly i18n contributors like developers + translators + Fedora QA people

3) Why are they doing them (is this a means to a different end?)
Making Fedora 30 stable release for i18n support.

4) When do they do them (every day? once a year?)
Once each Fedora release. This activity mostly happen whole week.

5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)
We communicated on #fedora-test-day and #fedora-i18n

Lastly, do you have any ideas for artwork concepts?
Earlier badge for similar activity for other Fedora release. https://fedorahosted.org/fedora-badges/ticket/640


Metadata Update from @riecatnor:
- Issue assigned to riecatnor

2 years ago

Metadata Update from @riecatnor:
- Custom field artwork adjusted to None
- Custom field concept_review_passed adjusted to None

2 years ago

Metadata Update from @riecatnor:
- Custom field artwork adjusted to approved (was: None)
- Custom field concept_review_passed adjusted to passed (was: None)
- Issue tagged with: artwork - approved, category - event

2 years ago

Thank you @riecatnor for your quick work response.

@sayanchowdhury Can you please push this badge?

Any one available to push this badge?

Oh! I thought I already pushed this badge. The assets were pushed but forgot to create the badge. will do it in a while.

Metadata Update from @sayanchowdhury:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Attachments 1