17:00:17 <tmcpeak> #startmeeting security
17:00:18 <openstack> Meeting started Thu Mar  3 17:00:17 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:20 <mvaldes> o/
17:00:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:21 <tmcpeak> #chair hyakuhei
17:00:21 <elmiko> \o
17:00:22 <openstack> The meeting name has been set to 'security'
17:00:24 <openstack> Current chairs: hyakuhei tmcpeak
17:00:28 <hyakuhei> Hi Guys
17:00:28 <tkelsey> o/
17:00:32 <hyakuhei> o/
17:00:34 <LHinds> hey all
17:00:35 <hyakuhei> thanks tmcpeak
17:00:37 <cjschaef> hi
17:00:40 <tmcpeak> sure :)
17:00:50 <browne> o/
17:00:57 <hyakuhei> I’ve got a copy-pasted agenda from last week here #link https://etherpad.openstack.org/p/security-20160303-agenda
17:01:07 <hyakuhei> Obviously need supdating with things people care about
17:01:56 <michaelxin> hello
17:02:00 <hyakuhei> hey michaelxin !
17:03:16 <hyakuhei> Ok so our room requests are in, lets wait to see what the openstack gods decide
17:03:31 <hyakuhei> Track choices should be out soon too I think
17:03:35 * elmiko lights sacrificial incense
17:04:45 <hyakuhei> hehe
17:04:53 <hyakuhei> We had to have the final decisions in by Monday
17:06:03 <tmcpeak> would be cool to know soon :)
17:06:10 <hyakuhei> Right ok, so I guess we can get started :)
17:06:12 <hyakuhei> Yeah it would!
17:06:48 <tmcpeak> allright
17:06:52 <hyakuhei> The track chairing (for security) went really well this year, good discussions on various aspects. We’ve tried to create a pretty inclusive track
17:07:02 <elmiko> nice
17:07:17 <mvaldes> awesome. thanks for the hard work on that
17:07:22 <elmiko> are there many security related talks submitted?
17:07:25 <hyakuhei> My pleasure
17:07:36 <hyakuhei> Righto, agenda wise - did any of you guys look at the BYOK stuff?
17:07:49 <elmiko> i did, not sure i have much to add though :/
17:07:50 <hyakuhei> #link https://review.openstack.org/#/c/271517/
17:07:59 <hyakuhei> If you have crypto thoughts, please add them
17:08:17 <hyakuhei> Although this is crypto stuff it’s a Security project
17:08:24 <hyakuhei> So it’s ours to screw up all on our own.
17:08:25 <michaelxin> trying to multitask here.
17:08:34 <hyakuhei> Though Barbican will help :P
17:08:45 <elmiko> hehe
17:08:52 <tmcpeak> looks like the bikeshed is alive and well with this one
17:09:03 <hyakuhei> Indeed
17:09:17 <hyakuhei> It’s all good content though
17:09:24 <hyakuhei> Just need a gentle nudge
17:09:32 <michaelxin> +1
17:09:39 <hyakuhei> Ok, so I don’t have anything to add regarding the summit
17:09:47 <hyakuhei> Anyone else got questions before we do Agenda things?
17:10:05 <elmiko> just curious if there are many sec. related talks
17:10:19 <hyakuhei> There’s a whole track
17:10:20 <tmcpeak> how much of a track did we get hyakuhei?
17:10:25 <tmcpeak> four days?
17:10:29 <hyakuhei> Oh I see
17:10:36 <elmiko> cool, very encouraging to hear
17:10:37 <hyakuhei> So we got hmmm… 10 slots I think
17:10:50 <tmcpeak> that's pretty solid
17:10:51 <hyakuhei> How they stack up over the week is beyond my understanding
17:11:12 <hyakuhei> Got a couple of good alternates in there too, we could have had a very compelling 15 talk track
17:11:24 <elmiko> neat
17:11:44 <tmcpeak> it's 4 days this time, right
17:11:45 <tmcpeak> ?
17:12:00 <michaelxin> great
17:12:24 <mvaldes> the conference is mon - thurs
17:12:39 <mvaldes> ops and design is mon - fri
17:12:41 <hyakuhei> yeah I think the big difference this time around is they’ve moved the ops stuff?
17:12:52 <hyakuhei> so it deconflicts with most of the rest of the design summit?
17:13:13 <mvaldes> https://www.openstack.org/themes/openstack/static/images/austin/schedule-chart.svg
17:13:36 <michaelxin> mvaldes: +1
17:13:52 <tmcpeak> cool
17:14:09 <elmiko> i'm really curious to see how that proposal to split the summit proceeds
17:14:12 <hyakuhei> WOO is such a cool acronym
17:14:16 <elmiko> +1
17:14:43 <hyakuhei> ok, agenda then
17:14:47 <hyakuhei> #topic Anchor
17:14:59 <hyakuhei> Stan did some good work on this, a bunch of stuff merged and 0.3 is in Pypi now
17:15:02 <hyakuhei> tkelsey: ?
17:15:07 <hyakuhei> Is that accurate?
17:15:26 <tkelsey> not sure about Pypi, sorry
17:15:37 <hyakuhei> oh ok, maybe that’s not updated then, as you own it.
17:15:38 <hyakuhei> heh
17:15:42 <tkelsey> Stan was asking about it, but i dont know if he got anything in
17:15:46 <hyakuhei> Unless Stan hacked your creds
17:15:55 <tkelsey> wait I own it :-/
17:16:01 <hyakuhei> which… I mean…. it’s stan, so entirely possible.
17:16:05 <hyakuhei> https://pypi.python.org/pypi/anchor/0.3
17:16:05 <tkelsey> OK i'll find out whats going on there then lol
17:16:06 <tmcpeak> yeah
17:16:16 <hyakuhei> https://www.dropbox.com/s/66acgvh3i7ugm9f/Screenshot%202016-03-03%2017.16.13.png?dl=0
17:16:23 <hyakuhei> ^ ANCHOR BOSS
17:16:53 <elmiko> nice, +1 tkelsey ;)
17:16:57 <tkelsey> well I guess thats good :D (yeah i'll find out what the deal is) been distracted with Bandit 1.0 and other suff
17:17:13 <hyakuhei> No problem.
17:17:23 <mvaldes> there was some interest re: anchor during my OWASP talk on syntribos last Friday
17:17:49 <tkelsey> mvaldes: oh, thats interesting :0
17:17:50 <tkelsey> :)
17:17:54 <hyakuhei> I’ve been wondering how/if Anchor should be positioned or extended to behave a little bit more like Amazon’s new certificate service
17:17:58 <mvaldes> i mentioned OSSP and a few of the projects. made sure they knew we were looking for help/testing/etc
17:18:06 <hyakuhei> Though I guess Barbican front ending some other CA makes more sense there, potentially
17:18:11 <hyakuhei> thats cool mvaldes
17:18:16 <hyakuhei> oh, I had one other thing
17:18:19 <tkelsey> mvaldes: awesome :)
17:18:28 <hyakuhei> I’ve got an in-depth anchor deck
17:18:54 <mvaldes> excellent
17:19:06 <hyakuhei> I mean, if you want 45 minutes on PKI deployments and passive revocation
17:19:07 <hyakuhei> https://docs.google.com/presentation/d/1HDyEiSA5zp6HNdDZcRAYMT5GtxqkHrxbrqDRzITuSTc/edit?usp=sharing
17:19:09 <hyakuhei> Tadaaa
17:19:27 <hyakuhei> Removed 99.3% of the copyrighted content too
17:19:31 <elmiko> we want it live!
17:19:33 <elmiko> ;)
17:19:57 <hyakuhei> Possibly needs some speaker notes as it goes into some interesting places
17:20:01 <hyakuhei> like CRLSets etc
17:20:06 <mvaldes> yes pls :)
17:20:21 <hyakuhei> My favorite bit here: https://www.dropbox.com/s/rkmw5kicwmoc5xn/Screenshot%202016-03-03%2017.20.15.png?dl=0
17:20:35 <mvaldes> lol
17:20:39 <tmcpeak> :#
17:20:57 <wayward710> nice
17:21:04 <hyakuhei> That is public domain / usable though at least heh.
17:21:12 <mvaldes> it may catch on
17:21:18 <hyakuhei> Right, I don’t have anything else to add on Anchor.
17:21:21 <mvaldes> if you're lucky
17:21:51 <ccneill> lol love the "SO MUCH PLUMBING" slide
17:21:58 <hyakuhei> :)
17:22:07 <hyakuhei> I’ve used that or some variation of it for years :)
17:22:16 <hyakuhei> Gets a good chuckle
17:22:30 <hyakuhei> My fave is probably “How security see’s openstack”
17:22:40 <mvaldes> FIRE
17:23:05 <mvaldes> the deck looks good
17:23:06 <elmiko> yea, that slide is awesome
17:23:09 <hyakuhei> Anyway, feel free to borrow as much (or as little) as you’d like from that
17:23:14 <elmiko> and so accurate XD
17:23:31 <hyakuhei> lol
17:23:51 <ccneill> https://i.ytimg.com/vi/C-zCzM5qPec/maxresdefault.jpg
17:23:59 <hyakuhei> ok, any questions on that before we move on ?
17:24:06 <hyakuhei> ccneill: amazing!
17:24:23 <tmcpeak> yeah I bet that's coming in a Rob speech soon
17:24:37 <elmiko> ha! ccneill++
17:24:43 <wayward710> those are great slides
17:24:51 <ccneill> someone made a flag of that picture at the Castle.. I'm so jealous lol
17:25:05 <elmiko> no they didnt... so awesome
17:25:46 <hyakuhei> lol
17:25:50 <hyakuhei> ook,
17:25:53 <hyakuhei> #topic Bandit
17:26:07 <tmcpeak> I think we have the last major feature added that we needed for 1.0
17:26:15 <tmcpeak> from now it should just be filing and closing bugs
17:26:18 <tmcpeak> doc fixes, etc
17:26:34 <tkelsey> yup
17:26:39 <tmcpeak> https://blueprints.launchpad.net/bandit
17:26:41 <tmcpeak> #link https://blueprints.launchpad.net/bandit
17:26:51 <mvaldes> great news!
17:26:56 <tkelsey> just need to land the stuff in flight than double down on docs and any bug fixes
17:27:03 <michaelxin> +1
17:27:08 <tmcpeak> could really use people hammering away at Bandit
17:27:14 <tmcpeak> try using it in ways you don't normally use it
17:27:22 <tkelsey> +1
17:27:45 <ccneill> tmcpeak: is there a slide deck / similar describing everything in 1.0?
17:27:46 <tmcpeak> other than that bit of shameless begging I don't have anything to add :)
17:27:56 <browne> there's been a lot of activity in other projects to hook up bandit into the pep8 testenv
17:27:59 <elmiko> nice, grats on the lp
17:28:02 <tmcpeak> ccneill: no, but that would be great to have
17:28:24 <ccneill> well, I don't know that I'm qualified to do it, but I'm definitely willing to TRY helping with docs
17:28:26 <ccneill> :)
17:28:42 <browne> ccneill:  like release notes?
17:28:45 <tmcpeak> ccneill: that would be awesome!
17:28:56 <LHinds> I had a good go at it this week, but could not find anything issues (which is good!)
17:28:57 <ccneill> browne: yeah, release notes of some kind would be great
17:29:03 <tmcpeak> LHinds: thanks!
17:29:10 <LHinds> s/anything/any
17:29:11 <tkelsey> thanks :)
17:29:12 <tmcpeak> yeah preferably release notes from somebody that isn't a core Bandit dev
17:29:17 <tmcpeak> so we have a fresh pair of eyes
17:29:45 <michaelxin> ccneill: +1
17:30:23 <LHinds> tmcpeak, a review or author?
17:30:31 <tmcpeak> author would be best
17:30:33 <ccneill> tmcpeak: any of these have a much higher priority than others?
17:30:38 <michaelxin> haha
17:30:43 <ccneill> they don't have assigned priorities at the moment
17:30:51 <tmcpeak> ccneill: which are you looking at?
17:30:55 <ccneill> the bps
17:30:59 <ccneill> the link above
17:31:03 <tmcpeak> oh, we're done on those
17:31:07 <ccneill> oh, sweet!
17:31:12 <tmcpeak> 1.0 ones are finished and none of the ones that aren't 1.0 are in
17:31:36 <ccneill> gotcha
17:31:49 <tmcpeak> I guess best thing to do is make sure 1) our wiki is in good shape
17:31:56 <tmcpeak> 2) the docs make sense for how to use it and nothing is missing
17:32:11 <tmcpeak> with those two we're in good shape from a doc perspective
17:32:27 <ccneill> cool, I'll see what I can do
17:32:34 <tmcpeak> ccneill: awesome, thank you!
17:32:41 <ccneill> np - thank you!
17:32:45 <ccneill> this is the easy part :)
17:33:01 <tmcpeak> anything else anybody wants to mention on Bandit?
17:33:12 <browne> tthere's a whole release note feature many of the other projects use.  not sure we should for bandit
17:33:25 <tmcpeak> browne: what's that about?
17:33:39 <elmiko> are you talking about reno?
17:33:44 <browne> yep reno
17:33:47 <elmiko> use it
17:33:58 <LHinds> I am hoping to get the OPNFV project to use Bandit, will keep you updated. Most of what they do is upstreamed, but they do have some infra stuff on LF repos.
17:34:00 <elmiko> it's very convenient for generating release notes
17:34:06 <elmiko> LHinds: neat!
17:34:11 <browne> elmiko: cool
17:34:20 <bknudson> from the discussion on the mailing list reno is generating content for deployers
17:34:27 <bknudson> and deployers don't care about bandit features
17:34:37 <elmiko> hmm, didn't think about that bknudson
17:34:48 <michaelxin> We tried Veracode python support early version
17:35:09 <bknudson> #link https://launchpad.net/bandit/+milestone/1.0
17:35:18 <elmiko> from a developer perspective, reno is really convenient for generating a release note with your changes. but i can see how it might make excess noise in some places.
17:35:57 <elmiko> bknudson: do the reno changes automatically get picked up outside the project, or does something need to be configured to comb the project for notes?
17:36:15 <tmcpeak> bknudson: oh yeah, I'm not sure ^ that is up to date
17:36:18 <bknudson> elmiko: I assume something has to be configured to get the release notes on the release web page
17:36:23 <tmcpeak> we haven't been great about assigning stuff to the milestone
17:36:27 <elmiko> bknudson: gotcha, thanks
17:36:48 <bknudson> so maybe bandit release notes wouldn't be included there?
17:36:51 <browne> the release notes can be included into the project docs.  i've seen projects do that
17:37:12 <michaelxin> +1
17:37:20 <michaelxin> good idea
17:37:23 <browne> and we could tailor to our target audience i believe
17:37:25 <tmcpeak> release notes have been traditionally included in the git commit
17:37:45 <elmiko> yea, i definitely recommend using reno for making the notes and in-project integration. for bandit, i agree with bknudson, it doesn't make sense to agregate those changes for operators.
17:38:33 <tmcpeak> anybody who has good experience with the release notes side - we could really use the help for Bandit
17:38:39 <browne> agregate where?  in my view, we can write them for whomever
17:38:40 <tmcpeak> I know I haven't done anything on that front before
17:38:43 <tmcpeak> I'm kind of shooting in the dark
17:38:55 * ccneill too :(
17:39:10 <elmiko> browne: i just meant, if they were being collated for release with the service project release notes
17:40:10 <browne> guess something worth digging into
17:40:18 <elmiko> tmcpeak: i've used it a bunch, i could take a stab at putting a patch together unless browne wants to dig in
17:40:26 <tmcpeak> elmiko: that would be awesome
17:40:36 <browne> elmiko: go for it
17:40:47 <elmiko> ok, cool
17:41:07 <tmcpeak> cool
17:41:11 <tmcpeak> allright moving on
17:41:15 <tmcpeak> #topic Docs
17:41:28 <tmcpeak> elmiko: looks like you're up :)
17:41:37 <elmiko> ok, well things have been moving along slowly
17:41:47 <elmiko> we have closing some bugs and generally improving the sec. guide
17:42:00 <elmiko> we are still blocked on creating the new pdf/book version though
17:42:02 <tmcpeak> improve is good
17:42:11 <elmiko> i'm not sure where sicarie has gotten to with that
17:42:15 <tmcpeak> what's the plan for the guide?
17:42:25 <tmcpeak> I guess it will need maintenance forever huh?
17:42:37 <elmiko> afaik, we need to get a pdf published and then make a new physical copy available
17:42:55 <hyakuhei> tmcpeak: it’s called a “living document”
17:43:02 <tmcpeak> yep yep
17:43:06 <elmiko> tmcpeak: pretty much, we continue to update, improve, and hopefully add more service content as we find domain experts/authors
17:43:19 <tmcpeak> are there any new chapters planned?
17:43:21 <michaelxin> elmiko: +1
17:43:50 <elmiko> i *think* we had some interest writing a networking chapter around neutron
17:43:53 <hyakuhei> Is there much on Barbican / Crypto
17:44:05 <elmiko> not muc
17:44:06 <elmiko> h
17:44:29 <elmiko> we'd like to get something on barbican, as well as others like trove and manilla
17:44:35 <elmiko> but,
17:44:45 <elmiko> we need more CPLs to help with writing those
17:44:53 <hyakuhei> Of course
17:44:59 <hyakuhei> and there’s a TA chapter in the works
17:45:04 <elmiko> +2
17:45:15 <hyakuhei> Something like https://openstack-security.github.io/threatanalysis/2016/02/07/anchorTA.html
17:45:18 <hyakuhei> but not terrible
17:45:22 <elmiko> lol
17:45:23 <hyakuhei> and finished.
17:45:29 <michaelxin> +2
17:45:43 <elmiko> i think that would be great, plus we could follow the nice checklists that we have for the other chapters
17:45:49 <tmcpeak> yeah a TA chapter would be cool for sure
17:46:15 <elmiko> i think these are great projects for Newton, but we need to do more outreach and hopefully get a few more contributors on board
17:46:30 <tmcpeak> yeah
17:46:36 <tmcpeak> we're spread pretty thin
17:46:58 <michaelxin> we need new blood for sure.
17:46:59 <elmiko> and getting a new leaf version for publishing is a high prio, i know it's been driving sicarie nuts
17:47:10 <wayward710> Sorry, I'll try to start doing stuff. :)
17:47:27 <elmiko> no prob wayward710, i'm just grousing in general XD
17:47:28 <tmcpeak> speaking of spread thin --
17:47:35 <ccneill> hyakuhei: this looks interesting! one tiny thing: looks like there are some headings where the "#" and the subsequent title don't have a space, so it's not rendering as a heading
17:47:36 <tmcpeak> I may be taking some time with less participation for a bit
17:47:48 <tmcpeak> I'm taking a new gig and will probably be busy getting up to speed for a while
17:47:55 <michaelxin> nooooo
17:47:58 <ccneill> oh noez
17:48:03 <wayward710> Thanks.  Just got busier than expected -- probably happened to many people here too. :)
17:48:06 <mvaldes> tmcpeak:  congrats :)
17:48:06 <elmiko> a sad day for the ossp
17:48:10 <tmcpeak> OSSP is awesome and I want to stay involved but it might take some time to get my head above water again :)
17:48:25 <tmcpeak> mvaldes: thanks!
17:48:26 <elmiko> tmcpeak++
17:48:35 <LHinds> I have been thinking of NFV aspects we could introduce, but need to find the differentiators. I will certainly try to come up with something, but only if its of value.
17:48:47 <michaelxin> tmcpeak: congrats!
17:48:48 <LHinds> a lot of what you have there applies to Telco
17:49:01 <LHinds> or rather Telco world
17:49:03 <elmiko> LHinds, thanks! we appreciate any contribs =)
17:49:25 <michaelxin> I am working on something tool
17:49:32 <michaelxin> hopefully it will be finalized soon.
17:49:36 <elmiko> ooh, a docs bonanza!
17:49:41 <elmiko> michaelxin: +1
17:49:50 <tmcpeak> all the docs!
17:49:53 <elmiko> hehe
17:49:55 <michaelxin> so, we will have some new blood joining.
17:50:00 <elmiko> great!
17:50:06 <michaelxin> :-)
17:50:33 <tmcpeak> allright
17:50:36 <tmcpeak> speaking of..
17:50:43 <elmiko> i think that's all i've got
17:50:43 <tmcpeak> #topic Publicity
17:50:46 <tmcpeak> we should try to get the deck presented more
17:51:09 <tmcpeak> that being said I don't think we got any new participation from browne and me presenting at the meetup
17:51:11 <hyakuhei> +1
17:51:16 <tmcpeak> so we might want to adjust our strategy
17:51:18 <ccneill> has OpenStack ever considered a bug bounty?
17:51:26 <ccneill> like, paid bug bounty?
17:51:31 <elmiko> tmcpeak: did you guys have any specific de-brief notes?
17:51:32 <hyakuhei> Yes a couple of times
17:51:39 <hyakuhei> HP considered sponsoring one via ZDI too
17:51:51 <ccneill> I think one of hte problem with getting OSSP people is either 1) they are already deeply dug into OS and know how much of a firehose we have to drink from
17:51:51 <hyakuhei> It was felt that we don’t have the logistical staff to deal with all the terrible reports
17:51:53 <tmcpeak> elmiko: nah, nothing in particular
17:52:03 <ccneill> or 2) they don't know what OS is or how to add value
17:52:04 <hyakuhei> ccneill: +1
17:52:10 <tmcpeak> ccneill: +1
17:52:12 <elmiko> tmcpeak: ack, maybe just a swing and miss... gotta keep up the pressure ;)
17:52:37 <tmcpeak> honestly I think a lot of security people are busy making money and stuff :)
17:52:43 <ccneill> hyakuhei: yeah, I've seen some amazingly bad reports..
17:52:53 <elmiko> i also feel that corporate interests don't always value having their people spend time on security work :/
17:52:56 <ccneill> need someone(s) to take it on basically full time
17:53:04 <tmcpeak> I've always felt OSSP is a great way to make an entry into the industry for college students
17:53:08 <hyakuhei> elmiko: yup
17:53:12 <elmiko> tmcpeak: agreed
17:53:16 <ccneill> elmiko: +1
17:53:21 <hyakuhei> tmcpeak: I agree in principle but I’ve struggled to get buyin
17:53:22 <tmcpeak> maybe we could focus there a bit
17:53:30 <hyakuhei> OpenStack is actually big and scary …
17:53:31 <elmiko> it's really staggering, the amount of sec. work that /could/ be done
17:53:33 <tmcpeak> hyakuhei: yeah, I've gotten shut down at the professor level
17:53:40 <tmcpeak> I think they think I'm pitching something
17:53:41 <ccneill> tmcpeak: I think it's hard to scope it to something they'd understand
17:53:43 <michaelxin> we can try
17:53:52 <mvaldes> michaelxin:  could be an opportunity with OSIC + UTSA
17:54:00 <ccneill> OSSP is too open-ended. "secure every component of a cloud provider" isn't something most college kids would even know where to start on, I think
17:54:03 <tmcpeak> could always start simple though, write a note, fix some docs, etc
17:54:10 <michaelxin> I will check with them for sure.
17:54:25 <ccneill> "too open-ended" meaning, I think we need a kind of "onboarding" process
17:54:41 <elmiko> ccneill: yea, i think we might be able to do more to create highly focused bugs that newer developers could work on. but, again, time....
17:54:42 <tmcpeak> ccneill: yeah that would be helpful too
17:54:44 <Akanksha08> I think probably this time an idea can be put up for Outreachy on OSSP
17:54:55 <michaelxin> http://osic.org/
17:55:15 <michaelxin> If they want to start, they can get some free clusters from this program
17:55:26 <elmiko> Akanksha08: good idea, we could certainly make more effort to get interns in on the OSSP
17:55:36 <singleth_> ccneill: could there be an executability requirement?  You must submit your bug as a program that exploits _insert_canonical_environment_here_
17:55:44 <tmcpeak> yeah OpenStack interns - that would be an awesome thing to have
17:56:14 <elmiko> going through Outreachy and GSOC are great ways to find some interested parties. we need to come up with projects that can be worked on though.
17:56:31 <elmiko> sadly, we just missed the last GSOC round and OpenStack wasn't included
17:56:41 <ccneill> singlethink: I was thinking of starting simpler, like doing a first pass of triage on mailinglist bugs
17:56:42 <Akanksha08> yes the project can even be fixing few small bugs
17:57:01 <elmiko> yup
17:57:12 <Akanksha08> so that the intern with get an idea of codebase and then I am sure the intern will continue contributing to OSSP
17:57:14 <elmiko> the hard part, is finding the time to have OSSP members groom and create the bugs
17:57:16 <Akanksha08> will*
17:57:25 <hyakuhei> Yeah that’s always been hard
17:57:29 <tmcpeak> elmiko: +1
17:57:34 <michaelxin> hyakuhei: Is it possible to associate syntriobs with OSSP at http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml
17:57:36 <tmcpeak> writing notes is nice and focused
17:57:50 <hyakuhei> michaelxin:  sure
17:57:52 <tmcpeak> oh yeah, I skipped Syntribos :(
17:57:58 <elmiko> doh!
17:58:07 <tmcpeak> #topic AOB
17:58:09 <tmcpeak> 2 mins!
17:58:24 <michaelxin> hyakuhei: Great! Thanks.
17:58:31 <hyakuhei> No problem
17:58:49 <ccneill> off topic: I made a Chrome Extension to help myself deal with the giant mess that is my tab bar
17:58:51 <ccneill> https://github.com/cneill/tagatab
17:59:03 <ccneill> if anyone else is a serial tab-hoarder
17:59:06 <michaelxin> hyakuhei: Please drop me a note once it is done. Thanks.
17:59:14 <tmcpeak> oh this looks cool
17:59:33 <michaelxin> We are adding features and start testing Solum using it.
17:59:45 <SergeyLukjanov> hey folks, sorry, it's time to wrap up
17:59:59 <hyakuhei> michaelxin: you could write the change and ask me to +2 it :P
18:00:05 <hyakuhei> #endmeeting