18:02:06 #startmeeting Fedora Docs Office Hours 18:02:06 Meeting started Thu Mar 19 18:02:06 2015 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:03:18 Hello 18:09:32 hey grundblom 18:09:32 * randomuser pulls grundblom's branch 18:09:52 Howdy Randomuser 18:09:55 thanks for taking a look 18:10:30 Running into a problem with the XML, thinking of making Boxes it's own chapter to compartmentalize it 18:11:28 * randomuser nods 18:11:30 makes sense 18:11:59 are you getting an error when trying to build? 18:12:49 Yeah, when I try to add more items about libvirt around lines 700(ish) I close all my tags, but then publican complains about line 912, and 918 18:13:07 So I figured 1000 lines is probably too long anyway 18:13:25 can you fpaste the error? I get a different one here, because of a bug 18:14:15 Not at the moment, I can send it to you later when I have my personal laptop available 18:14:25 okay 18:15:04 <- Unprepared for the meeting :-( 18:16:31 hmm, products.xml passes xmllint as is 18:17:11 I did comment out the part I am working on in the lower part of sec-boxes 18:17:37 * randomuser scrolls down 18:18:08 it should be in the 712 lines ish 18:21:53 grundblom, it's your warning 18:22:19 really? 18:22:22 Wow, 18:22:26 warning is a block level tag, not an inline tag; it does a whole callout thing with a title, a warning graphic, etc 18:22:41 admonitions like note, caution warning all work that way 18:23:19 Oh, good to know! Thank you very much 18:23:52 also important 18:24:21 you might try there 18:25:41 I might also word that a little more absolutely than "do not destroy this frequently" since it's pretty much always a bad idea :) 18:27:04 Right! 18:27:18 I think you have an extra section close on 563 - maybe 18:29:13 for me, using an editor that's smart about indenting really helps with xml 18:29:13 Thanks, I will look at that and see what I was doing 18:29:37 it might be easier to rip out the boxes content into the new file, then deal with the tags 18:30:20 smccann, do you have a branch of this guide set up? 18:30:41 fwiw - i have virt-manager as an independent chapter, so having boxes as a chapter would be a good match 18:30:59 sounds like it :) 18:31:06 randomuser - well, I pulled a branch, yeah. 18:31:20 smccann, are you pushing anywhere? 18:31:33 not smart enuf yet on git to know how grundblom made a branch available to y'all. :-) 18:32:02 and no, randomuser, haven't pushed yet. Was getting my 2 chapters in shape first. 18:32:11 okay 18:32:43 how do you two want to approach merging? 18:32:56 should I wait now til grundblom's stuff is committed since he sounds closer to that? then I can pull in his on my brach 18:33:01 at some point, we'll end up with you both working in master 18:33:06 smccann, I followed the git instructions here: http://fedoraproject.org/wiki/Infrastructure/fedorapeople.org 18:33:07 branch even 18:34:00 smccann, are you making commits as you go along? 18:34:04 thanks grundblom, I'll take a look. 18:34:19 randomuser....erm...ah...erm... 18:34:25 heh 18:34:28 that would be a no :-P 18:34:45 go ahead and make one now 18:35:07 ok so git tutorial 101 - was thinking 'commit when I have virt-manager chapter and install virt-manager chapter done" 18:35:19 sounds like maybe that's not the best approach? 18:35:36 yeah, not the best approach 18:35:48 it's best to commit for each discrete change 18:36:14 so you add a couple paragraphs about storage devices, say, and commit that 18:36:24 then add a couple about OS types, commit that 18:36:41 then, when the chapters are all done, that's when we merge all of your commits 18:37:07 ah ok 18:37:52 so should I move to a public git like grundblom has and start commits there? and again, should I wait for his stuff to be done or just do it independently? 18:37:55 this makes it a lot easier to follow along, for one, 18:38:27 using the public git repo - and he created a branch, too - allows him to share what he's working on 18:38:38 both for review and ultimate inclusion 18:38:58 gotcha... live n learn... :-) 18:39:08 you *could* work it out on your own, and use git to create patch files when we're ready to merge 18:40:26 yeah that sounds like the directions I read somewheres... but I can move it all easily anyway. better that way so y'all can see it 18:40:35 * randomuser nods 18:41:31 also, it's easier to assess when you have a good handle on using git and publican, and are ready to move on to direct commit access to the project's repos instead of personal repos 18:42:31 :-) 18:46:03 smccann, the other upside to having something to push to is free backup - you won't lose your work if your computer dies 18:47:34 randomuser - so very true 19:03:46 #chair jhradilek 19:03:46 Current chairs: jhradilek randomuser 19:04:13 Good afternoon! 19:05:25 I have to head back to $dayjob soon, but maybe you want to keep this going? 19:05:44 maybe not though, it's gone quiet 19:07:22 Sure, what's the topic? :) 19:07:27 office got busy 19:09:38 jhradilek, the virtualization getting started guide, best practices with committing, and a little docbook 19:09:58 * jsmith can help with the DocBook 19:10:26 #chair jsmith 19:10:26 Current chairs: jhradilek jsmith randomuser 19:11:13 * jsmith catches up on the scrollback 19:11:23 Right. Too bad Laura is probably somewhere between Brno and Vienna right now. 19:12:08 * randomuser & 19:24:10 pbokoc: Evening. :) 19:25:50 look what I parked next to when I went to buy groceries :) http://i.imgur.com/78aSs4C.jpg 19:26:30 1st generation Chevrolet Monte Carlo, made in 1970-72 19:29:09 (and yeah, my phone camera sux) 19:36:55 pbokoc: Your car looks tiny in comparison. :) 19:37:15 yeah, that thing looked like an aircraft carrier in comparison 19:37:46 I think my car could fit in the thing's cabin if you cut the roof off 23:26:41 #endmeeting