On Mon, Feb 15, 2016 at 8:43 AM, Keerthana Krishnan <contactkeerthana@gmail.com> wrote:
Hi Viorel,

Welcome to Commops, I hope you have fun! Feel free to ask us for anything you need. Make sure to check out the trac page to find something that catches your eye.

We're working on creating a new member join page here at Commops, so I would like to ask for your help and feedback for the same, by replying with anything and everything you'd like to see on such a page. I think you might be able to give us another perspective.

Welcome! :D

On 15 February 2016 at 04:18, Viorel Tabara <viorel.tabara@infrabit.net> wrote:
Hi all, I'm just starting up with Fedora as a volunteer and one of the groups I
would like to help out in is CommOps so I'm just "going by the book" ;) and
sending out this introductory email as noted on the CommOps group page along
with the two required "pieces of identification":

   IRC nick: smkr
   TZ: Mountain Time

Being at a stage in my life where I have more free time in hand, volunteering
for Fedora is just another opportunity I would like to use for giving back to a
community that has made my cyber life at both work and home so enjoyable for
the past 10 years. At the same time there is so much more fun stuff to learn
about, I love the open source atmosphere so all in all I'm excited to start
helping out with anything I can. There is no boring job for when it comes to
hacking open source :)

I've been a sysadmin all my life so while I'm quite comfortable taking on any
work in that area, I can't consider myself a DevOps as my programming skills
aren't at that level (unless someone else considers Bash a DevOps language
because of its associative arrays, I don't though :) so what I'd like to get
out of this experience is knowledge exchange on the dev side of things.  I get
along fairly well with Ansible, although it may be better suited for the
Infrastructure group (which I'm going to apply for as soon as I get past the
"observation" stage). I'm no stranger to programming and can read Python,
understand it and provide easy fixes by following the existing code structure,
but that's where all ends.

Where I'd like to start in CommOps? Anything that requires to get my hands
dirty as there is no better way to learn. From reading the CommOps wiki page I
would say that any of the areas would work with the exception of on-boarding
but at this point I'm surely in the need of your guidance...

Thanks for providing this opportunity and if I missed anything let me know.

--
Viorel
_______________________________________________
commops mailing list
commops@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/commops@lists.fedoraproject.org



--
Keerthana Krishnan
B.Tech Computer Science (2012-16)
Govt. Model Engineering College
Creative Director, Teezonic Studio
Email : keerthana@teezonic.com
IEEE CS Student Member
Blogger : https://cutencrazyindie.wordpress.com/

_______________________________________________
commops mailing list
commops@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/commops@lists.fedoraproject.org


Viroel,

Welcome! As Keekri said, we're happy to have you here, and are happy to help connect you with our team, as well as others in Fedora that you may be interested in.

If you are available, our team meets regularly in #fedora-meeting-2 on Freenode Tuesdays at 17:00 UTC. In the meeting we discuss ongoing tasks and tickets, as well as announcements and news to be included in the Community Blog (CommBlog.)

Since you mentioned that you are interested in joining the infrastructure team, here is a link to the latest presentation I just gave at Config Management Camp with puiterwijk, Authentication Lead for Fedora-Infra: https://github.com/decause/decks/blob/master/cfgmgmtcamp-fedoraopeninfra.pdf

Welcome aboard, and we hope to see you in #fedora-commops on Freenode in the meantime.

Looking Forward,
--RemyD.

--
Remy DeCausemaker
Fedora Community Lead & Council
https://whatcanidoforfedora.org