Nominate myself as ptl of requirements project for wallaby cycle
Change-Id: I21612dc0b03056630ac9502e9559c368a63d6ed0
This commit is contained in:
parent
5413dbd3b2
commit
935820362d
23
candidates/wallaby/Requirements/mthode@mthode.org
Normal file
23
candidates/wallaby/Requirements/mthode@mthode.org
Normal file
@ -0,0 +1,23 @@
|
||||
I would like to announce my candidacy for PTL of the Requirements project for
|
||||
the Wallaby 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 botocore).
|
||||
|
||||
3. 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. Json libs are on the short list
|
||||
this go around.
|
||||
|
||||
I look forward to continue working with you in this cycle, as your PTL or not.
|
||||
|
||||
Thanks for your time,
|
||||
Matthew Thode
|
||||
|
||||
IRC: prometheanfire
|
Loading…
Reference in New Issue
Block a user