17:00:01 <tmcpeak> #startmeeting security
17:00:01 <openstack> Meeting started Thu Oct 13 17:00:01 2016 UTC and is due to finish in 60 minutes.  The chair is tmcpeak. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:04 <openstack> The meeting name has been set to 'security'
17:00:05 <tmcpeak> #chair hyakuhei
17:00:06 <openstack> Warning: Nick not in channel: hyakuhei
17:00:06 <hyakuhei-> o/
17:00:07 <openstack> Current chairs: hyakuhei tmcpeak
17:00:16 <tmcpeak> #chair hyakuhei-
17:00:19 <openstack> Current chairs: hyakuhei hyakuhei- tmcpeak
17:00:20 <tkelsey> o/
17:00:25 <vinaypotluri> o/
17:00:27 <tmcpeak> #link https://etherpad.openstack.org/p/security-agenda
17:00:37 <knangia> o/
17:00:42 <hyakuhei> Hey! Sorry about that
17:00:55 <hyakuhei> My BNC doesn't auth with Nickserv properly
17:01:01 <ccneill> o/
17:01:21 <unrahul> o/
17:01:28 <redrobot> o/
17:01:36 <hyakuhei> Interesting, who put privacy badger on there. I'm guessing they browse reddit :)
17:01:39 <hyakuhei> oh hai redrobot !
17:01:47 <redrobot> hi guys!
17:01:51 <tmcpeak> hyakuhei: that would be fungi
17:01:56 <hyakuhei> excellent
17:02:13 <tmcpeak> allright, let's get started
17:02:19 <tmcpeak> #topic Privacy Badger + Security Blog
17:02:34 <tmcpeak> fungi: mentioned that Privacy Badger despises our security blog
17:02:37 <tmcpeak> fungi: you around?
17:02:57 <hyakuhei> Interesting
17:03:18 <hyakuhei> It's green[0] for me...
17:03:22 <tmcpeak> does anybody use security badger?  I assume this is a drawback of using the github.io?
17:03:34 <tmcpeak> green[0] sounds good
17:03:35 <redrobot> I use the badger
17:03:38 <redrobot> what's the url?
17:03:45 <hyakuhei> #link https://openstack-security.github.io/
17:03:46 <tmcpeak> http://openstack-security.github.io/
17:04:24 <tmcpeak> lol, welcome capnoday
17:04:26 <capnoday> o/
17:04:31 <capnoday> hey guys, sup?
17:04:35 <gmurphy_> it complains about logging into google user content or something...
17:04:40 <tmcpeak> <3 that nick
17:04:47 <tmcpeak> gmurphy_: yeah, that's what fungi said too
17:04:51 <hyakuhei> Interesting, that must be a non-default setting.
17:05:03 <gmurphy_> http://imgur.com/a/bi1wz
17:05:04 <tmcpeak> is that because of hyakuhei email address?
17:05:18 <hyakuhei> Hmm. Interesting.
17:05:30 <gmurphy_> https://www.eff.org/privacybadger == plugin
17:05:35 <lhinds> hi , sorry I am late
17:05:41 <ccneill> looks ok with noscript + uBlockOrigin
17:05:43 <hyakuhei> Yeah, I don't have that come up when I hit it
17:05:44 <tmcpeak> heh, hyakuhei must have always allowed google user content in the past
17:05:49 <ccneill> but I can see hyakuhei's email in plaintext O:-)
17:05:54 <sigmavirus> o/
17:06:00 <tmcpeak> hi lhinds and sigmavirus
17:06:02 <hyakuhei> tmcpeak narp, it's been installed all of 10 minutes
17:06:02 <redrobot> yeah, the badger is real upset about the Google User Content
17:06:07 <hyakuhei> The google content is images anyway
17:06:41 <tmcpeak> oh, it's linked to google drive
17:06:41 <hyakuhei> To my mind that's a false positive but we could move the images into github and link directly
17:06:41 <tmcpeak> I see
17:06:54 <hyakuhei> Though that makes tmcpeak grumpy because he doesn't like binary in Git
17:07:08 <tmcpeak> well we already have tons of them, might as well add  a few
17:07:11 <sigmavirus> hyakuhei: github has lfs right?
17:07:19 <tmcpeak> I think binaries that are unlikely to change are OK
17:07:31 <hyakuhei> I'll open it as a GH issue, if someone _wants_ to move it all out of Google I won't stop them :)
17:07:36 <hyakuhei> tmcpeak +1
17:07:44 <ccneill> find a free CDN tier somewhere maybe?
17:07:48 <tmcpeak> sweet
17:08:32 <tmcpeak> allright, next topic?
17:08:36 <capnoday> if only there was some kind of cloud thing we could host that on
17:08:40 <hyakuhei> ccneill I think just git will work, one less thing to worry about keeping track of
17:08:46 <capnoday> +1
17:08:47 <hyakuhei> capnoday there is no cloud...
17:08:50 <tmcpeak> capnoday: then the cloud will track you ;)
17:08:59 <capnoday> its just someone elses server?
17:09:04 <ccneill> hyakuhei: +1
17:09:18 <tmcpeak> honestly I don't understand what's the implication here?  google knows that I went to the OS security blog?
17:09:27 <ccneill> yep
17:09:45 <tmcpeak> top 20% on my list of things I don't give s' about :P
17:09:58 <tmcpeak> that being said, I've given up on privacy long ago
17:10:09 <hyakuhei> well, google _might_ know
17:10:23 <hyakuhei> It's more the concern that the blog is using something like single pixel images to track you etc
17:10:27 <ccneill> Google probably knows anyway if you're using Chrome :P
17:10:30 <hyakuhei> either way it's a false positive
17:10:46 <tmcpeak> but still would be nice to not have our visitors that are using privacy badger get nasty alerts
17:11:10 <tmcpeak> hyakuhei: +1
17:11:17 <tmcpeak> #topic OpenCIT
17:11:25 <tmcpeak> so I met with some of the Intel folks last week
17:11:33 <tmcpeak> has anybody heard of Intel CIT?
17:11:47 <tmcpeak> #link https://01.org/opencit
17:12:00 <hyakuhei> Only a little. I know we spoke about it before tmcpeak but it wasn't what I thought it was.
17:12:23 <tmcpeak> basically the idea is to use TPMs to perform host attestation to verify each progressive stage of boot up through the kernel
17:12:46 <tmcpeak> this can help detect certain attacks
17:12:52 <lhinds> I wonder if they are going to re-write the nova filter
17:12:52 <capnoday> do i care any more than about regular attestation?
17:12:53 <hyakuhei> Nice, yeah the boot chaining stuff is great
17:12:57 <lhinds> it badly needs it
17:13:13 <tmcpeak> lhinds: yeah, that's what this proposal is.  They want to bring that back up and figure out how to get it
17:13:29 <tmcpeak> OpenCIT can be used to do things like geofencing too, which is interesting given European data laws and such
17:13:33 <lhinds> good move
17:13:35 <hyakuhei> Interesting, does it have any of the people working on it who were involved with TrustedCompute?
17:13:39 <tmcpeak> so we'd like to use a security session to discuss how to move it forward
17:13:44 <tmcpeak> hyakuhei: I'm sure it does
17:14:23 <hyakuhei> Interesting. So I'd love to hear more about what they're doing. TC ended up bouncing out of Nova because it wasn't really used IIRC
17:14:38 <lhinds> tmcpeak: I am interested in jumping in and hearing whats possible
17:14:41 <hyakuhei> This is more the 'under-cloud' though right?
17:14:50 <hyakuhei> Or a fully trusted stack?
17:14:53 <tmcpeak> lhinds: awesome
17:15:05 <tmcpeak> hyakuhei: undercloud focus for now, but there are some other cool uses later
17:15:32 <tmcpeak> for example, you could use a trusted and immutable module in a kernel to validate the contents of containers and only deliver secrets to those that pass a check
17:15:34 <tmcpeak> that kind of stuff
17:15:46 <lhinds> I beleive a big problem with the former TC filter, is it marked a host as trusted based on last boot, but if it had been compromised after then, it would still say 'go ahead' to any VM's asking for a trusted compute host
17:16:23 <lhinds> false sense of security I guess would be the words to use
17:16:25 <hyakuhei> lhinds yup, that was the problem with TCP and OAT all over TBH
17:16:42 <hyakuhei> Knowing a host came up with good firmware 3 months ago is of little value
17:16:49 <lhinds> hyakuhei: +1
17:16:49 <tmcpeak> lhinds: yeah, there are some challenges along those lines.  Because of some work I've done in my day job I can help describe the current state of a lot of this too
17:16:54 <hyakuhei> However the ability to re-attest is interesting
17:16:59 <hyakuhei> In a live system etc.
17:17:01 <tmcpeak> Intel has some things to address that problem in their commercial product they may open source at some point
17:17:09 <lhinds> tmcpeak: definately intrested
17:17:23 <tmcpeak> lhinds, hyakuhei: awesome!
17:17:32 <tmcpeak> so I'm just going to add a session proposal to
17:17:33 <tmcpeak> #link https://etherpad.openstack.org/p/barcelona-security-sessions
17:17:46 <tmcpeak> seems like we have only 3 so far
17:17:47 <hyakuhei> Please do. I need to finalize those over the next few days.
17:17:50 <tmcpeak> how many rooms do we have hyakuhei?
17:17:59 <tmcpeak> we may need to give some back if we don't have additional topics
17:19:04 <hyakuhei> I'll mention it but my understanding is we are not pushed for space at this summit, in fact there were a few slots going spare.
17:19:12 <tmcpeak> hyakuhei: gotcha
17:19:21 <tmcpeak> I saw on the ML at least one project give some back
17:19:31 <tmcpeak> anyway, let's move to regular agenda
17:19:38 <tmcpeak> #topic Syntribos
17:19:48 <tmcpeak> ccneill, unrahul
17:19:59 <hyakuhei> I see a lot of Syntribos patches landing recently :)
17:20:07 <ccneill> mmm not as many as a few weeks ago haha
17:20:12 <unrahul> :D
17:20:31 <ccneill> we'd like to get browne's CR here merged: https://review.openstack.org/#/c/379844/2
17:20:38 <ccneill> if there's anyone here who can give it a nudge :)
17:20:45 <ccneill> oops, no /2 at end
17:20:53 <ccneill> I always do that >_<
17:21:07 <ccneill> so we've started planning for Ocata
17:21:10 <ccneill> https://etherpad.openstack.org/p/syntribos-planning-ocata
17:21:25 <browne> sorry, i need to revisit the patch.  been busy with my day job
17:21:50 <ccneill> browne: no worries, Andreas asked for a few minor edits so I just jumped in and made them real quick. hope you don't mind me jumping in
17:22:39 <browne> no problem at all
17:22:47 <ccneill> we have a few short-term objectives: get a working PyPI release cut, publish docs somewhere, and link it in a retrospective post on the OSSP blog
17:23:13 <ccneill> turns out we have the python job all set up for pypi releases, just gotta tag a release. anyone with experience numbering those, hit me up
17:23:15 <hyakuhei> As your planning these things can you start to think about OpenStack release phases ?
17:23:35 <ccneill> sure, our goal is to have a pypi release cut by the summit if possible
17:23:45 <ccneill> have a bit of work to do around the pypi installation process, but I think we might make it
17:24:13 <sigmavirus> ccneill: i can help with that
17:24:25 <sigmavirus> ccneill: there's little reason for you to start tagging things yourself
17:24:34 <hyakuhei> We need to do similar things (Release management, OpenStack Style) for Anchor, Bandit etc
17:24:35 <ccneill> ok, well that's just my ignorance talking
17:24:44 <ccneill> not sure what the common best practices are
17:24:44 <sigmavirus> ccneill: nah, it's probably out of date docs too
17:24:57 <sigmavirus> openstack/releases is the repo to use
17:25:08 <tmcpeak> hyakuhei, sigmavirus maybe we can use a session for that at the summit?
17:25:16 <tmcpeak> knock all of them out at once
17:25:18 <ccneill> so, we've been talking about how to package up templates and payloads for a base pypi install
17:25:18 <tmcpeak> sigmavirus: you coming?
17:25:23 <sigmavirus> I'm not
17:25:33 <ccneill> our thought right now is to basically have separate repos for them
17:25:41 <hyakuhei> tmcpeak that's a good idea. An idiots guide so to speak. There might be others who can drop in and help.
17:25:42 <sigmavirus> ccneill: data_files is what I'd use
17:25:47 <sigmavirus> but a separate repo could work too
17:25:47 <hyakuhei> Sorry to hijack ccneill
17:25:48 <ccneill> so on your first run, you go download the payloads, and can cache them or not
17:26:12 <tmcpeak> hyakuhei: +1
17:26:20 <ccneill> hyakuhei: no worries. so a session about uniting OSSP project releases?
17:26:25 <ccneill> sounds good to me
17:26:59 <ccneill> sigmavirus: so I've fumbled around looking at pbr a bit, and I'm not sure how to work with data_files in the way we need to
17:27:17 <ccneill> we want to ship them to ~/.syntribos/payloads in most cases
17:27:22 <sigmavirus> hyakuhei: do we have time to discuss that here or should ccneill and I move to -security?
17:27:30 <sigmavirus> ccneill: ah, neither pbr nor setuptools/wheel will make that easy for you
17:27:36 <ccneill> yeah :(
17:27:49 <ccneill> thought about package -> /usr/share/syntribos -> our folder maybe
17:27:52 <hyakuhei> sigmavirus we've got time, it's important for all our code-y projects.
17:28:11 <ccneill> but that intermediate step isn't always easy, since it might be /usr/share or /usr/local/share or /dev/null based on system..
17:28:24 <ccneill> (not really /dev/null, but it does vary)
17:28:43 <ccneill> anyway, if we were to do repos, I was curious if that would be something that we would host under openstack? or outside it
17:29:04 <ccneill> so we were thinking like "syntribos-payloads", "syntribos-keystone-templates", "syntribos-neutron-templates", etc
17:29:17 <ccneill> that way we don't ship you 5000 files on install, and you pick the pieces you want
17:29:23 <sigmavirus> ccneill: that'd be inside openstack
17:29:33 <sigmavirus> ccneill: right, having another package makes sense
17:29:56 <sigmavirus> ccneill: maybe even separate packages for separate services?
17:30:05 <unrahul> Also the repo way has the advantage of updating the payloads whenever its necessary and giving a sub command to update the user local version as well.
17:30:32 <ccneill> sigmavirus: that's the idea, splitting it all up so that we don't ship stuff that general end-users aren't interested in
17:30:40 <sigmavirus> ccneill: why not build into syntribos teh ability to download these from a git repo?
17:30:41 <sigmavirus> or website
17:30:43 <sigmavirus> or whatever?
17:30:58 <ccneill> sigmavirus: yep, that's where we're headed at the moment
17:30:59 <sigmavirus> i.e., syntribos download-templates http://github.com/openstack/syntribos-nova-templates
17:31:02 <ccneill> I believe unrahul is working on it
17:31:14 <unrahul> ccneill: +1 yup just started.
17:31:23 <sigmavirus> that way you don't need to package the templates
17:31:25 <ccneill> just wanted to air the idea and see if anyone had other ideas, but I'm hearing that this sounds reasonable
17:31:34 <sigmavirus> ccneill: absolutely
17:31:38 <ccneill> cool cool
17:31:51 <sigmavirus> that said, for releasing syntribos, using openstack/releases is the best idea
17:32:04 <ccneill> ok, will definitely look into that
17:32:05 <ccneill> thanks
17:32:06 <sigmavirus> we already have bandit imported there for now
17:32:10 <ccneill> sweet
17:32:21 <sigmavirus> (so for our next bandit release we can use that)
17:32:33 <ccneill> so one other thing that we're probably going to be revamping soon is our request template language
17:32:41 <ccneill> how we doing on time? want me to carry this to -security? or keep going?
17:32:53 <ccneill> tmcpeak? hyakuhei ?
17:32:55 <sigmavirus> ccneill: I'd revamp that before you release if it's going to break anything
17:32:56 <tmcpeak> yeah, let's move to security
17:33:08 <tmcpeak> got a few more agenda items to cover
17:33:11 <ccneill> ok, sounds good. figured we were getting in the weeds a bit. but tl;dr: fun stuff on the way
17:33:16 <tmcpeak> good stuff
17:33:18 <tmcpeak> #topic OSSN
17:33:19 <ccneill> and if anyone wants to get involved, please reach out! :)
17:33:24 <tmcpeak> lhinds: you're up
17:33:59 <lhinds> ok, been out of action a little bit, but I have one to go out after this call (embargoed glance note)
17:34:15 <lhinds> and we have four more then, hyakuhei is also very close to having a final draft.
17:34:33 <lhinds> after that we have another three to get out (one new one came in iirc)
17:34:48 <tmcpeak> capnoday: you've been dying to write embargoed notes
17:34:50 <hyakuhei> I think I'm still waiting for an OK on one of the embargoed ones
17:35:01 <capnoday> tmcpeak i live for that!
17:35:05 <tmcpeak> boom
17:35:24 <hyakuhei> haha +1
17:36:04 <lhinds> hyakuhei: couple of notes from gmurphy_ and o-tony
17:36:08 <lhinds> its close though!
17:36:24 <hyakuhei> ok, so what do we need to do to get them all over teh line.
17:36:25 <lhinds> or maybe even ready if the nits are missing the point
17:36:34 <hyakuhei> Ah on mine, yeah
17:36:51 <lhinds> should have said comments rather then notes...yep
17:37:18 <tmcpeak> posting versions of the note on Launchpad kind of sucks
17:37:24 <lhinds> tmcpeak and dg___ have some to work on too :)
17:37:30 <tmcpeak> wonder if we want to get to subscribing people to our google doc
17:37:50 <hyakuhei> Yeah, so generally I get the note up to scratch and then post the final-ish draft
17:38:09 <lhinds> ^ what hyakuhei said
17:38:11 <tmcpeak> I had to go back and forth 5 or 6 times on one of them on Launchpad
17:38:25 <lhinds> but I am not against extending it into the cores / vmt's
17:38:25 <capnoday> welcome to openstack tmcpeak
17:38:52 <tmcpeak> well, I'm happy to forget about it for now
17:39:04 <hyakuhei> lol
17:39:13 <lhinds> shall we try google-docs on the next one, maybe the one just assigned to you tmcpeak
17:39:13 <tmcpeak> lhinds: anything else for notes?
17:39:19 <hyakuhei> A better process for these embagoed OSSN would be nice
17:39:19 <tmcpeak> lhinds: yep
17:39:25 <lhinds> the main thing is making sure we accept from valid emails
17:39:31 <tmcpeak> hyakuhei: yeah, especially given how many of them there are these days
17:39:33 <hyakuhei> but so would a better gerrit process for all bad vulns
17:39:50 <hyakuhei> It's a constant issue for the VMT
17:39:59 <tmcpeak> yep
17:40:10 <tmcpeak> allright, we've got to move on
17:40:16 <lhinds> i am done
17:40:19 <tmcpeak> sweet
17:40:21 <tmcpeak> #topic Blog
17:40:30 <tmcpeak> lhinds: you post your masterpiece yet?
17:40:33 <lhinds> tmcpeak: mypost can go out
17:40:44 <hyakuhei> Cool! lhinds you should be able to publish it yourself?
17:40:45 <tmcpeak> hyakuhei: can you add lhinds to the repo so he can merge his own stuff?
17:40:48 <lhinds> I just needed to check real life names are ok
17:40:56 <lhinds> hyakuhei: cool, will take a look
17:41:11 <tmcpeak> #topic Security Review
17:41:17 <hyakuhei> capnoday ?
17:41:20 <tmcpeak> I actually don't think we have anything new hee
17:41:21 <tmcpeak> *here
17:41:29 <tmcpeak> we met with Kolla last week but already discussed that last meeting
17:41:30 <hyakuhei> I think the babrican one wrapped?
17:41:37 <tmcpeak> yeah, think so
17:41:46 <tmcpeak> capnoday: you are now Security Review point person :)
17:41:47 <capnoday> yeah the big news is the barbican one got merged
17:41:50 <tmcpeak> weekly wrap up
17:41:56 <hyakuhei> Do we need to create issues from the barbican one ?
17:42:07 <tmcpeak> hyakuhei: yeah, I think we had at least one that I remember
17:42:16 <tmcpeak> that is probably a note/OSSA
17:42:19 <sigmavirus> is there a repo where these reviews are being collected?
17:42:26 <tmcpeak> there is..
17:42:28 <hyakuhei> yup, capnoday got a linky ?
17:42:32 <capnoday> sigmavirus yes its the security-analysis repo
17:42:36 <capnoday> one sec and I'll dig out a link
17:42:42 <sigmavirus> openstack or on github?
17:42:45 <capnoday> openstack
17:42:48 <tmcpeak> capnoday: want to announce to ML about our completed Barbican review?
17:42:50 <sigmavirus> (sorry, I missed this in the past)
17:42:57 <capnoday> np sigmavirus
17:43:05 <tmcpeak> we should actually probably do a retro blog post on it too
17:43:25 <capnoday> tmcpeak yeah good idea, althugh shall we go through the list of findings first and see if we need to open tickets
17:43:32 <tmcpeak> yeah let's do that first
17:43:44 <sigmavirus> thanks capnoday
17:43:49 <tbarron> manila is interested in pursuing managed-vulnerability tag.  I take it we should look at barbican review as example?
17:43:50 <capnoday> we also need to figure out where we are going to publish completed reviews
17:43:54 * tbarron may be confused
17:43:55 <capnoday> this might be one for sicarie
17:44:11 <hyakuhei> check with redrobot first but I think that's a great idea (publish on the ML)
17:44:37 <capnoday> tbarron yes barbican is a good example, we are currently writing a chapter for the security guide that describes it, once its published (or in review at least) I'll reach out
17:44:40 <redrobot> hyakuhei ML sounds good to me
17:45:12 <tbarron> capnoday: excellent, we'd like to make good progress on this front in ocata
17:45:18 <hyakuhei> Sounds like we could do a blog post around it too, what the experience was like, where we need to improve etc?
17:45:19 <capnoday> excellent
17:45:41 <capnoday> hyakuhei maybe work with redrobot on that?
17:45:55 <hyakuhei> yupyup
17:46:08 <tmcpeak> tbarron: we're happy to work with you to complete a security review
17:46:17 <hyakuhei> We have to scale up to get these done faster :)
17:46:24 <tmcpeak> hyakuhei: yeah
17:46:27 <ccneill> bust out the markov chains!
17:46:28 <hyakuhei> Learning slow is fine so long as we can apply it quickly
17:46:29 <tbarron> tmcpeak: great
17:46:33 <ccneill> :P
17:46:43 <tmcpeak> hyakuhei: +1
17:47:00 <tmcpeak> tbarron: probaly won't have time before the summit
17:47:04 <tmcpeak> want to get with us at the summit?
17:47:05 <capnoday> tmcpeak hyakuhei any thoguhts on publishing reviews?
17:47:11 <tmcpeak> we can get started
17:47:20 <tbarron> tmcpeak: me either?  but yes, at the summit would be perfect.
17:47:28 <tmcpeak> capnoday: I'm pretty sure we should publish them
17:47:33 <capnoday> it would be nice if there was a way to view it in pretty markup like the security guide, rather than having to browse RST in the repo
17:47:35 <tmcpeak> seems like a lot of work to sit in a closet
17:47:37 <tbarron> s/?/:)
17:47:53 <capnoday> but without them being part of the security guide repo, or do we want to move them into there when they are completed?
17:47:53 <tmcpeak> tbarron: great, see you there
17:48:07 <tmcpeak> capnoday: emm, I have no idea
17:48:14 <capnoday> hahah ok
17:48:17 <capnoday> well have a think
17:48:21 <tmcpeak> yeah, would be awesome to have a nice pretty version
17:48:21 <hyakuhei> We can build RST ourselves with the relevant jobs or roll into the security docs stuff, whatever makes the most sense...
17:48:24 <capnoday> I'll talk to sicarie and see what he thinks
17:48:31 <tmcpeak> capnoday: +1
17:48:35 <hyakuhei> cool
17:48:47 <tmcpeak> speaking of sicarie, don't think we're going to have a sec guide update today
17:48:51 <tmcpeak> no sicarie, no elmiko
17:48:53 <capnoday> yeh hes afk
17:48:57 <tmcpeak> so…
17:49:00 <capnoday> i just spoke to him, RL
17:49:15 <tmcpeak> ok
17:49:17 <tmcpeak> #topic AOB
17:49:26 <tmcpeak> are we having a meeting next week?
17:49:37 <tmcpeak> we obviously aren't in Barcelona
17:49:44 <tmcpeak> I'm also gone the following week
17:49:57 <lhinds> I am around next week
17:50:11 <lhinds> is there something going on next week?
17:50:21 <hyakuhei> Traditionally we don't pre summit
17:50:22 <tmcpeak> no, just don't know if people are heading out early
17:50:24 <tmcpeak> I'm around too
17:50:30 <tmcpeak> hyakuhei: yea, that :)
17:50:32 <lhinds> ah ok.
17:50:35 <hyakuhei> I should be around I think
17:50:56 <hyakuhei> #vote Should we have a meeting next week?
17:51:12 <hyakuhei> Oh maybe I can't because I changed nick after I got chair
17:51:27 <capnoday> #vote Should we have a meeting next week?
17:51:34 <capnoday> nope, i cant
17:51:37 <hyakuhei> TBH I think we can skip it. Give people some breathing room before the summit
17:52:00 <tmcpeak> yeah, let's skip it
17:52:00 <capnoday> +1
17:52:10 <hyakuhei> ok cool.
17:52:19 <tmcpeak> allright, anything else?
17:52:19 <lhinds> I am ok with that
17:52:51 <tmcpeak> #endmeeting