#464 CommOps Onboarding Series Badge

Created a year ago by skamath
Modified 14 days ago

Badge description (like "You added a co-maintainer to a package. BFF!"):

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?

This badge is to be awarded to those who completes / have completed the Onboarding Series of Commops.

2) Who is doing them (are they packagers? translators? newcomers? veterans? users? sponsors?)

This badge targets the new-comers

3) Why are they doing them (is this a means to a different end?)

This will help keep track of the Onboarding series and this badge, if implemented can be a nice reward for it.

4) When do they do them (every day? once a year?)

They do it once.

5) How do they do them (by talking in IRC? by running commands in the console? by using a web interface?)

This badge is dependent on other badges / activities like :

If the user completes the above-mentioned activities, this badge is to be rewarded.

6) Lastly, do you have any ideas for artwork concepts?

Not yet.

Attachments
commopsmailmodbadge.jpg - 2016-06-21 20:01:00 Comment Download
commopsmailmodbadge.jpg - 2016-06-21 20:01:00 Comment Download
1.png - 2016-09-04 05:17:47 Comment Download
1.png - 2016-09-04 05:17:47 Comment Download
464_2.png - 2017-01-12 16:05:14 Comment Download
464_2.png - 2017-01-12 16:05:14 Comment Download
464_2.2.png - 2017-01-12 16:05:15 Comment Download
464_2.2.png - 2017-01-12 16:05:15 Comment Download

Thanks for filing this ticket, skamath. :) I'm going to triage up this ticket. If anyone has different ideas for any of the info I add / suggest below, please add your thoughts.

= Badge metadata =
'''Name''':
* Tying the Knot, ''OR''
* Dialed In
'''Description''':
* "Congratulations, you are now a sponsored member of the Fedora Community Operations (CommOps) team, helping tie the project together.

= Badge automation ideas =
We've been trying to discuss how to best automate the awarding of a badge like this. Maybe it would be better to award it for sponsorship into the FAS group for CommOps (which is a manual process to begin with and would require someone to review the on-boarding steps we have above).

Alternatively, we could try to automate this badge being awarded based on meeting criteria by what badges someone already has. For the examples above, we could run a check for the following badges:
Speak Up! (attend IRC meting)
Let Me Introduce Myself (edit your user page on the wiki)
Junior Editor (edit 10 wiki pages)
White Rabbit (indicate time zone...?)

Some of the requirements above are not yet badges (but some are proposals, like the mailing list activity). This is something worth discussing, probably on a more technical side, and we will bring up this point in our meeting today.

= Badge art concept =
I had a few ideas for the badge depending on which name idea has the most flexibility for the Design Team… we are totally open to ideas and other suggestions too based on what you all think is best or most doable. :)

The following two ideas are just suggestions!

=== Tying the Knot ===
You could have a "superhero" panda or badger who has a coiled rope around his shoulder, a belt with a phone-like object on it (or maybe a radio on its back?), and a headset on their head to keep the panda "looped in" on all the different things happening in Fedora.

=== Dialed In ===
This one is more a hint towards communication and staying alert to things happening around the panda / badger. In this one, you could have the headset on their head / radio on their back again, but maybe one of the computer assets (or a couple of them) with the panda / badger checking back between the info scrolling by on both.

= Triaged! Bringing in Design Team members =
This should be all of the needed information on the ticket to start some discussion. I'm CC'ing some members of the Design Team to get their thoughts and opinions on the proposed concepts.

Thanks for filing this ticket, skamath. :) I'm going to triage up this ticket. If anyone has different ideas for any of the info I add / suggest below, please add your thoughts.

= Badge metadata =
'''Name''':
* Tying the Knot, ''OR''
* Dialed In
'''Description''':
* "Congratulations, you are now a sponsored member of the Fedora Community Operations (CommOps) team, helping tie the project together.

