14:00:35 #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings 14:00:35 Meeting started Mon Mar 10 14:00:35 2014 UTC. The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:35 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:35 #meetingname Fedora Docs 14:00:35 The meeting name has been set to 'fedora_docs' 14:00:35 #topic Roll Call 14:00:49 * Sparks 14:01:12 * jjmcd 14:01:25 * pbokoc 14:01:46 * zoglesby 14:03:31 * jsmith 14:03:38 quiet today 14:04:01 * Sparks is still going through his email from over the weekend. 14:04:47 it would take me a while to get used to the idea of 'disconnecting' over the weekend 14:04:56 * lnovich is here 14:05:57 randomuser: It's easy. Just don't open *that* laptop 14:06:06 http://stream1.gifsoup.com/view4/1158287/tumbleweed-o.gif 14:06:19 randomuser: That's not to say that I wasn't tossing bits over the weekend, just not work-related emails. 14:06:28 hrmph 14:07:11 There's a "new Writers" section on the agenda, if there are such, speak up 14:07:16 * pkovar is late 14:07:36 until then, I'm moving past it to avoid pbokoc's tumbleweed assault 14:07:48 (do they even have tumbleweeds in CZ?) 14:07:58 not really :) 14:07:59 #topic Publican / Publishing 14:08:05 heh, i should mail you one 14:08:27 I have heard no news on the status of this project 14:08:43 Me neither. 14:09:01 AFAIK, the build system is up and operational but we're still waiting on the backend. 14:09:11 * jsmith hasn't heard anything either 14:09:13 nb might be able to update us more. 14:09:31 * Sparks has been trying to catch rudi in the evenings without any luck. 14:09:54 * randomuser waits hopefully for a response from nb 14:10:29 Sparks, i see you have some builds in el6-docs; that's progress 14:10:47 randomuser: Yeah, I need to go ahead and build the rest of my stuff there. 14:10:53 randomuser: And other people can too! 14:11:10 Sparks: are there instructions for that yet? 14:11:23 sounds like something I would break and not be able to fix 14:11:33 zoglesby: Ummm... sure. And I can write them down too. 14:12:04 randomuser: It's really quite easy. Two steps with no waiting. 14:12:18 #action Sparks to write preliminary howto for building docs in koji 14:12:29 #undo 14:12:29 Removing item from minutes: ACTION by randomuser at 14:12:18 : Sparks to write preliminary howto for building docs in koji 14:12:45 #action Sparks to add preliminary howto for building docs in koji to the documentation guide 14:12:49 ha! 14:13:33 randomuser: Okay 14:13:40 awesome 14:14:39 I have a suspicion that we can't get into the staging box, including nb to set up access, because we aren't rudi 14:15:27 randomuser: Well, you do need to be in the sysadmin group. 14:15:47 right, sysadmin-docs 14:15:55 Yeah, that one 14:16:11 that was the 'we' I referred to :) 14:16:14 I am in the group and still cant ssh into docs01.dev 14:16:55 we won't be able to fix it here, so 14:17:00 #topic Guide Status 14:17:33 * randomuser notes that the Networking Guide and Sysadmin Guide have been getting worked over, hard 14:19:06 I didn't have time to work on any guides last week 14:19:57 #info use a wishlist for your guide 14:20:18 I don't have anything to report again - working hard on RH docs 14:20:31 but when that's done, I'll port all of that into the Fedora guide, and it will be awesome 14:20:36 indeed 14:21:06 fat angels singing, clouds parting, water turning into wine, all that jazz 14:21:11 anyway, what about release notes? 14:21:18 aha! 14:21:20 do we have anything new other than changes to include there? 14:21:29 #topic Release Notes 14:21:51 pbokoc, we only included changes because that's all the research we took the time to do 14:22:11 ideally, there will always be more in the RNs than the Change list 14:22:36 randomuser, I know, we talked about it about two meetings ago. The problem is that it's really hard to scope bugs outside changes, since almost nobody uses the requires_release_note flag in Bugzilla. 14:23:11 right, we have to look at package changelogs, upstream changelogs, etc 14:23:19 *after* we decide what packages to look at 14:23:46 right. If we had a (short!) list of important packages, that could work 14:23:51 I may have missed this, but are we still only working on one set of release notes for the new release model? 14:23:55 https://git.fedorahosted.org/cgit/docs/tools.git/tree/tools/checkBeat 14:23:55 I plan to send mails to various groups asking for participation, but that hasn't worked out great in the last few releases 14:24:40 zoglesby, we haven't discussed an alternative, but most changes are generally global, and the more localized changes haven't been declared 14:24:58 The tech notes can expose new packages, checkBeats changes 14:25:16 But deciding what is "important" is a challenge 14:25:18 also, no WG or community member has requested any change to our product line 14:25:21 randomuser: So maybe we should just add a section for each "flavor" to the top of the release notes? 14:25:50 zoglesby, subset of each beat, or a dedicated beat per product? 14:25:50 I.e., what new with Desktop, server, and cloud 14:26:01 ah 14:26:08 randomuser: I have no idea, just talking at this point 14:26:30 Since ppl can install wahtever package onwhatever flavor, not sure that is worth the hassle 14:26:40 I am not even sure I have my head around this new model completely yet. 14:26:42 sheesh the typing this morning 14:26:45 that shouldn't be necessary - if the variants only differ in the default package selection 14:26:56 pbokoc, zakly 14:27:02 :) 14:27:05 pbokoc, they intend to also differ in default configurations 14:27:15 jjmcd pbokoc: okay 14:27:55 I like the idea of highlighting the flavors, but it seems like lots of work for little benefit 14:28:03 so far, the discussion I've seen is mostly *how* they will achieve that result, not how they would be different 14:28:43 hmm 14:28:44 randomuser: We may just have to wait and see how it plays out this cycle and adjust next time 14:28:58 good plan 14:29:19 well, they are supposed to be submitting Changes for every bullet point 14:29:38 so we should have a good picture of the products from that perspective 14:29:42 It seems to me that everyone has their own ideas of how this is going to work anyway. So why not just see what actually happens and adjust accordingly. 14:30:00 heh 14:30:53 proposal: table product representation in RNs until there's a specific strategy or event to discuss 14:31:13 +1 14:32:09 #link https://fedoraproject.org/wiki/Category:Documentation_beats?rd=Docs/Beats 14:32:18 #agreed 14:32:22 #info Start on beats now! 14:33:27 back to pbokoc's point - if the more experienced writers do things like list important packages for a beat - say, on the talk page - it would make it much easier for new beat writers to participate 14:34:27 that's all i've got for RNs now - zoglesby ? 14:34:50 I am good 14:35:04 for some reason it seemed appropriate to single you out :/ 14:35:15 #topic Docs FAD 14:35:18 randomuser: thanks 14:35:53 Sparks, any news on lodging? 14:36:49 ... or other FAD things? 14:37:28 randomuser: We have lodging. 14:37:37 ha, you're still here 14:37:38 * Sparks needs to update the wiki page and will do so today. 14:37:50 randomuser: Sorry, my VPN dropped out. 14:38:06 Sparks, since we're all confused about this products thing, do you know anyone in Raleigh that's involved that might like to visit with us? 14:38:20 I'm still waiting for a callback from the RDU person in charge of space. I've reserved meeting space but I'm not sure what I've reserved. 14:38:23 :) 14:38:31 I do not. 14:38:36 jreznik may attend in brno, for example 14:38:45 I mean, I guess I can talk to what I know. 14:39:04 * lbazan here 14:39:09 randomuser: I plan to do so 14:39:11 yeah, I'm hoping that you at least know who is involved :P 14:39:18 just I need reminder :) 14:41:18 okay, that was my one point on the FAD 14:54:25 Fr 13-18, Sa 08-20, Su 08-12 - How's that lnovich? 14:54:47 jjmcd: Who's timezone? 14:55:00 good point. 14:55:11 I guess we better all be on Z eh? 14:55:32 Of course, we'll all be screwed up after staying up to watch Albert Park the week before so ... 14:55:41 jhradilek and I had initially discussed a ~1400 or 1500UTC start time 14:57:01 I'm hesitant to block of a set number of hours for a given topic and try and force our actual work to fit into those blocks 14:57:39 randomuser: We should at least block out time... :) 14:57:43 bah 14:58:00 I'm guessing that some folks would work on publishing system while others working on guides 14:58:01 i think we're coming up against QA, everyone please join #fedora-docs to discuss this 14:58:06 i mean attempting to be somewhat professional about this would be good 14:58:20 lnovich, what? 14:58:50 the agenda jjmcd 14:58:50 lnovich, have you ever seen this crowd??? 14:58:59 heh 14:59:11 okay, shove over, people 14:59:14 #endmeeting