14:00:09 #startmeeting Docs Project Meeting - Agenda: http://fedoraproject.org/wiki/Docs_Project_meetings 14:00:09 Meeting started Mon May 28 14:00:09 2012 UTC. The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:36 #meetingname Fedora Docs 14:00:36 The meeting name has been set to 'fedora_docs' 14:00:40 #topic Roll call 14:01:23 well this is awkward 14:01:28 * pkovar is here 14:01:43 yay! i'm not alone 14:01:46 * sgordon is here 14:02:03 bcotton a meeting on a US holiday is always an issue 14:02:42 kk4ewt: yeah, but it seems like half of our attendees lately are non-us, so i though we'd have a slightly larger crowd. oh well 14:02:52 * jjmcd 14:05:21 okay, it's 5 minutes after, let's go down the list 14:06:03 we had no action items last week, so... 14:06:04 #topic Release Notes 14:06:12 #link https://fedoraproject.org/wiki/Release_Notes_schedule 14:06:20 #info GA is *tomorrow* 14:06:38 yepper 14:07:07 at this point, i guess everything there is to say about RN has been said? 14:07:09 I'll try to make an RPM for the repo today or tomorrow, and also deal with the bugs in the en-US for docs.fp.o 14:07:30 Been holding off so as to not corrupt translations so far 14:09:19 well if i may speak on behalf of everyone, thanks for doing either a great job or at least sufficiently hiding the sausage-making :-) 14:09:24 * nb here (but i don't have anything to day) 14:09:34 to say 14:09:55 Wish I could have been more on top of it, but RL keeps getting in the way. 14:10:27 it happens. sounds like things are interesting up in michigan these days 14:10:32 Right now getting morning briefing notes to my staff as we speak. Even tho we havn't done a lot, this fire is eating a lot of my time 14:11:46 does anyone have anything more re: release notes, or should we let jjmcd get to more important work? 14:12:08 I hope to be looking for karma before too long 14:12:53 okay, i'll karma the crap out of it when it's ready 14:13:01 +1 14:13:43 anything else on RN? 14:14:01 #topic Guide Status 14:14:44 anything to say on guides? pkovar, you've been cat-herding some of them 14:15:27 I plan to release the software collections guide later this week 14:15:48 #info pkovar will release teh Software Collections Guide later this week 14:15:49 that's awesome 14:16:22 probably under the fedora contributor docs 14:16:28 does anyone know offhand where we stand with the Inst. Quick Start Guide, Installation Guide, and User Guide? 14:16:48 i think installation guide we would have to ask rudi or jack reed 14:16:52 not sure about the others 14:17:19 i think that jreed is also working on the Inst. Quick Start Guide 14:17:48 user guide has seen some significant improvements 14:17:57 excellent 14:18:01 but not sure whether it is ready for release 14:18:07 probably not 14:18:38 anybody here has been working on this guide recently? 14:20:18 we might want to release live images and burning isos as well this week if anybody has checked them wrt f 17 updates? 14:20:38 ooh ooh i did that 14:20:47 i never branched them or anything, but the master is up to date 14:21:03 #action bcotton to branch and publish Live Images and Burning ISOs 14:21:22 great, thanks 14:22:35 anythign else on guides? 14:22:52 anyway, i think i will publish the user guide in the draft category this week if everybody agrees :-) 14:23:27 pkovar: do you think it's in a state where we can call it f17 and then make further updates 14:23:41 i'm concerned that if it goes into the draft category our target audience won't find it 14:24:19 bcotton: i will ask romain as he has been working on the guide recently 14:24:50 pkovar: sounds good. either way, it's better that we publish something than nothing :-) 14:25:00 agreed :-) 14:25:52 sgordon: if i were to #topic the koji proposal, would you be comfortable saying a few things about it on the record? 14:26:33 i can try sure 14:27:03 okay, well then since we're already talking about guides, it's a good lead-in to 14:27:17 #topic using koji to build docs.fp.o 14:27:30 so i am not sure if jjmcd got a chance to talk to rudi much further about it 14:27:43 but in theory the way such a system works is that either: 14:28:14 1) you build a SRPM using publican and send that to koji or 2) you use an option to publican that does both in one step 14:28:27 then koji builds the RPM(s) in a consistent manner 14:28:48 generating both a desktop RPM which you don't have to deploy but you can, and a web RPM 14:29:05 the same would happen for translations, basically it would replace the way we publish to web.git now 14:29:37 the web server would then be teed up to pick up packages built in this manner, and install them based on highest NVR as they become available 14:29:53 you can use tags to separate drafts and published guides etc if you want to set it up that way too 14:30:25 and this is what Red Hat does for their docs site, right? 14:30:29 that's correct 14:30:39 in our case there is an internal server where the drafts go 14:30:50 then when they are tagged with a certain tag they go to the live sit 14:30:52 *site 14:31:39 there are some issues to resolve with getting everyone set up with the right perms in koji, but it didnt seem like that big an issue when dgilmore and jjmcd were discussing it the other day 14:32:06 last i saw rudi was going to check up with one of the internal rel-eng guys just to clarify exactly what we need to ask their fedora equivalents for in a ticket 14:33:09 this sounds like a good idea overall, and i expect we'll have more conversation in meetings and on the list in the coming weeks. any questions for right now? 14:33:54 If there is something specific you want me to ask Rudi, let me know 14:34:07 I will be meeting w/him tomorrow morning 14:34:47 i think jjmcd already asked him on irc late last week 14:34:54 he just needs to follow up with marco 14:35:07 and yes, it's a very sensible idea 14:35:10 and probably about time 14:35:29 having to clone the web.git repo is definitely a barrier for people wanting to publish 14:35:45 even here in the office i find it a pain at times 14:37:31 anything else on this topic? 14:37:58 #topic Open Help Conference 14:38:07 #link http://openhelpconference.com 14:38:13 #info Open Help Conference is Aug 11-15 in Cincinnati, OH 14:38:22 i don't expect there's anything else new to discuss this week? 14:39:10 #topic Docs Leader elections 14:39:34 it's a tradition in Docs that at the end of each release, the leader offers up the throne to other willing participants 14:40:08 i'd hate to be the one to break this tradition, so i'll be posting a note to the list this week calling for volunteers/nominations 14:40:12 It is also the tradition that nobody raises his hand 14:40:22 LOL 14:40:26 jjmcd: so true. people usually get shoved in front of the train 14:41:01 if no one steps forward, i'll gladly keep going. if one person steps forward, they are the designated victim. if more than two people step forward, we'll get an election set up 14:41:11 #action bcottn to solicit docs leader candidates on mailing list 14:42:04 #info volunteer/nomination deadline for docs leader will be the start of the Monday, 4 June Docs meeting 14:42:55 #info 0 volunteers = continuing the bcotton era, 1 volunteer = a winner, 2+ volunteers = election/cagematch 14:43:19 so. having said many words, does anyone have any questions? 14:43:25 or comments 14:44:15 #topic Outstanding BZ Tickets 14:44:36 #link http://tinyurl.com/lbrq84 14:45:36 i think we have fewer than we started the release cycle with, so that's a good thing, right? 14:46:31 give it a week or two ;) 14:46:47 sgordon: can't we just bask in the lower bug count for now? 14:47:36 #topic Open floor discussion 14:48:46 wow. nothing this week? that's amazing 14:50:13 thanks to everyone for your work on this release. we've had some new people join the mailing list in the past few weeks, so let's see if we can take advantage of the post-release lull to get them spun up 14:50:36 #info everyone is awesome. enjoy your beefy miracle 14:50:45 #endmeeting