#446 Badge for Fedora 25 internationalization test day participants
Closed: Pushed None Opened 4 years ago by pravins.

Badge description (like "You added a co-maintainer to a package. BFF!"):
"You helped to test Fedora 24 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 24 before Beta.

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

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

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

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


Gentle ping :)
We can use design from last year testing event.

Gentle ping :)
We can use design from last year testing event.

= Badge Metadata =

  • '''Name''': F24 i18n Test Day Participant
  • '''Description''': You helped test i18n features in Fedora 24! Thanks!

Okay, triaging ticket! Everything should be ready for this badge to be designed and then ready to push as soon as possible. Also upgrading the priority here since the event is today. The badge will need to be manually awarded and privileges should be granted to pravins.

= Badge Metadata =

  • '''Name''': F24 i18n Test Day Participant
  • '''Description''': You helped test i18n features in Fedora 24! Thanks!

Okay, triaging ticket! Everything should be ready for this badge to be designed and then ready to push as soon as possible. Also upgrading the priority here since the event is today. The badge will need to be manually awarded and privileges should be granted to pravins.

Thanks Justin for triaging.
We already have around 10 participants for sprint. I think it will increase in coming 2 days.

Thanks Justin for triaging.
We already have around 10 participants for sprint. I think it will increase in coming 2 days.

we are in stage of creating report of test day. :)
Still any chance here or simply close this ticket?

we are in stage of creating report of test day. :)
Still any chance here or simply close this ticket?

What is the difference between this badge request and 360? That badge artwork has no release number or date on it, so if possible can we use that badge for the people who participated in this event?

What is the difference between this badge request and 360? That badge artwork has no release number or date on it, so if possible can we use that badge for the people who participated in this event?

Right, i think last time we did not thought regarding its usability in next release. Therefore there is no release number in earlier badge.

But since now there is good chance to have i18n testing day on Fedora 25 onwards as well. Good to have this badge with release number as well.

Right, i think last time we did not thought regarding its usability in next release. Therefore there is no release number in earlier badge.

But since now there is good chance to have i18n testing day on Fedora 25 onwards as well. Good to have this badge with release number as well.

