14:19:52 #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings 14:19:52 Meeting started Mon Mar 14 14:19:52 2016 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:19:52 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:19:52 The meeting name has been set to 'docs_project_meeting_-_agenda:_https://fedoraproject.org/wiki/docs_project_meetings' 14:19:52 #meetingname Fedora Docs 14:19:52 The meeting name has been set to 'fedora_docs' 14:19:52 #topic Roll Call 14:19:57 * Capesteve waves 14:19:58 * pbokoc 14:22:03 .hello bex 14:22:03 bexelbie: bex 'Brian (bex) Exelbierd' 14:22:15 well, zoglesby is in here somewhere, so we must be good to go! 14:22:25 #topic F24 Schedule review 14:22:44 I'll try to move through this quickly since we're starting late 14:22:53 #link https://fedorapeople.org/groups/schedule/f-24/f-24-docs-tasks.html 14:23:04 last weeks tasks include: 14:23:14 - recruit former beat writers 14:23:28 - begin alpha release notes 14:23:44 - send mail to devel-announce about release notes 14:24:10 these all still need action. 14:24:28 This week's tasks include: 14:24:35 - release readiness meeting 14:24:46 - alpha release announcement 14:25:11 - continued development of release notes 14:25:26 .hello corey84 14:25:27 linuxmodder: corey84 'Corey Sheldon' 14:25:30 these tasks also need action 14:25:35 who wants to play along? 14:25:49 * linuxmodder reading back 14:26:11 damnit, I was supposed to draft the devel-announce mail 14:26:36 I can tackle the devel-announce and tag team with someone on the alpha release notes this week 14:27:21 seeing as I'll be neck deep on devel and devel-announce for gsoc I don't mind 14:27:37 linuxmodder, you're familiar enough with our workflow and expectations from devel to explain to them how to get things into RNs and such? 14:28:18 I helped with last cycles branched RNs and I'm not afraid to ask if i get stuck 14:28:48 okay, cool. Ping pbokoc or I when you have a draft ready for review. 14:29:02 noted 14:29:54 ideally we'd like people to contribute to beats pages on their own, with their own changes, leaving their contact info (mail) in case we have more questions 14:30:58 yes, that would be an ideal way to do a publicly cooperative draft 14:31:04 e.g. if someone makes an update to doge.noarch and feels that it's important enough to feature in the RNs, they find the correct beat (Entertainment?), leaves a note about what the change is and mail 14:31:09 pbokoc, why wouldn't beats authors do so on their own? 14:31:10 everyone should put what they know into the page 14:31:25 linuxmodder, what beat authors? 14:31:55 linuxmodder, beats authors are us writers. The point is to get *developers* to provide info on their own - until now it's almost always been us chasing them (and them mostly ignoring us) 14:32:15 randomuser, re: pbokoc 's last comment about contributing on their own and leaving their mailing info ( email) 14:32:40 pbokoc, so more cross authoring ? 14:32:41 the beat writers have to get their info from somewhere; if you maintain a package, you should be aware of significant changes in your package; alternatively, as a developer, you can rely on me as a writer to know about every possible change in the platform and identify Your change as significant 14:33:05 one of these things requires one of the parties to do much more work 14:36:34 ahem 14:36:49 so, we're all WIP on an announcement mail drafting 14:37:20 we should all tackle solidified Changes too 14:37:39 and personally recruit writers and SMEs 14:38:59 Does anyone want to reset the beats table? 14:39:34 speaking of recruiting writers, last week someone introduced himself on the list and nobody talked to him, at least not there :) 14:39:42 randomuser, I guess I can do it 14:39:46 the table thing I mean 14:40:19 oh crap! pbokoc, I did send Stephen a "sorry I haven't had time for you" mail out of band 14:40:54 randomuser, I'm talking about Ryan Mason - on 03/05 14:41:17 well, double expletive, then - I missed that one completely 14:42:22 everyone should say hello to Ryan! 14:44:25 hmm.. bexelbie, still here? 14:44:52 #action randomuser to send beat recruiting mails 14:44:55 yes 14:45:14 you know this meeting is important - I am delaying a system reboot for it :) 14:45:18 heh 14:45:25 you 14:45:34 * randomuser bmashmashab sh 14:45:44 bexelbie, you've been quiet today, any thoughts? 14:46:01 just wanted to mention that I am going to submit two "workshops" to Flock this year 14:46:08 I hope that everyone will help on these :) 14:46:08 time changes are confusing 14:46:16 1) Hack fest on infrastructure - not writing 14:46:34 2) Discussion about what we want out of Fedora docs - what is causing people to use/not use our docs and how to get more of the good stuff? 14:46:45 not a discussion of formats, etc. But what actually drives you to use or not use them 14:46:54 i.e. do you always hit Arch .. or what 14:46:56 tool work and strategy, I approve 14:47:30 I still have a half-baked infra plan using static generators that i would like to complete as a head-to-head versus what you're building 14:47:40 bexelbie, loop me in on flock 'workshops' I'd be game 14:48:11 linuxmodder, absolutely - I was going to submit them as being from the project, barring objections 14:48:38 none form me but I'm still rather `green` on the team 14:48:46 bexelbie, please compete! maybe two half baked ideas will add up to... a still not fully baked idea? 14:48:54 but closer? 14:49:12 but I like soft-bake cookies 14:49:29 soft-baked cookies != workshops tho :) 14:49:31 bexelbie: care to share? I was working on a pitch for summer of code for randomuser tool, but maybe we can all work on something together 14:49:48 oh yeah, I was going to talk to decause about that 14:50:01 randomuser, which of your many tools ? 14:50:06 zoglesby, sure - happy to share 14:50:07 https://fedoraproject.org/wiki/Summer_coding_ideas_for_2016#Anerist 14:50:12 now or in a sep meeting? 14:50:44 heck, it is short 14:50:50 randomuser: we are almost out of time, students have already started put in requests 14:50:58 * randomuser nods 14:51:22 but jump in #fedora-summer-coding and start talking 14:51:22 several for hubs and web application 14:51:29 the theory is to use something like Middleman or Jekyll to convert our docs in one-shot. We should support markdown, asciidoc and docbook (possibly via translation to asciidoc). We should support single doc builds and full builds. We will have multiple repos for org 14:51:34 that is the short version 14:51:36 I dont care about any of the linuxmodder :P 14:51:44 zoglesby, I'll work on fleshing it out. I've been hesitant to suggest I could afford the mentoring time commitment; it seems open-ended to me 14:51:53 I will do that part 14:51:56 but if you're on board, I'll help make it happen 14:52:00 I just need some technical help from your brain 14:52:21 and if we work with bexelbie even better 14:52:26 okay, let's sync up on it 14:52:58 +1 14:53:16 I'll put some details into the idea page, at least 14:53:20 thanks! 14:56:10 #topic Open Floor 14:56:29 still a few minutes to take some action items! 14:56:45 Ryan's e-mail bounces back, but e might see my e-mail in the list. 14:57:10 that was regarding the "Intro" e-mail 14:57:20 I remember that email from last week (Ryan's) 14:57:29 #action randomuser to update google summer of code pitch 14:57:31 :P 14:57:37 thanks :) 14:59:18 I am not a chair 14:59:20 Okay, see you around, everyone. Thanks for coming, and apologies for starting late. 14:59:28 #chair zoglesby 14:59:28 Current chairs: randomuser zoglesby 14:59:33 #action randomuser to update google summer of code pitch 14:59:37 feel free to start without me 14:59:41 in the future 14:59:54 zoglesby, I don't think actions need chairing, but you're welcome to it anyway :P 14:59:59 #endmeeting