14:00:51 #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings 14:00:51 Meeting started Mon Mar 3 14:00:51 2014 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:51 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:51 #meetingname Fedora Docs 14:00:51 #topic Roll Call 14:00:51 The meeting name has been set to 'fedora_docs' 14:02:01 * roshi is here 14:03:02 I am Mohan Prakash to participate in Fedora docs meeting, how do I answer to the roll call 14:03:53 mpduty, just like you did :) 14:03:58 Typically just say you're here :) 14:04:19 ok 14:04:28 morning, roshi 14:05:00 Morning 14:05:22 * jjmcd 14:06:01 * pkovar 14:06:08 * jhradilek <-- 14:08:02 #topic New Writers 14:08:17 any new writers here to check in? 14:08:42 yes, I want to contribute 14:09:00 mpduty, great! where are you in the process? 14:09:36 Perhaps a wiki page is needed on burning ISO, I thought I could do that 14:09:56 well, we do have a Guide dedicated to that topic 14:10:08 ...and multiple wiki pages 14:10:39 ok 14:11:29 mpduty, have you read the docs onboarding wiki pages, starting at https://fedoraproject.org/wiki/Docs_Project?rd=DocsProject ? 14:12:04 ha, i found your intro email 14:12:12 * randomuser sips coffee 14:13:16 mpduty, why don't you pull readme-burning-isos and take a look; if you see room for improvement, attach a patch to a bug report 14:13:44 mpduty_, I can give you links and and guidance in #fedora-docs after the meeting 14:14:04 sure, that will be a good help 14:14:13 any other new writers? 14:15:35 okay, let's move on to FAD then 14:15:52 #link https://fedoraproject.org/wiki/Docs_FAD_2014 14:16:33 one of the things I'd like to deal with at the FAD is to figure out what we should do to represent the multi-product Fedora 14:16:47 ...and then figure out what we *can* do 14:17:32 it occurred to me that there might be product stakeholders in both Brno and Raleigh 14:17:43 Sparks, you might know better 14:18:37 ... 14:18:42 * lnovich is here 14:19:03 anyway, sitting down with such people at a prearranged time might be a good idea 14:19:31 true 14:20:07 what sort of people / information would be beneficial? 14:20:46 people that would want to participate in a discussion about how fedora docs will represent the multiple Fedora products 14:20:50 WG expectations, etc 14:21:54 It should be discussed on lists too, just pointing out the opportunity for a face-to-face 14:22:04 * Sparks is here 14:22:12 i think we could ask eg jreznik to join us for that discussion 14:22:16 as he is based in brno 14:22:39 yeah, jreznik ++ 14:23:27 * jreznik is here 14:23:33 re-reading backlog 14:24:10 jreznik, we're getting together 21MAR - 23MAR 14:24:18 there's probably pizza in it for you 14:24:46 free pizza? I'm in! 14:25:14 gee if it works that easily can we get more folks in Brno on board? 14:25:21 jreznik: Sign up here: https://fedoraproject.org/wiki/Docs_FAD_2014#Brno 14:25:23 it's a good idea to have a bridge 14:26:11 * randomuser notes we probably don't have a lot more funding for broad invitations 14:26:22 but hey, if people are just down the hall, let's talk to them 14:26:52 yep 14:27:08 jhradilek: signed up 14:27:17 thanks for heads up 14:27:28 good :-) 14:27:36 there are lots of people just down the hall 14:27:47 lnovich: hundreds! 14:28:33 Sounds like Sparks needs to up the pizza budget 14:29:30 otherwise, we all know when the FAD is and why, right? 14:29:44 and everyone knows how they're getting there? 14:29:48 we don't know what 14:30:39 ! 14:31:55 well, there's a rough outline on the wiki page 14:32:09 Meaning - we need to have a better looking agenda 14:32:33 pkovar: Zimbra invitation would help me a lot not to forget :) 14:33:27 does anyone want a tutorial on anything in particular? I am willing to run a session 14:34:23 lnovich, what's on the menu? 14:35:14 tell me topics that tutorials are wanted for and I can tell you if I can prepare something in time 14:36:21 * jreznik would like to see a bit more general one with workflows, what's needed for release etc. - he is aware of it but more details would help and it could be recorded and published for any other newcomers 14:37:04 jreznik, part of our agenda is to refresh the contributor docs 14:37:23 it would be good to have an elaboration of what that means in advance, though 14:38:14 ahem, let's move on to Guides 14:38:21 #topic Guide status 14:38:38 Capesteve, looks like the Networking Guide is coming together 14:38:56 ( and needs a bz component ) 14:38:57 pkovar published that for us 14:39:26 pkovar will publish SysAdmin Guide soon 14:40:09 I'm hoping to have my guide ready by FAD 14:41:18 that 14:41:21 hrm 14:41:31 lnovich, that's great, looking forward to it 14:42:05 anything else on Guides? 14:42:35 * roshi has nothing 14:43:04 #topic Outstanding BZ Tickets 14:43:13 #link http://tinyurl.com/lbrq84 14:43:38 please take a moment to glance over out bugs, and point out any that should be discussed 14:44:06 Is this Bug-Zappers? 14:44:24 Cydrobolt, this is docs - QA is later today, bugzappers is EOL 14:44:40 Okay, ty 14:46:11 oh, before I forget, RN Beat pages are cleared and ready for input 14:46:32 https://fedoraproject.org/wiki/Category:Documentation_beats?rd=Docs/Beats 14:46:54 i'll tackle the assignment table next 14:47:05 #info beats pages are ready for contributino 14:47:21 Good grief it is that time again? 14:47:25 ...already? 14:47:33 guess so sparks 14:48:07 I'm hoping it won't be so painful if we start early 14:49:39 #topic release notes 14:49:44 why not 14:50:19 So, I'm going to start this cycle by outlining areas that should be researched for a given beat in the beat's Talk: page 14:50:47 packages to check, projects to catch up on, people to talk to, etc 14:50:58 ok 14:51:26 hopefully that will make it easier for others to step in and follow up on the outline, instead of handing them a category and instructions to "figure it out" :) 14:52:19 #info use Talk: pages to outline beats todo 14:52:45 randomuser: Are you going to start contacting the previous beat writers? 14:52:53 Does everyone here know how to write a beat? 14:53:15 I don't 14:53:18 Sparks, yeah, and send out lots of mails to lists asking for participation 14:53:42 mpduty would you like to write one? 14:53:53 randomuser: Okay, I'll probably help John with the Amateur Radio stuff and wouldn't mind trying my hand at documenting the new SELinux stuff. 14:54:17 I can take the libvirt/virt stuff 14:54:22 awesome 14:54:26 I don't have much idea how to write a beat, but I can write 14:54:27 Do we have any AR changes? Seems to have been quiet lately 14:54:46 Sparks, i was hoping you could take the cert stuff too - that all confuses my pants off 14:55:34 randomuser: Yeah, I can do that. I've already wrote some of it up for the Security Guide 14:55:57 mpduty I can help you offline when you're ready 14:56:03 the SELinux stuff really needs some work 14:56:18 jjmcd: Yeah, no big changes but I figured we could mention some of the recent upgrades. CQRLOG has had a pretty big feature bump recently. 14:56:38 Inovich, ok I shall participate 14:56:45 we could probably throw 100s of man hours into updating guides with info from dan walsh's blog 14:57:26 randomuser: Agreed 14:57:54 ..and probably should 14:58:30 just a few minutes left, if you were saving anything, now's the time 14:58:43 pick a title you're interested in mpduty - easier topics are those with a developer attached 14:59:36 #action randomuser to mail writer and developer contacts for beats to ask for participation 14:59:54 Inovich, I have to browse through the topics, could you guide me, like give me some links? 15:00:25 mpduty, to some extent, finding the things to read is part of the work that needs to be done 15:00:59 #action Sparks to review the ARG for completeness 15:01:00 OK 15:01:24 mpduty, but we can talk in #fedora-docs 15:01:37 thanks for coming, everyone 15:01:43 #endmeeting