23:00:22 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 23:00:22 Meeting started Wed Jul 21 23:00:22 2010 UTC. The chair is Sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 23:00:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 23:00:22 #meetingname Fedora Docs 23:00:22 The meeting name has been set to 'fedora_docs' 23:00:22 #topic Roll Call 23:00:32 * Gearoid is here 23:00:39 * Sparks is here 23:01:59 * stickster 23:02:08 * crantila is here, barely 23:02:09 * bcotton is here 23:03:32 Okay, let's get started. 23:03:42 #topic Follow up on last week's action items 23:04:01 #action jjmcd to have doc-publican-rpm packaged and submitted for review by 21 July (overdue) 23:04:09 rudi_: rudi to come back with additional information on getting docs-writers building packages in koji for docs.fp.o 23:04:25 Yep -- real progress this week 23:04:35 excellent. go for it 23:05:01 So we now have a roadmap in place -- http://fedoraproject.org/wiki/Automating_publishing 23:05:09 with some specific goals. 23:05:21 The first one is to get Publican built for the infra repo 23:05:29 #link http://fedoraproject.org/wiki/Automating_publishing 23:05:47 And the immediate prerequisites for that are to get a number of deps built for EPEL 23:05:53 I'm working on that already 23:06:12 of the 8 deps, 3 are now built and about to go into testing 23:06:26 The maintainer of one of the others has also replied in the affirmative 23:06:50 excellent 23:06:54 sounds like you've been busy 23:07:06 Yeah :) 23:07:51 We can go into this some more in a bit. 23:08:02 #action Sparks Work on magazine article work about the guides and docs.fp.o 23:08:26 quaid: You around? 23:08:50 #action quaid to discuss on the list about Beacon and web-based XML editors for Docs use. 23:09:03 #topic Fedora 14 Schedule 23:09:42 Anyone have anything else on the F14 schedule? 23:10:34 Sparks: Dumb question, but did jjmcd get the changes he sought? 23:10:41 Not sure 23:11:09 * stickster not sure if there *were* specific changes left to seek 23:11:14 * stickster bows out for lack of info 23:11:27 #info Further changes to the schedule should be relayed to poelcat immediately. 23:11:36 concur 23:11:44 #action Publican 23:11:49 #undo 23:11:49 Removing item from minutes: 23:11:56 #topic Publican 23:12:27 So I hope I've summed up the state of play on that wiki page... 23:12:36 Does anybody have any questions? 23:12:51 Does that roadmap make sense to people? 23:13:04 Looks good to me 23:13:53 rudi_: Will this be done in time for F14? 23:14:04 I really, really hope so, for all our sakes :) 23:14:05 But... 23:14:22 EPEL has some strict rules 23:14:35 and packages need to spend at least two weeks in testing before going stable 23:14:55 So I really need to get those packagers involved 23:15:58 I've also volunteered to maintain the EPEL5 branch for any of those packages for any packager who doesn't want to head down the EPEL path 23:16:41 heh 23:17:10 Okay. Anything you need from me or anyone else? 23:17:39 Not unless anyone knows any of the maintainers on that list and can put in a good word for how important this is for Docs :) 23:18:25 A note to the list might be a good idea 23:18:39 Docs list? 23:18:41 Yeah 23:18:45 Will do 23:18:48 epel-devel-list@redhat.com 23:18:52 That too 23:18:53 That might also be useful 23:19:09 Thanks stickster :) 23:19:19 Anything else? 23:19:24 Not from me 23:19:29 #topic Release Notes 23:19:35 jjmcd isn't here tonight. 23:19:53 I think the beats are being reset this week, though. 23:20:25 #link http://poelstra.fedorapeople.org/schedules/f-14/f-14-docs-tasks.html 23:20:43 #action rudi_ to send a message to EPEL devel and docs discussing his EPEL packages need for Publican 23:22:19 #link https://fedoraproject.org/wiki/Docs/Beats 23:23:01 If anyone is interested in working on a beat sign up using that link above. 23:23:17 Questions? 23:24:06 #topic Guide Status 23:24:14 Which link? 23:24:23 Ah 23:24:25 * stickster lost it 23:24:36 stickster: And now you have me questioning myself. 23:24:38 :) 23:25:12 All quiet at the moment, as far as I can see 23:25:33 Anyone have any questions or comments? 23:25:48 * stickster thinks things will probably heat up after the Alpha is RC 23:25:54 Yes 23:25:59 At least... I hope they will! 23:26:00 Yeah; this is the calm before the storm :) 23:26:11 okay, I'll bite 23:26:37 if you're looking for something to do, please help proof-read the Musicians' Guide! One chapter or one section is enough to help 23:27:07 comments from previous proof-readers are surrounded !! like this !! in exclamation marks, so it's things that are already going to be fixed 23:27:09 crantila: Is that in fedorahosted? 23:27:18 links forthcoming 23:27:39 all drafts available here: https://fedoraproject.org/wiki/User:Crantila/FSC/Drafts 23:27:49 #link https://fedoraproject.org/wiki/User:Crantila/FSC/Drafts 23:27:57 two focus areas are Qtractor, here; https://fedoraproject.org/wiki/User:Crantila/FSC/Sequencers/Qtractor 23:28:08 and Audacity, here: https://fedoraproject.org/wiki/User:Crantila/FSC/Recording/Audacity 23:28:18 Looks like you've been busy. 23:28:38 the Guide should be moving into fedorahosted gradually within the next few weeks 23:28:46 crantila -- how are we tracking now towards the end of the week? 23:29:31 the SuperCollider mini-textbook is at about 2000+ lines currently, and I'm three-quarters done 23:29:45 Still think that Sunday is attainable? 23:29:48 that puts completion all drafts by Saturday 23:29:57 Awesome :D 23:29:58 two days should be enough 23:30:36 so... Audacity and Qtractor are popular programs, and I'm appreciate special attention for those chapters 23:30:49 I would appreciate** 23:30:51 So folks; that's the point at which there should be a complete first draft... 23:31:00 thanks! 23:31:07 So proofreading, comments and feedback are needed *now* :) 23:31:29 and I'm willing to entertain almost anything 23:32:55 I am willing to help with those since I'm new 23:33:08 thank you for volunteering; just pick a section, and go 23:33:11 (I'm new, too) 23:34:06 Okay, anyone else? 23:34:27 * bcotton has made progress on teh printing chapter for the UG 23:34:49 I hope to have a first draft finished and available before I leave for a vacation on Friday afternoon 23:34:58 excellent 23:35:21 * Gearoid will finally get working on the accessibility guide this week 23:35:48 as a result of working on the printing chapter (plus also applying to grad school and lots of "fun" projects at work and being lazy), the RPM guide hasn't moved forward very much. if anyone wants to pitch in, see https://fedoraproject.org/wiki/User:Bcotton/RPM_Guide_tasks 23:35:51 I should remind people to strike out items that they complete on the F14 Goals page: 23:35:54 #link https://fedoraproject.org/wiki/Docs_Project_guide_goals_for_F14 23:36:38 Anyone else? 23:37:05 #topic Outstanding BZ Tickets 23:37:16 #link http://tinyurl.com/lbrq84 23:37:34 #info 97 open tickets 23:38:00 #info 28 new tickets 23:38:30 Has everyone read the procedures for working with documentation bugs? 23:38:33 #link #link https://fedoraproject.org/wiki/Handling_Docs_Project_bugs 23:38:39 #undo 23:38:39 Removing item from minutes: 23:38:43 #link https://fedoraproject.org/wiki/Handling_Docs_Project_bugs 23:39:59 Anyone have any comments or questions about the procedure? 23:40:32 it's not clear to me how the QA person fits into this 23:40:59 it sounds like the QA person is only invovled after a bug has been patched, and before the reporter is notified 23:41:33 which seems a bit...unneeded in that case? it seems saner to me that the ticket would be marked VERIFIED *Before* a patch is committed. EOF 23:41:34 bcotton: The patch needs to be verified by a QA person 23:42:25 Yes, in theory a patch shouldn't be committed until it has been verified 23:44:19 bcotton: I guess the process didn't really talk about committing to the repo 23:44:21 From my perspective, it seems like the ticket statii aren't intuitively labelled and/or the steps are slightly out of order, but my perspective has been known to be a bit....suboptimal before 23:45:20 Well, I'm open to suggestions. 23:45:23 and it is a wiki! 23:45:55 sparks: now that i re-read it, it does say attach the patch to the bug, so that makes more sense as written, but i'm thinking that the people most likely to actually submit a patch probably already have repo access, so they'd just commit the patch directly? 23:47:00 In a perfect world the commit would occur after the QA 23:47:13 i've got no specific suggestions at the moment, and this certainly beats having no procedure, so i'm content to give it a +1 and then make some edits later if i have real ideas 23:47:27 Okay 23:47:29 anyone else? 23:47:38 i think it's a good start, we might just want to flesh it out more at some point 23:47:43 * bcotton is done for real now 23:48:29 #topic Open floor discussion 23:48:35 Okay, anyone have anything else? 23:49:28 Anyone? 23:49:30 Anything? 23:50:09 Okay, thanks everyone for coming out today! 23:50:24 #endmeeting