18:01:53 <zoglesby> #startmeeting
18:01:53 <zodbot> Meeting started Thu Mar 27 18:01:53 2014 UTC.  The chair is zoglesby. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:53 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:02:03 <zoglesby> #meetingname docs
18:02:03 <zodbot> The meeting name has been set to 'docs'
18:02:14 <zoglesby> #meetingtopic Docs Office Hours
18:02:36 <randomuser> #info randomuser is here
18:02:37 <zoglesby> #chair randomuser Sparks
18:02:37 <zodbot> Current chairs: Sparks randomuser zoglesby
18:03:11 <zoglesby> #info Office Hours are from 1800 - 1900 UTC
18:04:28 <randomuser> how did the server WG meeting go, zoglesby ? i read the summary, but not the log
18:05:21 <zoglesby> randomuser: good, it is the WGs opinion that a standalone doc would be better, so I am going to start working on that
18:05:40 <randomuser> cool
18:06:06 <randomuser> do they have their roles defined yet?
18:06:14 <zoglesby> It is going to be slow starting as I don't yet have my head wrapped around the end goal
18:06:53 <randomuser> easier administration, i think
18:07:20 <randomuser> enterprisey deployments
18:07:23 <zoglesby> randomuser: Database and Domain Controller
18:07:37 * randomuser will have to read up on cockpit before he knows what he's talking about, obviously
18:07:53 <zoglesby> thankfully I have lots of experience with PostgreSQL, so I have a leg up on that one
18:08:18 <zoglesby> randomuser: indeed, the first I heard about it was at the FAD
18:09:11 <zoglesby> #info If you have questions or issues for Docs fell free to join the conversation
18:09:29 <randomuser> yeah, i've only been able to keep up because of frequent mandatory idle time situations
18:12:10 <zoglesby> randomuser: Have you had the time to compile the action items list from the FAD?
18:12:33 <randomuser> zoglesby, no, I should do that now
18:12:58 <jhradilek> #info jhradilek waves.
18:13:06 <jhradilek> (Sorry, I had to try that at least once.)
18:13:10 <randomuser> after I finish scarfing this terrible lo mein
18:13:10 <zoglesby> #chair jhradilek
18:13:10 <zodbot> Current chairs: Sparks jhradilek randomuser zoglesby
18:19:18 <randomuser> we have a lot of stuff that could probably be announced on some $announce@ list
18:19:26 <jhradilek> So, the office hours for EMEA are on Sunday?
18:19:29 <randomuser> but not too soon or too late ...
18:19:44 * jhradilek has never seen the Fedora Calendar before.
18:20:47 <zoglesby> jhradilek: it look like that is what lnovich set up
18:22:34 * randomuser 's fortune cookie advises he will "travel to many exotic places"
18:23:06 <jhradilek> randomuser: Are you coming to Prague this August? :)
18:23:30 <randomuser> ahh... I would like to, but I'm not confident it will work out
18:23:56 <randomuser> not sure I will be able to take that much time off so soon after starting this new job
18:25:13 <randomuser> i heard you're hiring a bus for the event, jhradilek ?
18:25:25 <jhradilek> Too bad, it would be nice to see meet you. :)
18:26:03 <randomuser> yah. I'll ask, anyway
18:26:03 <jhradilek> randomuser: I don't know yet, I am still figuring out how many of the local Fedora Docs contributors want to go. :)
18:28:08 * Sparks is here
18:28:09 <randomuser> there is a deadline for talks looming, if you want to present you'd better get on that
18:28:28 <jhradilek> I know, the deadline is April 3rd.
18:28:35 <jhradilek> I am thinking about it.
18:31:40 <randomuser> vim plugins talk, maybe?
18:32:02 <jhradilek> We definitely want to have a hackfest there.
18:32:02 <jsmith> randomuser: Great idea!
18:32:38 <randomuser> #info Sparks and jsmith have joined
18:32:40 <jhradilek> randomuser: Would anybody be interested in that? :) It's a pretty boring subject.
18:33:04 <randomuser> jhradilek, propose it and see - there's a voting process next iirc
18:34:18 <randomuser> i would definitely do a vimscript crash course
18:35:20 <jhradilek> In that case stay tuned, the next thing I intend to add is a "classbrowser" for DocBook. I want to see the outline of my chapter in the sidebar.
18:36:09 <jsmith> jhradilek: Ah, that's easy ... it's just XSLT :-p
18:36:18 * jsmith is only half-joking
18:36:46 <jhradilek> jsmith: It's not difficult. :)
18:38:52 <randomuser> crap, i just looked at the docs list archive and was reminded we're well into Change proposal season
18:39:03 <jsmith> randomuser: Aye...
18:40:22 <zoglesby> randomuser: I think it ends next week for system wide
18:40:57 <randomuser> Sparks, how is that "docs contact" bz field working for you?
18:41:08 <randomuser> better than cloning, you think?
18:41:29 <zoglesby> anything is better than cloning
18:41:30 <Sparks> randomuser: I'll still clone but I can at least work on the same ticket to work out the details first.
18:41:53 <randomuser> zoglesby, what's your problem with cloning?
18:42:59 <zoglesby> randomuser: It creates extra work, information is in more spots, I am sure I could think of other reasons
18:43:31 <randomuser> aye
18:43:47 <randomuser> I like that it 1) reminds the change owners we're doing stuff
18:43:56 <randomuser> 2) gives us a way to track coverage
18:44:34 <zoglesby> randomuser: I think its an okay idea, but if we can track the same information in the same ticket that is a better option
18:44:49 <Sparks> zoglesby: There is even a "docs" spot in BZ now
18:47:12 <randomuser> too bad jreznik isn't around for this discussion
18:47:13 <zoglesby> Sparks: indeed, I think we should use that and not clone bugs
18:47:39 <randomuser> I don't really care one way or the other, as long as we can keep track of what's getting done
18:48:47 <Sparks> zoglesby: I guess my only concern is...
18:49:05 <Sparks> zoglesby: That we lose the ticket because it wasn't assigned to a guide.
18:49:46 <randomuser> Last time, I did separate bugs for RNs and Guides
18:50:25 <randomuser> it was a PITA, but the intent was to make a process that more people could participate in without excessive coordination overhead
18:56:07 <zoglesby> Sparks: for guides I think we still need tickets, but for tracking changes for the release notes I think this is a better method
18:58:02 <zoglesby> that is not to say that I am correct, but I think it makes everything more manageable
18:59:27 <randomuser> I like it
18:59:43 <randomuser> lazy consensus?
19:01:36 <zoglesby> +1
19:02:15 <Sparks> zoglesby: +1
19:02:16 * zoglesby is going to #endmeeting in 5 min
19:03:32 <zoglesby> randomuser: do you want to bring this up at the meeting next week?
19:03:44 <randomuser> heh
19:03:52 <randomuser> honestly, no, i think we should just do it
19:03:54 <zoglesby> or take a three man vote
19:04:02 <zoglesby> okay works for me
19:04:20 <Sparks> DOIT
19:04:38 <randomuser> if someone wants to take responsibility for documenting a change, and they feel they need a cloned bug to make that happen, I won't stand in their way
19:07:12 <randomuser> #agreed Change process will involve us using the Docs Contact BZ field for RNs tracking
19:08:04 <randomuser> #info randomuser will not be cloning RN tracking bugs
19:12:10 <zoglesby> Thank you everyone!
19:12:13 <zoglesby> #endmeeting