16:03:48 <ttx> #startmeeting incub_sync
16:03:49 <openstack> Meeting started Thu Jan 15 16:03:48 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:50 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:03:52 <openstack> The meeting name has been set to 'incub_sync'
16:03:53 <ttx> #topics Barbican
16:03:55 <ttx> #topic Barbican
16:04:17 <ttx> #link https://launchpad.net/barbican/+milestone/kilo-2
16:04:35 <ttx> redrobot: is that all you expect to add in k2, or just a partial view ?
16:05:05 <redrobot> just a partial view... I need to go through the bug list and assign a handful of recent bug fixes.
16:05:32 <ttx> redrobot: ok, if you have other stuff being worked/on added for k2 try to reference them here
16:06:10 <redrobot> ttx will do... there's a few things that are in flight, but I don't think they'll land until k3
16:06:12 <ttx> redrobot: is the Certificate API a whole new set of Ai primitives ? Or a new version of stuff already there ?
16:06:21 <ttx> s/Ai/API
16:07:10 <redrobot> ttx we're defining the certificate ordering api, we should hopefully end up with something that is flexible enough for different CAs
16:07:16 <ttx> OK, that's all I have at this point in the cycle. Did you have questions ?
16:07:55 <redrobot> not at this time. thanks
16:07:57 <ttx> redrobot: note that we'll skip 1:1s next week, I'll be on a plane.
16:08:03 <redrobot> noted
16:08:13 <ttx> So next one on the 29th, one week before k2 drop
16:08:29 <ttx> bswartz: around?
16:08:33 <redrobot> ok, I should have the k2 launchpad milestone up to date by then
16:08:44 <ttx> yep
16:08:55 <ttx> redrobot: thx and have a good week
16:09:01 <redrobot> ttx you too!
16:09:09 <bswartz> ttx:  yes
16:09:11 <ttx> #topic Manila
16:09:18 <ttx> #link https://launchpad.net/manila/+milestone/kilo-2
16:09:27 <ttx> That is a rather busy milestone
16:09:36 <bswartz> err
16:09:38 <bswartz> yes
16:10:02 <bswartz> we've sort of targeted everything to k-2, with the understanding that some will slip
16:10:09 <bswartz> is that a bad practice?
16:10:17 <ttx> There are two "unknown" states and 4 'Undefined' priorities which you might want to clarify
16:10:33 <bswartz> yes
16:10:40 <ttx> bswartz: it's not really bad practice, as long as there is a chance that it will make it
16:10:55 <ttx> When you're reasonably sure it will skip, you should target it to k3
16:11:10 <bswartz> it's getting close to the deadline so I need to review these at least and go ask questions
16:11:11 <ttx> the goal being, to inform downstream stakeholders of when what is coming
16:11:24 <bswartz> we're still doing a lot of design work for some of these so they're pretty iffy
16:11:26 <ttx> Good progress on that list though
16:11:49 <bswartz> by next week I can probably have this mostly cleaned up
16:11:52 <ttx> So yeah, by the next time we need in two weeks, we'll probably trim that list down
16:12:02 <ttx> s/need/meet/
16:12:09 <bswartz> I can put an agenda item on the weekly to review this
16:12:15 <bswartz> but mostly I'll just grab people 1on1
16:12:40 <ttx> (we'll skip next week 1:1s as I'll be on a plane -- ping me if you have urgent questions)
16:13:16 <ttx> That's all the questions I had
16:13:16 <bswartz> hmm okay
16:13:20 <ttx> Anything on your side ?
16:13:22 <bswartz> so jan 29 for next meeting?
16:13:27 <ttx> bswartz: yes
16:13:32 <bswartz> that's just 1 week before the milestone
16:13:37 <ttx> yes
16:13:45 <bswartz> I guess that will work out okay though
16:13:49 <ttx> good time to push things out
16:14:03 <bswartz> some of this definitely needs to get pushed out
16:14:07 <bswartz> thanks for the reminder
16:14:16 <ttx> bswartz: any other question ?
16:14:17 <bswartz> I don't have any questions on my side
16:14:26 <ttx> bswartz: alright then, have a great week!
16:14:32 <bswartz> you know the bot is having problems right?
16:14:36 <bswartz> it can't set topics in IRC
16:14:44 <ttx> Ah? no I didn't know
16:14:55 <bswartz> meetings are recorded, but topic never changes
16:15:04 <bswartz> thanks, see you in 2 weeks
16:15:07 <ttx> Oh right, missing channel rights
16:15:50 <bswartz> same problem exists in meeting channels
16:15:51 <ttx> maybe that will help
16:16:02 <ttx> flaper87: around?
16:16:05 <bswartz> or the -alt meeting channel in any case
16:23:26 <ttx> flaper87: not around?
16:23:26 <Kiall> ttx: In the office when your ready.
16:23:37 <ttx> Kiall: you can do now
16:23:40 <ttx> #topci Designate
16:23:42 <Kiall> Sounds good..
16:23:44 <ttx> #topic Designate
16:23:58 <ttx> #link https://launchpad.net/designate/+milestone/kilo-2
16:24:30 <Kiall> So - You're going to ask about the # of open/inprogress bugs ;) We have a unit test sprint tomorrow, and a mid-cycle hackathon next week to knock all these out :)
16:24:31 <ttx> 2 blueprints up -- does that represent most of what's coming in k2 or do you have more being worked on ?
16:24:49 <Kiall> k2 has been 99% cleanup after k1 merges, so very few new features
16:24:50 <ttx> no, the bugs looks fine to me :P
16:24:58 <Kiall> lol..
16:25:23 <ttx> ok, that works! As long as it represents what's being done, I'm fine :)
16:25:37 <ttx> No sync next week, I'll be in the air
16:25:46 <Kiall> Anyway - There is another BP to file, but the code has been put up so it'll be marked implemented near immediatly ;)
16:25:50 <ttx> ping me if you have urgent stuff between now and jan 29
16:25:59 <ttx> Did you have questions ?
16:26:28 <Kiall> No - I tend to eyeball the logs and get most of my answers that way ;)
16:26:45 <ttx> alright then... have a great week!
16:26:53 <Kiall> Ohh.. 1 thing
16:26:59 * ttx pauses
16:27:10 <Kiall> mid-cycle next week, I likely can't attend our 1:1.
16:27:22 <ttx> Good thing theer isn't a 1:1 next week then
16:27:24 <Kiall> (ping me on the day, I might.. Just not 100% sure yet)
16:27:27 <Kiall> Oh.. heh
16:27:38 <ttx> <ttx> No sync next week, I'll be in the air
16:27:50 <Kiall> I missed that - Thanks :)
16:28:03 <ttx> Kiall: anything else ?
16:28:05 <Kiall> Okay - I'm good then :)
16:28:14 <ttx> ok, talk to you later!
16:28:20 <ttx> flaper87: around now ?
16:30:34 <ttx> I guess that's a "no"
16:30:37 <ttx> #endmeeting