14:00:22 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 14:00:22 Meeting started Mon May 14 14:00:22 2012 UTC. The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:30 #meetingname Fedora Docs 14:00:30 The meeting name has been set to 'fedora_docs' 14:00:40 #topic Roll Call 14:00:42 beep 14:00:42 .fas nick@bebout 14:00:43 nb: nb 'Nick Bebout' 14:01:18 * jjmcd 14:01:27 * claneys 14:01:36 * pkovar is here 14:03:27 oooookay 14:03:32 #topic Release Notes 14:03:38 #link https://fedoraproject.org/wiki/Release_Notes_schedule 14:03:52 New RPM -- needs karma 14:04:01 #info New RPM -- needs karma 14:04:03 #link https://admin.fedoraproject.org/updates/fedora-release-notes-17.0.1-1.fc17 14:04:51 I'm going to wait until release to fix remaining bugs so as to not impact L10n 14:05:14 But I won't have much ability to do anything this week - todo list too awful 14:05:27 Plus, will be out of town 18-20 14:06:20 remaining bugs fairly minor 14:06:46 https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&classification=Fedora&product=Fedora%20Documentation&component=release-notes&bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=FAILS_QA&bug_status=RELEASE_PENDING&bug_status=POST 14:07:43 Apparently since 17.0.0 never got karma, bodhi added those bugs to 17.0.1 14:07:51 #info jjmcd is awesome 14:08:00 But the only difference between .0 and .1 is four languages 14:08:18 Also 14:08:36 It looks as if the way to choose languages on f17 has changed 14:08:51 and I haven't been able to figure out how to log on as dutch, for example 14:09:39 jjmcd, karma given 14:09:45 Thanks Nick 14:10:29 So I can manually look at other languages, but can't test that they actually get chosen 14:12:22 karma given 14:13:16 jjmcd: apart from karma, is there anything else you need from the group? 14:13:34 Oh yes 14:13:37 I forgot 14:13:52 I have a tx problem an need to manually pull translations 14:14:12 so nightly updates won't necessarily get new trans, especially over the weekend 14:14:36 if someone can run a cronjob in the late evening EDT to tx pull and push to f17, that would be a help 14:14:37 jjmcd: sgordon is your backup while you're out of town, right? 14:15:06 bcotton, correct, he should make an RPM if new translations on Sun/Mon 14:15:12 i can take care of the crong job 14:15:21 #action bcotton to run a cronjob in the late evening EDT to tx pull and push to f17 14:15:23 That would be a help 14:15:43 Needs -af to work correctly 14:15:59 jjmcd: if you're around after the meeting, i'll sanity check with you 14:16:09 * jjmcd will email you my script 14:16:27 awesome 14:17:18 might need someone who does NOT have infra privs, tho 14:17:52 jjmcd, ? 14:17:58 * nb wonders why someone who does not have privs? 14:18:17 nb, when I push translations, and ONLY when I push translations, it wants the password for my cert 14:18:28 Which I can't give it in a cron job 14:18:32 pushing them to tx.net? 14:18:39 no, to git 14:18:51 jjmcd, you need to make a ssh key that doesn't have a passphrase 14:19:03 to be able to do that 14:19:11 Yeah, but when I push normally it doesn't ask for it 14:19:23 jjmcd, probably because you have Ksshaskpass or something set up 14:19:25 Only after I have done a tx pull 14:19:27 or the gnome equivalent 14:19:34 interesting. we can discuss after meeting 14:19:53 anything else on Release Notes? 14:20:05 Nope, that's plenty 14:20:11 hah 14:20:19 #topic Guide Status 14:20:35 #link http://rbergero.fedorapeople.org/schedules/f-17/f-17-docs-tree-tasks.html 14:21:19 So we're past the string freeze at this point. Anything that's going to be ready for GA should probably be done. Anything that isn't will come out on it's own schedule 14:21:42 anything on guides? 14:22:05 yes 14:22:12 go ahead Capesteve 14:22:21 I looked through the Wireless guide, just needs 14:22:26 a few screenshots 14:22:32 wil try and do tonight 14:23:18 excellent, thanks for getting that going 14:24:52 #info Capesteve will finish updating the Wireless Guide 14:25:09 anything else on guides? 14:25:22 just a question 14:25:45 how a guide leaves draft state ? 14:25:55 do we still want to convert that one thing from svn to git? 14:26:13 and gor what stand for 'GA'? 14:26:26 for* 14:26:41 claneys: when it's ready. :-) 'draft' is a way to publish docs that are still a work in progress. 14:26:49 * jjmcd still needs to look back in the log and remember what it is, and then get with the BNEers, but that won't happen until after the 22 nb 14:26:55 oh 14:26:57 claneys: GA is "General Availability" 14:26:58 ok 14:27:15 bcotton: thanks 14:27:28 anything else on guides? 14:27:46 i would say just go ahead and convert it to git :-) 14:28:02 nb Do you mean Wirelss Guide? 14:28:02 #topic RN location 14:28:12 I will go get a look about user guides, see if it is ready, so :) 14:28:16 #link https://bugzilla.redhat.com/show_bug.cgi?id=694075 14:28:28 Capesteve, yeah i think so? 14:28:34 did we come to a decision about this or are we going to ignore it until after F17 is out? 14:28:52 jhradilek: can help me 14:28:57 with git repo 14:29:01 I've to leave, see you 14:29:31 * jhradilek nods. 14:30:15 bcotton, I just filed a bug to myeslf to remind me 14:30:32 jjmcd: re: RN location? 14:30:48 Yes 14:31:01 okay, do we need to keep it on the agenda, or can i let it drop? 14:31:03 We decided that we would make a note in the RNs that they will move next release 14:31:12 okay, great 14:31:47 To the normal doc location /usr/share/doc/fedora-release-notes-18.0.0 14:31:59 #agreed We decided that we would make a note in the RNs that they will move next release 14:32:07 #topic Open Help Conference 14:32:13 #link http://openhelpconference.com 14:32:20 #info Open Help Conference is Aug 11-15 in Cincinnati, OH 14:33:15 anything on the OHC? 14:33:59 #topic Outstanding BZ Tickets 14:34:05 #link http://tinyurl.com/lbrq84 14:34:28 we do have an urgent ticket to merge fr_FR into fr 14:34:33 #link https://bugzilla.redhat.com/show_bug.cgi?id=816765 14:35:21 bcotton: i think this is not only about fr_FR, but about other duplicated lang codes as well 14:35:31 meaning: lots of work :-( 14:35:33 looks like rudi's been assigned to it, but there's been no updates 14:35:45 pkovar: well of course it is. :-) 14:35:58 there are still many guides around with duplicated lang codes 14:36:35 if anybody is willing to work on those, i can assist, but my spare time is rather limited 14:36:54 anyway, i still remember the procedure 14:37:01 with the tx tool 14:37:06 pkovar: do you have a list that we can add to the ticket? 14:37:44 bcotton: no, i was checking the transifex project links in the guides table on the wikik 14:38:22 I can poke him tomorrow and ask him about it 14:38:24 i think burning isos is one of those guides 14:38:52 too 14:39:31 i will comment on that bug 14:40:18 awesome 14:40:51 are there any other issues you want me to ask rudi about? 14:41:15 lnovich: probably, but nothing comes to mind 14:41:39 lnovich: maybe ask him about the fedora installation guide too? 14:41:45 as I am new to this group - let me just say hello and I am a RH tech writer, looking to enter into the Fedora pool 14:42:10 it hasn't been pushed to transifex yet, AFAICT 14:42:18 lnovich: welcome to the club. i'll reply to your email post-meeting :-) 14:42:32 lnovich: welcome, and thanks :-) 14:42:36 NP! 14:43:08 anything else about open bugs? 14:43:58 #topic Open floor discussion 14:44:38 anybody has any comments re http://www.fedorareloaded.com/instructions.html ? 14:45:04 has anybody tried playing with it? 14:45:12 yes 14:45:23 share your thoughts on the docs list :-) 14:45:54 we were asked to test it 14:45:56 it works 14:46:01 #info comments on http://www.fedorareloaded.com/instructions.html welcome 14:46:21 will try to make use of it and give more feedback 14:47:37 we were asked : i.e. those in the fedora channel a few hours ago 14:47:54 i started looking at it 14:48:03 it's always a good idea to share your feedback via the list so more people can comment 14:48:04 #info Thursday is the Release Readiness meeting. bcotton plans to report "yeah, we're ready" 14:48:27 by when do you need to receive feedback? 14:49:23 lnovich: i'd say ask jwulf 14:50:13 ok we spoke earlier today 14:50:24 the fudcon hackfest is scheduled for the next week, i think 14:51:42 may 18 -20, yes 14:52:03 this week's friday then :-) 14:52:57 ok will take a look this week before Thurs 14:53:11 anybody here planning to participate remotely? :-) 14:53:31 lnovich: great, thanks 14:55:35 okay, we've only got 5 minutes left. anything else that needs to be brought up quickly? 14:56:35 hearing crickets 14:56:38 #endmeeting