00:03:13 #startmeeting Fedora Docs 00:03:13 Meeting started Thu Mar 10 00:03:13 2011 UTC. The chair is nb. Information about MeetBot at http://wiki.debian.org/MeetBot. 00:03:13 Useful Commands: #action #agreed #halp #info #idea #link #topic. 00:03:17 #meetingname docs 00:03:17 The meeting name has been set to 'docs' 00:03:45 alright Nick 00:03:48 I believe all of the action items have been done? 00:04:34 I will try to muddle through some sort of meeting, not sure how much we can cover 00:04:36 I don't recall the open help conference thing 00:04:41 oh true 00:04:44 but i could easily have missed it 00:04:49 Is anyone interested in attending the open help conference? 00:04:55 I did see the tx note, tho 00:04:59 there is a possiblity of fedora subsidizing your attendance 00:05:05 * jjmcd is interested but can't 00:06:11 #info Open Help Conference is in Cincinnati, OH June 3-5, 2011 00:06:30 #info let nb know if you are interested in attending, there is a possibility of Fedora subsidizing your cost of attending 00:06:46 #topic Transifex 00:07:01 if there's anything you need to know about the conference, let me know 00:07:08 I haven't really spent any time on this in the last week 00:07:14 Does anyone have any questions or anything? 00:07:51 there is still some room left for team sprints 00:07:52 I still need maintainers to email me with their transifex.net username and what docs they maintain 00:08:46 rlandmann/rudi and I have access to all of docs's projects on transifex.net so let us know if you have any problems 00:08:55 shaunm, unfortunately, I need to be here in river city on that Saturday 00:08:58 Most git repos have .tx/config files in them now, I haven't touched svn 00:09:07 i'll try to work on finishing them up soon 00:09:10 * _logan_ has a couple of questions about tx,net 00:09:15 and I'm still to get to the frontmatter 00:09:15 _logan_, sure, go ahead 00:09:19 nb, I'll still need some coaching, but not gonna happen this week 00:09:40 jjmcd -- the good news is that it's all very easy :) 00:10:19 <_logan_> nb: tanks. First. About the documentation project (http://www.transifex.net/projects/p/fedora/r/fedora-15-docs/) 00:11:24 <_logan_> Those modules are the same that eventually we'll find under each guide projects (http://www.transifex.net/search/?q=fedora+guide) 00:11:31 yes they are 00:12:08 <_logan_> nb: great. so we can pick one or another and the result will be the same? 00:12:37 _logan_, yeah, its the equivalent to http://www.transifex.net/projects/p/fedora/r/fedora-15/ 00:12:52 but docs made a separate one instead of adding a whole lot more resources to fedora-15 00:14:45 <_logan_> Perfect. Now, my second question... I'm accostumed to publish our finished guides (http://git.fedorahosted.org/git/?p=docs/web.git;a=summary). Can we be able to still do that, or these another different MO? 00:15:02 <_logan_> these=trere is. 00:15:19 No, nothing different. 00:15:30 _logan_, that should be fine, just remember to run tx pull first 00:15:31 The publishing part of the process is unfortunately still the same for now! 00:15:46 (my fault) 00:16:13 <_logan_> well rudi, I kinda like it :) 00:16:20 _logan_, tx pull will get the updated po's from the transifex site 00:16:40 _logan_ -- you will like the automated system better, I guarantee you :) 00:16:42 <_logan_> nb: tx pull when? 00:17:20 <_logan_> tx pull instead of git pull? 00:17:24 rudi, _logan_ would need to do that before building the doc right? 00:18:11 Yes, need to do that before running "publican build" 00:19:00 I guess we need to add tx pull to the website-building howto 00:19:12 * nb has never built the website, so I don't know much about it 00:19:25 <_logan_> So, rudi, nb, this page need to be updated?---> https://fedoraproject.org/wiki/Publishing_a_document_with_Publican 00:19:58 yeah, it should say Change to the directory where you keep a checked-out copy of the document that you want to publish, then run: 00:20:00 tx pull -a 00:20:09 then the publican build command 00:20:23 or you can tx pull --lang=es_ES or whatever if you don't wnat to update all of htem 00:20:25 Yes, I'll add the extra step 00:21:22 <_logan_> great. I'm sure warrink will need that info as well 00:21:36 Thanks for pointing it out! 00:22:45 nb -- anything else to add on Tx? If not, I have a question 00:22:56 i don't have anything else 00:22:58 rudi, go ahead 00:24:12 So I'm still looking at getting Tx running on one of the public test servers; do you know of one that I could use for this? I'm not sure of the procedure to "formally" request one, or even that such a procedure exists! 00:24:22 I've been spoiled in the past by your hand-holding! :) 00:24:26 file a RFR 00:24:29 let me find the template 00:25:00 #link http://fedoraproject.org/wiki/Infrastructure/RFR 00:25:07 #link http://fedoraproject.org/wiki/Infrastructure/RequestForResourcesTemplate 00:25:27 i'd shortcircuit the process, but due to the politics i'm going to let it go as a RFR and stuff like normal 00:25:43 Oh yeah, understood! :) 00:25:55 This needs to be by-the-book obviously :) 00:26:43 i think that's about all i have for tx 00:26:44 Thanks -- you should see a RH sysadmin introduce himself on the infra list shortly 00:26:46 Me too 00:27:31 #topic release notes 00:27:36 anyone have anything about this? 00:28:57 The Alpha release notes looked awesome 00:29:02 Nice job on the aplha notes 00:29:04 * jsmith was happy w/ them 00:29:11 Zach and others who worked on them 00:29:59 #topic Guide Status 00:30:16 all git docs have been branched except musicians guide 00:30:38 if you make changes, please make sure they get in both f15 and master, ask someone if you need help with how to merge branches 00:31:11 So yeah, now that alpha is out, we need to start verifying content in the f15 and master branches 00:34:24 #topic Open floor discussion 00:34:29 Anyone have anything? 00:35:21 Thanks nb for taking the helm! 00:35:37 amen to that 00:36:41 <_logan_> yeap. awesome chair :) 00:36:43 no problem, glad to help 00:36:47 hopefully I didn't miss too much 00:36:49 #endmeeting