18:02:05 #startmeeting 18:02:05 Meeting started Tue Feb 3 18:02:05 2015 UTC. The chair is isharacomix. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:05 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:02:20 #chairs isharacomix whippythellama billf mhrivnak jackhill 18:02:27 #topic Un-meeting next week 18:02:41 Everyone want to quickly look over the announcement draft? 18:02:44 https://trilug.org/2015-02-12/un-meeting 18:02:46 for reference 18:02:50 and the record 18:03:12 billf: i'm planning on just copying the lightning talk signup sheet and simplifying it for this 18:03:21 for topic suggestions, that is 18:03:23 that would probably be wise. 18:03:27 pizza is at 6:45, not 7. 18:03:27 I wouldn't use the term "mini-workshop" - how about "mini-panel" ? 18:03:34 i banged my head against google forms too long 18:04:16 panel to me indicates multiple ppl at a table discussing something - is that what you had in mind? 18:04:25 If I get up to show something, I would prefer people who also want to contribute to come down next to me 18:04:28 …or am i just way off? :) 18:04:39 i like that idea 18:04:40 workshop makes it sound like hands-on stuff 18:04:57 i was thinking something along the lines of jack's vim session 18:05:05 which felt semi-workshop-ish to me 18:05:08 but i'm open 18:05:11 it might be a good idea if the steering committee comes planned with topics to drive 18:05:15 panel does sound good 18:05:23 strength in numbers, that sort of thing 18:05:33 that way even if audience participation is down, we have 4 or 5 strong topics 18:05:35 it is very hard for people to follow if audience members shout out comments 18:05:45 i've got one or two topics in mind, isharacomix - yeah 18:05:59 we had jtate talking quietly to jack in the front row, but the people at the back can't hear 18:06:16 make em stand up front and take a turn 18:06:28 i like that 18:06:37 ok, mini-panel it is - i'll re-edit 18:06:50 note mhrivnak's reminder that pizza is 6:45 18:07:00 noted 18:07:18 Room reservation is still in progress. Should hear something tomorrow or thursday 18:07:27 ah, so we're back to doing pizza at the beginning? 18:07:47 worst case, we hold it in the attrium :-) 18:07:53 Haha. :) 18:08:00 Pizza in the middle was an accident last time 18:08:22 yeah, but we had discussed making that non-accidental :) 18:08:25 what needs to be done for this topic 18:08:46 I'm in favor of changing as little as possible. 18:09:03 I would prefer pizza at 7am, so we can do the intro and call for topics before people eat 18:09:10 7pm 18:09:14 billf: good point 18:09:26 I think it worked well doing pizza in the middle, except that eating at 7:45pm is probably pretty late for most people. 18:09:42 people come up with ideas if they can discuss with friends over pizza 18:09:49 * mhrivnak has been known to eat pizza at 7am 18:10:14 So, pizza at 7 or 7:15 after intro, community announcements, and pitches? 18:10:20 +1 18:10:21 gather in the room @ 6:45, announcements @ 6:55, pizza @ 7:15? 18:10:40 How do we want to divvy tasks this time around 18:10:41 ? 18:10:45 I vote for Meet at 6:45pm, pizza at 7pm. 18:11:07 meet in the lobby at 6:45? Or meet in the room for announcements, then go to the lobby for pizza? 18:11:07 actually, 7:15pm pizza is better 18:11:22 meet in the lecture room 18:11:27 Everyone should be in room at 6:45. I can put information to that effect on the signs. 18:11:54 Ok, we need to communicate that very clearly since it's a substantial change. 18:12:02 we'll need someone letting folks in - maybe whoever will be waiting for pizza 18:12:07 one SC person can stay in the attrium and direct people to the room 18:12:19 I can do that. 18:12:20 promotion !! 18:12:23 I think people are used to the idea that if they don't want pizza, they don't need to show up until about 7:15. 18:12:23 yes, and do the new person greet stuff. 18:12:33 yep 18:12:49 will we have more than 15 minutes of announcements? 18:12:55 during the announcements we can outline how the signup thing will work 18:13:17 not sure, mhrivnak 18:13:22 yeah, I think we will use the time to explain the meeting format 18:13:35 +1 18:13:42 i can see that easily pushing us over 15 mins 18:14:00 I'm in favor of this. I would include a proper agenda on the email that shows the time breakdown. 18:14:10 6:45 everyone in EB2 room 18:14:15 7:15 pizza 18:14:18 7:30 sessions 18:14:20 or whateve 18:14:24 ok. Should I have the pizza arrive maybe at 7:05 in case we're a little ahead? 18:14:33 probably a good idea 18:14:41 i agree with whippythellama 18:14:42 based on last time, it can take nearly 10 minutes for everyone to even get pizza, let alone eat it. 18:15:06 yeah, i think 20 mins at least for eating 18:15:11 (15 minute warning) 18:15:49 I think we're agreed on this. We'll cover the minute-level specifics next week. Shall we continue? 18:16:10 #action whippythellama finish and send announcement 18:16:27 sure. I'll just encourage us to consider keeping the announcement phase to 20 minutes if possible. 18:16:28 #action whippythellama finish setting up topic suggestion form 18:16:42 I will keep an eye on the mail queue and let the announce mail through if I see it 18:16:43 so we're not starting the meeting much after 7:30. 18:16:48 thank you, billf 18:17:07 #topic March speaker 18:17:17 Looks like mhrivnak has a lead! 18:17:38 I have verbal confirmation for March. 18:17:41 that's a great topic and slide set. thanks. 18:17:52 one last thing on february - try to think of any topics all of you might like to see at the un-meeting 18:17:57 mhrivnak: that's awesome 18:18:00 everyone else needs to hunt for a march speaker 18:18:15 you mean april? 18:18:17 billf: april? 18:18:18 yeah 18:18:24 the other march :) 18:18:36 i've got a lead at cumulus. 18:18:59 he's got a great talk on the linux internals 18:19:13 that sounds like a good one 18:19:22 i think if i can get him to speak, sponsorship should be easy to secure that month too 18:19:24 do you know a timeframe yet? 18:19:44 me? not yet. we just both got back from travel, so I'l broach the subject this week. 18:19:49 sounds good 18:20:12 #topic Feb Hack Night 18:20:39 Bill brings up automating pilot backups 18:20:41 we're confirmed for thursday, 2/19 here at webassign 18:20:57 Spectacular. Does that conflict with devops? 18:21:03 no, it shouldn't 18:21:15 awesome. we need to put it on the slides and send the reminder 18:21:17 third thursday looks like it may work out well for us 18:21:23 agreed 18:21:34 we should only send the reminder after the main meeting, tho 18:21:39 Agreed. 18:21:53 Is third thursday good for the rest of the SC as well? 18:22:17 works for me 18:22:18 yep 18:22:23 when i say it's "good" i mean in regards to scheduling conflicts with other recurring meetups and such, btw 18:22:28 I see. 18:22:36 Looks like a majority seems OK with it. 18:22:36 it seems to be the least-conflicting 18:22:44 excellent 18:22:49 #topic Emergency Phone 18:23:02 Seems general sentiment is to discontinue 18:23:20 i don't see the need for it, personally 18:23:24 I agree 18:23:28 I object to making changes without a clear plan about how/why we can improve. 18:23:33 seems like a f2f topic 18:23:41 If I recall correctly, the emergency phone is a google voice number, so in theory we should be able to pass the number to other phones if we just want to save costs 18:23:54 we could do that 18:24:06 jackhill: do you see a need for the phone? 18:24:09 Is the motivation cost saving or admin overhead reduction? 18:24:09 It is not currently. I've wanted to do that. Perhaps we can do that on the hack night :) 18:24:38 isharacomix, in my mind, both. 18:24:44 same here 18:24:48 likewise 18:25:49 I would like to see coxn have a say in this decision. He may be privy to details we are familiar with ourselves. 18:25:55 I think we would have more effect if we made it known who was on the SC and what someone should do if they witness or are harrassed 18:26:07 agreed, billf 18:26:16 whippythellama: I don't have enought data about they best way to be accessible (other organizations do, and we should try to get input from them), but am wary that it will send the wrong signal if we discontinue it without being able to articulate why the thing we're moving to is better. 18:26:16 the SC should also be trained (reminded) how to respond 18:26:50 In that case, perhaps a f2f is in order in the near future 18:26:54 for example, we are able to help NCSU LUG this weekend with thier FOSS education event with the phone. 18:27:01 jackhill, we don't necessarily have to say we're moving to something better. We also have the option to say we are not going to provide a service anymore because we can't justify the cost vs. value. 18:27:01 billf++ 18:27:23 In the last 2 years we have had zero (0) calls 18:27:38 That's a fair point. 18:27:44 use the money to buy name tags for meetings. 18:28:00 i think coxn is footing the bill for this currently 18:28:08 try to help people socialize and meet new people 18:28:22 this came up because i asked him if he's being reimbursed 18:28:31 2 minute warning, btw 18:28:51 This may be an indicator that the phone is either not needed or not perceived as valuable by the membership. 18:29:08 or is unknown to them 18:29:12 The phone is for people who are non-members that we would like to be members 18:29:13 whippythellama: if I don't see an email from you today, I will send out a "save the date" email tonight. OK ? 18:29:20 sounds good, billf 18:29:24 thanks for pinging me 18:29:41 jackhill: that's not my understanding of its purpose 18:29:48 nore mine 18:29:54 i think a f2f discussion of this would be good 18:29:55 jackhill, I also did not think that was the purpose. 18:30:03 i will make arrangements for a f2f meeting 18:30:12 gotta head out, folks 18:30:14 * mhrivnak has to go to another meeting now 18:30:23 #action isharacomix will arrange a f2f steering meeting 18:30:28 ah yes, that's probably the path forward is unclear :) 18:31:05 All righty. I'll get out a doodle poll and send that with the meeting minutes. 18:31:08 #endmeeting