23:00:09 #startmeeting Doc Meeting - agenda http://fedoraproject.org/wiki/Docs_Project_meetings 23:00:09 Meeting started Wed Sep 15 23:00:09 2010 UTC. The chair is jjmcd. Information about MeetBot at http://wiki.debian.org/MeetBot. 23:00:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 23:00:16 #topic Roll call 23:00:23 * nathant is here 23:00:36 * jjmcd 23:01:13 * bethlynn is here 23:01:25 * bcotton is hurr 23:02:05 I don't see too many other troublemakers on the channel. I know Sparks and rudi will be gone missing 23:02:51 #topic follow up on last week's action items 23:02:55 #link http://meetbot.fedoraproject.org/fedora-meeting/2010-09-08/fedora_docs.2010-09-08-23.00.txt 23:03:09 I think this might be kinda dull, too 23:03:56 Sparks isn't here, I did chat with rbergeron at OLF about the announcements, but we really need get mizmo in on the conversation 23:04:15 sorry i'm late 23:04:20 I didn't plan to be looking at process until after today 23:04:21 * nb 23:04:29 hi frostbite you didn't miss anything 23:04:48 nb? Did you get to email about invite-only? 23:05:03 yes 23:05:08 and i received 0 response 23:05:08 cool 23:05:12 heh 23:05:20 The question is, do we want to make the docs group invite only? 23:05:27 docs-writers and docs-publishers already are 23:05:36 . 23:05:44 nb: +1 from me 23:05:48 i think it might be a good thing if we did 23:05:52 And I don't know how many requests we have been getting that are sort of off 23:06:03 The issue is someone has to sponsor a new member anyway 23:06:08 if only so that we're aware of new contributors who might need a hand 23:06:20 * nb is generally +1 to this, because i will put a message that says emaiil the docs list if you want to join 23:06:35 So basically, requests to join are really only an anyoance for me and sparks 23:06:47 jjmcd, and me :) 23:06:48 /win 48 23:06:50 woo 23:07:03 And when I follow up on one, I always ask them to post a self-intro anyway 23:07:35 nb, yes, and I think there are a few others, stickster, quaid, prolly rudi. But me and Sparks generally deal with them 23:07:51 jjmcd, yeah 23:08:11 Well, do we want to vote on it, or should we wait until we have more folks here. Pretty light on the heavy hitters tonight 23:08:12 i'd help but im not as knowledgable of the day-to-day workings of docs, i'm mainly just our infrastructure person 23:08:43 Speaking of which, rudi sends his regrets that he can't be here, but does expect to be back in the office Monday 23:09:11 i think we're all in favour, so unless any of the 'heavy hitters' has any objections, I'd say go for it 23:09:20 nb, it isn't a real big problem, and I think it is best if the requestor gets an email from the docs leader anyway 23:09:25 yeah 23:09:37 * nb is kind of +0 23:09:39 BUt when he is away I try to cover 23:09:51 i can see both ways and will be happy with what everyone else decides 23:10:03 In fairness, tho, the number of folks who first appear there and end up being contributors seems to be pretty small 23:10:31 I suggest we wait until Sparks and rudi can be heard. I could go either way, actually 23:10:47 #action Sparks to talk with rbergeron and mo about who will handle the Release Announcements 23:11:00 #action jjmcd to document the process of translating non-English source guides 23:11:14 #action Sparks to set default ticket holder to Docs list to allow everyone ability to see new tickets 23:11:49 Just filling in the ones that haven't been handled 23:12:14 I don't recall whether sparks sent a message about rudi, but since he will probably be back Monday it is moot 23:12:34 Oh, shall we make a note for next meeting 23:13:08 #action Meeting Sep 22, Sparks and rudi to chime in with feelings about making docs group invite only 23:13:14 nb, how is that?\ 23:13:27 is fine 23:13:40 #topic Release Notes 23:14:17 OK, beta rpm went to testing. I don't really know whether it is where it needs to be, but it would help if some of you could give it some karma 23:14:37 yeah. because now it can't pus h to stable unless it waits 2 weeks or has karma 23:14:56 So if we could get one other person to bless it 23:15:16 * bcotton has added it to TuDu 23:15:24 I posted to the list with a link with gory detailed instructions on giving a doc karma 23:15:37 As we start packaging guides we'll be doing this a lot 23:15:49 jjmcd: i'll look at it too 23:16:03 Did you guys see the wiki page? 23:16:21 * bcotton saw the link, has not looked at the page proper yet 23:16:27 No, but I saw your email 23:16:34 #link https://fedoraproject.org/wiki/Giving_a_document_karma 23:16:42 Will take a good look at it! 23:16:52 * nb 'll go bless it as a proventester 23:16:56 then i think you only need 1 more karma 23:16:59 that way it's in the minutes. 23:17:11 Someone checked it out on LXDF today 23:17:22 * nb thinks that his f13 update needs karma too 23:17:24 E F one of them 23:17:32 Yes, I gotta go do that 23:18:12 jjmcd: i'll be checking it on Xfce 23:18:18 Great! 23:18:28 OK, anything else on release notes? 23:18:58 #topic Guide Status 23:19:26 OK, rudi has the IG done 23:19:51 and expects to branch the IG and IQSG this weekend 23:20:07 ANyone have anything else to report on guides? 23:20:16 . 23:20:51 Do we need to do anything this time round to push built guides to fedorapeople? 23:21:02 I mean so trans can have a look at them 23:21:03 the rpm guide is a very long guide. expected release date: June 2, 2513 23:21:18 We really should. I am pushing RNs now. 23:21:39 Err, is that documented anywhere? 23:21:47 Once you have branched, you ought to build nightly. POT updates need to be synched with L10N 23:22:00 nathant, yes, I'll have to go digging to find the link, tho 23:22:23 nb at one point considered giving us a place we could do that 23:22:42 No biggie for me but not every keeps a server up 24/7 23:22:44 jjmcd: great, cos i've forgotten it all! 23:23:14 #action jjmcd to post the link to sending draft translations to fedorapeople 23:23:21 we have a group space on the fedorapeople i think dont we? 23:23:23 There is a page out there 23:23:26 we thought about using docs.stg.fedoraproject.org 23:23:26 nb, yes 23:23:33 but that'd be harder to get set up i think 23:23:41 We have space in groups/docs we have been using 23:23:58 But it would be good if the infra could run the cron jobs instead of every contributor 23:24:19 * nb might be able to, but will have to look into it 23:24:42 They're all pretty much the same. clone, shuffle translations around, publican build, scp to fedorapeople 23:25:40 Once I get the link out there you will be able to see what is involved 23:26:18 jjmcd, just put a #action for me to look into it 23:26:23 Yeah, we have drafts for public consumption in docs.fp.o, but a lot of the translators don't want to see partial work available 23:26:40 * nb is discussing it with abadger1999 in -admin 23:26:46 #action nb will look into providing a way for infra to create the l10n drafts 23:27:02 plus ill have to have publican installed somewhere 23:27:12 I do the ARG at 6PM and the Release Notes at like 4AM 23:27:42 OK, anything else on guides? 23:27:56 * nb could probably make docs.drafts.fpo or docs.stg.fpo 23:28:00 if that would work for people? 23:28:26 Well, the space is handled pretty cleanly, its the cronjobs 23:28:39 jjmcd, well, cron is not available on people1 23:28:54 so i'll have to move it to another server, which is ok, just need to work out where to put it and what url to use 23:29:30 i think rudi mentioned that publican will soon have a publish-to-web feature 23:29:32 Yeah, so people run the cronjobs at home and then scp to fpeople. But some folks have like laptops or whatever that aren't up in the middle of the night when they would want to run the cron job 23:30:05 so maybe we just stick with the current method this time 23:30:10 nathant, yes, it has now. But that works for polished documents. Here, the failure log is almost more important than the actual doc 23:30:23 jjmcd: ah ok 23:30:37 L10N does their edits, and often screws things up. This lets them fix it instead of us 23:30:42 jjmcd, can you get me example of what your cron looks like? 23:31:15 nb, yes, I have it on the wiki somewhere, which I will post when I find it. Meanwhile, I'll email you the script I use for RNs 23:31:43 Pretty tame. I always start with a git clone just so I know I'm using what L10N sees 23:31:58 jjmcd, ok 23:32:12 Well, an rm -Rf then a git clone 23:32:30 OK, anything else on Guides? 23:32:53 #topic Outstanding BZ tickets 23:33:10 I didnt look at the counts, but does anyone need any help? 23:34:10 OK, then 23:34:22 #topic Open Discussion 23:34:38 #info bethlynn did an outstanding job on OLF 23:34:53 And most of you guys missed a great event 23:34:58 thanks jjmcd 23:35:13 I regret us not FADing there too 23:35:41 bethlynn, yeah, but that would have meant missing some awseome presentations, so it is a blaancing act 23:35:41 is anyone from -docs going to the etherpad FAD? 23:35:59 I don't know of anyone 23:36:06 That's at SLC? 23:36:25 it seems like a great tool for doc drafts 23:36:57 bethlynn, yeah. Actually, it would have been great if all the docs folks could have heard Jim Campbell's talk at OLF 23:37:10 https://fedoraproject.org/wiki/Etherpad_FAD in Needham,MA 23:37:37 Oh, in the People's Republik. FOr some reason I was thinking it was in Utah 23:37:42 heck, I didn't hear Jim Campbell's talk, but the oggs will be available 23:38:14 The main problem with OLF was that every hour there were 2 or 3 presentations you couldn't miss 23:38:23 bethlynn: will that be from the OLF website? 23:38:54 we at olf believe in freedom so we will distribute on archive.org 23:39:03 bethlynn: ace 23:39:04 ahhhh 23:39:18 Will there be links from ohiolinux.org? 23:40:00 yes, availability will be announced on ohiolinux.org 23:40:16 Some of the Friday sessions the best part was the discussion afterward, much of which wasn't recorded 23:40:34 I was thinking especially of mchua and rbergeron's talks 23:40:47 Klaatu, of the fedora art project, will have to train some of the folks at my home lug on audio editing, then we will have at ripping these files 23:41:20 the recording devices were different this year 23:41:42 cool ... anxious to see some that I had to miss, and the slides from some, too. Like Paul's. the climagic one, and Stormy's, too 23:41:45 if it could be heard from the stage, the recording device got it 23:41:55 excellent 23:42:19 jjmcd: was it your first linuxfest? 23:42:24 Mel and Robyn both ended up going out into the middle of the room hear 23:42:35 OLF, yeah. Went to LinuxTag last year 23:43:06 I'm not a huge fan of these, but when the agenda is killer how can you not go? 23:43:29 yeah, we had a great variety 23:43:35 Plus rbergeron browbeat me to meet her and Mel 23:44:48 OK, anything else for the good of the order? 23:45:23 bethlynn, as soon as I see some daylight I expect to get back to that process page, too 23:45:36 This week has been nuts, tho. 23:45:57 no kidding 23:46:16 * jjmcd should probably blog a little about his "other" life so folks know why he's in hiding from time to time 23:46:32 what is your blog 23:46:40 * nathant has his hands full with just teh one life 23:46:44 I don't even know if we met at olf 23:46:47 jjpmcd.livejournal 23:46:53 I only know you as jjmcd 23:47:08 bethlynn, yeah, we did. But only flying by! 23:47:13 why are there so many red hat / fedora folk on livejournal 23:47:28 Dunno. It integrates well with planet I suppose 23:48:06 I was doing everything on multiply, but it doesn't play well with planet, so I moved my fedora stuff to lj and left my lunatic ravings on multiply 23:48:22 because they're all too lazy to set up wordpress on their own domains? 23:48:49 bcotton, odd, isn't it. I think most have a domain or four of their own 23:49:12 speaking of which I gotta renew one of mine like today 23:50:09 bethlynn, I think I shook hands with you towards the end. I was going to say I was the oldest fart there, but maddog was close enough to my age to be confusing 23:50:54 OK, anything else before we close? 23:51:22 anyone? 23:52:22 5 23:52:27 4 23:52:33 3 23:52:38 2 23:52:42 1 23:52:56 Thanks everyone. Have a great week and stay safe. 23:52:59 #endmeeting