#464: CommOps Onboarding Series Badge -------------------------------------+------------------------------------- Reporter: | Owner: skamath skamath | Status: new Type: | Keywords: New badge idea | Has a description: 0 Priority: | Artwork status: None minor | External requirements: Has a name: | Triaged (triagers only): 0 0 | Concept approved (reviewers only): | 0 | Badge definition status: | None | Manually awarded: | 0 | -------------------------------------+------------------------------------- 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 :
* Creating a FAS Account and signing the FPCA ( [https://badges.fedoraproject.org/badge/involvement Involvement badge] )
* Sending an introductory email to the [https://admin.fedoraproject.org/mailman/listinfo/CommOps CommOps Mailing Lists]
* Attending a commops meeting
* Getting sponsored to the [https://admin.fedoraproject.org/accounts/group/view/commops CommOps group]
* Editing wiki-pages ( [https://badges.fedoraproject.org/badge/junior- editor Junior Editor] ) / blogs / fed-mag articles
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.
#464: CommOps Onboarding Series Badge -------------------------------------+------------------------------------- Reporter: skamath | Owner: Type: New badge | skamath idea | Status: Priority: minor | new Keywords: commops | Resolution: Has a description: 1 | Has a name: Artwork status: Concept | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 0 | Badge definition status: | None | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by jflory7):
* cc: decause, commops@…, riecatnor, mleonova, duffy (added) * has_name: 0 => 1 * triaged: 0 => 1 * has_artwork: None => Concept * keywords: => commops * has_description: 0 => 1
Comment:
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.
#464: CommOps Onboarding Series Badge -------------------------------------+------------------------------------- Reporter: skamath | Owner: Type: New badge | skamath idea | Status: Priority: minor | new Keywords: commops | Resolution: Has a description: 1 | Has a name: Artwork status: Concept | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 0 | Badge definition status: | Full, needs review | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by jflory7):
* has_complete_yaml: None => Full, needs review
Comment:
'''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.
#464: CommOps Onboarding Series Badge -------------------------------------+------------------------------------- Reporter: skamath | Owner: Type: New badge | skamath idea | Status: Priority: minor | new Keywords: commops | Resolution: Has a description: 1 | Has a name: Artwork status: Concept | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 0 | Badge definition status: | Full, needs review | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by riecatnor):
@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
#464: CommOps Onboarding Series Badge -------------------------------------+------------------------------------- Reporter: skamath | Owner: Type: New badge | skamath idea | Status: Priority: minor | new Keywords: commops | Resolution: Has a description: 1 | Has a name: Artwork status: Concept | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Full, needs review | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by riecatnor):
* concept_review_passed: 0 => 1
#464: CommOps Onboarding Series Badge -------------------------------------+------------------------------------- Reporter: skamath | Owner: Type: New badge | a2batic idea | Status: Priority: minor | assigned Keywords: commops | Resolution: Has a description: 1 | Has a name: Artwork status: Proposed | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Full, needs review | Manually awarded: | 0 -------------------------------------+------------------------------------- Changes (by jflory7):
* owner: skamath => a2batic * status: new => assigned * has_artwork: Concept => Proposed
Comment:
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? :)
#464: CommOps Onboarding Series Badge -------------------------------------+------------------------------------- Reporter: skamath | Owner: Type: New badge | a2batic idea | Status: Priority: minor | assigned Keywords: commops | Resolution: Has a description: 1 | Has a name: Artwork status: Proposed | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Full, needs review | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by riecatnor):
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
#464: CommOps Onboarding Series Badge -------------------------------------+------------------------------------- Reporter: skamath | Owner: Type: New badge | a2batic idea | Status: Priority: minor | assigned Keywords: commops | Resolution: Has a description: 1 | Has a name: Artwork status: Proposed | 1 External requirements: | Concept approved (reviewers only): Triaged (triagers only): 1 | 1 | Badge definition status: | Full, needs review | Manually awarded: | 0 -------------------------------------+-------------------------------------
Comment (by mleonova):
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?
badges@lists.fedoraproject.org
-
fedora-badges