18:30:12 <whippythellama> #startmeeting
18:30:12 <Tribot> Meeting started Mon Jan 23 18:30:12 2017 UTC.  The chair is whippythellama. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:30:12 <Tribot> Useful Commands: #action #agreed #help #info #idea #link #topic.
18:30:19 <whippythellama> #chair jeremyhwllc stmiller mhrivnak qqx whippythellama
18:30:19 <Tribot> Current chairs: jeremyhwllc mhrivnak qqx stmiller whippythellama
18:30:29 <whippythellama> #topic Check for Agenda Additions
18:30:35 <whippythellama> anyone have anything to add to the schedule?
18:30:42 <mhrivnak> Nothing here.
18:30:45 <qqx> not I
18:30:55 <jeremyhwllc> none
18:31:09 <stmiller> nothing here
18:31:14 <whippythellama> ok, coolio
18:31:27 <whippythellama> #topic January Hack Night Recap / General Hack Night Discussion
18:31:34 <whippythellama> so that didn't happen
18:32:01 <whippythellama> i intended to attend, but i'd forgotten my wife was going out of town
18:32:17 <stmiller> Yeah it was a mess. Sorry to qqx. I suppose we need to see what events are going on in the same area there in the future
18:32:18 <whippythellama> so there were things that had to be done
18:32:32 <mhrivnak> Bummer it didn't work out.
18:32:37 <whippythellama> yeah  :/
18:32:43 <whippythellama> i was looking forward to it
18:33:02 <mhrivnak> I certainly agree with the sentiment of not holding these unless we can get a base level of interest expressed.
18:33:08 <stmiller> I think you were the only one, no responses on list or on irc.
18:33:10 <whippythellama> i wonder whether this was mainly because of the parking situation this time
18:33:21 <whippythellama> mhrivnak: agreed
18:33:41 <qqx> To me the parking situation didn't seem much different than normal.
18:33:45 <whippythellama> no?
18:33:59 <mhrivnak> three non-SC people RSVP'd
18:34:41 <stmiller> I couldn't find any spots driving around for 15 minutes or so, saw huge lines of persons going to the durham theater
18:34:48 <whippythellama> yeah, that's what had me wondering if maybe congestion affected the attendance
18:34:48 <qqx> Didn't look much like anybody else showed up.
18:35:05 <qqx> I hung around by the door until a few minutes after the start time, and didn't see anyone.
18:35:11 <whippythellama> hmm...
18:35:41 <jeremyhwllc> it might be cool to team up with the TriPython group hack nights who meet at same location
18:35:59 <whippythellama> they meet there and at webassign
18:36:17 <whippythellama> i've gone to the one at webassign a few times - there are generally a dozen or so folks there at least
18:36:49 <whippythellama> they do have pizza, tho, and the webassign snack bar/drink fridge
18:36:57 <whippythellama> which doesn't hurt
18:37:08 <whippythellama> i don't know how the ones at caktus go
18:37:29 <stmiller> I think trilug is a one-meeting a month type of crowd. It's hard enough to get the main monthly meeting organized
18:37:35 <mhrivnak> I'd support the idea of making sure that 1) each hack night has a well-defined theme/goal, as this recent one did. And 2) we cancel if we don't reach a minimum number of RSVPs 24h in advance.
18:37:39 <whippythellama> heh.. true, stmiller
18:37:46 <stmiller> I'm not going to do hack nights anymore,
18:37:57 <stmiller> so any future ones, someone else can do it. Or just scrap it.
18:38:17 <whippythellama> mhrivnak: i agree on your first point
18:38:35 <whippythellama> we did have rsvps this time, tho, making me wonder how we can be somewhat certain
18:38:44 <whippythellama> stmiller: i can totally understand that
18:38:55 <whippythellama> you have put in more than your fair share of time on them
18:39:03 <whippythellama> thank you for doing so!
18:39:04 <jeremyhwllc> I really can't commit to more than 1 night per month
18:39:21 <mhrivnak> meetup RSVPs are not very reliable on an individual basis, so I'd probably want to see 10+ before feeling confident that 4 will show up.
18:40:06 <whippythellama> mhrivnak: i agree in spirit, but then we're faced with cancelling an event with, say, 6 rsvps or something
18:40:23 <qqx> Yeah, the other option would be to have some type of sanction for people who RSVP but don't show. But no idea what that could be.
18:40:34 <whippythellama> qqx: yeah, that's a bit of a challenge
18:40:40 <mhrivnak> Heh. The TriLUG wall of shame.
18:40:44 <whippythellama> double the membership dues for them!
18:41:11 <jeremyhwllc> if it needs a vote I would support suspending hack nights until there is interest and/or demand
18:41:28 <whippythellama> heh... rsvp and you're entered in the wall of shame, which goes public after hack night.  the interface for removing yourself is only available on-site
18:41:34 <whippythellama> bwuahhahaha
18:41:54 <mhrivnak> I would be very happy suspending this as a regular event, and only do one-offs when we think they really make sense and we can drum up a lot of interest.
18:42:00 <whippythellama> mhrivnak: i agree
18:42:12 <whippythellama> i think for some of our topics they will be well suited
18:42:31 <whippythellama> i'm primarily thinking about when we can get the speaker to come back and lead a workshop type setup
18:42:45 <jeremyhwllc> right
18:42:50 <qqx> That does somewhat add to the main meeting planning then.
18:42:50 <jeremyhwllc> I agree
18:43:02 <whippythellama> qqx: only in some cases
18:43:08 <qqx> Rather than being somewhat separate, and able to be delayed by a week.
18:43:19 <whippythellama> ?
18:43:24 <jackhill> from the institutional memory: we used to do non-recurrent extra events on Saturday. We tried out the weekday thing because Saturday is suboptimal for some people and I observed that other groups (e.g. the now-defunct TA3M) had sucess with the weekday format.
18:43:25 <whippythellama> sorry, i'm not sure what you mean
18:43:29 <whippythellama> ^^ qqx
18:44:11 <qqx> If we only want to do that when we can get the speaker back, we need to check on their availability and arrange for a location.
18:44:12 <whippythellama> jackhill: gotcha; thanks  :)
18:44:23 <qqx> Ideally before the main meeting for both of those.
18:44:32 <whippythellama> qqx: agreed
18:45:02 <qqx> Not necessarily a big addition, but still something.
18:45:06 <whippythellama> yeah, it is
18:45:07 <mhrivnak> yep.
18:45:28 <jeremyhwllc> I usually ask the speakers to lead a hack night. no takers this year
18:45:46 <qqx> It's pretty early in the year. :)
18:45:47 <mhrivnak> The selinux speaker is interested in doing this.
18:46:02 <whippythellama> to be fair, there are only some topics which are well suited for them
18:46:21 <whippythellama> drones probably wouldn't be, for example, nor would sdr necessarily
18:46:51 <whippythellama> both require additional hardware that most members probably don't have, and those that do may not need a hack night to get up and running with them
18:47:12 <jeremyhwllc> if the speaker is from out of town the hack night is unlikely
18:47:17 <qqx> Or for things like that it might be good to have more than a week between the presentation and the hack night.
18:47:24 <whippythellama> the selinux thing that mhrivnak just mentioned would, because really all you need is your linux laptop/vm
18:47:30 <whippythellama> jeremyhwllc: agreed
18:47:39 <whippythellama> qqx: very true
18:47:45 <qqx> Allow the presentation to get people interested, then have time to order the hw.
18:47:48 <whippythellama> or possibly on a weekend
18:48:55 <mhrivnak> In the interest of time, should we just agree that we'll suspend these as a regular event, and only bring them back for presenters who really want to do one, or other special occasions?
18:49:02 <jeremyhwllc> hardware requirements and hack night details used to be announced on the same post and promo email
18:49:02 <whippythellama> so i'll go ahead and ask...
18:49:09 <mhrivnak> And we can consider them individually?
18:49:27 <whippythellama> jeremyhwllc: definitely a good idea
18:49:47 <whippythellama> do we all agree that we are going to suspend hack nights in their current incarnation?
18:49:55 <jeremyhwllc> that cuts down on announcements
18:49:58 <whippythellama> any objections?
18:49:58 <mhrivnak> +1
18:50:00 <qqx> whippythellama: agreed here
18:50:06 <stmiller> good with me :)
18:50:17 <whippythellama> stmiller: i kind of figured ;)
18:50:24 <jeremyhwllc> and allows us more time to promote next meeting
18:50:24 <whippythellama> jeremyhwllc: you?
18:50:42 <jeremyhwllc> i vote in favor
18:50:49 <whippythellama> so for one-off hack nights / workshops
18:51:13 <whippythellama> shall we just ask each speaker if they're willing and available to do it sometime in the same month they're speaking?
18:51:25 <jeremyhwllc> yes
18:51:35 <mhrivnak> Sure.
18:52:03 <whippythellama> it will make for some additional logistics if they say yes, but assuming we get enough lead time it shouldn't be too onerous
18:52:23 <qqx> Between the speaker and us, we should probably also consider if it makes sense.
18:52:30 <whippythellama> qqx: absolutely
18:52:49 <mhrivnak> Agreed. A RHV/ovirt hack night would probably not work well. :)
18:52:55 <mhrivnak> So we wouldn't offer.
18:52:59 <whippythellama> heh
18:53:01 <jeremyhwllc> we can probably use the frontier if needed for hack nights
18:53:08 <stmiller> Just bring your own netapp cluster, and servers, and you can setup rhv
18:53:11 <whippythellama> jeremyhwllc: probably so - good point
18:53:20 <whippythellama> exactly!
18:53:22 <whippythellama> no problem
18:53:44 * mhrivnak has another meeting at 2
18:53:45 <whippythellama> ok, i think we've probably sufficiently flogged the deceased equestrian mammal
18:53:48 <qqx> The parking situation at the Frontier is definitely better, even compared to normal nights at Caktus.
18:54:00 <whippythellama> #topic February Meeting
18:54:19 <whippythellama> jeremyhwllc: have you received summaries and bios yet?
18:54:29 <jeremyhwllc> I plan to post Feb meeting details. contact second speaker for abstract and bio. promote to local groups. ask brian henning to print 2 blinky morse code TriTux for the speakers. and perhaps some small ones as well
18:54:32 <mhrivnak> Also, jeremyhwllc thanks for tracking down more speakers!
18:54:41 <stmiller> +1
18:54:46 <whippythellama> +`
18:54:49 <whippythellama> er
18:54:51 <whippythellama> +1
18:54:53 <whippythellama> that
18:54:59 <jeremyhwllc> :-)
18:55:03 <whippythellama> jeremyhwllc: awesome, thank you!
18:55:25 <jeremyhwllc> good intentions to do it tonight
18:55:27 <mhrivnak> woot
18:55:31 <whippythellama> sweet
18:55:51 <whippythellama> ok, since we went long on the hack night discussion let's move on
18:55:57 <whippythellama> thank you again, jeremyhwllc :)
18:56:11 <whippythellama> #topic Future Topics
18:56:26 <whippythellama> mhrivnak: looks like selinux is on track for march, yes?
18:56:30 <mhrivnak> yes.
18:56:35 <whippythellama> excellent
18:56:51 <jeremyhwllc> awesome
18:56:52 <whippythellama> you mentioned a hack night along with it?
18:57:07 <mhrivnak> Yes, the speaker wants to do a workshop.
18:57:21 <whippythellama> stmiller: thank you for chasing down the serverless django+aws talk
18:57:25 <whippythellama> sweet
18:57:35 <stmiller> yeah! It will be an awesome talk
18:57:54 <whippythellama> does he think he can fit it into a two hour window, or did he want to do something longer on a saturday or something?
18:58:05 <whippythellama> stmiller: i'm definitely looking forward to it :)
18:58:16 <mhrivnak> I think 2 hours of selinux is enough for anyone. ;)
18:58:19 <whippythellama> lol
18:58:21 <whippythellama> fair enough
18:58:39 <stmiller> I'll ask. I think it will fit within a regular meeting. Can demo launching a site serverless, show aws console, some lambda code, and more.
18:59:15 <whippythellama> heh... that question was actually to mhrivnak about the hack night, but good to know  :)
18:59:37 <whippythellama> ok, time running short
18:59:43 <whippythellama> #topic General Business
18:59:54 <whippythellama> we still need to figure out the os upgrade on pilot
19:00:11 <whippythellama> but not today
19:00:16 <mhrivnak> Gotta go. I'll catch up with you all later.
19:00:22 <whippythellama> anyone have anything else they need to talk about?
19:00:27 <whippythellama> ok, thank you mhrivnak
19:00:28 <qqx> Nope
19:00:31 <stmiller> nothing
19:00:37 <jeremyhwllc> notta
19:00:52 <whippythellama> alrighty then.... on that note...
19:00:55 <whippythellama> #endmeeting