= Badge automation ideas =
We've been trying to discuss how to best automate the awarding of a badge like this. Maybe it would be better to award it for sponsorship into the FAS group for CommOps (which is a manual process to begin with and would require someone to review the on-boarding steps we have above).

Alternatively, we could try to automate this badge being awarded based on meeting criteria by what badges someone already has. For the examples above, we could run a check for the following badges:
Speak Up! (attend IRC meting)
Let Me Introduce Myself (edit your user page on the wiki)
Junior Editor (edit 10 wiki pages)
White Rabbit (indicate time zone...?)

Some of the requirements above are not yet badges (but some are proposals, like the mailing list activity). This is something worth discussing, probably on a more technical side, and we will bring up this point in our meeting today.

= Badge art concept =
I had a few ideas for the badge depending on which name idea has the most flexibility for the Design Team… we are totally open to ideas and other suggestions too based on what you all think is best or most doable. :)

The following two ideas are just suggestions!

=== Tying the Knot ===
You could have a "superhero" panda or badger who has a coiled rope around his shoulder, a belt with a phone-like object on it (or maybe a radio on its back?), and a headset on their head to keep the panda "looped in" on all the different things happening in Fedora.

=== Dialed In ===
This one is more a hint towards communication and staying alert to things happening around the panda / badger. In this one, you could have the headset on their head / radio on their back again, but maybe one of the computer assets (or a couple of them) with the panda / badger checking back between the info scrolling by on both.

= Triaged! Bringing in Design Team members =
This should be all of the needed information on the ticket to start some discussion. I'm CC'ing some members of the Design Team to get their thoughts and opinions on the proposed concepts.

'''Badge automation ideas discussed in CommOps [https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-06-14-15.58.html 2016-06-14 meeting].'''

In our meeting, we decided it would be best to have the approval be based off of the FAS group sponsorship, which is an easier one to write and we know it is a less expensive operation. It also makes it a little more human-verifiable as well.

I created the YAML file (and a patch for it) to add the badge rule to the official repository. Note, as of now, the YAML + patch assumes the badge name is "Dialed In". This obviously easy to change later if we decide to use the other suggestion.

'''Badge automation ideas discussed in CommOps [https://meetbot.fedoraproject.org/fedora-meeting/2016-06-14/commops.2016-06-14-15.58.html 2016-06-14 meeting].'''

In our meeting, we decided it would be best to have the approval be based off of the FAS group sponsorship, which is an easier one to write and we know it is a less expensive operation. It also makes it a little more human-verifiable as well.

I created the YAML file (and a patch for it) to add the badge rule to the official repository. Note, as of now, the YAML + patch assumes the badge name is "Dialed In". This obviously easy to change later if we decide to use the other suggestion.

YAML rule file for "Dialed In" badge
fas-commops.yml

YAML rule file for "Dialed In" badge
fas-commops.yml

Git patch for adding in the YAML rule file to the badges repository
0001-Added-Dialed-In-rule-for-CommOps-on-boarding-badge.patch

Git patch for adding in the YAML rule file to the badges repository
0001-Added-Dialed-In-rule-for-CommOps-on-boarding-badge.patch

Patch file for adding the commops=>dialed-in mapping to the cron script for awarding the badge to past members of the FAS group before the badge rule existed
0001-Add-commops-dialed-in-mapping-to-oldschool-cron-scri.patch

Patch file for adding the commops=>dialed-in mapping to the cron script for awarding the badge to past members of the FAS group before the badge rule existed
0001-Add-commops-dialed-in-mapping-to-oldschool-cron-scri.patch

@decause, thanks for your experiment. I am wondering how this artwork is related to the CommOps Onboarding. Please explain further :)

Possible Concepts:
Use the CommOpps logo with a badger holding a clipboard and other badger and pandas hanging out in the bubbles

A badger or panda hanging out inside one of these: https://www.zanebenefits.com/hs-fs/hub/149308/file-334986197-jpg/images/Onboarding_and_Education.jpg

