20:59:53 #startmeeting infrastructure2 20:59:53 Meeting started Thu Feb 17 20:59:53 2011 UTC. The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:59:53 Useful Commands: #action #agreed #halp #info #idea #link #topic. 21:00:23 CodeBlock: Error: Can't start another meeting, one is in progress. 21:00:25 meh 21:00:26 ok 21:00:31 well then 21:00:32 #meetingname infrastructure 21:00:32 The meeting name has been set to 'infrastructure' 21:01:10 Probably better to either use #fedora-admin or #fedora-meeting-X for future meetings, though. 21:01:12 ok so 21:01:21 * skvidal doesn't care 21:01:23 anyway, what did averi want to discuss - wordpress? 21:01:30 And killing it? :-) 21:01:32 ricky: mailing lists, I think 21:01:35 Ah, that too. 21:01:41 #chair skvidal jds2001 21:01:41 Current chairs: jds2001 skvidal smooge 21:01:41 both blog's future and mailing lists 21:01:52 #topic Blogs 21:02:14 I think we have two possibilities at the moment for blogs: 21:02:45 1. update them to something newer avoiding security issues with wordpress-mu being so old 21:02:55 2. remove everything and say goodbye to blogs.fp.o 21:03:03 I thought we already all agreed on 2 :-/ 21:03:21 3. get blogs on wordpress and have blogs.fp.o redirect to those 21:03:22 i thought so too 21:03:33 Or more specifically, 3 21:03:44 smooge, exactly, forgot that point 21:04:00 I believe we agreed to pursue 3. 21:04:01 however 21:04:13 as I have learned this week, communication is important 21:04:22 so until it is communicated, it isn't happening 21:04:53 * ricky has been busy last week or two, but will have time to start that end of this week, hopefully. 21:04:53 What needs to take place to communicate it? 21:04:54 we are in the research phase of it.. so what is the research point for costs and such 21:05:12 One thing. 21:05:14 We need to let the people on blogs know, we need to let the marketing and other groups using it know 21:05:21 Do we think we're at the point where it's reasonable to disable new signups? 21:05:32 we need to let the board know. 21:05:37 I don't want to have to deal with another 20 blogs just because we tok a long time to get this done 21:05:41 *sigh* 21:05:41 ricky: yes 21:05:45 why does the board need to know? 21:05:46 Why must everything be a "ask the board" nowadays? 21:05:47 Seriously. 21:05:56 We run this, and we don't have the resources to run this. 21:06:02 because the board has a blog on it 21:06:05 ricky: +1 21:06:13 OK, then replcae "the board" with "all users" please 21:06:16 oh, well, they're just another user :) 21:06:16 based on the numbers i saw a copule of weeks ago.. a couple more signups won't matter much 21:06:26 and I am not going to have a shitfest again with the tx transition 21:06:40 sijis: Yeah, I just don't want somebody to start relying on the service and then we kind of screw them over a week later 21:06:46 We already agreed on it happening. I say kill signups. 21:07:02 s/it happening/the move to wp.c/ 21:07:20 i actually think we shouldn't redirect from blogs.fp.o -> wp.com. not sure what that will do 21:07:36 so you kill signups and existing folks have time to migrate (or we do it) over 21:07:36 I still wouldn't call that a shitfest (although the timeframe we have for transifex was particularly tight, which means stuff got rushed, yes) 21:07:36 huh? 21:08:39 I think it'd be reasonable to put in blog-specific redirects for some period of time for people who request them. 21:08:40 +1 to kill signups. 21:08:49 +1 to kill signups 21:09:01 +1 to kill signups. 21:09:25 +1 to kill signups 21:09:30 if we do redirect from blogs.fp.o.. for how long then? 21:09:32 +1 to kill signups. 21:09:51 sijis: thats a very low maintainence thing 21:09:52 sijis, redirection will be dependent on how it is done 21:10:36 if we just do it with rewriterules (not sure that's feasible or not), then it can just stay there.... 21:10:58 my only thing with redirects is that it doesn't force folks to change things. we have redirects here that are years old and its only a temp thing but folks are things pointing to old location 21:11:11 sijis: yes, and? 21:11:13 (just ranting a bit.. sorry) 21:11:35 That's a good reason to set a time limit 21:11:58 sijis, websites are like linux api's 21:12:40 I feel your pain.. I had to redirect for 4 different RH websites at one point 21:12:51 hmm 21:12:52 I think the config file was mostly redirects 21:12:55 anyway. 21:13:29 * sijis can disable the blogs registration right now 21:13:33 we have moved that we will kill signups to the blog. 21:13:45 sijis: Great, thanks1 21:13:48 so go ahead. if I get blowback I will let you know 21:13:49 #agreed willing blog signups in preparation for move to wp.c 21:13:55 * CodeBlock wonders if he needs to be a chair to do #agreed 21:14:07 and killing* not willing 21:14:08 * CodeBlock failed that up 21:14:13 *anyway* 21:14:20 * sijis registrations disabled 21:14:46 i'm not sure if we #startedmeeting 21:14:50 in that case 21:15:04 #action sijis killed blog registration in preparation for move to wp.c 21:15:08 ;D 21:15:19 sijis: yeah, I think smooge did 21:15:33 because he added a few chairs above 21:15:34 we can't start another meeting, one is running already 21:15:47 ok so what else 21:15:54 #topic hosted mailing list pruning 21:16:11 I gave a look at the hosted mailing list and http://averi.fedorapeople.org/inactive_lists.hosted.txt 21:16:11 * CodeBlock isn't a chair, and zodbot isn't op'd and the channel is +t so that is completely pointless. BUT ANYWAY. 21:16:38 #action sijis killed blog registration in preparation for move to wp.c 21:16:41 I've found out dozens of lists are unused and inactive since some time now 21:16:44 it will be in the logs 21:17:10 point is what should we do with them? and what's the current policy for new lists there to avoid people making new lists with no point? 21:17:26 We can ping list owners and ask them if they're still needed. 21:17:50 to put some context on this 21:17:50 We could also ping with an "if you don't respond in X, we'll delete the lists (but not the archives)" 21:17:52 196 total lists 21:18:06 76 of them have no messages 21:18:10 56 more no messages in 2011 21:18:26 Before doing something like that, I think it'd be good to investigate how easy it is to restart a deleted list 21:18:28 averi: I'd be fine with a "If your list goes inactive for 60 days or more, it will be considered for deletion" policy, personally. 21:18:29 The main reason I would want to clean up lists: we are making "free spam" websites for people finding unused lists, signing up, and filling up stuff and then sending bit.ly urls out the woods 21:18:42 ricky: maybe in lieu of deleting them 21:18:48 ricky: we could consider closing them 21:18:53 ricky: which means no new posts 21:18:53 CodeBlock, yup 21:18:55 skvidal: what about lists with no messages since 6 months ago, August 17, 2010? 21:18:55 Perhaps hosted lists have turned into something people just request automatically when making a project. 21:18:56 but the archives persist 21:19:12 skvidal: Ah, and it's easy to go from closed -> active if we somehow need to do so? 21:19:20 ricky: you can just reopen the list 21:19:31 ricky: in the mailman config 21:19:39 So maybe we can make it clearer on the hosted pages "please only request a list if you'll actually use it" 21:19:42 Cool. 21:19:53 Or "if you have <3 developers and 0 users, you probably don't need a list yet" 21:20:08 +1 contact list owners with no traffic in 3+ months. Close off lists versus delete 21:20:23 worksforme. 21:20:43 if no answer from owner in 14 days list is closed 21:20:46 * ricky signs at the amount of time we need to spend cleaning up crap. Not much else to do though I guess. 21:20:58 Er, sorry, I misphrased that second sentence 21:20:58 ricky: there are other projects 21:21:01 "Not much choice though" 21:21:02 correct. it is why we get paid the big bucks 21:21:07 and averi lemme ask you a question 21:21:12 averi: is this something you would like to work on? 21:21:17 averi: helping us clean up the lists? 21:21:26 averi: b/c if you would I'd +1 to giving you list admin access right now 21:21:29 There are definitely other projects - didn't mean to say that :-) 21:21:31 smooge: See you can say that being an RH employee. Some of us can't. 21:21:32 :P 21:21:43 CodeBlock: trust me - he can't :) 21:21:47 I got paid the big bucks to do this when I was a volunteer 21:21:49 skvidal, sure, it was part of my cleanup duty started yesterday :) 21:22:02 anyone else object to averi working on the above project? 21:22:06 its all confederate money 21:22:17 OK, so the group would be sysadmin-tools - I'd b ehappy to sponsor 21:22:26 skvidal, averi is there a ticket number for this? 21:22:34 ricky: tools? 21:22:48 smooge, not yet, I started this off yesterday after a chat with skvidal 21:22:51 -hosted, no? 21:22:58 Oh, never mind, I was thinking lists.fp.o, sorry. 21:23:03 averi: can you make a ticket and we'll get it underway 21:23:11 skvidal, sure 21:23:20 And he's already in -hosted, great. 21:23:24 ricky: yep :) 21:23:41 * CodeBlock sponsored him yesterday. He's my first sponsoree. I think. 21:23:45 * nirik thinks a 'inactive list sop' might be good too. ;) Just sayin... 21:24:14 nirik: I can draw that up today 21:24:28 averi: so since you're in -hosted 21:24:33 well at least with the rules. I'm not sure how to actually close lists yet 21:24:54 averi, put in a ticket to cover this please.. just list what you are doing, what you found and track progress in it. 21:25:10 smooge, ok, will do after meeting 21:25:17 thanks 21:25:40 and an SOP will definately be needed. 21:25:45 ok anything else? 21:25:56 one thing 21:26:01 #topic one thing 21:26:14 ricky: are you looking for another project to help with cleanup that's not just browsing and deleting? 21:26:30 smooge, sure, I am full of stuff for uni, so please remember it will take a bit for me to complete the SOP and the whole work 21:26:39 Sure, why not :-) 21:27:12 smooge, guess we don't need to rush on this anyway :) 21:27:12 averi: of course 21:27:15 * CodeBlock accidentally laughs out loud in the completely quiet building he is in ($dayjob) at smooge's #topic 21:27:33 ricky: how about working on the db/script for tracking publictest instances/shutdowns 21:27:52 right now if it were just a cron job which sent out 'shut it down' notices 21:27:53 it would be fine 21:27:58 just need the data 21:28:29 I haven't had a chance to get to this 21:28:38 Sure thing, I'll take a look 21:28:42 and it seems like something which could benefit us for nuking the publictest boxes 21:29:07 * ricky is thinking a simple sqlite database that lives on puppet01 somewhere. 21:29:15 With a spam cronjob 21:29:29 +1 21:30:22 okay 21:30:27 another task for someone 21:30:34 does someone want to change the sudoers for publictest* 21:30:40 so sysadmin-main is password-less? 21:30:50 sure 21:31:01 I'd be happy to make my first private repo commit :) 21:31:31 Woo, glad to finally have that 21:31:56 CodeBlock: make it so 21:31:57 skvidal: Will do that tonight/next time I get on my laptop..which is now the only place that my ssh key resides. 21:32:03 pretty much 21:32:10 I'm looking at this list 21:32:10 https://fedoraproject.org/wiki/Infrastructure_Cleanup_Tasks_2011 21:33:02 ok 21:33:22 that's all I had 21:33:26 thanks 21:33:30 Ok .. so things I have to do tonight - aside from precalc homework: Start on a SOP for FH list removal, make -main have passwordless sudo on ptXX 21:33:45 got it. :) 21:33:56 :) 21:34:15 * CodeBlock really needs to find that cli todo program he used to have.. it was really good. :( 21:34:36 * ricky uses vim-outliner - I think abadger1999 and lmacken use it as well. 21:34:47 Er, I mean vim-vimoutliner 21:34:55 smooge: Want to #endmeeting? 21:35:22 #endmeeting