== What == Most sub-projects have a series of wiki pages for their project dedicated to on-boarding new members and providing a way for them to become involved with any given sub-project. It provides a clear, ordered list of "things to do" in order to become an official member of any given sub-project.
== How == To come up with a thorough walk-through of how to become a CommOps member, we need to identify key tasks and things that a new member would do to become fully integrated into the team. This might include adding your timezones to the wiki page, attending a meeting, and introducing yourself on the mailing list.
This part of the ticket demands the most discussion.
== When == Seeing as this is something that makes it easier for new people to become a part of CommOps, defining this as soon as possible is an urgent task. Therefore, the ticket escalation is set to reflect this.
== Why == The need for this is self-apparent -- having a Join series on the wiki will make it easier for someone to become involved with CommOps ''now'', and this will also make it easier for us later on when we get to defining our own on-boarding badge series, just for CommOps.
'''Discussed in [https://meetbot.fedoraproject.org/fedora-meeting-2/2016-02-09/commops.2016-02-09-16.56.html 2016-02-09 meeting].'''
We're going to begin putting together our own on-boarding process on the mailing list, watch your inboxes for more later this week. :)
'''Discussed in [https://meetbot.fedoraproject.org/teams/commops/commops.2016-02-16-16.55.html 2016-02-16 meeting].'''
The 6-step process detailed on the [https://lists.fedoraproject.org/archives/list/commops@lists.fedoraproject.org/thread/BEIBVIIFGUOH3L32YSHFEDMO7IDGQOB5/ mailing list] was approved, with some slight revisions into an 8-step process.
= How to CommOps 101 =
= Vote = As discussed in the meeting today, I would like to put this ticket to vote. Voting will be done in a lazy consensus manner. We will move forward with the next step on Thursday, Feb. 18 or later.
+1 from me.
+1 for me. I guess that "The 6-step process" will only include the first 6 steps.
Replying to [comment:4 fale]:
I guess that "The 6-step process" will only include the first 6 steps. The 6-step process I proposed on the list would be modified to this 8-step process I described above. With relevant hyperlinks added, of course. :)
+1
'''Discussed in [https://meetbot.fedoraproject.org/fedora-meeting-2/2016-02-23/commops.2016-02-23-16.55.html 2016-02-23 meeting].'''
= 8-step process approved = The 8-step process was approved as shown earlier in this ticket. This is the process we will officially recommend for those looking at officially becoming involved with CommOps.
= Join wiki page = Now that the details are finished, a wiki page was the next objective. Fortunately, keekri wrote the [https://fedoraproject.org/wiki/CommOps/Join entire page]! The page is mostly there as of now. The next steps are going to be publishing the Join page across pre-existing pages advertising "Join the Fedora Project!"
Earlier, I had identified the pages that would need updating. I can take on the remainder of this responsibility of publishing our Join page across the Project. I'll share a full list of all pages changed before closing the ticket.
= Our personalized Join page = It's official! We have a static page documenting our "Join" process that new contributors can use to become on-boarded with our own team. This page lives on the [https://fedoraproject.org/wiki/CommOps/Join wiki] (and will likely be replaced by Badges some day… but alas, a discussion for another day!).
= The mothership Join page = And finally, the global [https://fedoraproject.org/wiki/Join Join page] on the wiki also has some new, snappy bullets added talking all about this new, hot-off-the-press CommOps team. :P Anyways, there were multiple sections I added CommOps to here, and I shared with the mailing list about reviewing my additions and seeing if I effectively covered all applications of what CommOps can do.
Thanks for creating the join page and this helped me a lot in joining the team :)
Login to comment on this ticket.