@decause, thanks for your experiment. I am wondering how this artwork is related to the CommOps Onboarding. Please explain further :)

Possible Concepts:
Use the CommOpps logo with a badger holding a clipboard and other badger and pandas hanging out in the bubbles

A badger or panda hanging out inside one of these: https://www.zanebenefits.com/hs-fs/hub/149308/file-334986197-jpg/images/Onboarding_and_Education.jpg

I experimented for this ticket.
1.png

I experimented for this ticket.
1.png

I missed the previous comment here! Seems like a start in the right direction to me – maybe some of the other Badges team can leave some comments and feedback here? :)

I missed the previous comment here! Seems like a start in the right direction to me – maybe some of the other Badges team can leave some comments and feedback here? :)

Hi there! The experiment you made is cute! I am not sure it's working well for this badge idea though. The panda looks kind of infantile, and I don't think that is what we are trying to get across.

Let's try something like this badge: https://badges.fedoraproject.org/badge/trust-me%2C-i-know-what-i-am-doing but instead of a keyboard the panda is holding a clipboard and on the back is the CommOps logo (https://fedorahosted.org/design-team/ticket/415)

Or we could attempt to use a panda with his head through one of these -> https://www.zanebenefits.com/hs-fs/hub/149308/file-334986197-jpg/images/Onboarding_and_Education.jpg

Hi there! The experiment you made is cute! I am not sure it's working well for this badge idea though. The panda looks kind of infantile, and I don't think that is what we are trying to get across.

Let's try something like this badge: https://badges.fedoraproject.org/badge/trust-me%2C-i-know-what-i-am-doing but instead of a keyboard the panda is holding a clipboard and on the back is the CommOps logo (https://fedorahosted.org/design-team/ticket/415)

Or we could attempt to use a panda with his head through one of these -> https://www.zanebenefits.com/hs-fs/hub/149308/file-334986197-jpg/images/Onboarding_and_Education.jpg

For some reason png got attached twice. But here's my suggestion:
[[Image(https://fedorahosted.org/fedora-badges/raw-attachment/ticket/464/464_2.2.png)]]
Does this look like the discussed concept?

For some reason png got attached twice. But here's my suggestion:
[[Image(https://fedorahosted.org/fedora-badges/raw-attachment/ticket/464/464_2.2.png)]]
Does this look like the discussed concept?

6 months ago

Metadata Update from @skamath:
- Issue assigned to a2batic
- Issue tagged with: commops

Hi @riecatnor @mleonova – following up on this one, is the artwork ready to be approved?

5 months ago

Metadata Update from @jflory7:
- Custom field concept_review_passed adjusted to on (was: 1)
- Custom field has_description adjusted to on (was: 1)
- Custom field has_name adjusted to on (was: 1)
- Custom field needs_manual_award reset (from 0)
- Custom field triaged adjusted to on (was: 1)
- Issue close_status updated to: None

@mleonova @jflory7 looks good to me! setting to approved

a month ago

Metadata Update from @riecatnor:
- Custom field artwork adjusted to None
- Custom field concept_review_passed adjusted to None (was: on)
- Custom field has_complete_yaml reset (from Full, needs review)
- Custom field needs_manual_award reset (from false)

a month ago

Metadata Update from @riecatnor:
- Custom field artwork adjusted to approved (was: None)
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)

a month ago

Metadata Update from @riecatnor:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)
- Issue tagged with: artwork-approved, community

@jflory7 since you have more insight on this one. can you push these badges?

14 days ago

Metadata Update from @sayanchowdhury:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)

14 days ago

Metadata Update from @sayanchowdhury:
- Custom field has_complete_yaml reset (from false)
- Custom field needs_manual_award reset (from false)
- Issue assigned to jflory7 (was: a2batic)

Login to comment on this ticket.

approved

on

on

None

false

false

on

cancel