[election][Requirements] PTL candidacy
I would like to announce my candidacy for PTL of the Requirements project. The project was recently updated to allow multiple PTLs this cycle and I imagine tony will be my better half. 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. 3. Fix some automation of generate contstraints (pkg-resources being added and setuptools being dropped) 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. 5. introduce better python version range support into constraints. An image with all the python versions we want is likely needed. I look forward to continue working with you in this cycle, as your PTL or not. Thanks for your time, -- Matthew Thode
On 2022-09-05 16:21:43 -0500 (-0500), Matthew Thode wrote: [...]
The project was recently updated to allow multiple PTLs this cycle and I imagine tony will be my better half. [...]
Just to be clear, the Requirements project team is now under a distributed project leadership, so there are technically no elected PTLs for it. Instead, the project is led by role-specific liaisons chosen through team consensus, as listed here: https://governance.openstack.org/tc/reference/projects/requirements.html But also, thanks for taking care of requirements! -- Jeremy Stanley
On 22-09-05 21:33:55, Jeremy Stanley wrote:
On 2022-09-05 16:21:43 -0500 (-0500), Matthew Thode wrote: [...]
The project was recently updated to allow multiple PTLs this cycle and I imagine tony will be my better half. [...]
Just to be clear, the Requirements project team is now under a distributed project leadership, so there are technically no elected PTLs for it. Instead, the project is led by role-specific liaisons chosen through team consensus, as listed here:
https://governance.openstack.org/tc/reference/projects/requirements.html
But also, thanks for taking care of requirements! -- Jeremy Stanley
yep :D I'm only sending this because of the email earlier saying that ptls would be appointed. we are probably on that list because we changed the leadership to distributed very recently. (after nominations started I think). -- Matthew Thode
Yeah we need to update the election code to handle teams that are under distributed leadership. Something for the next cycle. On Tue, 6 Sept 2022 at 08:48, Matthew Thode <mthode@mthode.org> wrote:
On 22-09-05 21:33:55, Jeremy Stanley wrote:
On 2022-09-05 16:21:43 -0500 (-0500), Matthew Thode wrote: [...]
The project was recently updated to allow multiple PTLs this cycle and I imagine tony will be my better half. [...]
Just to be clear, the Requirements project team is now under a distributed project leadership, so there are technically no elected PTLs for it. Instead, the project is led by role-specific liaisons chosen through team consensus, as listed here:
https://governance.openstack.org/tc/reference/projects/requirements.html
But also, thanks for taking care of requirements! -- Jeremy Stanley
yep :D
I'm only sending this because of the email earlier saying that ptls would be appointed. we are probably on that list because we changed the leadership to distributed very recently. (after nominations started I think).
-- Matthew Thode
-- Yours Tony.
On 2022-09-06 11:26:10 +1000 (+1000), Tony Breeds wrote:
Yeah we need to update the election code to handle teams that are under distributed leadership.
Something for the next cycle. [...]
https://review.opendev.org/855981 looks like an attempt at a workaround. -- Jeremy Stanley
Yup It's a solution for this election. Nice work On Tue, 6 Sept 2022 at 22:17, Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2022-09-06 11:26:10 +1000 (+1000), Tony Breeds wrote:
Yeah we need to update the election code to handle teams that are under distributed leadership.
Something for the next cycle. [...]
https://review.opendev.org/855981 looks like an attempt at a workaround. -- Jeremy Stanley
-- Yours Tony.
participants (3)
-
Jeremy Stanley
-
Matthew Thode
-
Tony Breeds