#34 [Onboarding Series] [MASTER TICKET] Creating sub-project on-boarding badge series
Closed: Complete a year ago Opened 3 years ago by jflory7.

Originally determined as a goal with the founding of CommOps, officially discussed in the 2016-01-26 meeting.

Quick reference

Need to cut the chase and find all the links? Here you go:

What is it

This ticket is to help us track progress on helping the different sub-projects of Fedora identify key steps in their on-boarding process and find ways to convert these preliminary steps (of becoming a "full" contributor) into a series of badges that a newcomer can pick up.

A hypothetical example for joining CommOps:

  1. Contributor edits the CommOps wiki page (presumably to add his information to our info box).
  2. Contributor gets badge. Jack participates specifically in a meeting with the name "commops".
  3. Contributor gets badge. Jack posts five times in the CommOps mailing list.
  4. Contributor gets badge.
  5. Contributor writes article for Community Blog.
  6. Contributor gets badge.

Why do it

On-boarding is one of the most important processes for gaining new contributors in any given sub-project. Every sub-project does it a little bit differently: becoming a member of the Docs Team is not the same as becoming a Package Maintainer.

Having badges to help identify the steps, help streamline those steps, and ultimately bring the newcomers into the sub-project on the right foot will make it easier for sub-projects to gain new contributors. Badges have proven to be a very effective tool for engaging both past and new contributors into the project, and adding an easy "track" of badges to joining a sub-project shows promising benefits to the entire Fedora Project community.

How do we do it

This is going to be a very hands-on process with each individual sub-project that we work with. We are going to want to talk to contributors in that sub-project to find the "things" or tasks that help someone become a member of their sub-project. A basic walkthrough of this process is given as an example below.

  1. Send mail to the sub-project mailing list explaining this idea, why it's important, how to do it, and then how CommOps can help.
  2. Begin discussions with sub-projects to identify key "steps" or tasks that new contributors often take to join the sub-project. Some groups have this better mapped than others – no two sub-projects will be the same.
  3. Once the steps are identified, begin the brainstorming for coming up with badge names, badge subtitles, and maybe an image idea. All of the badges must have a consistent theme for a sub-project for image unity / branding purposes.
  4. Begin working with Fedora Design Team / Badges Team to create the badges and get them deployed in the infrastructure.
  5. Share the news! A Community Blog article highlighting the series is an excellent idea. Updating the Join wiki pages are another important step after completion.
  6. Sit back and relax… your new on-boarding badge series is ready to help make all of our lives easier.

When do we do it

Since there are many sub-projects and not as many of us, breaking this into small steps is a must. I think it is important for us to work individually with sub-projects one at a time to:

  • Ensure the maximum attention possible is given to their team
  • Help expedite the process and begin having working examples of this across the Fedora Project
  • More thoughts and ideas during brainstorming is always helpful

For the above mentioned reasons, this milestone is identified as "ASAP" because it will be a very much ongoing process.


For later reference, some badges were designed for G11n / i11n but were never deployed for legal reasons (flags of real countries cannot be used). This ticket is found here. It might make an easier place to jump off from for G11n badges later on.

A duplicate ticket for this was filed (#60). That ticket is being closed and the comments from that ticket are being added here.

Quoting from [ticket:60 decause]:

Work In Progress Text:

Onboarding Series

Ambassadors
    0) Get a FAS Account (sign the FPCA)
    1) Create a User Wiki Page
    2) Join Mailing Lists and IRC Channels
    3) Contact a Regional Mentor, get sponsored
    4) Get mentor approval
    -----decause adds-----
    5) Attend regional ambassador meeting, introduce yourself
CommOps
    0) If no fas account,  create one and sign FPCA
    1) intro to mailing list, intro to https://admin.fedoraproject.org/mialman/listinfo/CommOps
    2) join IRC #fedora-commops
    3) get with a mentor and  start  writing  / editing blog / fed mag  articles
    4) 
Design
    0) create a FAS account (sign the FPCA)
    1) Join the mailing list, introduce yourself: https://admin.fedoraproject.org/mailman/listinfo/design-team
    2) Claim a ticket in the Design Trac: https://fedorahosted.org/design-team/report/1
    3) Update your ticket, send updated information to Design List
    4) Once work is approved, request an invite for your FAS username for the design-team group on the design team list: https://admin.fedoraproject.org/mailman/listinfo/design-team
    5) Add yourself to the contributors list: http://fedoraproject.org/wiki/Artwork/Contributors
    ----decause adds-----
    6) Attend Design Team IRC meeting?
    7) subscribe to the design tasks fedocal: https://fedorapeople.org/groups/schedule/f-24/

Documentation
0) Create a FAS Account (sign the FPCA)
1) Create a GPG Key, and upload it to keyservers, one of which being keys.fedoraproject.org
2) write a self-introduction to the mailing list with some ideas on how you would like to contribute: https://fedoraproject.org/wiki/Introduce_yourself_to_the_Docs_Project
3) create your own user wiki page, or update with new info if one exists from another prject
4) attend the freenode.net InterRelay Chat channel #fedora-meeting meetings on Mondays.
5) hang out on freenode.net InterRelay Chat channel #fedora-docs
6) Interact with other fedora contributors (how to use fasinfo, lookup others wiki user pages, asking for sponsorship)
6) Make a contribution Choose an item from this page: https://fedoraproject.org/wiki/How_to_contribute_to_Docs
7) Post to mailing list, describing which contribution you want to make, asking for feedback
8) Post to mailing list with links to your contribution

