00:00:29 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 00:00:29 Meeting started Thu Dec 24 00:00:29 2009 UTC. The chair is sparks. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:00:29 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:00:39 #chair jjmcd 00:00:39 Current chairs: jjmcd sparks 00:00:46 #topic Roll Call 00:00:47 * sparks 00:00:59 * jjmcd . 00:01:23 * nb . 00:01:38 oh look, a meeting 00:03:33 oi! 00:03:47 wow! quaid is here! 00:03:52 :D 00:04:17 Okay, let's get started. 00:04:46 #topic F13 Docs Schedule 00:05:13 So we had a two and a half hour phone conference/Gobby meeting last night... 00:05:37 where we got the F13 release schedule hammered out. 00:05:37 Great fun it was 00:06:00 So we made a few changes from previous releases that we need to talk about tonight. 00:06:58 The first items is that we aren't going to freeze development of the Release Notes or Guides until the very end 00:07:22 So everyone should keep working through the Alpha and Beta freezes 00:07:50 Any questions about this or any comments? 00:08:08 We will be producing pots for L10N on a regular schedule 00:08:08 what reason was there for that? 00:08:20 jjmcd: Yeah, that's the next thing. 00:08:30 ianweller: for which that? 00:08:33 All the branches we had to keep track of what L10N had was confusing 00:08:37 18:06:52 < sparks> The first items is that we aren't going to freeze development of the Release Notes or Guides until the very end 00:08:40 ^ that that 00:08:44 :) 00:08:50 ANd really, we were giving them the MINIMUM amount of time to translate 00:08:50 Yeah, it just doesn't make sense. 00:09:02 oic 00:09:04 This way they get the maximum amount of time 00:09:10 yeah 00:09:20 We had changes we were holding for them that they could have been workin gon 00:10:15 The second thing we decided was that we were going to push POT files constantly. 00:10:33 This way, As soon as we have text it will be available for L10N 00:10:35 so nightly we should be pushing updated POT files so the translators aren't just sitting around waiting 00:11:37 that means that the guides should be pushing POTs now! (Except we are still waiting for Transifex 0.7) 00:12:24 Anything else on this topic? 00:13:25 #topic Sandbox on Fedora People 00:13:33 jjmcd: Want to talk about this? 00:13:38 For Fedora 12, we built release notes each night for L10N. It turns out I didn't have the quota on fedorapeople.org for 42 languages, so I ended up putting them on is-sixsigma.com where I had some space. 00:13:54 Having the RNs on an external host doesn't have the caché of having them on fedoraproject, and it doesn't do anything for guides. 00:14:07 Ricky agreed to make us a group place where we can put draft documents. 00:14:24 People in docs will have write access to /srv/groups/docs and that will be accessible via http://fedorapeople.org/groups/docs/ 00:14:36 Just remember that files owned by you in that directory still count against your quota, so let infra know if you need more. 00:15:13 I think that sums it up 00:15:17 Any questions? 00:15:41 This is for drafts. Finished docs still on docs.fp.o 00:15:57 ya 00:17:06 Okay, works for me... We'll publish the path when it is all setup. 00:18:01 Okay, moving on 00:18:07 #topic Release Notes 00:18:18 jjmcd: Anything you want to talk about on this? 00:18:23 I think we covered the exciting stuff 00:18:32 Works for me 00:18:36 We have a handful of bugs before we push an update 00:18:58 One thing I should mention 00:19:35 I am giving serious consideration to doing the F13 notes in html rather than Yelp. Plenty of time to change so if you want to dissuade me .... 00:20:31 Well... As long as it is easy for the users to find the documents from the GUI... 00:20:45 html addresses other desktops and I now know how to get the same functionality as yelp 00:20:50 I don't have a problem with it. I'm hoping Yelp 3.x will fix a lot of problems for us. 00:21:06 IF it addresses KDE, XFCE 00:21:18 ya 00:22:16 On the menu they will be hidden under "Release Notes" instead of "Help" 00:22:44 And you can have it automagically select the proper language? 00:22:54 of Vrigave Informatie nar Hulp 00:23:35 I'm going to assume that means yes 00:23:39 yes 00:23:44 :) 00:23:47 Make it so 00:23:53 Not just the doc, but also the menu 00:23:59 perfect 00:24:04 and it's all in the same SRPM? 00:24:07 yes 00:24:22 You didn't read the C, did you? 00:24:43 I know, C is a write-only language 00:25:09 I looked at it briefly but I haven't had a chance to study it 00:25:47 It really is pretty simple 00:26:12 The only gotcha is that part of the javascript has to be in rather than 00:26:57 Strangely, in it works sometimes for some languages 00:27:05 Hmmm 00:27:23 but in it always works 00:27:30 well, there you go 00:27:41 ja 00:28:21 Okay... anything else? 00:28:26 not here 00:28:39 Okay.. moving on 00:28:52 #topic Status on CMS (Zikula) 00:29:00 Anyone have any updates on this? 00:29:39 ke4qqq: You around tonight? 00:30:48 Okay, maybe he'll be around in a few minutes. 00:31:09 #topic Does yum langpack support help us? 00:31:17 Do we have anything else on this? 00:32:42 I guess not 00:32:51 #topic Guide Status 00:33:07 Okay, anyone have anything they want to talk about on their Guide projects? 00:34:06 I'd like some help writing up a section of the Security Guide describing PolicyKit 00:34:35 Is that even understandable by mortals? 00:35:22 PolicyKit? I want to make it understandable... 00:35:24 if I can understand it 00:35:49 I just assumed it was as impenetrable as SELinux policies 00:36:16 SELinux isn't impenetrable 00:36:21 that's a guide for that 00:36:41 Yeah, and books. And it makes good sense until you try to understand a policy 00:36:56 heh 00:37:23 I figured "policy" was a code word for too complicated 00:37:49 nah 00:38:31 anything else? 00:39:29 #topic New Guides 00:39:40 Anyone have any new guides? 00:40:56 #topic Outstanding BZ Tickets 00:41:58 There are quite a few open tickets for Fedora Documentation 00:42:15 most look to be chapter reviews 00:42:24 Yes 00:42:56 I screwed up by not tracking down notting this week I hope I don't have to wait for Jan 4 00:42:58 There are quite a few customer requests in there too 00:43:10 Might have to 00:43:29 yeah. Just dunno 00:44:13 Okay, anything else on this>? 00:45:05 #topic Everything else 00:45:14 Anyone have anything they want to discuss? 00:45:33 Do you want a 10 minute tutorial on multilanguage rpm? 00:45:48 Now? If you want to. 00:46:02 Pretty straightforward if you have the stomach for it 00:46:57 I don't hear anyone running away screaming 00:47:17 OK, first, you need a tar. The tar has your doc in a directory per language 00:47:43 A lot like you have in Publican, except the "format" directory pulled out 00:47:51 You need 3 additional files 00:48:11 At the top level, you have an index.html with some magical javascript 00:48:30 The javascript includes a list of languages that will be in the rpm 00:48:42 In head, it grabs the browser's language 00:49:07 In body, it compares the browser language to the list and launches the doc based on the list 00:49:42 The one tricky part is the language from the browser might be, for example, bn, bn-IN, or bn_IN 00:49:52 THe list contains bn-IN 00:50:19 If there is a hit against bn-IN, use it. If not, look for bn* and use the value from the list 00:50:31 The two other files are desktop files, almost the same 00:51:00 The menu language in the desktop file can be stolen from Article_Info.xml in the appropriate language 00:51:10 The two desktop files are almost identical 00:51:42 Now, the rpm install puts the index file in /usr/share/doc/HTML/ 00:51:50 Anyway we can script this? 00:51:58 And the publican in /usr/share/doc/HTML// 00:52:06 Yes, that is what the C program does 00:52:24 You simply give it a publican directory and get an RPM 00:52:42 cool 00:52:48 You going to package it? 00:52:52 The desktop files go in /usr/share/applications and /usr/share/applications/kde4 00:53:03 I wasn't planning on it, but I suppose I could 00:53:20 There is a pdf in there that has a gory description of the program 00:54:05 I have 2 tars on my fedorapeople, one for the app and doc and another for the source 00:54:15 cool 00:54:42 I called it buildrpm. If I was going to package it I would rename it to something less generic 00:54:59 ya 00:54:59 like package-fedora-doc or something 00:55:32 But if you build a guide in a few languages, you should be able to run it 00:55:39 then install the rpm and try it out 00:55:52 It packages what html 00:55:54 s 00:55:58 you have built 00:56:11 so you can package any arbitrary collection of languages 00:56:38 Cool 00:56:45 It looks to find tmp//html/index.html 00:57:13 We should get David to review the spec it makes 00:57:33 Yeah... That would be good 00:57:45 In = publican directory plus a short config file, out=SRPM, RPM, spec 00:58:33 Sounds good to me! 00:58:51 read the pdf, altho it is kinda boring 00:59:39 Okay... anything else? 00:59:39 It does have pictures, tho 00:59:43 nope 00:59:44 Pictures? 00:59:46 Cool 01:00:08 Okay, anyone else? 01:00:10 dot pictures, but pictures 01:00:53 Does anyone have anything else they want to talk about? 01:01:19 we put them to sleep 01:01:27 I think so 01:01:38 Okay, thanks for everyone coming! 01:01:41 #endmeeting