07:01:16 <prometheanfire> #startmeeting requirements
07:01:17 <openstack> Meeting started Wed Feb 21 07:01:16 2018 UTC and is due to finish in 60 minutes.  The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:01:18 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
07:01:21 <openstack> The meeting name has been set to 'requirements'
07:01:46 <prometheanfire> #subject rollcall
07:01:52 <prometheanfire> #topic rollcall
07:01:57 <prometheanfire> tonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis ping
07:02:09 <tonyb> o/
07:02:14 <toabctl> hi
07:02:28 * prometheanfire got the gentoo foundation to use the meetbot but we use # and they use .
07:02:48 <prometheanfire> also, hi :D
07:02:49 <dirk> o/
07:02:56 <tonyb> prometheanfire: It wouldn't be hard to patch meetbot to accept either ;P
07:03:48 <prometheanfire> :D
07:03:53 <prometheanfire> that seems like most of us
07:04:01 <prometheanfire> #topic Any controversies in the Queue?
07:05:16 <prometheanfire> guess that's a no
07:05:23 <prometheanfire> #topic PTG
07:05:27 <prometheanfire> what day?
07:05:38 <prometheanfire> dhellmann requested !tuesday
07:05:43 <prometheanfire> and dirk requested !monday
07:05:51 <prometheanfire> so w/t/f?
07:06:02 <tonyb> LOL, I was about to request !(wed-fri)
07:06:24 <prometheanfire> ya, classicly those are for the projects :|
07:06:52 <tonyb> anyway I can do Thursday afternoon
07:07:12 <prometheanfire> sgtm
07:07:22 <prometheanfire> we can narrow down the hour the week of
07:07:32 <tonyb> prometheanfire: so it depends on hwo long you think we'll need and who we'll need there
07:07:34 <prometheanfire> anyone else have suggestions?
07:08:07 <tonyb> prometheanfire: Let's just take from end of lunch (13:00?) until 17:30
07:08:26 <prometheanfire> I think that'd be well more than enough
07:08:35 <tonyb> cool
07:08:42 <prometheanfire> I was thinking 2ish hours (maybe 3)
07:08:52 <prometheanfire> given https://etherpad.openstack.org/p/rocky-PTG-requirements
07:08:58 <prometheanfire> #link https://etherpad.openstack.org/p/rocky-PTG-requirements
07:09:24 <tonyb> cool
07:09:36 <prometheanfire> anyone else have anything ptg related?
07:09:42 <tonyb> We can hack out the constraints publishing on Monday and Tuesday
07:09:51 <tonyb> while we can borrow someone from infra
07:10:06 <prometheanfire> yarp
07:10:09 <dirk> tonyb: well, actually only monday morning. I should be there by 3pm or so
07:10:13 <dirk> eh, prometheanfire
07:10:18 * dirk goes back into his corner
07:10:36 <tonyb> dirk: Okay
07:11:33 <prometheanfire> dirk: ya, didn't mention that because later in the week allows us to 'mingle' and be better informed for our discussion
07:11:40 <prometheanfire> discussion(s) :p
07:12:05 <prometheanfire> anyway, moving on :D
07:13:21 <prometheanfire> #topic open discussion
07:13:37 <prometheanfire> next week we'll skip the meeting (making it official)
07:14:20 <tonyb> I created a (google)calendar entry for the session we just discussed, send me your google compatible addresses and I'll add you
07:14:34 * tonyb can't keep things straight without an exo-brain
07:14:42 <prometheanfire> can't send ical?
07:14:54 <tonyb> prometheanfire: Same thing
07:14:56 <prometheanfire> understandable :P
07:15:39 <prometheanfire> sent
07:15:51 <prometheanfire> will close in a couple min if no one has anything
07:16:52 <tonyb> I'm good
07:18:04 <dirk> tonyb: what kind of calendar is that? something official?
07:18:28 <prometheanfire> super serial
07:18:37 <tonyb> dirk, nope it's just a (personal) google calendar invite
07:18:43 <prometheanfire> and super secrete. don't tell anyone
07:18:54 <prometheanfire> this isn't logged so we good
07:19:09 <tonyb> if we had more to discuss I'd suggest we do soemthign like triplo and cerate a public ics file but we're not that big
07:19:45 <prometheanfire> not sure you can answer, but you working more on tripleo now tonyb ?
07:20:17 <tonyb> Yup, that's where 75% of my development went this year
07:20:30 <tonyb> https://review.openstack.org/#/q/topic:bp/multiarch-support
07:20:33 <prometheanfire> cool, seemd like it
07:20:36 <dirk> one more q, when do we unfreeze constraints for master?
07:20:58 <prometheanfire> when cycle trailing have queens branches
07:21:05 <prometheanfire> tripleo and puppet
07:21:09 <tonyb> dirk: after the PTG?
07:21:18 <prometheanfire> looks like we can yell at tony for one :P
07:21:18 <tonyb> prometheanfire: tripleo has queens branches
07:21:33 <prometheanfire> oh, nice, checked yesterday
07:22:12 <dirk> ok, thanks
07:22:16 <tonyb> So perhaps we validate they have mereged all the "use the queens constraints url" chnages and then unthaw?
07:22:40 <prometheanfire> tonyb: ya
07:22:58 <prometheanfire> though, imo, having a queens branch is enough
07:23:04 <prometheanfire> the constraints url is 'their' work
07:24:17 <tonyb> prometheanfire: Hmm maybe, I'd rather wait a little longer but it doesn't make a huge difference
07:24:25 <prometheanfire> ya
07:24:37 <prometheanfire> end of ptg, after official release makes sense to me
07:24:46 <tonyb> we can still muck up thier gate/CI from master ;P
07:25:03 <prometheanfire> tonyb: sounds like their problem if they have a queens branch
07:25:13 <prometheanfire> but maybe I'm just a bit agressive
07:25:17 <tonyb> That gives us time to identify projects that are lagging and encourage them to catch up :)
07:25:21 <prometheanfire> anything else this meeting?
07:25:52 <tonyb> not from me
07:27:29 <prometheanfire> #endmeeting