From 200f48d6a7145cf29cc598a13ac22d0b513eb53b Mon Sep 17 00:00:00 2001 From: Matthew Thode Date: Sat, 9 Mar 2019 09:18:20 -0600 Subject: [PATCH] Add Matthew Thode as candidate for Train requirements PTL Change-Id: Ie763c076082c89e8aea4a6a7084408ea718536e8 --- .../train/Requirements/mthode@mthode.org | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 candidates/train/Requirements/mthode@mthode.org diff --git a/candidates/train/Requirements/mthode@mthode.org b/candidates/train/Requirements/mthode@mthode.org new file mode 100644 index 00000000..01a43bc0 --- /dev/null +++ b/candidates/train/Requirements/mthode@mthode.org @@ -0,0 +1,28 @@ +I would like to announce my candidacy for PTL of the Requirements project for +the Train cycle. + +The following will be my goals for the cycle, in order of importance: + +1. The primary goal is to keep a tight rein on global-requirements and +upper-constraints updates. (Keep things working well) + +2. Un-cap requirements where possible (stuff like cmd2 and grpcio). + +3. Publish constraints and requirements to streamline the freeze process. + This is in progress, but did not make it for Stein. + +https://storyboard.openstack.org/#!/story/1719006 is the story tracking the +publish job. + +4. Audit global-requirements and upper-constraints for redundancies. One of +the rules we have for new entrants to global-requirements and/or +upper-constraints is that they be non-redundant. Keeping that rule in mind, +audit the list of requirements for possible redundancies and if possible, +reduce the number of requirements we manage. + +I look forward to continue working with you in this cycle, as your PTL or not. + +Thanks for your time, +Matthew Thode + +IRC: prometheanfire