22:28:41 #startmeeting testing 22:28:41 Meeting started Sat Feb 8 22:28:41 2014 UTC. The chair is threebean. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:28:41 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:16 randomuser: Error: Can't start another meeting, one is in progress. 14:00:16 #meetingname Fedora Docs 14:00:16 The meeting name has been set to 'fedora_docs' 14:00:17 #topic Roll Call 14:00:26 * lnovich is here 14:00:40 can't start another meeting !?! 14:00:43 #endmeeting 14:01:00 ahem 14:01:06 15:28:41> #startmeeting testing 14:01:10 hahahah 14:01:25 * Capesteve waves 14:01:33 * jhradilek waves too and leaves. 14:03:16 hang on folks, we'll see if we can get someone to prod the bot 14:03:46 #endmeeting 14:03:54 zodbot, chairs 14:04:00 zodbot, ping 14:04:00 pong 14:04:29 hm. threebean started a test meeting .. and never ended it 14:04:48 throw a bean bag at the bot then 14:05:15 three bean would be a good name for a coffee shop 14:05:16 #chair fenris02 14:06:01 well, we've at least got the greetings out of the way 14:06:11 #topic New Writers 14:06:27 any new writers here today? 14:07:35 guess not 14:07:46 would seem so 14:08:08 #topic Publican and Publishing 14:08:47 this seems like it's getting somewhere; rudi had a staging instance up last week and was doing things behind the curtain 14:12:10 any indication when things will be done? 14:14:19 nb set up a sysadmin-docs fas group, of which rudi is the sponsor 14:14:19 so afaik rudi will work out the scripts to pull in guides from koji, then we'll ansibleate the instance and start publishing guides 14:14:52 ok 14:15:40 what do we plan to do with the old docs.fp.o instance? (and the guides in it) 14:16:10 archive/move to something like docs-old.fp.o? 14:20:05 pkovar, not sure - i'm sure it will stay around until everything is published, and web.git won't go away 14:20:32 #chair lnovich jhradilek Capesteve 14:20:47 I'm battling some weird routing issues here, sorry 14:21:04 all ok? 14:22:09 for some reason, my routing table starts using the wrong interface to access a given host, or drops a route, or forgets the gateway 14:22:12 randomuser: so, are we going to republish *all* guides on docs,fp.o? 14:22:28 pkovar, as I understand it, yes 14:22:46 pkovar, are you suggesting an alternative? 14:22:47 hm, that looks like a lot of work though 14:22:55 yeah. 14:23:20 i would suggest to only republish guides from recent releases 14:23:36 and archive/move everything else 14:23:39 no point anything before F18 14:23:54 I agree 14:23:56 but we can't remove it 14:24:09 there are customers who still use it 14:24:19 lnovich, there are? 14:24:20 i mean people and companies 14:24:40 yup i just helped a company move from F11 14:24:41 maybe set up redirects to an -old instance? 14:25:13 we could migrate over after a given number of guides are published, and see if anyone squawks 14:25:28 although they probably will squawk, but not to us 14:26:17 we could keep just the PDF and trash the HTML - that would save us some space! 14:26:37 ... or vise versa 14:26:42 true 14:27:21 pkovar, if we want to have the old content around, i don't think we should maintain two different workflows, processes, instances, etc and bridge them with a redirect 14:27:53 i think the biggest concern here are broken URLs 14:27:58 easier now, but... 14:29:07 hmm... there are probably error_logs 14:30:52 #action to investigate docs.fp.o httpd error logs 14:31:17 it would be interesting to see what kind of traffic we're getting, anyway 14:32:07 #endmeeting