17:59:53 <smooge> #startmeeting
17:59:53 <zodbot> Meeting started Thu Jun 21 17:59:53 2012 UTC.  The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:59:53 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:03 <smooge> #chairs smooge skvidal ianweller
18:00:12 <smooge> #chair smooge skvidal ianweller
18:00:12 <zodbot> Current chairs: ianweller skvidal smooge
18:00:14 * relrod here
18:00:17 * lmacken 
18:00:20 * ianweller here
18:00:22 * skvidal is here
18:00:30 * cyberworm54 here
18:00:36 <smooge> ianweller, what is it to say what meeting this is?
18:00:42 * whiterhino is here
18:00:45 <ianweller> #meetingtopic Fedora Infrastructure
18:00:46 * pingou not here
18:00:47 * jaysonr here
18:00:50 <ianweller> i guess that was it!
18:00:55 <relrod> and #meetingname
18:00:58 <ianweller> yeah
18:01:02 <ianweller> #meetingname fedora infrastructure
18:01:02 <zodbot> The meeting name has been set to 'fedora_infrastructure'
18:01:18 * ingm4r is here
18:01:22 <smooge> #topic New folks introductions and Apprentice tasks.
18:01:24 * rossdylan is here
18:01:38 <smooge> thank you for coming to the $name meeting
18:01:39 * threebean is here!
18:01:58 <smooge> sorry for my lack of organization.. it has been over a year since I ran this :)
18:02:14 <smooge> Who is new here and would like to say what hteir skills are?
18:02:26 * jaysonr says hi!
18:02:37 <smooge> hi jaysonr
18:02:39 <jaysonr> I'm new - willing to help where I can, not sure where to start
18:02:42 <cyberworm54> I am not new but I am an apprentice :)
18:02:52 <jaysonr> kevin added me as an apprentice already
18:03:13 <smooge> hi cyberworm54 could you help out with things jaysonr might need to do and read?
18:03:50 <jaysonr> cyberworm54: i've looked at the easy-fix tickets, but didn't know what else to look at.
18:04:16 <cyberworm54> jaysonr: have you looked at the network diagram?
18:04:30 <jaysonr> i've been using desktop linux for 11 years, but have been a windows admin at work - finally convinced those at be to switch more and more systems to linux, so just learning linux 'sysadmin' skills
18:04:39 <jaysonr> cyberworm54: i have not
18:05:16 <smooge> jaysonr, ok after the meeting we will get you squared away.
18:05:24 <jaysonr> awesome - that's guys
18:05:26 <smooge> thank you very much for your time
18:05:36 <smooge> any other new people?
18:05:37 <rossdylan> I am not really new, But I am redhat intern working on Fedora badges
18:05:37 <jaysonr> thanks*
18:05:53 <rossdylan> figured I would introduce myself again get the official process going
18:05:56 <smooge> cool rossdylan you will be up for a status report next :)
18:05:59 <sdrfed17> hey this is my second fedora-infra meeting, looking for apprentice tasks
18:06:04 <ingm4r> cyberworm54 I woul like to see the network layput, too
18:06:33 <smooge> if the apprentices could pm your email addresses I will email out stuff after the meeting
18:06:40 <cyberworm54> sure will post link after the meeting
18:06:45 <cyberworm54> :)
18:06:50 <ingm4r> thx
18:06:51 <cyberworm54> or smooge will
18:07:00 <smooge> or cyberworm54 will :)
18:07:03 <skvidal> http://skvidal.fedorapeople.org/hidden/fedoraservices.png <-- this is sorta what it looks like
18:07:13 <skvidal> actually I need to edit this - we've fixed a bunch of things
18:07:27 <skvidal> http://skvidal.fedorapeople.org/hidden/fedorasvcsfuture.png <-- getting closer to
18:07:36 <smooge> you forgot the sacrifice table for getting things to work when all else fails
18:07:40 <ingm4r> I hope the  "This needs work" Cloud :)
18:08:25 <threebean> skvidal: those are so frelling helpful.  honestly.
18:08:41 <cyberworm54> there is another that is simplify
18:08:45 <sdrfed17> smooge: do i need to give my email-address here
18:08:59 <skvidal> threebean: I need to edit up the first one - we really have fixed a number of the horrible dependencies
18:09:01 <skvidal> especially fas
18:09:14 <smooge> sdrfed17, no I will contact you after meetin
18:09:24 <smooge> we can talk in #fedora-admin then
18:09:28 <sdrfed17> smooge: ok thanks
18:10:46 <smooge> #topic Applications status / discussion
18:11:07 <smooge> threebean, abadger1999 rossdylan this is your section I believe
18:11:54 <sarabande> hi, I have a question about testing varnish, ticket #3294
18:11:57 <threebean> I've been working on ssl stuff for fedmsg.  There's a place here to discuss the code if you'd like to help critique it ( https://github.com/ralphbean/fedmsg/pull/38 )
18:12:20 <threebean> I'm filing a ticket with infra right now to discuss the other more sysadmin-y side of things.
18:12:36 <smooge> sarabande, I will add that to the meeting later
18:12:49 <sarabande> ok, thanks
18:12:50 * relrod has a tiny bit of an update on the fedorahosted app, it's pretty much ready for testing, I talked to nirik yesterday and he said I was fine to test on hosted01 and hosted02 before we migrate to those. I'll be doing that probably later today/tomorrow/start of next week.
18:12:55 <abadger1999> threebean: That code looked interesting, in a good way :-)
18:12:56 <threebean> I can go into it more now if anyone would like, otherwise you can comment in those two places or join the conversation in #fedora-apps
18:13:08 <threebean> abadger1999: flattering.  Thanks :)
18:13:33 <smooge> threebean, is there a 10k view of what it will accomplish?
18:13:40 <threebean> smooge: 10k?
18:13:46 <skvidal> threebean: 10k foot
18:13:49 <skvidal> threebean: high level
18:13:55 <smooge> sorry
18:14:09 <skvidal> smooge: it signs each msg leaving fedmsg with an ssl signature of that host
18:14:09 <threebean> sorta.  one second.
18:14:18 <skvidal> so any receiving host can say 'oh this msg came from that host'
18:14:30 <skvidal> threebean: sorry - is that a good enoug summary?
18:14:43 <threebean> skvidal: that's it :D
18:14:48 <smooge> OMG. that is fantastic.
18:15:07 <threebean> The docstring at the top of this file adds only a little more -- https://github.com/ralphbean/fedmsg/blob/feature/crypto/fedmsg/crypto.py
18:16:11 <smooge> having tried that a looooooong time ago and run into your CPU is 10 years too slow to make this viable
18:16:43 <threebean> ha :D
18:16:56 <skvidal> threebean: it still makes me feel like we could benefit from having a special fedmsg-communication key - hell - maybe even a separate certificate authority for it
18:17:10 <skvidal> threebean: b/c then, ostensibly, we could hand out app-specific fedmsg keys
18:17:31 <skvidal> so instead of knowing that a message was sent by proxy01 we'll know it came from apache inside proxy01
18:17:48 <smooge> I also learned that if you are trying to do crypto in awk.. you are definately doing it wrong :)
18:17:53 <skvidal> obviously we could end up with an arseload of certificates
18:18:05 <skvidal> which might be a giant pain to manage but....
18:18:10 <skvidal> anyway - just a fleeting thought
18:18:15 <threebean> For everyone who missed the earlier conversation:  we were planning on using the keys/certs already in place from puppet to do fedmsg authn.  That way there'd be a minimal impact to set it all up.  The blocker is that the keys are owned by puppet and so how do we make them readable for apps that need to send messages, but not to joe-user or eve-attacker.
18:18:33 <smooge> actually having a seperate key authority would be good
18:18:56 * skvidal grumbles
18:19:04 <smooge> in case we go with the "Seth get to pour kerosene on ruby" strategy
18:19:08 <threebean> smooge: I totally defer to you guys on that question.  I don't have any sense of scale as to how difficult that would all be to setup/maintain.
18:19:27 <skvidal> threebean: it REALLY sucks that gnupg is such a giant pig to use as an api
18:19:42 <skvidal> b/c signing individual messages is EXACTLY where we could use it
18:19:55 <threebean> skvidal: I can always write a wrapper and save the world :)
18:20:03 <skvidal> threebean: have you looked at gpgme?
18:20:09 <threebean> I'll look into it.  I wrote it off weeks ago when we first started looking at puppet certs.
18:20:14 <skvidal> threebean: it makes me want to die inside
18:20:14 <threebean> skvidal: nope :)
18:20:15 <smooge> threebean, I thought that was skvidal's job now he doesn't do yum anymore
18:20:32 <skvidal> smooge: I did the gnupg stuff in yum - it makes me so very sad
18:20:57 <skvidal> threebean: after the meeting - we should talk about it a bit
18:21:02 <skvidal> it may just be crackrock
18:21:09 <skvidal> but sometimes that's handy to establish
18:21:19 <threebean> cool :)
18:21:22 <smooge> and make sure there is enough to share.
18:22:12 <smooge> rossdylan, how goes the fight club trophy program?
18:22:16 <rossdylan> I believe it is, the fedbadges project is going very well, I am working on packaging up everything up so I can eventually push it into staging. So far only one package has made it to updates-testing, the rest are waiting on dependancies. We also have a wiki page for Fedora Badges (https://fedoraproject.org/wiki/FedoraBadges) and a github for badge ideas (https://github.com/rossdylan/Fedora-Badges-Ideas).
18:22:49 <rossdylan> basically the core system is ready for deployment, I just need to package it all up
18:23:03 <threebean> .fasinfo rossdylan
18:23:04 <zodbot> threebean: User: rossdylan, Name: Ross Delinger, email: rossdylan@csh.rit.edu, Creation: 2012-06-04, IRC Nick: rossdylan, Timezone: UTC, Locale: en, GPG key ID: , Status: active
18:23:07 <zodbot> threebean: Approved Groups: fedorabugs packager cla_done cla_fpca
18:23:09 <smooge> cool I will get with you since I put this down as something I am supposed to help people with this quarter :)
18:23:22 <rossdylan> alright cool
18:23:46 <threebean> smooge: cool, I've been helping with the app dev side of things (but not much.. rossdylan has it on lock).
18:23:47 <smooge> rossdylan, just to clarify who have you been working with so far?
18:24:00 <smooge> and that answers my question :)
18:24:00 <threebean> smooge: he'll need fi-apprentice rights to start poking, I think.
18:24:06 <smooge> okiedokie
18:24:07 <rossdylan> yup
18:24:57 <rossdylan> right now I am blocking on the need for python-pyramid to be updated from 1.1.2 to 1.2dev
18:25:23 <smooge> ok that is in EPEL updates-testing or F-something?
18:25:32 <lmacken> rossdylan: feel free to apply for commit privs on the pyramid stack
18:25:40 <rossdylan> lmacken: k
18:25:53 <threebean> lmacken tried updating it to 1.3 a little while back, but upstream had some major dep switch-a-roos that makes it difficult for 1.3 to coexist with our TG2 stack (I think).
18:26:00 <rossdylan> ah
18:26:02 <lmacken> basically just webob pain
18:26:03 <smooge> lmacken, crap sorry I forgot to ask your status on this..
18:26:12 <abadger1999> So I thought of soething I needed to ask this week.
18:26:42 <lmacken> smooge: no worries... nothing major, I've been doing a lot of bodhi2 hacking behind the scenes. Also trying to fix some bugs in the fedora-packages deployment.
18:26:51 <smooge> ok cool
18:26:58 <smooge> abadger1999, ?
18:27:30 <abadger1999> which seems to tie into this... last year we were porting stuff to TG2 b/c moksha was TG2, f-comm was moksha, and so it was something we'd have to be running for a long while.
18:27:37 <abadger1999> Is that chain of assumptions still valid?
18:27:56 <abadger1999> Or should we skip TG2 for things that are not written for it?
18:27:57 <lmacken> we weren't porting anything to tg2 because of moksha?
18:28:06 <lmacken> moksha doesn't rely on tg2 anymore either
18:28:25 <abadger1999> lmacken: We considered it safe to port to TG2 b/c we'd have to run TG2 apps in infra b/c moksha did.
18:28:26 <lmacken> I also don't see a reason to "skip tg2"...
18:28:39 <abadger1999> lmacken: Right... I thought I heard that in #fedora-apps :-)
18:28:42 <abadger1999> lmacken: welll...
18:28:58 * lmacken writing all new stuff in pyramid, but tg2 is still alive and well
18:29:09 * threebean notes that tg-2.2 comes out july 1st.
18:29:28 <abadger1999> right now it seems we're maintaining apps written against TG1 (early versions w/ SO and kid) TG1 recent (SA + genshi), TG2, pyramid, and flask.
18:29:45 <smooge> so cutting down to a small set would make our webservers happier :)?
18:29:45 <abadger1999> Which means (1) we need to retain knowledge of all of these.
18:29:54 <abadger1999> and (2) that we're maintaing the packages for all of these.
18:30:11 <threebean> smooge: moreso our webapp maintainers ;)
18:30:53 <threebean> abadger1999: I agree.  I think if we can narrow that down to TG2, pyramid, and flask, then I'd be happier.
18:31:12 <threebean> I had to wander into the SO+kid land a while ago and had to take extra time to figure things out.
18:31:20 <lmacken> threebean: honeslty I think we've had more issues with TG2 in production than TG1. mostly dep related though.
18:31:23 <threebean> that said, that older code runs fine
18:31:26 <lmacken> yeah
18:31:29 <abadger1999> threebean: Sure.  But why TG2?  Right now, legacy f-comm (and raffle which I've said is throw-away-able) are the only two TG2 apps?
18:31:40 <lmacken> abadger1999: fedora-packages and tagger are tg2
18:31:49 <abadger1999> ah... I thought they were pyramid.
18:31:58 <lmacken> we don't have any pyramid in prod afaik
18:32:02 <abadger1999> okay.
18:32:09 <threebean> lmacken: agreed.
18:32:11 <abadger1999> So we're adding pyramid to the mix with fedbadges?
18:32:21 <lmacken> and bodhi2 (eventually)
18:32:25 <abadger1999> (and bodhi 2.0?)
18:32:26 <abadger1999> yeah
18:32:58 <lmacken> I just wrote a new pyramid app last night, but I think I'm going to host it on openshift instead of our infrastructure
18:32:59 <threebean> i'll add that the group of Summder Undergraduate Research Fellowship (SURF) students at RIT are all leaning towards pyramid for the Fedora-RPG
18:33:27 <relrod> There's also issues (tests failing) with Flask on el6, the EPEL maintainer said (I was going to take a look, but I haven't yet, and not sure how helpful I'll be with that) -- so if someone wants to take a look at that, that'd be cool. He pushed stuff to the el6 branch of the flask repo.
18:33:27 <lmacken> threebean: no code is supposed to be written this summer for that, but that's another story :P
18:33:40 <threebean> lmacken: ugh.. right?
18:33:45 <relrod> I don't know if I know enough about Flask to be helpful in fixing those.
18:33:55 <lmacken> what flask apps do we have in production??
18:34:01 <threebean> relrod: You seem to know more than any of us :)
18:34:04 <relrod> Nothing in production yet
18:34:14 <relrod> soon the fedorahosted app I've been working on, I hope
18:34:16 <abadger1999> ianweller's got some stuff I think but hosted on openshift.
18:34:16 <skvidal> lmacken: relrod is working on one for hosted admin requests
18:34:27 <lmacken> ah, cool.
18:34:28 <skvidal> lmacken: and i'm working on something for coprs - I'm just doing it on openshift, too
18:34:46 * threebean watches as openshift replaces FI.
18:34:47 <abadger1999> We still need to code for it and mess with the internals if there's bugs inside the framework.
18:34:56 <skvidal> threebean: it's good for testing I will say that
18:35:02 <abadger1999> <nod>
18:35:07 <skvidal> threebean: fire and forget is convenient
18:35:08 <smooge> damn that mmcgrath and his super running openshift
18:35:19 <threebean> :)
18:35:22 <skvidal> well it's not the super-running that is the big feature
18:35:37 <skvidal> the big feature is being able to spin it off trivially and have the apps isolated from each other
18:35:41 <threebean> if we're counting openshift apps, there's the leafy-miracle too.  running pyramid.
18:35:54 <smooge> leafy miracle?
18:35:57 <lmacken> threebean: hah, I forgot about that :)
18:36:05 <lmacken> http://leafy-miracle.rhcloud.com/
18:36:10 <abadger1999> I guess I think we should be counting anything that we're on the hook to support.
18:36:11 <lmacken> threebean & I wrote it
18:36:16 <skvidal> abadger1999: agreed
18:36:55 <threebean> lmacken: side note -- we should plug that radial graph into the 'relationships' tab in Packages.  Or at least provide an external link to the leafy miracle.
18:37:06 <lmacken> threebean: yup, I agree
18:37:52 <skvidal> so...
18:37:54 <skvidal> anything else here?
18:38:04 <threebean> quickly, can we revisit abadger1999's question?
18:38:08 <abadger1999> So if we can say -- leafy-miracle is nothing that we link to or people depend on, etc... we don't need to count it.
18:38:18 <abadger1999> But if we do, then we do need to start counting it.
18:38:23 <abadger1999> yeah..
18:38:33 <smooge> so what items do we want to focus on?
18:38:46 <smooge> s/we/royal you/
18:38:52 <abadger1999> So I'm wondering if we, as a group, can start narrowing down what frameworks we're going to use i nthe future.
18:39:11 <abadger1999> and when we port apps away from TG1, we move to one of those.
18:39:54 <threebean> An outstanding question for me is "what webob version with tg-2.2 require?"  We'll find out soon.
18:39:59 <abadger1999> Logically, I'd like to have One framework that we decide is the one we want.
18:40:07 <abadger1999> But I'm not sure we can get to that point :-)
18:40:33 <skvidal> abadger1999: given the high-churn rate of all the frameworks and the 'ooo shiny' problem of new folks coming in to work on new apps
18:40:42 <skvidal> I'm not sanguine on us getting to one framework
18:41:18 <relrod> abadger1999: Not what you want to hear when you spend 3 weeks coding a fedorahosted app on a framework we don't use anywhere yet. ;)
18:41:33 <abadger1999> Yeah, me neither.... but continuing to add a new framework with every new app leaves huge holes when one person stops working on infra.
18:41:40 <abadger1999> relrod: heh :-)
18:41:44 <skvidal> abadger1999: I thought it was progress that we were onto MOSTLY a single language :)
18:41:55 <skvidal> abadger1999: agreed on all points
18:41:59 <abadger1999> relrod: Well, push for your $framework to be one of those that we port to :-)
18:41:59 * threebean begins writing fedmsg-scala
18:42:08 * smooge kickbans threebean
18:42:27 <skvidal> abadger1999: another issue that may bear some thinking
18:42:53 <lmacken> I think a lot of it has to do with how active the fedora/epel maintainer is with packages & following through with issues upstream
18:43:05 <skvidal> we have a number of apps that are maybe less decoupled from their frontend tech than they could be?
18:43:06 <lmacken> for TG, toshio and I handled most of that
18:43:30 * mdomsch has no intention of moving MM from TG1
18:43:47 <mdomsch> I already don't have the time to devote to it that it deserves
18:43:51 <lmacken> mdomsch: I think that's fair. if it's working as is, why change.
18:44:00 <skvidal> lmacken: I can think of many reasons to change
18:44:07 <skvidal> lmacken: not the least of which is having to maintain the older server
18:44:10 <skvidal> and not having the deps fight
18:44:17 <mdomsch> lmacken: yep - that's what we agreed to at FUDCon
18:44:25 <abadger1999> mdomsch: Well... the thing is... eventually, I'll stop packaging TG1.
18:44:33 <lmacken> skvidal: deps fight? TG1 apps should work fine on RHEL6, no?
18:44:37 <mdomsch> abadger1999: timeframe?
18:44:43 <mdomsch> yes, TG1 works on RHEL6
18:44:43 <skvidal> lmacken: how well does f-comm work with rhel6?
18:45:00 <lmacken> skvidal: I don't know, I haven't tested it in ages, plus it's TG2
18:45:08 <skvidal> lmacken: my point is not specifically about TG1
18:45:10 <skvidal> or even about mm
18:45:14 <abadger1999> mdomsch: As soon as I port all of our nedded code to something else ;-)  (So yeah, if you don't have time, I [or pingou, or someone else] will likely do mm)
18:45:16 <skvidal> it's about the costs of keeping a napp running
18:45:36 <skvidal> which often involves holding on to potentially dangerous code and sometimes maintaining older servers
18:45:46 <abadger1999> mdomsch: Right now... I just don't want to dump TG1 for a framework that we're not going to be running in a few years either.
18:45:57 <skvidal> and that says nothing of the cost of knowledge-rot on how to fix it when it breaks or blows up
18:46:00 <mdomsch> all fair points, skvidal and abadger
18:46:07 <skvidal> mdomsch: this is not about MM
18:46:09 <abadger1999> TG1 and TG2 are actually bad choices for a long term framework, I think
18:46:14 <abadger1999> Neither one is going to port to python3
18:46:29 <threebean> abadger1999: not true, we started work on tg2->python3
18:46:33 <mdomsch> skvidal: right, you're asking the bigger question; I'm just narrowly focused :-)
18:46:42 <abadger1999> threebean: Did someone new take over paste?
18:46:46 <threebean> abadger1999: it's just a mess, and will be a while
18:46:57 <smooge> ok guys.. I would like to give a 4 minute warning to this conversation
18:47:05 <threebean> abadger1999: pyramid forked paste and we're going to generalize it back to tg2.  hopefully in a year.
18:47:09 <abadger1999> threebean: B/c paste's upstream said they weren't going to port to python3 at one point.
18:47:17 <threebean> yeah, paste is dead.
18:47:46 <relrod> abadger1999: What about something like Django? I think we have at least two django apps (reviewboard and askbot)
18:47:48 <abadger1999> threebean: cool.  If it's been forked and progress made, then it's got a better future than when I looked.
18:47:54 <abadger1999> relrod: ugh.
18:48:09 <threebean> abadger1999: not all that great.  forked and then included in pyramid.  we have to extract it back ;)
18:48:12 <abadger1999> relrod: So django could also be on the table but:
18:48:28 <abadger1999> (10 We don't currently code django, we just deploy it.
18:48:58 <abadger1999> (2) After talking with django developers... it seems that django is more like an application server than a framework.
18:49:09 <relrod> hm
18:49:24 <abadger1999> Which, I'm not sure if it's good or bad... it's just "different" and needs to be considered.
18:49:27 <skvidal> so it's more like running tomcat/jboss than it is like running a tg2 app
18:49:32 <abadger1999> Right.
18:49:36 <relrod> ah
18:49:52 <relrod> Never thought of django like that, interesting.
18:49:56 <abadger1999> So the way we've been trying to make our django apps work is taking a square peg and making it fit in a round hole.
18:50:23 <abadger1999> Not sure if we want to continue doing that or if we want to see about setting things up like upstream django recommends.
18:50:37 <skvidal> I think I've said this before but perhaps it bears restating
18:50:54 <skvidal> our current apps* server structure, I think, exacerbates a lot of issues
18:51:07 <skvidal> b/c we end up having to glom a number of things (sometimes precariously) together
18:51:20 <skvidal> we do this for scale, I get that - but it is not obvious that we require that scale
18:51:22 <smooge> skvidal, I will agree on that.
18:51:30 <skvidal> and it is not obvious that combining them in that way is best for scale
18:51:54 <skvidal> I like what we're doing more and more which is to isolate related/big apps to their own instances
18:52:00 <skvidal> like the packages## instances
18:52:22 <skvidal> b/c it allows us clearer decision making when it comes to server maintenance/updating processes
18:52:42 <skvidal> now - this only helps the ops-ish side of things in terms of maintainence
18:52:54 <abadger1999> <nod>  If we have the server resources to isolate to different machines, it makes sense to me to do more of that.
18:53:11 <skvidal> the other piece the dev side is specifically abadger1999's concern, I think - and that's becoming more important
18:53:13 <skvidal> as our apps age
18:53:33 <abadger1999> yeah.  especially as our apps age and maintainers leave the project.
18:53:39 <smooge> ok guys, do we want to take this to fedora-apps after meeting? we have 5 minutes left
18:53:46 <abadger1999> smooge: Sounds good.
18:53:51 * threebean nods
18:53:56 <skvidal> cool
18:54:02 <smooge> #topic FAD ? https://fedoraproject.org/wiki/FAD_Infrastructure_Security_2012
18:54:33 <smooge> since we don't have a lot of time on this I will just say that people who are interested need to get in touch with relrod and follow the discussion on the list
18:55:10 <smooge> relrod, did you have anything to add?
18:55:16 <relrod> https://fedoraproject.org/wiki/FAD_Infrastructure_Security_2012/attendees
18:55:26 <relrod> nirik asked me to make a table on the wiki for interested people
18:55:38 <smooge> ok I will add mysefl after this meeting
18:55:40 <relrod> so please fill out a row there, put your preferred locations (probably RDU or westford?)
18:55:50 <relrod> and do a quick expedia.com to get an estimate of airfare
18:56:09 <relrod> that's all I have
18:56:14 <smooge> okie dokie
18:56:17 * skvidal would recommend kayak.com or hipmunk.com - if only b/c they have better graphics
18:56:24 <lmacken> ah, so it's narrowed down to just 2-factor auth?
18:56:44 <smooge> lmacken, well primary issue. secondary issues can be focused on
18:56:45 <skvidal> lmacken: that's the focused must-complete feature, yes
18:57:21 <relrod> smooge: huh, those do look nicer ;)
18:57:24 <relrod> skvidal: *
18:57:27 <skvidal> relrod: :)
18:57:36 <skvidal> relrod: they have non-crappy phone apps, too
18:57:55 * threebean got a 1/2 price flight from kayak.com.. orbitz just didn't find it.
18:58:01 <smooge> #topic Upcoming Tasks/Items
18:58:02 <smooge> #info 2012-06-21 to 2012-07-04 Kevin is off on trains and boats.
18:58:02 <smooge> #info 2012-06-26 Fedora 15 end of life.
18:58:02 <smooge> #info 2012-06-28 Seth at jury duty.
18:58:02 <smooge> #info 2012-07-02 remove people with pkgdb bugzilla issues.
18:58:02 <smooge> #info 2012-07-05 nag fi-apprentices
18:58:06 <smooge> #info 2012-07-12 drop inactive apprentices.
18:58:08 <smooge> #info 2012-08-07 to 2012-08-21 F18 Alpha Freeze
18:58:10 <smooge> #info 2012-08-21 F18 Alpha release.
18:58:12 <smooge> #topic Open Floor
18:58:27 <smooge> sorry hit paste a little quick
18:59:21 <smooge> was there a varnish problem someone had a question on?
18:59:27 * relrod doesn't have anything else for the meeting, but wants to say good job smooge, and thanks for filling in as Meeting Guy for nirik.
18:59:58 * jaysonr says thanks smooge!
19:00:09 <threebean> smooge: :)
19:00:20 <lmacken> smooge++
19:00:32 <sarabande> yes, I do not know how to access to staging host
19:00:40 <smooge> ah ok.
19:01:25 <smooge> sarabande, I think that would be proxy01.stg.fedoraproject.org via bastion01
19:01:44 <smooge> lets do that in the fedora-admin after the meeting and I get some food.
19:01:54 <smooge> if that is ok?
19:01:56 <sarabande> good.
19:02:16 <smooge> alright I will close out this meeting. thanks for all of your time
19:02:21 <smooge> #endmeeting