14:00:03 <randomuser> #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings
14:00:03 <zodbot> Meeting started Mon Jun 24 14:00:03 2013 UTC.  The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:00:03 <randomuser> #meetingname Fedora Docs
14:00:03 <randomuser> #topic Roll Call
14:00:03 <zodbot> The meeting name has been set to 'fedora_docs'
14:00:46 * Capesteve is here
14:00:49 <randomuser> GDTY, all
14:01:01 * jjmcd 
14:05:04 <randomuser> We'll let the rest speak up as they will
14:05:25 * jhradilek is here.
14:06:57 <randomuser> #topic Follow up on last week's action items
14:07:19 <randomuser> Capesteve, you were doing something with the wiki, i think?/
14:07:42 <Capesteve> randomuser: was supposed to be
14:08:01 <Capesteve> I statred amking a template but was not sure how to create a page
14:08:18 <Capesteve> I believe you have been proof reading already?
14:08:26 <randomuser> ha! I know how to make a page, but not a template
14:08:40 <randomuser> Capesteve, yeah, i have a #topic just for you in a bit
14:08:51 <Capesteve> can you sugest a location?
14:09:11 <randomuser> for my action items, I did go over some stale bugs but not the RN process docs
14:10:10 <randomuser> http://fedoraproject.org/wiki/Docs_Project_Review_Table maybe ?
14:10:18 <Capesteve> https://fedoraproject.org/wiki/Docs_Project?rd=DocsProject maybe under "Current Issues'?
14:10:48 <Capesteve> for the name?
14:11:05 <randomuser> let's defer this until the topic comes up so we can provide some context, please
14:11:14 <Capesteve> http://fedoraproject.org/wiki/Docs_Project_F18_Sys-Admin_Guide-Review_Table
14:11:19 <Capesteve> ok
14:11:42 <randomuser> thanks
14:11:44 <randomuser> #topic Release Notes - Changes coming
14:12:05 <randomuser> just a heads up here
14:12:15 <randomuser> #info we should start thinking about F20 *now*
14:12:45 <randomuser> the Changes process is already rolling, and we'll be asked to assign writers to tracker bugs soon
14:13:39 <randomuser> that's all
14:13:47 <randomuser> #topic Guide status
14:14:44 <randomuser> i think pbokoc took over the installation guide?
14:15:52 <randomuser> #info it looks like we should have security guide, IG, sysadmin guide, and virt guide for f19
14:16:05 <jhradilek> Here he is. :)
14:16:14 <randomuser> welcome, pbokoc !
14:16:18 <pbokoc> sorry, had some computer trouble here
14:17:14 <randomuser> no worries
14:17:36 <randomuser> we're reviewing guide status, pbokoc - I understand you're working on a guide?
14:18:01 <pbokoc> randomuser, yes. Two actually - the Installation Guide and the Power Management Guide (for now).
14:18:39 <pbokoc> The Power Management Guide only has one issue that needs to be taken care of: https://bugzilla.redhat.com/show_bug.cgi?id=831619
14:19:38 <pbokoc> Unfortunately I'm not copletely sure I'll be able to take care of this on time. It depends on how fast can I get info from Jaroslav Skarvada. Jack Reed did some changes already, but they don't seem to cover everything.
14:19:54 <randomuser> can we assist, pbokoc ?
14:20:16 <jhradilek> jskarvad: ^
14:21:35 <pbokoc> What would help me here would be if jskarvad went over the changes Jack has already done and told me if it's enough, or what do I need to add or modify. I haven't really had the chance to look through Jack's commit
14:21:56 <randomuser> fair enough
14:22:14 <randomuser> jskarvad is the tuned maintainer, then?
14:22:41 <jskarvad> randomuser: yes
14:22:48 <randomuser> hi :)
14:22:58 <pbokoc> :)
14:23:00 <jskarvad> pbokoc: I am working on the guide update
14:23:03 <jskarvad> hi
14:23:26 <jskarvad> pbokoc: I already rewrote the powertop chapter
14:23:48 <randomuser> jskarvad, do you have or need docs-commit privileges?
14:23:51 <jskarvad> pbokoc: did some work on the tuned chapter - it is not complete yet
14:24:05 <jskarvad> randomuser: I already obtained it a few weeks ago
14:24:17 <pbokoc> jskarvad, that's excellent, I didn't realize you were actually providing the docs yourself.
14:24:42 <jskarvad> pbokoc: ye, I am devel wich writes docs :)
14:25:03 <pbokoc> In that case, do you think you're going to finish in time for the release? Do you need any help?
14:25:13 <jskarvad> pbokoc: deadline?
14:26:23 <randomuser> jskarvad, to put it into context, we won't refuse to publish if you're done after the release day
14:26:34 <pbokoc> jskarvad, the release is July 2nd (next Tuesday)
14:26:54 <pbokoc> I'll be available over the weekend if you don't have enough time to do it by this Friday
14:27:34 <pbokoc> or as randomuser says, it's not the end of the world if it's available after release. Depends on how busy you are, really...
14:27:52 <jskarvad> pbokoc: I will try, I think I could finish it in time
14:28:02 <jskarvad> pbokoc: or in the worst case few days later
14:28:26 <jskarvad> pbokoc: I would really want it to the release :)
14:28:35 <jskarvad> pbokoc: I will provide you info about the progress
14:28:57 <randomuser> jskarvad, there's usually someone in #fedora-docs if you need help with markup, processes, or whatever
14:29:13 <pbokoc> jskarvad, all right then. Thanks for doing it, it's a big help.
14:29:25 <jhradilek> I am willing to help as well. :)
14:30:07 <pbokoc> jhradilek, I'll ask you offline if I need anything. I'll definitely need your help with publishing :)
14:30:23 <jskarvad> pbokoc, jhradilek: ok, thanks, I will provide you the draft, it may require language correction
14:30:33 <randomuser> jskarvad- it's awesome that you're handling this, thanks. Please commit and push often?
14:30:59 <jskarvad> I will do my best with the markup (I wrote / edit some chapter earlier)
14:32:30 <jskarvad> randomuser: OK, I would rather push to private branch and let jhradilek or pbokoc to merge it into master
14:32:30 <jskarvad> after review
14:32:53 <pbokoc> jskarvad, OK, no problem.
14:33:17 <jskarvad> pbokoc: ok, thanks
14:33:47 <jhradilek> jskarvad, pbokoc: Thanks guys. :)
14:33:59 <randomuser> jskarvad, that's probably fine - but FYI committing to a public branch helps the rest of the group know what you're working on and allows us to scale up
14:34:20 <randomuser> EOF
14:34:34 <randomuser> #topic System Administrator's Guide
14:34:46 <randomuser> #chair Capesteve
14:34:46 <zodbot> Current chairs: Capesteve randomuser
14:34:51 * LoKoMurdoK here
14:34:52 <randomuser> #chair jhradilek
14:34:52 <zodbot> Current chairs: Capesteve jhradilek randomuser
14:34:56 * LoKoMurdoK late
14:34:58 <randomuser> welcome, LoKoMurdoK !
14:35:06 <LoKoMurdoK> :-)
14:35:14 <randomuser> Sorry for putting you off, Capesteve, please continue
14:35:19 <randomuser> oh
14:36:11 <randomuser> I was going to say that for now, a single dynamic page for review tracking might be better than setting a precedent for a bunch of wiki/Guidename_releasever pages
14:36:16 <Capesteve> How about /wiki/Docs_Project_Review_Table-F18_System_Administrators_Guide
14:36:35 <Capesteve> maybe just an etherpad page?
14:36:57 <Capesteve> dynamic page = ?
14:37:41 <randomuser> dynamic, as in we'll change it's content as needed if different guides need to be reviewed
14:37:54 <Capesteve> oh
14:38:02 <Capesteve> generic name then
14:38:35 <Capesteve> ok, will do: https://fedoraproject.org/wiki/Docs_Project_Review_Table
14:38:37 <randomuser> to keep down on the number of deprecated and abandoned wiki pages, yes
14:39:41 <jhradilek> I agree, I think that one page for all guides would be better and less confusing.
14:39:41 <randomuser> anyone want to work up some cursory review guidelines to go with the tracking table?
14:39:47 <jhradilek> And definitely easier to find
14:40:02 <randomuser> jjmcd perhaps you have some cycles for that?
14:40:19 <jjmcd> I doubt it
14:40:41 <jjmcd> But I might get lucky
14:41:06 <randomuser> heh
14:41:32 <randomuser> ok, we'll call that a group effort unless Capesteve doesn't want us hacking on his page
14:41:52 <jjmcd> I have a relatively unusual situation - not a lot of places to be in the next week or so, but a helluva to-do list
14:42:41 <randomuser> I think I have the opposite problem
14:42:50 <jjmcd> Usually I do, too
14:43:32 <jjmcd> Well, usually the to-do list AND places to be
14:43:53 * randomuser nods
14:44:06 <randomuser> Capesteve, any other updates for your guide?
14:44:17 <randomuser> were my potshot bug reports helpful?
14:45:15 <Capesteve> randomuser: yes thank you
14:45:39 <Capesteve> I'll ping you when the draft is published
14:45:45 <Capesteve> sp others can review too
14:45:54 <randomuser> I have a suspicion there were some changes with gnome remote auth stuff too
14:46:14 <randomuser> adding a user to an AD domain through the GUI
14:46:27 <Capesteve> I will make the wiki page, anyone can hack, keep it simple
14:47:56 <randomuser> okay, looking forward to it
14:48:09 <randomuser> #topic Outstanding BZ Tickets
14:48:17 <randomuser> #link http://tinyurl.com/lbrq84
14:48:25 <randomuser> we've got some bugs
14:49:41 <randomuser> #info all bugs should have docs-qa@lists.fp.o as QA contact, subscribe there to track
14:50:01 <randomuser> #topic Open Floor
14:50:43 <Capesteve> https://fedoraproject.org/wiki/Docs_Project_Review_Table << Please take a look
14:51:05 <randomuser> #link https://fedoraproject.org/wiki/Docs_Project_Review_Table
14:52:10 <randomuser> so, anyone making it to Flock?
14:53:51 <randomuser> probably a long way for most
14:53:52 <jhradilek> Capesteve: Can you move the instructions one level up?
14:55:16 <jhradilek> Capesteve: The instructions are quite universal, I don't think they need to be specifically for the System Administrator's Guide. Instead, we should probably add a link to the latest available version of the guide (Fedora 17) and to Bugzilla.
14:57:26 <Capesteve> Proof Reading Exercise for the Fedora 18 System Administrators Guide  >> Proof Reading Exercise for the Fedora 18 Guides ?
14:58:02 <Capesteve> how universal?
14:58:48 <randomuser> jhradilek, you're suggesting define the sections to be reviewed in each table row , and feedback in bugzilla ?
14:59:04 <randomuser> vs create rows with feedback as you generate it?
14:59:23 <Capesteve> I would prefer to keep it informal
15:00:10 <randomuser> maybe bugs reserved for patches or dialog
15:00:22 <randomuser> let's take this to #fedora-docs, our time is up
15:00:26 <Capesteve> anyway, meeting time is almost up, we can continue this in docs channel
15:00:32 <Capesteve> yes
15:00:34 * randomuser highfives Capesteve
15:00:38 <randomuser> #endmeeting