Rel-eng
0) Create a FAS Account (Sign the FPCA)
1) Join the #fedora-releng IRC Channel on Freenode and introduce yourself.
2) Attend a #fedora-releng meeting, and notify the team you'd like to contribute during "open floor" (speak up badge)
3) Subscribe to the rel-eng calendar on Fedocal:
EPEL?
0) Create a FAS account, (Sign the FPCA)
1) Join the EPEL SIG mailing list:
Infrastructure
- cc: keekri
Infra Apprentice Onboarding Proces:
0) Get a FAS Account (sign the FPCA)
1) You start with getting started doc https://fedoraproject.org/wiki/Infrastructure/GettingStarted
2) IRC, Mail List, and say "hi, I like to join the Apprentice group."
3) Answer the monthly apprentice status update about what systems you are working with, what you are doing
with them, and what you are learning.
4) Participate in the Fedora-infra weekly meeting.
Localization
globalization
0) Create a FAS Account, (sign FPCA)
1) Introduce yourself on the g11n list: https://lists.fedoraproject.org/admin/lists/g11n.lists.fedoraproject.org/
2) Language Tester Badge
3) First Contribution Accepted!
Magazine < https://fedoramagazine.org/writing-an-article-for-the-fedora-magazine/ >
0)
Marketing
0) Create a FAS Account (and sign the FPCA)
1) Join the mailing list and introduce yourself: https://fedoraproject.org/wiki/Introduce_yourself_to_the_marketing_group
2) Choose a marketing task you'd like to help with, and post to the mailing list asking for feedback:
https://fedoraproject.org/wiki/Marketing/Schedule
3) Post to the mailing list with a link to your contribution.
4) Request to join the marketing group in FAS
Package Maintainers
Quality Assurance
Websites

Discussed at 2016-03-29 hack session.

Some more progress was made on this ticket in the form of new tickets in the Fedora Badges Trac. You can find the links to those new tickets at the following links. It's important to note that these badges can be universally applied to any sub-project and don't rely on a single group.

Discussed in 2016-05-31 meeting.

We have a hack session on the books for this Friday! Find it on Fedocal here.

Discussed in 2016-06-07 meeting.

Taking a magnifying glass to CommOps

In today's meeting, we agreed that we would focus ''first'' on the CommOps on-boarding badge series. We discussed many meetings ago that we wanted to start with our own sub-project as a "test run", seeing how it works and how it goes, before then helping assist other sub-projects develop their own.

@skamath will be filing a ticket in the Badges Trac for the CommOps on-boarding series. Once it's up, we can aim to contribute the YAML rules file (requires knowledge of fedmsg and datagrepper), and possibly any artwork assets too (elioqoshi did just create an updated badges resources sheet, which might make it easier to pull together something creative and/or unique).

This would be a good thing to tackle at a hack session!

Discussed in 2016-07-05 meeting.

Overall update

This ticket doesn't get a whole lot of updates, but that's because a lot of the activity related to this ticket is happening in smaller, more specific tickets, for the different sub-projects / sub-groups. So anyone not seeing activity on this ticket should not be alarmed. :wink:

CommOps on-boarding

As of right now, we just finished up our efforts on the CommOps on-boarding ticket (ticket #57), and we've put together the YAML definition and other details in the accompanying Fedora Badges ticket (fedbadges#464). @decause uploaded some artwork he had created of the Canadian goose to the ticket. Once the artwork assets are finalized for that ticket, we can finally close that ticket out! We'll officially have one on-boarding ticket under our belt at that point.

Modularity on-boarding

This was the next group we wanted to target and help get started, after CommOps finished up. This is found in CommOps ticket #69. More details about this specific sub-group can be found in that ticket. You can find the Fedora Badges info in fedbadges#466.

Infrastructure on-boarding

This will be our next target sub-project (ticket #49) after CommOps and Modularity begin wrapping up and closing out. Unlike both CommOps and Modularity, Infrastructure already has a lot of badges for FAS sponsorships. Improving the Infrastructure on-boarding process is actually something that will be helpful to the on-boarding process for about any group in Fedora.

Badges related to Infrastructure that I have earmarked are the ones for mailing list activity and Pagure contributions, such as fedbadges#434, fedbadges#441, and fedbadges#442.

Discussed in 2016-10-04 meeting.

We briefly discussed this ticket during the meeting. The Python SIG ticket ( #84 ) and Modularity team ( #69 ) ticket are both nearing completion, and hopefully soon we can have them crossed off the list entirely. It's probably time to select another sub-project to focus on. I was thinking Globalization might be one we could review and assist with. I will open up discussion about this on the mailing list.

Metadata Update from @jflory7:
- Issue priority set to: no deadline (was: normal (1-2 weeks))

2 years ago

It was decided in CommOps meeting on 2017-09-13, that CommOps would work towards an integrated document to guide different teams on how-to create effective onboarding guidelines and provide them with examples.

More Info here -
https://meetbot.fedoraproject.org/fedora-meeting/2017-09-13/commops.2017-09-13-17.05.log.html

Ticket for how-to document to guide different teams on creating and implementing effective onboarding guidelines is here -
https://pagure.io/fedora-commops/issue/117

Metadata Update from @bee2502:
- Issue marked as depending on: #117

2 years ago

Ticket closed

In the CommOps FAD, we agreed to close the on-boarding series tickets since they have stalled out. Most of them are blocking on specific Fedora Badges (and there are tickets already filed). If we want to revisit a specific team, we should file a new ticket and start from a fresh slate.

I think it's worth noting a lot of awesome work was done on this series in our beginning two years – thanks everyone who has helped on the on-boarding work over the years.

Metadata Update from @jflory7:
- Issue close_status updated to: Complete
- Issue marked as depending on: #117
- Issue set to the milestone: Fedora 28 (to May 2018) (was: Future releases)
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.