9:52 p.m.
Hi CommOps,
This email goes out discussing a hot topic that we discussed at our
meeting today.
https://meetbot.fedoraproject.org/fedora-meeting-2/2016-02-09/commops.201...
We identified that most of the other Fedora sub-projects have Join pages
on their wiki, describing how a newcomer can look at becoming a part of
their sub-project. CommOps does not have anything like this (yet)! This
need has been addressed in Ticket #37 on our Trac.
https://fedorahosted.org/fedora-commops/ticket/37
As a result, I think we should begin discussing our own on-boarding
process and coming up with ideas for "how someone becomes a CommOps
member". Below, I have proposed a (loose) ordered list of the process
that we could recommend someone to follow who is interested in joining
up in what we do.
It is very much hands-on – feel free to edit, remove, or add other steps
or lines as you think is fit!
=== How to CommOps 101 ===
1) First, send a self-introduction to the CommOps mailing list
explaining a bit about yourself. Are you new to contributing to
Fedora? If so, tell us why you're interested in contributing or
what interests you most. Already a contributor? Share what other
areas of Fedora you are working in and your role in the Project.
In addition to this, tell us what areas of CommOps you are
interested in contributing to most and how WE can help YOU get
started.
2) After sending your self-introduction, add your name, timezone, and
interest areas to the CommOps wiki page. This will help map an idea
of who is contributing to CommOps and what areas we are all wanting
to work on.
3) Join the "CommOps" FAS group after sending your self-introduction
and adding your info to the wiki page. A sponsor will add you into
the group after completing these steps.
4) Join the #fedora-commops IRC channel on Freenode. A lot of our
discussion and planning happens in real-time on IRC, and it's the
best place to meet some of the team and get a view of what's
happening in CommOps.
5) Attend a Fedora CommOps meeting and introduce yourself during roll
call. Every week, the CommOps team comes together to discuss items
on our agenda and check in on the tasks that everyone is working
on. Introducing yourself during roll call is another great way to
get involved and will let others know you are part of the meeting.
6) Find a task to work on. All of CommOps tasks are mapped out in our
Trac. Tasks, problems, or objectives are added as "tickets" to the
Trac page. Check and see what CommOps is working on now here to see
what is happening this week. After that, look at all of the open
tickets on our Trac? See something that looks interesting? See if
the ticket has an owner. If it doesn't, you can step up and take
ownership! If it does, contact the owner of the ticket and see if
they need any help. This also provides a great opportunity to get
mentorship and help with getting started on a new task!
Insert links where appropriate.
Looking forward to hearing all of your thoughts. :)
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com