00:20:05 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:20:05 Meeting started Thu Jan 7 00:20:05 2010 UTC. The chair is sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:20:05 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:20:06 jjmcd, I'd vote +1 to work on KDE, and +1 to move GNOME to HTML 00:20:21 #topic Roll Call 00:20:22 * sparks 00:20:28 Big change midstream, but it would eliominate a lot of grief 00:20:33 * jjmcd . 00:20:42 *me 00:21:05 ***nathant 00:21:34 Sorry for being late. I didn't realize the time! 00:21:56 * rudi is here 00:22:34 Okay, let's get started! 00:22:40 ok 00:22:58 #topic F13 Release Schedule 00:23:07 #link http://poelstra.fedorapeople.org/schedules/f-13/f-13-docs-and-trans-tasks.html 00:23:15 poelcat: You around? 00:23:30 I have a few notes, but unfortunately I referenced line #s in the doc sked, and you pointed to the combined sked 00:23:46 Okay, so the URL above is for both the translators and us... 00:23:49 jjmcd: Yeah, sorry. 00:23:59 I was reviewing everything. 00:24:16 Yeah, I should have looked first, but I was fixating on making sure we had the right order 00:24:27 So what do you have for the docs? 00:24:35 But most of my catches were nit-picks, the real meat is ok 00:24:52 Well, the POT generation and html generation really don't match very well 00:25:12 We have 0 days to do the beta notes when in reality we have weeks 00:25:25 Theres the docs.fp.o vs fh.o thing still 00:25:45 Okay, are you going to put those together and send them to poelcat?> 00:25:49 And on GA RNs also an unnecessary delay ins tarting 00:25:52 Yepper 00:26:43 Plus a few notification I would move from beta to ga 00:26:46 but same dates 00:26:51 Cool 00:27:10 Hopefully he can generate the calendar files for me so I won't miss anything. 00:27:29 He has the sources out there so you can do that easily 00:28:11 Hey, another country heard from. Hi Susan 00:28:12 ya 00:28:47 Okay, anythign else on this topic? 00:28:53 * laubersm sneaks in while listening to a basketball game 00:29:56 Okay, moving on 00:30:10 #topic Release Notes 00:30:19 For F12, Release Notes are in XML (Yelp) only. This means there is no easy way for a KDE user to view them. We can display HTML notes in any window manager. However, if we provide XML for Gnome and HTML for KDE, this doubles the size of the package. 00:30:26 We could provide HTML only (and quite easily), but now Gnome users see a major change mid-stream. 00:30:33 If we do anything for KDE, we should talk about where to put the docs on the menu. Talking with rudi before the meeting we may have little choice. 00:31:08 So basically I'm looking for input. I'm pretty open for now 00:31:18 * sparks thinks we might have to do release notes for the Release Notes! 00:31:26 hehe 00:31:38 Well... I'm a big advocate for accessibility... 00:31:56 but I hadn't thought of the accessibility within different desktops... 00:32:06 I feel like nothing for KDE (well, they still have online) is a bad deal 00:32:22 so it would seem that pushing everything as HTML would be the answer. 00:32:27 Thinking about it, maybe a double-sized package might not be a bad idea for the rest of the F12 lifespan? 00:32:28 while I personally use gnome and so "as is" sounds good :) I agree that KDE users need just as easy access to local RN 00:32:40 And look at HTML only for F13? 00:32:48 What about XFCE? 00:32:51 Yeah, I'm kind of leaning that way 00:33:00 Well, html will work for everyone 00:33:13 Xfce Spin doesn't use Yelp 00:33:17 although I have no clue how to make a menu entry for XFCE 00:33:24 That way, nobody gets surprised, and we also get a chance to fine-tune the HTML strategy before F13... 00:33:41 Yeah; we need to look at how to integrate with XFCE too 00:33:53 nathant: Ya... Will Xfce handle html? 00:34:00 Doex XFCE have a .desktop type thingie? 00:34:18 * laubersm loves the technical terms 00:34:24 sparks: Yes, Xfce documentation is in html 00:34:45 jjmcd: Yes, and menu configuration is fairly easy from the look of it 00:34:58 Ahh good. From an rpm? 00:35:50 Think so, there's a package called xfce-doc 00:36:01 nathant, as best I can tell, it is easy to add/replace a file from an rpm. kind of messy to change a file 00:36:40 OK, so for F12 update, html or both? 00:36:53 Sounds like we have support for html only for f13 00:37:05 jjmcd: Do you have time to generate a HTML-only version for F12 so we can play with it? 00:37:12 sure 00:37:42 The f11 update provides html for KDE, but no menu option on Gnome since that is available through yelp 00:38:13 bu you can always open index.html with htmlview 00:38:26 I'm good with aiming F13 towards HTML-only 00:38:37 sparks: I second that 00:38:53 count me in for only html in F13 00:39:07 Okay... who can test a package in KDE? 00:39:24 * rudi volunteers 00:39:27 sparks, I made myself F11 and F12 KDE sticks to test on 00:39:35 Cool 00:39:41 rudi: You are on for KDE 00:39:44 jjmcd, I can help with testing :) 00:40:02 nathant: Can you test in Xfce? 00:40:07 BTW, a stick is the cat's meow for testing cuz you can save off the overlay file and that makes it easy to start over 00:40:09 Sure 00:40:27 Good deal 00:40:46 jjmcd: There you go. 00:40:50 I can test in Xfce 00:40:50 I'll put together an F12 html only with just a few languages so it is small 00:40:59 jjmcd: When do you want to do the tests? 00:41:24 I guess in a few days, my little prog can make the rpm pretty painlessly 00:41:39 jjmcd: It might be good to do this on IRC so any issues can be fixed in real time 00:41:43 I need to do some xfce research 00:41:48 Yeah, good plan 00:41:58 Are we missing any desktops? 00:42:00 OLPC? 00:42:12 errr... Sugar 00:42:14 BTW, did you see my note on the list? The rpm maker sources are on github for the terminally curious 00:42:16 sparks: LXDE 00:43:01 With html, it may only be a matter of providing a handful of menu files 00:43:08 #action jjmcd to rebuild F12 Release Notes in HTML-only and test in GNOME, KDE, Xfce, ... 00:43:21 Yeah; Sugar and LXDE are the only other two that we offer groupinstalls for 00:43:38 Anyone use either of those? 00:44:43 I can shoot something out on the Planet to see if we can get some help 00:44:58 Now there's a good idea 00:45:28 http://github.com/jjmcd/FedoraDox/tree/master/tools/doc-publican-rpm/ 00:45:40 Allows you to make your own custom set of languages 00:46:06 #action sparks to ask on the Planet for assistance on testing LXDE and Sugar 00:46:10 Cool 00:46:20 and there's an rpm at http://github.com/jjmcd/FedoraDox/downloads 00:46:33 If you just want to recklessly install it withough studying the sources 00:47:34 heh 00:47:53 Okay, anything else on the Release Notes? 00:48:09 Oh, F11 00:48:26 An update has been pushed, should hit the repos in the next day or so 00:48:41 It fixes some bugs but also adds a menu item for kde 00:48:59 Testing languages seems a pain in KDE. Maybe rudi can help here 00:49:08 jjmcd -- will do 00:49:13 There must be an easier way 00:49:39 That's what I had on RNs 00:49:57 Cool 00:50:08 Yeah, F11 should be in the wild now 00:50:26 Okay, moving on! 00:50:27 Oh yeah, that RPM makes has man pages, info pages, etc 00:50:42 #topic Status on CMS (Zikula) 00:50:52 #link https://fedoraproject.org/wiki/Zikula#Module_status 00:50:57 ke4qqq: You around? 00:51:40 I think Marketing pushed a Fedora skin for Zikula last week 00:51:44 so that's exciting. 00:51:47 cool 00:52:12 I thought I saw mchua here, perhaps she could brag on it 00:52:29 I haven't heard anything else on this in a while. Hopefully ke4qqq can provide some info on this next week. 00:53:16 Okay, moving on.. 00:53:30 #topic Does yum langpack support help us? 00:53:39 #link https://fedoraproject.org/wiki/Features/YumLangpackPlugin 00:53:47 jjmcd: Was this of interest? 00:53:49 I have some concerns on how we might make this work 00:54:02 okay 00:54:04 Well, it would be nice, and easy for yelp, not so much for html tho 00:54:23 ya 00:54:35 Do we need it for HTML? 00:54:54 well, yeah, if we are going to do dox in html 00:55:14 true 00:55:23 This would allow us to push selected langs, but for html, I don't know how to make it work 00:55:34 Not that it can't, but I can't see the way. 00:55:38 Why would it be any different? 00:55:50 Perhaps a long heart to heart with spot or some other expert 00:55:56 ya 00:56:00 Well, yelp has some cool features 00:56:33 #action jjmcd and sparks to setup a meeting with spot and others to discuss YumLangpack and HTML 00:56:39 In particular, you can add a language by adding files. HTML doesn't know how to select languages by itself, tho. So you have to MODIFY files which is a lot harder inside rpm 00:57:12 And even if you can the logic is a lot harder 00:57:20 yes 00:57:34 maybe the plugin can be smarter than us 00:57:48 Now you're fantasizing 00:58:12 Maybe we can teach the browser to translate on the fly 00:58:20 well, there's tha 00:58:22 that 00:58:36 Still, it shows promise 00:58:46 I don't think we can dismiss it out of hand 00:58:52 ya 00:59:34 But HTML wouldn't need to know how to select languages by itself... 01:00:07 You'd generally only need one language, you just need to pick the right one initially 01:00:25 Or am I not following the discussion? 01:00:27 nathant, in Gnome, you select a language on logon, and everything (that is translated) shows up in your selected language 01:00:43 Ahh 01:00:47 That makes sense now 01:00:49 In some places (India, Belgium) this is very handy 01:01:09 In India, the guy down the street probably doesn't speak the same language you do 01:01:22 Not quite so bad in Belgium 01:01:34 In Canada, the law requires multilanguage 01:01:50 jjmcd, agreed, I am from India but the differences aren't so much 01:02:14 dhillon-v10, seems like half the languages we have are Indic languages 01:02:27 jjmcd, really wow :) 01:02:58 A lot of them I never heard of 01:03:24 jjmcd, okay i could hlep out with translations then yay :) 01:04:16 They all use weird characters, too. And different 01:04:30 heh 01:05:08 jjmcd, lol 01:05:20 Okay... anythign else on this? 01:05:48 I don't think so. I'll get with spot 01:06:06 cool 01:06:12 #topic New Guides 01:06:17 Any new guides in the works? 01:06:42 sparks, I want to pick the one on live installer, it currently doesn't have anyone to work on it, can i 01:07:16 live installer? 01:07:58 Is that not covered in the Installation Guide? 01:08:19 sparks, sorry its the Live Images one :P 01:08:33 making a live image? 01:09:05 sparks, not quite sure its the last thing on this page: http://fedoraproject.org/wiki/Docs_Project_meetings#Agenda_for_Next_Meeting 01:09:50 Hmm... not sure what that is. 01:10:07 sparks, yah same here :D 01:10:13 That's the live images doc 01:10:42 ie - http://docs.fedoraproject.org/readme-live-image/en-US.html 01:10:46 rudi: Okay, looks like you are handling that doc, correct? 01:10:48 rudi, thanks :) 01:11:08 sparks -- only by virtue of nobody else handling it 01:11:14 I'm more than happy to give it away 01:11:22 AHhh, looks like we have a victim 01:11:27 rudi, can I pick it, I am a new member though 01:11:53 dhillon-v10: rudi is an excellent resource 01:11:53 dhillon-v10 -- that's no problem, but you might want to discuss any changes on the mailing list first before jumping in :) 01:12:30 The only real "trap for new players" is the realization that when we change something in a doc, we create work for 20 or more translation teams 01:12:55 rudi, okay yah I work over at Ubuntu and FreeBSD and it does increase a *lot* of work 01:12:56 So we only change stuff in existing docs if we absolutely *have* to (ie, something is out-of-date and factually wrong) 01:13:57 Okay, anything else for New Guides? 01:14:15 There was a draft Command Line Survival Guide posted to the list today 01:14:43 * sparks hasn't caught up on his email 01:14:45 That looks like a goody 01:15:00 sparks -- power management and resource management guides sometime soon :) 01:15:06 cool 01:15:31 Will start moving as soon as I finish playing whack-a-mole with the IG :) 01:15:37 ya 01:15:44 rudi: let me know if you need a paragraph on the new xfce power manager 01:16:04 nathant -- Ta! I'll make a note 01:16:53 rudi: no problem 01:16:54 * laubersm *should* be available for some proofreading (or more) next week 01:17:29 Okay, let's move to the existing guides 01:17:36 #topic Guide needs 01:17:52 that darn peer 01:18:12 * jjmcd still needs to recruit more helpers for the ARG 01:18:12 Have we figured out if the new Transifex is up and ready? 01:18:25 sparks -- still coming 01:18:32 Okay 01:18:32 But there's definitely traction there now 01:18:37 +1 01:18:57 I need some help with documenting PolicyKit in the Security Guide. 01:19:02 Only about a month until we start sending them publican pots 01:19:02 jjmcd: ARG? 01:19:10 Amateur Radio Guide 01:19:34 Independent of that, we should pick a time soon to migrate all existing Guides' POT and PO files to Publican 1 (in the master branches at least) 01:19:57 jjmcd: We also need to update the RNs and SG for the PackageKit vulnerability 01:20:04 Yep 01:20:21 There are a bunch of updates to F12 rn's I need to do 01:20:21 All my guides are in Publican 1, I think. 01:20:24 And then co-ordinate with L10N when/if to move the Publican 1 PO files into the current working Transifex branches 01:20:34 Now that F11 is put to bed, that is the next big thing 01:20:53 rudi, how much of a pain will that be? 01:21:03 Yeah, the PackageKit thing in the RN and the processors list are still blockers for the 0 --> 1 migration 01:21:22 Also a blocker for me moving my F10 box to F12 01:21:22 jjmcd -- not much of a pain at all, actually. It's just picking the right moment. 01:21:41 There's a few other blockers in the IG 01:22:01 I hope to have those all put to bed in the next few days. 01:22:19 did you see jsmith's Publican bug? 01:22:26 I didn't 01:22:48 I think we're in a position now to fix the PackageKit thing in the RN, but what about the processor list? 01:22:58 I saw that bug, but haven't tested it yet 01:23:04 I should get to that today 01:23:08 I was trying to reproduce it, but had no joy at all making 1.0 work from scratch. Fine with an existing doc but not new 01:23:08 Well, we can push it separately 01:23:36 jjmcd -- that's a bug in 1.0; the issue was fixed in 1.3 01:23:51 Now that ppl are back to work I should be able to get with notting, but I've been on the phone all week it seems 01:24:08 rudi, it was 1.3 i was struggling with 01:24:10 jjmd -- you can also fix it by removing any empty fields from the publican.cfg file 01:24:24 ahh, i'll look at that 01:25:01 It was whining about not finding ___DocName____ 01:25:11 Who knows where all those _ came from 01:26:41 Okay, anything else guide-wise? 01:28:26 #topic Other business 01:28:32 Anyone have anything else? 01:28:42 Want to mention the yelp meeting 01:30:06 Yeah 01:30:23 The Gnome folks are organizing a meeting on help display in March in Chicago. They are getting together Gnome, KDE and XFCE folks from Fedora, The Gnome folks are organizing a meeting on help display in March in Chicago. They are getting together Gnome, KDE and XFCE folks from Fedora, Ubuntu and others to talk about what is needed for help display. 01:30:23 Ubuntu and others to talk about what is needed for help display. 01:31:18 They have some thoughts about an improved language for help content, maybe a common help application 01:31:35 But obviously, their prerspective is from Yelp 01:32:08 Yeah... Looks like some KDE folks have already RSVP'd 01:32:30 I have a conflict on Saturday, but I think I may prioritize this higher 01:33:03 Besides, I need an excuse to buy sparks a guinness 01:33:08 :) 01:34:00 Sparks, you are going by train???? 01:34:05 #action sparks to talk to Max about funding 01:34:14 jjmcd: If I go then I will be going by train, yes 01:34:26 Long ride 01:34:48 better than being strip searched at the airport! 01:34:54 Well, there is that 01:35:08 plus I like taking the train! 01:35:09 It's about 6 hours drive from here, -2 minutes by air 01:35:15 hehe I can see that 01:36:12 Okay, anything else? 01:36:15 I did some teaching at the Motorola University, so I have some experience with the drive 01:36:38 Ya 01:38:27 Okay, thanks everyone for coming! 01:38:39 * mchua here now if zikula updates needed *fades back into background until called* 01:38:57 mchua: Go for it! 01:39:15 I think we may be ready for staging, with hiemanshu's skin package in and working. 01:39:35 Trying to find itbegins to sit down and confirm it - so if y'all see him around, ping plz 01:39:47 that's it - once we get that, we'll be on staging, and shortly thereafter (we assume) production 01:40:14 cool 01:40:26 what's missing for us to use it for docs.fp.o? 01:40:37 you may want a translations workflow. 01:41:13 Other than that, i'm not sure what else you'd need that we don't already have 01:41:32 EOF 01:41:32 excellent 01:41:44 any questions for mchua? 01:42:15 for that matter, if you figure out a translations workflow, we'd love to use it too - Marketing hasn't really had any i18n-ness in our formal workflows in the past, so that's something we'd like to learn from you on. 01:42:34 will do 01:42:40 * mchua can't think of anything else, is done 01:42:58 Okay, thanks mchua for the update 01:43:12 And we'll go ahead and close the meeting at this time. 01:43:22 Thanks, everyone, for coming! 01:43:28 #endmeeting