Badge description (like "You added a co-maintainer to a package. BFF!"): "You helped to test Fedora 37 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 37 for i18n test day on 6th Sept 2022
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 37 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://pagure.io/fedora-badges/issue/860
Event is happening next week. Can someone help here?
Any update here? Can someone help?
Hi @pnemade created badges for F37 F38 & F39 so we can get ahead on these for next time. Thanks for your patience.
Badge admins, please push all three of these badges and give award rights to @pnemade and categorize them as event badges. Thanks!
<img alt="internationalization_testday_i18n_f39.png" src="/fedora-badges/issue/raw/files/262af1bcb7113f535c16182ab11eaaa34a46e3a3673a71e53f4e8667e8f9e0cb-internationalization_testday_i18n_f39.png" /><img alt="Internationalization_testday_i18n_f39.svg" src="/fedora-badges/issue/raw/files/30dfe3b6210cec2b8bfc8d57cae5aded4dc0673883f6deb5c68abdb0a4346f85-Internationalization_testday_i18n_f39.svg" /><img alt="internationalization_testday_i18n_f38.png" src="/fedora-badges/issue/raw/files/b818bfee41d6576426a99e4f85e14767cca1dddd05aa1408d391b2146216cac1-internationalization_testday_i18n_f38.png" /><img alt="Internationalization_testday_i18n_f38.svg" src="/fedora-badges/issue/raw/files/b9f26bd8a24b7d8c178ab27f39f10ae3c83910d348fcc7f67ef071998902f080-Internationalization_testday_i18n_f38.svg" /><img alt="internationalization_testday_i18n_f37.png" src="/fedora-badges/issue/raw/files/c9f96491704bf14b3808883739176705917816dda9a17c75fc9707b49b480565-internationalization_testday_i18n_f37.png" /><img alt="Internationalization_testday_i18n_f37.svg" src="/fedora-badges/issue/raw/files/22d7f0851d606f77ba3cce8726eff4918db21ed2f6cec80db7f178e1cea0bbb4-Internationalization_testday_i18n_f37.svg" />
Metadata Update from @riecatnor: - Custom field artwork adjusted to None - Custom field concept_review_passed adjusted to None
@riecatnor Is it possible to find some active Badges developer here who can push these badges and give me admin rights to award them? Thanks!
Hi @pnemade,
Sorry for the delay. I'm still in the process of catching up, devoting as much time as I can. I will push these badges today. Regarding admin access to award the badges, I still don't have administrative access to the web interface. I will chase some admin today to get this done.
But luckily that's something @riecatnor could help you with in the meantime.
Metadata Update from @gui1ty: - Issue assigned to gui1ty - Issue priority set to: critical (next week) - Issue set to the milestone: short term - Issue tagged with: AW: approved, C: community, C: event, S: ready to push, T: badge request
Badges are already on the servers: https://badges.fedoraproject.org/pngs/i18n-test-day-f37.png
All that's needed is handing out access, so they can be awarded.
Since this is a manually awarded badge, it still needs to be added manually in the web interface. I just tried granting authorization using a script, I found. Turns out the new badges are not yet known. Verified by looking at the list of i18n badges.
Badge for F37 i18n test day has been added and authorization granted to @pnemade.
I'll do F38 and F39 later today.
F38 and F39 have also been added and authorized.
Metadata Update from @gui1ty: - Issue close_status updated to: pushed - Issue status updated to: Closed (was: Open)
@gui1ty Thank you so much for your help here.
Issue status updated to: Open (was: Closed)
Issue status updated to: Closed (was: Open) Issue close_status updated to: pushed
Log in to comment on this ticket.