11:59:59 #startmeeting requirements 12:00:00 Meeting started Wed Jun 1 11:59:59 2016 UTC and is due to finish in 60 minutes. The chair is tonyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:00:03 The meeting name has been set to 'requirements' 12:00:22 Roll call Who's here for the requirements meeting? 12:00:53 Hello 12:00:57 o/ 12:00:57 * coolsvap is 12:01:37 I think dims is sleeping, prometheanfire is on vacation 12:01:55 Hey 12:02:01 dirk: hey. 12:02:29 * dirk is on vacation as well 12:02:45 dirk: Wel thanks for being here then :) 12:03:06 Anything in the review queue that stands out? 12:03:24 coolsvap: has a bunch of cruft cleaning reviews up 12:03:55 yes 12:03:56 There was a ping recently 12:04:27 https://review.openstack.org/315348 12:05:00 I am not sure what this one is waiting for.. 12:05:13 dirk: Yeah .... doug/dims to review it 12:05:29 I'm still trying to find time to go through coolsvap 's reviews 12:05:40 But family is first this week.. 12:05:53 dirk: good plan 12:06:10 dirk, sure take your time :) 12:06:14 I'm also looking at coolsvap's reviews when I get free cycles 12:06:35 i just got some free and uploaded the reviews 12:06:49 * tonyb wonders if 315348 is blocking anything? 12:07:18 coolsvap: Thanks. That kind of curation takes time and energy 12:08:33 tonyb I guess it does - there is no reason given though 12:08:54 tonyb, can you add action-item to dims/dhellman to review patch 315348 12:09:12 For me it makes sense to cherry pick it although it probably is outside stable policy 12:09:31 #action dims, dhellmann to review https://review.openstack.org/#/c/315348/ 12:10:06 Yeah but requirements doesn't have the stable:follow-policy tag so we can be flexible 12:10:26 also for requirements we *really* want a single code base regardless of the branch 12:10:33 it's the data that matters 12:11:08 +1 12:11:49 yeah 12:11:59 * tonyb was thinking abotu how to spilt the code from the data earlier today 12:12:20 can't say I got very far but it's there as a thing to do ... 12:13:02 Anything else for general reviews? 12:13:12 Not from me 12:13:21 no 12:13:33 okay .... 12:13:43 #link https://etherpad.openstack.org/p/requirements-tasks 12:14:00 any of the 16 or so todo items to talk about? 12:14:48 coolsvap: You're the only one game enough to put your name next to an item 12:14:56 coolsvap: how's that going? 12:15:27 tonyb, remove-cruft is in good progress 12:16:04 i think by next meeting i will have upto 100% done 12:16:12 coolsvap: great! 12:16:28 i have updated the https://etherpad.openstack.org/p/requirements-cruft for details of the packages 12:16:55 which are removed 12:17:12 coolsvap: thanks. 12:17:59 i am still new to requirements, reviews are most appreciated 12:19:11 coolsvap: +1 12:19:15 coolsvap, I took a pass on several from an ubuntu perspective, hopefully that is useful 12:20:10 coreycb, yeah 12:21:50 anything else for the uber todo list? 12:22:09 nothing more from my side 12:23:22 open discussion? 12:24:23 * tonyb started writing a script to "correct" the pip package names. 12:24:46 tonyb, that is very useful 12:24:56 It's a little tricky as the Requirements class rewrites the specificatons which makes the diff bigger 12:25:16 also I'm not 100% certain we want to do it but it's a fun little script 12:26:10 tonyb, yeah i think it should be useful considering some package conflicts i have seen in current remove-cruft reviews 12:27:21 coolsvap: my worry is that this will break horribly if it merges 12:27:42 Tonyb I actually started that ages ago but ran out of time 12:27:49 tonyb, once you have some thing ready lets put it on review 12:28:02 lets test it locally for a month or so as a dry run 12:28:04 coolsvap: will poxix_ipc suddenly cause the bot to fail? 12:28:05 and improve 12:28:27 Sure 12:29:05 tonyb, i did not get context for the poxix_ipc question earlier 12:29:08 https://review.openstack.org/#/c/207629/ 12:29:19 coolsvap: It was poorly worded 12:29:21 Ah, toabctl actually started that 12:29:33 So, yes, it will cause an issue with the bot 12:29:42 Didn't.het around fixing that yet 12:30:21 dirk, i will take a grab at it some time in this week 12:31:00 Cool, be happy to review it 12:31:07 Ahh yeah that thing. 12:31:23 So far something else was always more urgent to do :-/ 12:31:41 :/ 12:32:38 Anyone else? 12:33:08 nothing else from my side 12:33:25 dirk, coreycb ? 12:33:37 Nothing from me today 12:33:38 tonyb, nothing from me, thanks 12:34:01 okay I'll end the meeting then 12:34:06 Thanks everyone 12:34:20 #endmeeting