19:00:50 #startmeeting FUDCon Tempe planning (Agenda: https://fedorahosted.org/fudcon-planning/report/9) 19:00:50 Meeting started Mon Sep 27 19:00:50 2010 UTC. The chair is stickster. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:50 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:57 #meetingname FUDCon Tempe planning 19:00:57 The meeting name has been set to 'fudcon_tempe_planning' 19:01:02 #topic roll call 19:01:05 * stickster 19:01:12 ohai 19:01:17 #chair rrix 19:01:17 Current chairs: rrix stickster 19:01:21 Hi Ryan :-) 19:01:24 Hi Paul :) 19:01:45 * stickster knows that jsmith is in a Board meeting right before this, so he might not be here at opening. 19:02:10 Not sure if any of herlo, SMParrish, or inode0 are around 19:02:21 #info rbergeron is doing some kid-shuttling and may not be available 19:02:30 * jsmith lurks 19:04:02 OK, let's proceed then :-) 19:04:20 #topic https://fedorahosted.org/fudcon-planning/ticket/16 (pbrobinson airfare) 19:04:31 Oh wait... 19:04:32 #undo 19:04:32 Removing item from minutes: 19:04:39 #topic Last week's action items 19:04:48 * SMParrish here 19:05:07 #link http://meetbot.fedoraproject.org/fudcon-planning/2010-09-20/fudcon_tempe_planning.2010-09-20-19.00.html <-- last week's stuff 19:05:21 I'm looking at the "Action items" list 19:05:39 #1 -- SMParrish, did you hear back from SugarLabs about a sponsorship for pbrobinson? 19:05:45 Hiya, by the way Steven :-) 19:06:12 stickster: Walter said will know by the end of the week 19:06:26 SMParrish: That's great, if you don't mind adding that to the ticket if it's not already there? 19:06:51 stickster: will do 19:07:00 #info SMParrish heard back from Walter @SugarLabs, they'll have an answer for us at the end of this week 19:07:18 #2 -- I haven't completed this yet, but I will do that right after this meeting. I have an email ready. 19:07:25 * stickster skips rbergeron for now 19:07:31 I did #4 and #6 19:07:46 #action rbergeron reach out to Cat @GOOG to figure out what she needs in terms of prospectus, to guide work 19:07:53 #action rbergeron will keep working on the welcome packet and wants YOUR help! 19:08:20 #action rbergeron write a follow-up blog post to Paul's post about subsidies and lodging 19:08:47 That's all for last week's action items 19:08:54 hi, I have a question with booking my flight for the Fudcon 19:09:12 djf_jeff: Can we get to you at the end of this meeting?> 19:09:27 stickster: I'll get another blog post up tomorrow about the sessions and hackfests 19:09:30 * stickster will be as quick as possible with tickets :-) 19:09:41 SMParrish: That is AWESOME. Thank you so much for doing that! 19:09:52 #action SMParrish will blog about sessions and hackfests 19:09:54 stickster: yeah, sure, didn't see the meeting was going on, please excuse me for disturbing 19:10:07 djf_jeff: No problem my friend, should only be a half hour or so 19:10:38 #topic https://fedorahosted.org/fudcon-planning/ticket/49 (GoDaddy sponsorship) 19:10:55 #info This one belongs to inode0, no update yet 19:11:06 #action stickster to update ticket with ping 19:11:49 #topic Tickets we're breezing past for now since they're in progress 19:12:07 #link https://fedorahosted.org/fudcon-planning/ticket/16 <-- pbrobinson airfare 19:12:21 #link https://fedorahosted.org/fudcon-planning/ticket/48 <-- Google sponsorship, see above 19:12:46 #link https://fedorahosted.org/fudcon-planning/ticket/19 <-- internet pipe, waiting to hear back from jsmith about his contact 19:13:24 Talked to my contact this morning... he still hasn't followed up for an on-site survey 19:13:25 #link https://fedorahosted.org/fudcon-planning/ticket/61 <-- internet pipe, rrix is reaching out to Zach this week again 19:13:37 He asked me to email him to remind him, and I'm sending that email now. 19:13:42 * rrix nods 19:14:16 jsmith: Cool, can you update ticket 19 with that when you get a chance? 19:14:33 Of course! 19:14:44 #link https://fedorahosted.org/fudcon-planning/ticket/50 <-- welcome packet, Robyn's working on it 19:15:00 * rbergeron is driving brt! 19:15:07 rbergeron: no problem :-) 19:15:21 OK, I'm going to whiz over to "tickets we should not breeze past" 19:15:46 Oh, one other: 19:16:04 #link https://fedorahosted.org/fudcon-planning/ticket/47 <-- Sponsor prospectus, herlo and anyone else interested should be working on this 19:17:11 If anyone out there thinks they don't need a checkup on their action item, we can always remove it from the agenda. 19:17:18 To do that you just remove 'na-meeting' from the keywords. 19:17:59 #info Remember, 'na-meeting' keyword indicates a ticket should be discussed at the meeting. If a ticket becomes invalid or no longer needed, you can remove that keywords. 19:18:04 #undo 19:18:04 Removing item from minutes: 19:18:06 #info Remember, 'na-meeting' keyword indicates a ticket should be discussed at the meeting. If a ticket becomes invalid or no longer needed, you can remove that keyword. 19:18:20 Let's talk about booze! 19:18:37 stickster: and non-booze too! 19:18:39 ohhh im here now 19:18:39 #topic https://fedorahosted.org/fudcon-planning/ticket/64 (FUDPub beverages, specifically the adult kind) 19:18:51 not really; booting up :) 19:19:02 rbergeron wrote an excellent summary in that ticket which everyone should check out. 19:19:49 A cost of $3.25 per person covers sodas, juice, and other non-alcoholic stuff, as well as mixers and bar standards like ice, cups, lemons/limes, and other supplies. 19:19:50 * rbergeron bows 19:19:54 * jsmith has read it, and is in violent agreement 19:20:10 plus we need to throw in some tip on top of that, which shouldn't make it much more. 19:20:24 #info $3.25/person = something like $600 or so, including the gratuity for our size crowd 19:20:34 That's *eminently* affordable. 19:20:58 I looked it over and it sounds good to me. And I agree with out crowd more beer than wine. And a good variety of beers too 19:21:13 I think we can't go crazy on the variety, without them wanting to kill us :) 19:21:18 they do have to be able to keep track of it all 19:21:23 #info The deal is, Pourmasters runs the bar, we secure the permit from ASU and the law, and buy and provide the booze to Pourmasters. 19:21:48 i think 4-5 is probably the limit there. 19:21:57 since he said 3 or 4... mayyyyyybe 5 :) 19:22:01 rbergeron: I agree, and that number is almost exactly what I was thinking 19:22:08 Like, 3 cases of 4 types of beer should be plenty. 19:22:17 michelob ultra light, guinness, and some stuff in-between 19:22:29 for the dieters in the crowd :) 19:22:59 rbergeron: Agree :-) 19:23:09 we can debate those details at some point in the future - not heavily concerned about it now 19:23:22 rbergeron: Yup, I mainly wanted to just #info the important parts 19:23:33 we should figure out if we want max to take me alcohol shopping, or if we want to collect donations prior. 19:23:36 I'll add a few good choice to the ticket :) 19:23:36 I think all of this is very affordable, do-able, and actually will give us a cheaper FUDPub than we've had in the past. 19:23:44 rbergeron: I think shopping early is the right answer. 19:23:50 I say prior because we aer prohibited from taking money for alcohol on site 19:24:00 rbergeron: jsmith won't be there early, I'm thinking of changing my flight so I can help more. 19:24:05 . 19:24:07 okay. 19:24:22 i know max & commarch are thinking of coming early to do some team stuff also 19:24:29 #info We are prohibited from accepting $$ for booze on site, so it must all be bought in advance, and we cannot buy more and bring it in during the event. 19:24:52 Anything else important to note here Robyn? 19:25:02 we can take out our leftovers and give them to someone of age who lives nearby :) 19:25:16 * rbergeron smirks at rrix 19:25:27 #agreed Someone(s) @RHT will be there early to help purchase booze. Anything leftover will be given to people who are able to take it with them, and that does not include rrix :-) 19:25:41 * rrix is not of age D: 19:26:06 and people who are underage don't have to be separated from others in any way; they will be carding 19:26:12 so bring your IDs! 19:26:12 stickster: the thought *never* crossed my mind, me being the good underage student I am. 19:26:22 * rbergeron adjusts rrix's halo 19:26:29 Of course not! ;-) 19:26:37 o:) 19:26:37 ..anyways :P 19:26:39 #chair rbergeron 19:26:39 Current chairs: rbergeron rrix stickster 19:26:40 :-) 19:26:44 #chair SMParrish 19:26:44 Current chairs: SMParrish rbergeron rrix stickster 19:27:14 rbergeron: Does Pourmasters do the carding? 19:27:29 yes. 19:28:19 #info Underage patrons don't need to be cordoned off. Pourmasters will card people, and as long as we make sure under-21s don't have access to alcohol our permit should be no problem. 19:28:39 rbergeron: you and I will work on the permit at the appropriate time. It doesn't need to be "omg right now" 19:29:12 Anything else on this? 19:29:41 nada. 19:30:16 rbergeron: Do we need/have a Pourmasters "reservation" for Saturday night the 29th? 19:30:57 Already made. :) 19:31:02 AWESOME. 19:31:14 #info Pourmasters reservation already made by the magnificent rbergeron 19:31:30 OK, that brings us to... 19:31:47 #topic https://fedorahosted.org/fudcon-planning/ticket/57 ("looking for roommate" on wiki) 19:32:55 rbergeron: Should I work on revamping the instructions on the wiki so people use the "Room sharing" box the way we want? 19:33:29 hrmm 19:33:32 * rbergeron goes to revisit what they say 19:34:36 The wiki basically now says: "If you want or need to share a room, mark an X in the "Roomshare?" column." above the pre-reg table 19:34:44 Yeah, that's what i see 19:35:04 #action stickster build out the instructions for room sharing so they're more helpful 19:35:13 I think it might be helpful to say something like "If someone doesn't have a roommate marked... ask them!" 19:35:18 +1 19:35:32 or maybe have a separate box of ID's looking for roomates, even if it becomes too difficult somehow 19:35:34 Anyone else on things that would improve the instructions? SMParrish? rrix? 19:35:43 * rrix looks 19:36:00 rbergeron: I worry that we'll have too many separate places for people to fill out things -- but I'm *not* opposed to that if it will help 19:37:20 let's go with the first part. if we still have confusion, we can revise. 19:37:25 "If you want or need to share a room, mark an X in the Room Share column, and list who you would like to room with" or something? 19:37:26 rbergeron: OK 19:37:49 rrix: Yes, I'll provide a little more explanation, but that's the gist -- list who you *are* rooming with 19:38:07 Yes :) 19:38:15 Rather than just "you are rooming with someone" 19:38:51 #info We want people who are being paid out of some part of Red Hat's budget (whether subsidies, or direct funding) to room together, which makes everyone's lives easier 19:39:26 Then everyone else who is looking to cut their own costs will have an easier time knowing whom to contact for rooming together. That's what inode0 was getting at the other day I think. 19:40:16 Anything else on this? 19:40:44 i have nothing :) 19:40:47 OK, last ticket topic: 19:41:01 #topic https://fedorahosted.org/fudcon-planning/ticket/58 (Bus info, light rail to hotel) 19:41:15 I am getting there slowly but surely :) 19:41:20 sorry, i should have updated the ticket 19:41:27 OK rbergeron, I'll #action you for that if OK 19:41:29 * rbergeron has had crap internet all weekend 19:41:32 yes, go ahead :) 19:41:41 and crap internet today too... up down up down up down 19:41:47 #action rbergeron will fill in bus info when she gets a chance (non-emergency)' 19:41:55 which brings us to... 19:42:00 #topic AOB (all other business) 19:42:24 Are we going to have shirts - and if so do we need to order a design from design? 19:42:51 rbergeron: We have a request for posters but not a shirt, that's a great catch! 19:42:54 I know there is a design that was used at emea and latam but i wouldn't be opposed to having some variety :) 19:43:04 #link https://fedorahosted.org/fudcon-planning/ticket/51 <-- poster, request is pending with design team 19:43:50 rrix: You were working on the poster part, are you interested in also making sure we have a T-shirt design for the event? 19:45:18 OK, maybe we'll need to come back to that one then 19:45:29 #action stickster ask about T-shirt design on list 19:45:47 #idea How well is the Trac working for everyone? 19:45:53 excellently :) 19:46:03 great 19:46:13 OK, I'm pretty happy with it after being on it for a few months but I wanted to make sure no one else was UNhappy :-) 19:46:18 * rbergeron nods 19:46:35 I think as we get closer we could probably make a "week of" milestone 19:46:46 last-minute stuff before everyoen is there 19:46:49 but we're not there yet :) 19:47:04 because a lot of the milestones end long before fudcon 19:47:09 either that, or bump those milestones out 19:47:28 things like "print nametags" and "buy alcohol" and "pick up stickster from airport" 19:47:30 rbergeron: It might make sense to keep those last-minute things in a task list on the wiki (Tempe logistics page?), then we mass enter them a few weeks out 19:47:47 that would probably work well. 19:48:03 Or we can just have a new milestone for 2 weeks before, 1 week before, 3 days... etc. and enter them any ol' time we feel like it on the Trac 19:48:39 yup 19:48:51 I just don't want to leave loose ends tied up in trac 19:49:26 * rrix notes that he'll probably whip up something for his design-team on-campus poster ticket in the next few days 19:50:19 rbergeron: By which you mean -- you don't want things to get moldy in Trac? Or do you mean, it's harder to make sure loose ends are tied up at the last minute if they're in Trac? 19:51:00 i just don't want to say things like 19:51:19 "we now know the status of pourmasters and we just need to buy alcohol" 19:51:26 and then forget to make the ticket to buy alcohol 19:51:29 the next steps of each ticket 19:51:33 rbergeron: PRECISELY! 19:51:37 not that *that* particular one would be forgotten 19:51:37 Each task should be a ticket, IMHO. 19:51:47 That makes it easier to assign things to people. 19:51:47 but say - we need to buy lanyards and badge holders 19:51:56 we need to have the separate task of printing the badges 19:52:04 rbergeron: Yup, separate ticket. 19:52:19 rbergeron: I encourage everyone to just enter those tasks *whenever* they think of them 19:52:32 We can always de-dupe or assign later, the capture is the important part 19:52:34 okee dokee 19:52:35 :) 19:53:04 we shoudl probably use a meeting at some point maybe 2 months before to go through closed tickets and make sure we haven't forgotten a next step anywhere 19:53:08 rbergeron: BTW you did a great job this weekend putting in some tickets for these kinds of things. "Decide on alcohol," "Get alc. permit," "Decide on food menu" 19:53:41 rbergeron: Sure, we can absolutely do that! Great idea. 19:53:55 #idea Have a 2-months prior meeting to check all closed tickets, making sure we didn't forget any next steps. 19:54:42 just because that's when we start approaching deadlines and so forth :) 19:54:54 have we talked to the hotel about how many rooms we've booked so far at all? 19:55:22 rbergeron: Not yet -- but a good task would be to check with them ~Oct. 1 to see how much has been booked. 19:56:09 we might also want to send out a nag mail around the 15th to request that all sponsored people have booked their rooms 19:56:22 also, i know a lot of people are coming in on thursday (or even wednesday) - i don't knwo if our hospitality / hack suite is only for friday night, but we might consider having it all day friday 19:56:31 smparrish: good idea 19:56:46 rbergeron: I can ask about that too. Can you ask these questions on the list and I'll answer them there after talking to the hotel? 19:57:10 Yes. :) 19:57:16 I *think* we have it for all day Friday - Monday. 19:57:38 #action rbergeron ask on list about (a) how many rooms booked (b) all-day hospitality suite on friday 19:58:37 :) 19:59:04 #action rbergeron ask on list about sending out nag mail around 15th to request all sponsored ppl have booked their rooms 19:59:06 #link https://fedorahosted.org/fudcon-planning/roadmap <-- This is a great way to check our progress. 19:59:48 :) 19:59:56 Anything else for today? 20:00:00 If not, closing in 30 20:01:02 #endmeeting