We'd like a Fedora 37 test day badge.
Example of a previous test day badge:
https://badges.fedoraproject.org/badge/fedora-34-coreos-test-day
Metadata Update from @gui1ty: - Custom field artwork adjusted to needed - Custom field concept_review_passed adjusted to None - Issue priority set to: normal (1-2 weeks) - Issue tagged with: artwork - needed, category - community, category - event, difficulty - easy, good first issue
What's the desired deadline for this?
Since the badge art contains the release, we need a new/modified artwork. Who is taking care of that?
<img alt="Core_OS_test_day_F37_participation_badge.png" src="/fedora-badges/issue/raw/files/b0ab6b830d2ece936614cd09925d437d55512f161ebe156df1fa00b7fa30207d-Core_OS_test_day_F37_participation_badge.png" /><img alt="Core_OS_test_day_F37_participation_badge.svg" src="/fedora-badges/issue/raw/files/0f5c3d491e93013c7bd091c64abc283df422333e634eb1d8ecc90a1726d8c3e4-Core_OS_test_day_F37_participation_badge.svg" />
Here's the updated art for F37. @jasonbrooks who should the award rights be given to?
Metadata Update from @smeragoel: - Issue untagged with: AW: needed, good first issue - Issue tagged with: AW: approved, S: needs rules, S: ready to push
I'll push this with the next run and assign rights to @dustymabe as I have done for the CoreOS 36 badge.
Metadata Update from @gui1ty: - Issue assigned to gui1ty
Badge has been pushed and @dustymabe has been authorized for awarding it. Let me know if there's a list of people who should be awarded, then I can use a script on badges-backend01 for awarding it to a batch of users.
https://badges.fedoraproject.org/badge/fedora-37-coreos-test-day
Metadata Update from @gui1ty: - Issue close_status updated to: pushed - Issue status updated to: Closed (was: Open)
Thank you so much @gui1ty - can you use the list of names from https://testdays.fedoraproject.org/events/143 ?
If it would be better I can pull those names into a text file/list for processing.
@dustymabe I awarded the badge to all users mentioned on the wiki page.
Thank you so much!
Log in to comment on this ticket.