[openstack-dev] [ptl][requirements] nomination period started
tony at bakeyournoodle.com
Wed Jul 27 16:13:03 UTC 2016
On Wed, Jul 27, 2016 at 08:41:17AM -0500, Matthew Thode wrote:
> We've started a period of self nomination in preparation for the
> requirements project fully moving into project (as it's still under Doug
> We are gathering the self nominations here before we vote next week.
> Nominees should also send an email to the openstack-dev list.
I'd like to nominate for PTL of the, to be formed, requirements project.
For as long as I've been working on OpenStack the requirements data, code and
process has been managed as a sort of sub-team of release management with
strong overlaps to the stable branch team(s). The workload has grown to the
point it needs it's own team with a PTL to manage priorities and reduce the
cross project pain points.
I feel like I understand the role of the requirements team and have advocated
that the requirements team should be more active in cross project issues.
The requirements team, like probably every other team, has a lot of debt.
We've worked hard to reduce that since Austin and I see that in the near future
we'll be able to tackle some of the bigger problems.
In rough priority order:
- Improving communication, often decisions are made in the requirements team
that affect many projects, I have a commitment to bringing more experts in
for strategic reviews/discussions
- cross-project testing for upper-constraints changes. Once this is done
it'll make breakage, like the recent oslo.context one, much harder to hit.
- Work closely with the release managers as there is still a lot of common
issues there. In that a release of $project will trigger processes in the
- Getting openstack_requirements *code* to the point it can be installed as a
library. We've seen issues in the past where stable branches need largish
backports to work correctly. Really the *code* and *data* should be treated
I suspect that if you look at the review statistics for the requirements repo
I'm much lower than many of the core team.
I believe I'm eligible for nomination due to any of the following reviews.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 473 bytes
Desc: not available
More information about the OpenStack-dev