18:04:26 <randomuser> #startmeeting Fedora Docs Office Hours
18:04:26 <zodbot> Meeting started Thu Jun  4 18:04:26 2015 UTC.  The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:04:26 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:04:41 <randomuser> #meetingname fedora_docs
18:04:41 <zodbot> The meeting name has been set to 'fedora_docs'
18:09:36 <wdashley> I am new here. It has been suggested that I work on the virtualization docs since I have a lot of experience with that topic. Who should I take direction from on what needs to be done?
18:14:47 <randomuser> hey wdashley, glad you could make it
18:15:07 <randomuser> Sorry for procrastinating on the reply to your introduction
18:15:17 <wdashley> np
18:16:45 <randomuser> since you have experience with docbook and such, the best approach would probably be to work on the one big virt book we have, the Virtualization Administration and Deployment Guide
18:17:45 <randomuser> Laura Novich (lnovich here) writes that for RHEL/RHEV and our version is derived from that
18:18:24 <randomuser> that's somewhat atypical for our books, usually the Fedora guide would be upstream for the Red Hat guide, but I think she has her hands full with the RH books so this one doesn't get ahead
18:19:48 <wdashley> that actually makes sense to me
18:19:56 <randomuser> good :)
18:20:36 <randomuser> I'd be surprised if there were any dramatic procedural or functional changes to be made in the book, really
18:20:51 <randomuser> maybe some feature adds
18:21:37 <randomuser> but for the most part, I think it needs checking over for product context - things like references to RHEV, support agreements, etc
18:21:44 <wdashley> One of the areas that is weak is virsh and the libvirt interface. A virsh guide might be very useful
18:21:58 * randomuser nods
18:22:17 <randomuser> there is an upstream virsh guide that's half finished... I wonder if I can find it again
18:22:55 <randomuser> ah, here we go: http://libvirt.org/virshcmdref.html
18:23:28 <wdashley> But we can discuss those later. I will contact lnovich and see what sh e thinks
18:23:32 * randomuser clones
18:24:23 <randomuser> wow, someone committed to this since the last time I looked :)
18:24:51 * zoglesby is here'ish
18:25:50 <randomuser> anyway, that book could be an option.  It isn't strictly under Fedora Docs purview, but I'm sure it's permissively licensed and that the libvirt developers would be cooperative - especially considering we'd be offering to maintain a book that's had one commit in the last four years
18:26:02 <randomuser> hi, zoglesby, sort of
18:27:32 <randomuser> lnovich is.. UTC+0300 iirc, for IRC, it's best to catch her in the daytime
18:28:33 <randomuser> wdashley, do you want a crash course in setting up a git repo while you're here?
18:29:02 <wdashley> I found the wiki page. I think I can get done from there
18:29:15 <randomuser> I sponsored you for 'docs', but 'docs-writers' gives commit access; I have been asking people to set up a remote on fedorapeople for git acclimation
18:29:49 <randomuser> http://fedoraproject.org/wiki/User:Tmz/How_to_use_git_on_fedorapeople.org has instructions for that
18:30:16 <wdashley> I have a lot of subversion experience and some old cvs experience. I think I can manage
18:30:47 <randomuser> clone the repo, create a branch for yourself, push the branch to fedorapeople; we'll merge after you've worked on it a while and lnovich or whoever is satisfied
18:31:04 <wdashley> ok
18:31:11 <randomuser> I have no doubt that you'll handle it :)
18:40:48 <randomuser> wdashley, I'm excited about some examples and such for libvirt-libvirt
18:41:10 <randomuser> that seems very interesting
18:41:17 <randomuser> err... libvirt-python
18:42:05 <wdashley> That would be very interesting as I am just learning that interface myself
18:42:37 <randomuser> I've looked at the code that buildbot uses to spin up libvirt builders, briefly, but that's about it
18:43:37 <wdashley> I actually wrote a small libvirt interface to ooRexx to help with some automation for a client.
18:44:01 <wdashley> The python interface is much more robust
18:44:10 <randomuser> I'm not familiar with ooRex
18:44:51 <wdashley> ooRexx is an object-oriented Rexx interpreter. Fedora actually offers it for installation
18:45:55 <randomuser> I didn't know about rexx either :P
18:46:21 <wdashley> it is an old IBM interpreter that was open sourced in 2005
18:46:53 <wdashley> very fast and with a very nice object approach
18:51:50 <randomuser> well, I should head back to $dayjob
18:51:55 <randomuser> #chair zoglesby
18:51:55 <zodbot> Current chairs: randomuser zoglesby
18:52:09 <wdashley> me too
18:52:12 * randomuser puts zoglesby on the hook for continuing and closing the session
18:58:20 <zoglesby> um...
18:58:31 <zoglesby> Okay!
19:00:38 <zoglesby> #endmeeting