23:05:04 #startmeeting Fedora Docs 23:05:04 Meeting started Wed Mar 31 23:05:04 2010 UTC. The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot. 23:05:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 23:05:16 #meetingname Fedora Docs 23:05:16 The meeting name has been set to 'fedora_docs' 23:05:19 #topic Roll call 23:05:22 * stickster 23:05:24 * jjmcd 23:05:30 * laubersm . 23:05:40 * Emad78 is here 23:05:59 * ke4qqq is here 23:06:18 * rudi is here 23:06:25 * stickster apologizes for the late start. Composing can be dangerous! 23:06:40 Thanks for taking the meeting, Paul 23:06:59 #link https://fedoraproject.org/wiki/Docs_Project_meetings#Wednesday_March_31.2C_2010 <-- Agenda 23:07:11 Thankfully there's some fluff built into the time this week :-) 23:07:15 Hi everyone! 23:07:21 #topic Follow up on last week's action items 23:07:33 #link http://meetbot.fedoraproject.org/fedora-meeting/2010-03-24/fedora-meeting.2010-03-24-23.00.html <-- last week's meeting notes 23:08:02 There were only two action items listed in last week's meeting notes. I'm not sure whether that was the *real* total or whether we were under-using the #action link 23:08:28 jjmcd: You were on the hook for Beta relnotes actions, and I think we actually managed to pull off everything needed there, right? 23:08:32 Release notes RPM, thanks to help from Paul and Jesse, is on the way 23:08:42 Yes, I hope maybe it will appear in tonight's compose 23:08:57 #info Beta fedora-release-notes RPM is in the RC2 (second release candidate) for F13 Beta which stickster just tried 23:08:59 I saw it in updates testing today 23:09:07 ahhh, cool 23:09:07 not long ago I did a yum update 23:09:13 it installed 23:09:18 Yup, so awesome job there everyone. 23:09:19 I didn't realize it was the first 23:09:30 I think we still have a lurking problem but we'll get to that in a sec 23:09:34 I did see some strange behavior with arora, working with arora maintainer 23:09:48 Is nathant around tonight? 23:10:09 He was #action'd to take over the Live Images guide 23:10:15 Last week he got wor maybe bright enough to stay away 23:10:16 I think we can save that for guide status in a few minutes. 23:10:36 He is on the list and also git 23:10:59 jjmcd: wor? I'm not parsing the last bit properly maybe 23:11:23 His name is on the agenda page as owning it, and he joined the commit group for the doc 23:11:59 stickster: s/wor/work/ 23:12:01 Agenda page includes table of guide owners 23:12:02 oh! 23:12:03 duh. 23:12:27 It was the "bright enough to stay away" I wasn't grokking :-) 23:12:32 ahhhhh 23:12:45 #link http://git.fedorahosted.org/git/docs/readme-live-images.git?p=docs/readme-live-image.git;a=summary 23:13:06 I see some commits in the last week, which is great 23:13:14 OK, so that looks in hand, then. 23:13:26 #topic Release Notes 23:13:44 #info Beta relnotes in F13 Beta -- yay! 23:13:55 Portuguese went to 100% and Chinese and Russian are closing fast 23:14:00 Nice work to everyone, esp. jjmcd, rudi, and our AWESOME translators 23:14:24 Was great to see help from nathant, Emad78 and other new contributors 23:14:51 nathant, Emad78: You guys did great. 23:14:54 https://translate.fedoraproject.org/projects/p/docs-release-notes/c/f13/ 23:15:20 I am doing a nightly build to fedorapeople.org/groups, could add POTs but I want to check with rudi about how L10N gets those 23:15:25 There's our translation statistics -- 6 languages at 100%, and five more are close to 1/2 done or better 23:15:35 Yeah, they are doing amazing 23:15:38 jjmcd: Yes, I have two things I want to talk about specifically wrt. L10n 23:15:50 1. POT/PO building on a regular basis 23:16:06 2. Technical issues with the *display* of L10n'd notes 23:16:24 #topic Release Notes - POT/PO building 23:16:46 rudi: jjmcd: Are the POT files being regularly regenerated now that we have a release notes in the Beta? 23:16:55 Not yet 23:16:56 stickster -- we haven't yet 23:17:03 * stickster asks better question 23:17:06 Do we *want* to do that? 23:17:13 Yes 23:17:14 That was the plan 23:17:14 I would think that translators will want changes as soon as they come in 23:17:22 I would be happy to do that 23:17:33 Yep; there haven't been any changes yet, is all :) 23:17:39 but I was reluctant until I understood I wasn't going to mess up L10N 23:17:40 * stickster made one today :-) 23:17:47 which triggered my wanting to talk about it :-D 23:17:50 I have a few queued 23:17:54 I was careful to add elements, not change them. 23:17:54 OK -- I didn't see that come in. 23:18:15 #info As changes are made, we want to make sure we change as few strings as possible, zero would be great if we can manage it 23:18:38 rudi, do I want to simply add update-pot and push to my job, or do we need to be more selective? 23:19:12 One sec -- let me look at stickster's revision :) 23:19:30 * stickster thinks we'd want to regenerate the POT, and also regenerate all PO files, and then push 23:19:45 Are we all aware that RN's and all guide drafts should go to fedorapeople.org/groups/docs/ 23:19:46 Otherwise, if you think about it, the translation statistics will be wrong 23:19:59 Ah -- *don't* use &PRODUCT; when you mean "Fedora" :) 23:20:04 rudi: Oh! 23:20:05 Thanks 23:20:59 #info Helpful Tip #1: When auto-generating drafts of release notes and guides, put them in fedorapeople.org/groups/docs/ shared area 23:21:29 NP -- &PRODUCT; is the Bugzilla product, ie "Fedora Documentation"; it also breaks the grammar of some languages that need to change the final "a" in Fedora sometimes. 23:21:31 #info Helpful Tip #2: When making a change, don't use &PRODUCT; entity when you mean "Fedora" -- just use "Fedora" 23:21:40 rudi: Makes perfect sense, sorry about that 23:21:54 rudi: I'll take the action of correcting it :-) since I done broke it 23:22:09 #action stickster Fix commit that uses &PRODUCT; erroneously in relnotes Desktop.xml file 23:22:15 So we need to agree how often to regenerate the POT and PO files 23:22:39 rudi: jjmcd Is daily too often? 23:22:43 I think it might be frustrating for translators if we did that too often (and risk collisions) 23:23:03 Daily would be the upper limit, I think 23:23:12 So maybe something like every 3 days 23:23:25 yeah; I was thinking twice a week might be better 23:23:28 Or simply, "Monday/Thursday" 23:23:32 yeah 23:23:37 jjmcd: Can you set up the cron job appropriately? 23:23:42 NP 23:24:00 cron is my friend 23:24:07 #action jjmcd Set up cron job to rebuild and push regenerated POT + PO every Monday + Thursday 23:24:18 rudi: Will you notify the trans@ list we're doing that? 23:24:23 Yep 23:24:26 awesome! 23:24:40 #action rudi Notify trans@lists.fp.o about our clever scheme on pushing POT + PO 23:25:36 rudi: jjmcd: Seems like the *last* day we would want to do that is... 23:25:37 rudi, if L10N would like something different we should accomodate 23:25:42 * stickster checks schedule 23:25:51 Oh yeah, for sure 23:25:53 2010-04-19 23:25:57 I'll present it as a suggestion 23:26:05 yep, my calendar says that too 23:26:07 That last push would be a week before we collect the PO for the final RPM 23:26:10 Make sense? 23:26:29 #agreed Docs team suggests that last push would therefore be Monday 2010-04-19 as the schedule indicates 23:26:36 #undo 23:26:37 Removing item from minutes: 23:26:45 Oops, I didn't mean to send that until everyone agreed! :-) 23:26:49 #link http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-tasks.html 23:27:12 * laubersm agrees (without calendar handy) - 1 week prior to rpm sounds reasonable 23:27:42 Hopefully if we're being attentive about content changes -- watching wiki, putting content in as soon as possible -- it shouldn't be much of a chore for translators 23:27:54 In essence, they now have ~1 month to finish translations, with minor changes ongoing 23:28:06 rudi: jjmcd: +1? 23:28:12 +1 23:28:20 +1 23:28:27 OK, then... :-) 23:28:29 #agreed Docs team suggests that last push would therefore be Monday 2010-04-19 as the schedule indicates 23:28:34 Now it's really agreed :-) 23:28:40 So that brings me to part 2 23:28:51 #topic Release Notes - I18n/L10n problem displaying relnotes 23:28:53 This is trickier 23:29:16 Last I've seen, when someone in another locale calls up the release notes, they only see them in English, despite the fact that we have multiple languages shipping. 23:29:29 * Emad78 will be back in a sec. 23:29:33 Is this based on something like the browser setting where I'm simply not triggering it properly? 23:29:54 I tested the languages that are complete and they work on f13 beta, except for weirdness with arora 23:30:11 I also did some limited testing on KDE 23:30:21 not on the other desktops tho 23:30:32 * stickster pulls fresh copy 23:30:49 There was an issue initially, now I have to noodle what it was 23:30:49 jjmcd: Did you try in another language session? 23:30:53 Yes 23:30:57 * stickster may not have done it right. 23:31:04 I logged on in Dutch, Spanish, a few others 23:31:14 Like I said, initially there was some issue 23:31:14 I only did LANG=___ and then fired off the menu item 23:31:16 OH yes 23:31:22 bug in Firefox 23:31:24 So maybe my browser settings were affecting it, and that was the wrong way to do it 23:31:27 fixed on an update 23:31:36 OK 23:31:40 I never tried that, just logged on with another lang 23:32:07 There is also a GDM_LANG which doesn't seem to get set for all languages 23:32:45 jjmcd: If it worked through login, I'm satisfied 23:32:49 I didn't try it properly 23:32:51 AHA! 23:32:57 * stickster just got it fired up -- that was indeed the problem. 23:33:29 #info There is no issue now -- Firefox bug affecting this behavior fixed, all's well! 23:33:33 Moving on then? 23:34:24 * jjmcd notes that he should be more vocal when he's working some of these probs so others are aware 23:34:34 * laubersm agrees 23:34:37 :) 23:34:43 jjmcd: I didn't spend too long on it in this case, but... yeah it would be helpful :-) 23:34:49 communication == super-important in FOSS.. 23:35:00 Not that I always do it perfectly myself! ;-) 23:35:12 Yeah, a lot of the time I figure it;s my own stupidity I'm fighting 23:35:17 No big deal -- all's well that ends well! 23:35:24 In this case it was *my* stupidity so I'm happy to move on now :-D 23:35:39 I thin laubersm caught the FF update 23:35:45 Is there any other component content needed at this point for Release Notes? 23:36:01 We will rebuild the minor docs 23:36:11 and post them to docs.fp.o when the time is right 23:36:18 * stickster hasn't even looked at them in a while, but good deal 23:36:23 along with the release notes, 4/5 I think 23:36:30 There may be a README or two that Oxf13 will need for release. 23:37:07 * jjmcd will check with Jesse 23:37:27 #action jjmcd will check with Oxf13 (Jesse Keating) to see if there is any other content he's expecting from us 23:37:35 OK then 23:37:37 #topic Guide status 23:37:43 We're a little behind, so I'm picking up the pace 23:37:48 UG? 23:37:49 * stickster has another meeting at 8pm EDT 23:38:09 #LINK https://fedoraproject.org/wiki/User:Laubersm/F13_UG_Update_Checklist#TODO_List 23:38:25 laubersm: Yeah, so you've been getting some help with this it seems! 23:38:51 some yes, but apparently I agreed to get it done by tomorrow?!? A little more help would be nice. 23:38:59 Wow 23:39:09 * stickster wonders, anyone here able to do some docs help tonight? 23:39:10 wow indeed - what help do you need tonight? 23:39:12 It is not hard, just need to make sure everything is correct on F13 23:39:21 I can help with a chapter I'm sure, after my 8pm meeting's over 23:39:28 There are a handful of Chapters to go through. 23:39:37 #info laubersm needs immediate help on the checklist at https://fedoraproject.org/wiki/User:Laubersm/F13_UG_Update_Checklist#TODO_List 23:39:38 Most are pretty close - a few menu name changes here and there 23:39:46 a few changes of default behavior 23:39:58 laubersm: You just need a pre-F13 box, right? Something up2date? 23:40:07 Yes. 23:40:25 And if there is anything that looks like it need major work, comment it out so that translators do not waste their time 23:40:29 * rudi volunteers to verify the KDE desktop tour 23:40:30 #info To help, just show up in #fedora-docs with a pre-F13 box or even a running VM, up to date with the latest RPMs. 23:40:35 rudi: Awesome! 23:40:39 We can still add to it over the next week but we want to let them start 23:40:45 #action rudi to help with KDE desktop tour 23:40:49 It's the only desktop that really matters; we really should get it right 23:40:56 #action stickster will help with at least one, and hopefully more, chapters 23:41:11 .bug 514641 23:41:12 rudi: -1 Troll 23:41:13 laubersm: Bug 514641 Input Method for other languages - https://bugzilla.redhat.com/show_bug.cgi?id=514641 23:41:21 stickster: feel free to action me for at least chapter 23:41:29 #action ke4qqq will help with at least one chapter 23:41:33 If someone could check and snaz this one up I would also appreciate it. 23:41:40 OK, work to commence right after this meeting then? 23:41:44 It is about changing input methods for other languages 23:42:11 #agreed Help to commence after this Docs meeting, volunteers appreciated 23:42:14 yup - right after meeting. I'll be in docs 23:43:01 OK, the only other thing I had for this item was -- 23:43:07 Are we blocked on any branching? 23:43:37 Or is that all good to go? I think rudi probably branched everything needed thus far, but if not, there are several of us here who know how to do that with git, and can show others if needed. 23:43:48 I've branched everytghing that's ready 23:44:09 I've also documented the procedure, although it's a little more complicated this time around 23:44:20 And documented it on the wiki 23:44:20 Oh, aha 23:44:31 Great job! The cobbler's children HAVE THEIR SHOES! 23:45:04 OK, situation normal, moving on then. 23:45:10 link? 23:45:11 #topic Schedule review 23:45:14 #undo 23:45:14 Removing item from minutes: 23:45:24 https://fedoraproject.org/wiki/Branching_a_document_in_git 23:45:30 rudi: awesome - thanks 23:45:40 #link https://fedoraproject.org/wiki/Branching_a_document_in_git <-- just what it looks like 23:45:52 and now... :-) (Mr. Impatient!) 23:45:55 #topic Schedule review 23:45:58 ke4qqq -- I'll have updates for the IG and IQSG backported from RHEL in the next couple of days 23:46:10 #link http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-tasks.html 23:46:20 That's the schedule, and it looks like we're doing... not too badly! 23:46:30 Nice work pulling together for the Beta everyone. You guys are superstars. 23:46:40 I wanted to make sure that lines 31-42 there are well covered. 23:47:08 I have a calendar on my wall with all of those on it, plus my other appointments 23:47:13 The next item up is 2010-04-01 -- tomorrow -- sending a reminder to the devel@ list that we are going to be freezing release notes on 2010-04-12 23:47:25 jjmcd: Do you have that one in hand then? 23:47:30 Yepper 23:47:31 ROCK ON! 23:47:51 #action jjmcd will send reminder to devel@ list about 2010-04-12 freeze for release notes -- get your wiki changes onto the beats PRONTO! 23:47:59 jjmcd: I'm confused about what line 32 is 23:48:18 It says "Build and post release-notes to fedorahosted.org" -- is that really just something our automated build is taking care of? 23:48:29 poelcat's way of spelling docs.fp.o 23:48:32 Ah! 23:48:54 #action poelcat Correct line 32 in docs tasks to read "docs.fedoraproject.org" instead of "fedorahosted.org" 23:49:17 jjmcd: I'm going to assume you'll do the 7 days out notice too (line 33) 23:49:22 Affirm 23:49:30 #action jjmcd will send reminder to devel@ list again on 2010-04-05 23:49:36 you're the bees' knees. 23:49:43 I would like to get someone, maybe someone new 23:49:52 to work with me on some of the grodier stuff 23:49:59 so there is someone else around who knows 23:50:02 jjmcd: Are those reminders grody? 23:50:11 No, I was thinking building RPMs 23:50:13 Ah 23:50:33 It is down to where it is pretty easy 23:50:42 But I'm not confident it isn't a secret 23:50:43 Yeah, we should have that documented in the repo itself 23:50:49 Good point 23:50:55 ISTR there being a README in there, probably out of date. 23:51:00 Yes 23:51:02 I'd just put the instructions there, and ta-da! 23:51:11 self-documentation at its finest :-) 23:51:19 The push to fedorapeople is documented on the wiki 23:51:32 I've seen jjmcd's readme... someone else will need to make sure it makes sense without asking him any questions :) 23:51:44 OK, a link to that wiki page in the repo's README would be good 23:51:48 Yeah, sometimes I can be a little opaque 23:52:00 jjmcd: I can suss that out, I'm good at asking caveman questions :-) 23:52:15 OK, that's all I had for schedule really. 23:52:39 #action jjmcd Ensure the README in the release-notes repo is up to date and includes instructions for RPM building, and a link to the wiki page for building/pushing onto fedorapeople.org 23:53:01 #topic Beta announcement 23:53:25 OK, this is on Docs + Marketing plates right now. rrix agreed to draft something. 23:53:40 * rrix perks up 23:53:48 rrix will notify the marketing list about it, and when he does, I'll make sure Docs folks know to check it over 23:53:53 I'll be happy to proofread/bleed on 23:54:13 rrix: If you could have a draft by around Friday night or Saturday, that would be great 23:54:18 * rrix nods 23:54:23 Gives us time to proof, edit, etc. and be ready in plenty of time for Tuesay 23:54:25 will draft it now, in fact 23:54:26 *Tuesday 23:55:13 rrix: https://fedoraproject.org/wiki/F12_Beta_Announcement has a F-12 version you can use 23:55:24 rrix: https://fedoraproject.org/wiki/Fedora_13_Alpha_release_notes have updated information you can use for the body too 23:55:35 rrix: Thanks for taking that on! 23:55:39 Let us know if you need help at all. 23:55:42 No problemo :) 23:55:57 Awesome... I love it when a plan comes together 23:56:10 OK 23:56:28 #agreed Docs will proof and edit announcement after rrix notifies us it's ready 23:56:40 #topic Outstanding BZ tickets 23:56:45 #link https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&product=Fedora%20Documentation&bug_status=NEW&bug_status=ASSIGNED 23:56:56 I don't have anything to add here, this is purely informational. 23:57:18 #info If you're new and want to help, come by #fedora-docs and we can get you started on a bug or a helpful task 23:57:25 That leaves us with 3 minutes! 23:57:30 #topic All other business 23:57:37 open floor! 23:57:52 I have a thing on my calendar says "Porting Party" on 4/17, but I have no idea what that means 23:58:14 from wiki to xml for RN 23:58:20 jjmcd: Ah, that is a work party to bring changes from the wiki into XML 23:58:21 Ahhh 23:58:25 Yeah, what laubersm said! 23:58:25 that is when (at one time) we though we had to do that 23:58:47 Then we all suddenly realized that date was porting pary 2 - the sequal 23:58:50 Well, should be easy, there haven't been a lot of changes so far 23:58:51 We will still need to at least check all the beats' history to make sure they haven't changed, and if so, did we get the changes in XML 23:59:00 jjmcd: Right 23:59:03 But maybe after tomorrow's reminder 23:59:07 But after the "OMG PANIC" notice to devs... 23:59:08 right 23:59:26 OK, cool 23:59:39 Anything else on that? 23:59:59 #action stickster to remind list of 2010-04-17 porting party 00:00:05 Not to be confused with "portapotty" 00:00:17 * stickster holds gavel up for 30 sec 00:00:22 we have a reminder training set for after 4/14 meeting too 00:00:39 Yup, that's pre-porting party "sign up, account foo, git foo, etc." 00:00:51 Thanks! 00:00:52 #undo 00:00:52 UG proof reading party in docs - now 00:00:53 Removing item from minutes: 00:01:09 #action stickster to remind list of 2010-04-14 pre-porting party training session after Docs meeting, and 2010-04-17 porting party 00:01:32 * stickster holds gavel up for 30 sec 00:01:50 15 00:01:58 10 00:02:03 5 00:02:09 #endmeeting