14:01:32 <randomuser> #startmeeting Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/D
14:01:32 <zodbot> Meeting started Mon Mar 25 14:01:32 2013 UTC.  The chair is randomuser. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:32 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:01:40 <randomuser> #meetingname Fedora Docs
14:01:40 <zodbot> The meeting name has been set to 'fedora_docs'
14:01:45 <randomuser> #topic Roll Call
14:02:00 * shaiton Kévin Raymond
14:02:00 <suehle> beep
14:02:30 * jjmcd 
14:02:50 * pkovar is here
14:04:10 * rbergeron pops in
14:04:59 * randomuser bumps rbergeron's topic up the schedule
14:06:13 <randomuser> hello, everyone
14:06:21 <randomuser> let's get started
14:06:39 <randomuser> #topic Follow up on last week's action items
14:07:15 <randomuser> we had one of these - lnovich was going to touch base with rudi about the proposed publishing platform, and she did
14:07:59 <randomuser> #link http://lists.fedoraproject.org/pipermail/docs/2013-March/014873.html
14:08:17 <randomuser> Did anyone get a chance to read over rbergeron's email from this morning yet?
14:08:59 <suehle> yup
14:09:31 <randomuser> me too
14:11:19 <rbergeron> it doesn't have to be a topic necessarily - i figure folks will likely respond when they rae functioning later today :)
14:11:31 * rbergeron thinks there is a similar topic on deck for today anyhow from mmaslano
14:11:31 <randomuser> yeah, that's fair
14:12:02 <nb> hi
14:12:08 <randomuser> we can come back to it if someone wants to
14:12:14 <randomuser> morning, nb
14:12:28 <randomuser> #topic Docs Infrastructure
14:13:16 <randomuser> I managed to catch a moment of rudi's time last week, and he clarified some of the confusion I had about the new publishing platform
14:14:21 <randomuser> publican is handling everything from initial packaging to public deployment, with a repo as a conduit for the content - as many of you are probably already familiar with
14:15:07 <randomuser> rudi is going to work up some process docs, i believe, and we, as a group, will have a fair amount of effort to expend in building our legacy guides with publican3
14:15:18 <randomuser> although he didn't think we should start on that yet.
14:15:51 <randomuser> Are there any other thoughts on the topic?
14:16:26 <shaiton> thx for the update
14:16:53 * randomuser nods
14:18:42 <randomuser> No comments? Let's talk about beats instead.
14:18:48 <randomuser> #topic Beat Assignments
14:19:01 <randomuser> #link https://fedoraproject.org/wiki/Category:Documentation_beats
14:20:39 <randomuser> I've pulled unconfirmed names from the table, and it's looking sparse now
14:21:30 <randomuser> If you can grab another beat, or you have a friend in the project might be able to pitch in, now is the time to get started
14:23:21 <randomuser> The beats are very much a 'many hands make light work' kind of task - so please don't get intimidated about putting your name down for one. Even if you add just one factoid, the end product is improved.
14:25:18 <randomuser> tough crowd today...
14:25:34 <randomuser> #topic Planning Process
14:25:45 <randomuser> #link https://fedoraproject.org/wiki/User:Mmaslano/Feature_process
14:25:50 <randomuser> #link http://lists.fedoraproject.org/pipermail/docs/2013-March/014857.html
14:26:32 <randomuser> We've been asked to review the proposed feature/changes/planing process(es) to verify our role and scope
14:27:15 <randomuser> We haven't had much to say about it thus far, but here's a reminder anyway
14:29:15 <randomuser> Let's move on to bugs, then
14:29:15 <rbergeron> I think the only thing I've ever really seen (from the feature wrangler POV, as well as mktg/docs stuff)
14:29:29 <randomuser> oh, go ahead
14:29:42 <rbergeron> is that ... a lot of stuff that gets dropped at the last second ... those drops wind up sometimes not making their way back to release notes, etc.
14:29:59 <rbergeron> Esp. stuff that is granted exceptions, etc.
14:31:10 <randomuser> there were a few bugs filed to help us out with that last time, but we probably should have a review/verify process
14:31:11 <rbergeron> So it might be worthwhile to have some sort of minor checkpoint for "double check that all the stuff that's about to be printed in RN" or etc. is really still valid.
14:31:42 <rbergeron> yeah, stuff falls through the cracks. People remove their own features, all sorts of wacky things.
14:32:17 <randomuser> hmm... Perhaps I - or someone more familiar - can find where we can fit that into our process docs
14:33:31 <randomuser> although I suspect the greater problem is lack of cycles, not lack of process
14:34:12 <rbergeron> yeah
14:35:20 * rbergeron just offers it up as a thought :)
14:35:59 * j_dulaney lurks until the QA meeting
14:35:59 <randomuser> thanks, I will repeat the thought
14:35:59 <randomuser> #topic Outstanding BZ Tickets
14:35:59 <randomuser> #link http://tinyurl.com/lbrq84
14:35:59 <randomuser> We've got bugs!
14:37:13 <randomuser> here's a good one: https://bugzilla.redhat.com/show_bug.cgi?id=904083
14:37:32 <randomuser> is the storage administration guide obsolete?
14:38:29 <randomuser> perhaps not the best venue to pose the question
14:38:59 <randomuser> #topic Open floor discussion
14:39:22 <shaiton> I've got one topic :)
14:39:32 <randomuser> #chair shaiton
14:39:32 <zodbot> Current chairs: randomuser shaiton
14:39:35 <randomuser> go ahead :)
14:39:46 <shaiton> no need for that, Open floor is fine
14:39:49 <shaiton> http://lists.fedoraproject.org/pipermail/docs/2013-March/014869.html
14:39:50 <shaiton> ;)
14:40:09 <shaiton> could we go ahead and remove those teams? Finally. It pollutes fedora.transifex.com
14:40:32 <randomuser> nb, do you have time to help shaiton with this?
14:40:57 <nb> what is needing to be done?
14:41:16 <randomuser> thre are duplicate or overlapping transifex translation teams
14:41:29 <shaiton> nb: we need to merge what has to be, and then delete the old language code teams. That's... more than 2 years old.
14:41:30 <randomuser> shaiton, you have a script to fix it, iirc?
14:41:56 <nb> shaiton, i was just looking at the message, so you just need me to add you to maintainers for those?
14:42:28 <shaiton> randomuser: yep, just need to have the maintainer access at transifex. But I would prefere not to do it with the script. manually is best as this script is 1 year old... :D. In fact the actual script is nice to know what we have to do
14:42:43 <shaiton> nb: could work yeah
14:43:03 <shaiton> or just having someone else do it. But since I know what has to be done, that should be faster.
14:43:53 <shaiton> nb: http://paste.fedoraproject.org/5974/42226171/ the projects that need merge
14:44:31 <shaiton> I only checked the one under the fedora-docs release. There should be more. But will find them later quickly. (if they are some other hidden).
14:45:40 <randomuser> shaiton, iirc, there are a handful of bugs to merge trans teams floating out there, can you clean those up while you're at it?
14:46:11 <shaiton> randomuser: sure, I have already few of them on my tabs... But many are from me. ah ha
14:47:16 <randomuser> i saw they were fr, thought you might be involved. self-service at it's best!
14:48:00 <shaiton> yep ;)
14:48:05 <shaiton> that should be all for me
14:48:09 <shaiton> thanks
14:48:29 <randomuser> thanks, shaiton
14:48:36 <randomuser> anything else?
14:48:53 <randomuser> we'll give the group a couple more minutes before we close up shop
14:50:09 <nb> shaiton, i added you to maintainers for those
14:50:13 <nb> if i missed any, let me know
14:50:26 <shaiton> nb thanks
14:52:11 <randomuser> going once!
14:52:59 <randomuser> well, that's probably counting high enough
14:53:03 <randomuser> #endmeeting