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