14:00:22 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 14:00:22 Meeting started Mon Dec 5 14:00:22 2011 UTC. The chair is suehle. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:27 #meeting name Fedora Docs 14:00:33 #meetingname Fedora Docs 14:00:33 The meeting name has been set to 'fedora_docs' 14:00:52 #topic Roll Call 14:01:09 * jjmcd 14:01:25 * randomuser percolates 14:01:38 Oh good, randomuser's making coffee ;) 14:01:55 One of you know how to do the PingLists? Because I think I failed. 14:02:50 * sgordon 14:04:18 #topic Action items 14:04:35 There's been some changes in that, but I haven't been paying that close attention 14:04:48 The bug squashing party appears to be rolling along, so check. 14:05:07 fnadge to start a Style Guide book -- any info on that? 14:06:02 I can see this is going to be a lively and short meeting. :) 14:06:07 #topic FUDCon Blacksburg 14:06:09 Not all bad 14:06:32 Well, Sparks and bcotton have most of the items on the agenda, and they're the two who aren't here. 14:06:56 * jjmcd and jsmith-away have a pres, no gnus on that 14:07:03 We've got the two classes going 14:07:06 yup 14:07:57 #Docs QA 14:07:57 huh Fudcon? 14:08:14 Southern_Gentlm: Could you expound on the question? 14:08:27 suehle, whats the question 14:08:46 Southern_Gentlem: I don't know, you said "huh Fudcon?" Do you have a question? 14:08:56 * randomuser passes a cop of coffee to Southern_Gentlem 14:09:07 Southern_Gentlem generally has the answers 14:09:08 no i pop up if someone else has a question about Fudcon 14:09:26 Oh, OK. :) Just didn't want to pass any questions by! 14:09:35 i am still trying to work out if i can get there 14:09:40 flights looking expensive 14:10:04 sort of a damp drive for you 14:10:07 suehle, i have a highlighter on the word FUDCon 14:10:10 sgordon: I suspect it's not an easy place to fly to. But if you can get to Raleigh, we're working on a vanpool, but so far it's a very small one. Like... me. 14:10:24 yeah i am in toronto 14:10:30 so the problem is it's 2 hops 14:10:34 gets expensive quick 14:10:35 Southern_Gentlem: Sorry, it's my first round running a meeting. I'm on slow. 14:11:08 So, Docs QA is another Sparks one. 14:11:09 #link https://fedoraproject.org/wiki/Docs_QA_Procedure 14:11:19 Agenda notes "Please comment. We will come up with a procedure after the Bug Squashing Party" 14:11:42 #topic Guide Status 14:12:04 i dont think we got to guide status last week, but the musicians guide did eventually go up 14:12:08 Tech Notes en-US and ja-JP published 14:12:16 high fives all around 14:12:19 i think there was another email question about german translations though? 14:12:21 but translation is weird on that one, looking for rudi 14:12:30 rudi has spawned an underling 14:12:35 so he has been off work for a week or so 14:12:44 That seems to be going around. 14:12:55 yes, I knew that was coming, so not a surprise 14:13:05 but he did some magic last time 14:13:46 Protb with TNs is that 90%+ of the strings don't need to be translated, he did something to reduce the noise for L10N but I don't know what it was 14:15:35 Is that about it on guides? 14:16:28 * fnadge here 14:16:45 * pkovar here 14:16:52 well i did still have the open question on the german translations 14:17:16 did we get bugzilla components set up to track the new process for pushing these? 14:17:40 I am unfortunately short on answers about that. 14:18:03 I suspect not 14:18:09 i am happy to assist and push some of them but there seem to be a number so it might be worth getting bugs raised and splitting it up if we can 14:18:20 there have been a number of postings on the l10n list about pushing translations 14:18:40 and some translators have been doing a fair bit of pushing themselves 14:18:47 yeah i am only on fedora-docs so i only got the crossposts 14:19:34 re the new translations publishing process 14:19:44 the new component has been set up 14:20:17 did we get the notification thing squared away? 14:20:18 and also the default assignee is now set to the docs-publishers FAS group, meaning everything should work 14:20:41 cool beans 14:20:44 translators only need to file a bug against the right component 14:20:59 so i will ask the german translator to do that 14:21:29 then we need to get as many trans people as possible to the FAS group so that they can help out with thw publishing process 14:23:04 of course, as i said before, this is not related to teams doing their publishing 14:24:05 so if anybody of you docs-publishers is interested in helping with publishing, please go ahead 14:26:08 also please note that now you will probably receive some publish request in your inbox unless you have set up your email to filter out such messages 14:26:28 * publish requests from time to time 14:27:10 so any comments, thoughts on that? 14:27:23 everybody agrees? :-) 14:27:33 no problems that i can see for now 14:27:37 Sounds good to me 14:27:50 great, thanks 14:28:13 Excellent 14:28:21 #Bug Squashing Party 14:28:26 #link http://tinyurl.com/lbrq84 14:28:38 scheduled for December 15 at 2 p.m. EST (1900 UTC) 14:29:09 suehle, should be a #topic Bug Squashing Party 14:29:14 Doh. 14:29:22 randomuser never gave me coffee :) 14:29:28 #topic Bug Squashing Party 14:29:34 It said #topic in my head! 14:29:38 * randomuser scrambles to pour a cup 14:29:43 #link http://tinyurl.com/lbrq84 14:29:49 and still scheduled for December 15 at 2 p.m. EST (1900 UTC) 14:30:36 Any outstanding BZ tickets we need to discuss? 14:34:19 #topic Open floor 14:34:31 * jjmcd has a couple of FYIs 14:34:49 Release notes bugs swatted, 16.3 published on docs.fp.o 14:35:06 Still 4 langs that were in the original RPM not 100% translated 14:35:32 so when Spanish, French, Italian and Russian reach 100% I'll make a new RPM 14:35:43 Including any other langs that get to 100% by then 14:36:07 I do have a question, tho 14:36:34 With lotsa folks publishing it gets a little tough to see what is already published 14:36:47 Mostly langs with non-Latin charsets are a problem 14:36:51 any hints? 14:38:23 jjmcd: since this will be tracked in bugzilla, i think that's not a problem 14:38:47 Well, I suspect when a translator publishes their own they won't file a bug 14:38:53 you can easily see the open requests by displaying the right component 14:39:12 jjmcd: then we don't need to care, i guess .-) 14:39:15 or do we? 14:39:31 Oh, OK. So we can rely on L10n to advise what needs to be published - yeah, that will work 14:40:08 I have a tough time distinguishing Assamese from Bengali, for example, so BZ will help a bunch 14:40:11 they always know better i think 14:44:03 Does that about wrap it up? Any more FYIs jjmcd? 14:44:12 I think that's it 14:44:29 Awesome. One day when I competently hold a meeting, you can all point back to this day and laugh at me. :) 14:44:43 #endmeeting