gave this one a try; here's what I have right now
[[Image(badge ticket #446_attempt 1.png)]]

gave this one a try; here's what I have right now
[[Image(badge ticket #446_attempt 1.png)]]

Only issue, how can we identified this is for i18n testing activity?

Only issue, how can we identified this is for i18n testing activity?

I can play around and find a way to incorporate i18n into the design and repost

I can play around and find a way to incorporate i18n into the design and repost

this might be a little too squished, but here's some food for thought
[[Image(badge ticket #446_attmept 1.1.png)]]

this might be a little too squished, but here's some food for thought
[[Image(badge ticket #446_attmept 1.1.png)]]

Looks good to me. Rather than adding complicated graphics, words make it simple.

Looks good to me. Rather than adding complicated graphics, words make it simple.

Hi maryshak1996,

Thank you very much for your efforts on working this ticket. Sorry to reply late here but I have 2 suggestions

1) Can it be possible to keep 'f' and '24' on same line, maybe minimize 'f' height.

2) the another panda showing hairs is somewhat distracting eyes first, so IMHO it looks not good, can it be replaced by some other panda image?

Hi maryshak1996,

Thank you very much for your efforts on working this ticket. Sorry to reply late here but I have 2 suggestions

1) Can it be possible to keep 'f' and '24' on same line, maybe minimize 'f' height.

2) the another panda showing hairs is somewhat distracting eyes first, so IMHO it looks not good, can it be replaced by some other panda image?

ya I wasn't sure how I felt about that one panda either. just to see how it looks, I did an iteration with just the one panda so that there's not so much going on in such a small space.
[[Image(badge ticket #446_attmept 1.2.png)]]

ya I wasn't sure how I felt about that one panda either. just to see how it looks, I did an iteration with just the one panda so that there's not so much going on in such a small space.
[[Image(badge ticket #446_attmept 1.2.png)]]

The above updated badge image looks good to me. Pravin, what do you say?

The above updated badge image looks good to me. Pravin, what do you say?

Agree, feels more organized now. +1 from me as well.

Agree, feels more organized now. +1 from me as well.

I am still not sure how this badge is different from 360, although it is a new year, why not just add the year onto that badge and use that for later use?

I am still not sure how this badge is different from 360, although it is a new year, why not just add the year onto that badge and use that for later use?

I am fine with both. Lets get approval for design for now and apply it for next test day. Its not far though just couple of months away :)

Let me change ticket name.

I am fine with both. Lets get approval for design for now and apply it for next test day. Its not far though just couple of months away :)

Let me change ticket name.

So early we are actually able to test reusability of design. maryshak1996 can you create it for F25? :)

So early we are actually able to test reusability of design. maryshak1996 can you create it for F25? :)

riecatnor,
looks like there is sudden big activity happening for badges now and when tickets got filed no one replied. If possible good to triage tickets regularly so that there will be no delay in future.

riecatnor,
looks like there is sudden big activity happening for badges now and when tickets got filed no one replied. If possible good to triage tickets regularly so that there will be no delay in future.

pravins, here's the design with the "24" changed to "25"
[[Image(badge ticket #446_attmept 1.3.png)]]

pravins, here's the design with the "24" changed to "25"
[[Image(badge ticket #446_attmept 1.3.png)]]

@maryshak1996, thanks for your work :)

Because this a yearly event, and we already have a badge, the best course of action is to stick with the previous approved badge artwork and update it once a year, instead of making a unique badge for each event. I have updated the existing artwork, for f24 and f25. The first badge will be different for now, but we can change it to say f23 if @pravins you think that would be good. Because you did request the badge with in the correct time frame, I think allowing the badge for the event that already occurred is fine.

Here is what I have come up with:

[[Image(internationalization_testday_i18n_f24.png)]]
[[Image(internationalization_testday_i18n_f25.png)]]

@maryshak1996, thanks for your work :)

Because this a yearly event, and we already have a badge, the best course of action is to stick with the previous approved badge artwork and update it once a year, instead of making a unique badge for each event. I have updated the existing artwork, for f24 and f25. The first badge will be different for now, but we can change it to say f23 if @pravins you think that would be good. Because you did request the badge with in the correct time frame, I think allowing the badge for the event that already occurred is fine.

Here is what I have come up with:

[[Image(internationalization_testday_i18n_f24.png)]]
[[Image(internationalization_testday_i18n_f25.png)]]

Thanks riecatnor. These badges looks awesome. Lets proceed ahead.
I already have list of people participated in F24 test day, so one done i will award it to them.

I am sure, this will also motivate more participants in f25 test day :)

Thanks riecatnor. These badges looks awesome. Lets proceed ahead.
I already have list of people participated in F24 test day, so one done i will award it to them.

I am sure, this will also motivate more participants in f25 test day :)

Thanks Sayan for changing tp approved. Let me know if anything further remaining from my side here.

Thanks Sayan for changing tp approved. Let me know if anything further remaining from my side here.

We are planning for Fedora 25 i18n test day next week. It will be great if we can have both (F24, f25) badge ready before it.
* https://fedoraproject.org/wiki/Test_Day:2016-09-28_I18N_Test_Day
Design is ready, badge is also approved.

We are planning for Fedora 25 i18n test day next week. It will be great if we can have both (F24, f25) badge ready before it.
* https://fedoraproject.org/wiki/Test_Day:2016-09-28_I18N_Test_Day
Design is ready, badge is also approved.

I'm going to make the assumption that the artwork for this badge is definitely approved. Working on pushing it now.

I'm going to make the assumption that the artwork for this badge is definitely approved. Working on pushing it now.

= Badges pushed, need fixing =

I pushed the badges, but it seems like I had whitespace in the name field, and the naming schemes for the badge IDs were incorrect. Currently the badges are living here:

I filed tickets in the Infra Trac to help correct that. Once it is corrected, I will grant authorization rights to pravins and noriko (or anyone else who might need privileges).

= Badges pushed, need fixing =

I pushed the badges, but it seems like I had whitespace in the name field, and the naming schemes for the badge IDs were incorrect. Currently the badges are living here:

I filed tickets in the Infra Trac to help correct that. Once it is corrected, I will grant authorization rights to pravins and noriko (or anyone else who might need privileges).

Replying to [comment:29 jflory7]:

= Badges pushed, need fixing =

I filed tickets in the Infra Trac to help correct that. Once it is corrected, I will grant authorization rights to pravins and noriko (or anyone else who might need privileges).

For i18n only grant it to me. If requires to Parag and Tagoh. Thanks :)
Volume is not that big, so i think its fine.

I will start working on post to community blog now.

Replying to [comment:29 jflory7]:

= Badges pushed, need fixing =

I filed tickets in the Infra Trac to help correct that. Once it is corrected, I will grant authorization rights to pravins and noriko (or anyone else who might need privileges).

For i18n only grant it to me. If requires to Parag and Tagoh. Thanks :)
Volume is not that big, so i think its fine.

I will start working on post to community blog now.

Any progress here? i18n test day starting from tomorrow..

Any progress here? i18n test day starting from tomorrow..

= Badges pushed =

Sorry for the delay here. Ralph created a script for deleting badges yesterday, so I was able to use that to fix the issue.

= Badges pushed =

Sorry for the delay here. Ralph created a script for deleting badges yesterday, so I was able to use that to fix the issue.

That's great. Thanks @jflory :)

That's great. Thanks @jflory :)

Metadata Update from @pravins:
- Issue assigned to maryshak1996

3 years ago

Login to comment on this ticket.

Metadata