Hello all, my IRC handle is ke4zvu3, i'm in the Eastern time zone, and I also have a wiki page[1] setup. My skill set, most of which I have or still get to work with at $dayjob, would include but not be limited to (in no particular order) VMware (i.e. vSphere, Lab Manager, vCloud Director), PHP, NetApp SANs, various Apache implementations, Ci$co load balancers, various LDAP implementations, various radius servers, tacacs, RHEL, satellite & kickstart, mediawiki, JBoss, squid, a modicum of perl and bash scripting, BIND, mysql (booo), PostgreSQL, Nagios, SVN, postfix, sendmail, and mailman. I currently serve as a Systems Engineer role where I end up doing alot of R&D, PoC, and some documentation work. At various times in my $dayjob and overall career I've also toggled between serving in a sysadmin role of production and non-production systems. Infra seems to make prolific use of Puppet which is very exciting to see personally. I've helped implement/use Puppet on a contract job and in the end learned enough to know that there's so much more I have to learn. I'll actually be working more with KVM at $dayjob in the upcoming days and weeks which I'm pretty stoked about. Among other things, I look forward to learning more about the distributed nature of the infrastructure used at Fedora and to hear, see, and learn how awesomely you guys are using Puppet. For now I've currently blocked off about 5 - 7.5 hours per workweek to dedicate to Infra work. I've been hanging out in #fedora-admin and #fedora-noc off and on for several months now and plan to keep doing so on a more steady basis. I've also been in the marketing group for I think a couple releases or more now. I'm not 100% sure if I'm limited to choosing just one FIG to start off with[2], but based on the limited amount of info I know about each FIG, their relationships, lines of separation, division of labor, and what’s required to work on the tickets I referenced below, I would say maybe some or all of these: sysadmin-web sysadmin-hosted sysadmin-tools If I do need to narrow down my FIG selection, I may need to seek out info from the FIG leaders or others in Infra that can give guidance beyond what's described about them on the wiki[3]. >From looking at the trac list of active tickets[4], the following ones seemed like easy low hanging fruit that I would be interested in and capable of diving into and hopefully taking care of, pending conversations with the respective current ticket assignees: https://fedorahosted.org/fedora-infrastructure/ticket/1968 https://fedorahosted.org/fedora-infrastructure/ticket/504 https://fedorahosted.org/fedora-infrastructure/ticket/2816 https://fedorahosted.org/fedora-infrastructure/ticket/1658 --- [1]: https://fedoraproject.org/wiki/User:Jnalley [2]: https://fedoraproject.org/wiki/Infrastructure/GettingStarted#What_do_I_do_next.3F [3]: https://fedoraproject.org/wiki/Infrastructure/FIGs [4]: https://fedorahosted.org/fedora-infrastructure/report/1 _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
