20:30:23 #startmeeting requirements 20:30:24 Meeting started Wed May 30 20:30:23 2018 UTC and is due to finish in 60 minutes. The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:30:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:30:27 The meeting name has been set to 'requirements' 20:30:31 #topic rollcall 20:30:37 tonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis, dhellmann ping 20:30:47 o/ 20:30:51 o/ 20:31:35 o/ 20:31:56 Likely not awake enough to be useful though 20:32:01 will wait another meeting just in case 20:32:21 not much to go over other than the cmd2 stuff 20:33:55 #topic Any controversies in the Queue? 20:34:24 I don't have anything (cmd2 isn't a controversy, just annoying) 20:34:31 Lol 20:34:43 Well, you need to remove your -2 20:35:00 yeah, is it clear which of those patches we need? 20:35:04 done 20:35:09 I think the correction of the requirements is something we want, right? 20:35:29 The propose stuff is no longer happening, right? 20:35:48 So we can merge the changes without causing churn 20:36:22 Or are there downsides? 20:36:27 These should be few and far between on stable branches, mainly masking known bad versions or in extreme adding a maximum version allowable for a package. We work to remove these caps as well. Raising effective minimums is only acceptable during Phase I, and only due to security issues. 20:36:38 that's our policy for stable branch GR maint 20:37:15 I think the py3 only situation makes sense here 20:37:15 I thought we got rid of that nasty phases stuff? 20:37:41 Yeah, I think the cap for py2 is good 20:37:57 Not sure about the addition of py3 though 20:38:15 The old version worked for both, right? 20:38:30 py3 should be >=0.6.7 or whatever 20:38:31 ya 20:38:36 not >=0.9.1 20:39:05 Ok, so the current review still needs a refinement 20:39:31 commented 20:39:31 yep 20:39:34 What about the tc resolution? The phases are gone I understand 20:39:42 new news? 20:40:47 if no one has anything else I'll open it up to 'open floor' 20:42:09 #topic open floor 20:42:38 #topic open floor 20:43:02 will close in a 3 min unless someone says something 20:44:30 I think there was some board evaluation on whether the requirements team needs any help? 20:44:42 Have you heard about that prometheanfire ? 20:45:12 no, but I have heard that I was brought up at some point, probably in relations to the reqs team 20:45:16 I talked about it at the joint leadership meeting on sunday and encouraged people to help 20:45:18 we do need more people 20:45:25 the requirements team was one of several teams mentioned 20:45:50 cjloader: do some reviews :D 20:46:09 cjloader: our docs are here https://docs.openstack.org/project-team-guide/dependency-management.html :D 20:46:13 Maksim Malchuk proposed openstack/requirements stable/queens: Freeze cmd2 library on python2 https://review.openstack.org/571259 20:46:40 Well, the alternative is that we fold into some other team 20:46:56 true 20:47:04 I think with the per project requirements it lost most of the work load 20:47:22 Might not actually make sense to continue with this 20:47:38 ya, I'd like to have things settle down again, we need to get working on those caps some more 20:47:49 we still need someone to manage the u-c list and the g-r list for license compatibility 20:47:55 but yeah, I hope that means a lot less work for the team 20:48:47 it's something to think about, could be folded into stable/releases 20:48:54 Yep 20:48:59 anyone have anything else in the mean time? 20:49:19 possibly 20:49:39 dhellmann: go ahead :D 20:49:53 I do... 20:50:10 prometheanfire : oh, that was in response to the comment about folding into other teams, not your question :-) 20:50:11 sorry 20:50:15 cjloader : please go ahead 20:50:16 prometheanfire: how does one get involved? 20:50:39 cjloader: reviews are the best way 20:51:13 not just +1s everywhere, sometimes things need changing, and when they do, constructive feedback is best 20:51:31 to me that second part is what makes a reviewer most valuable 20:51:39 true 20:51:55 * dirk reviews constructively his bed now 20:52:00 Bye 20:52:02 dirk: nn 20:53:07 ok, ending 20:53:14 #endmeeting