[watcher][tc] watcher-drivers launchpad membership
Hi folks o/ Following up form the PTG discussion https://etherpad.opendev.org/p/r.79644f8f3cd04686c4f45c10aa35d8ac#L65 and the recently merged governance patch https://github.com/openstack/governance/commit/1e547ae39f9913dc9cfd9c755b24e... I wanted to raise the topic of the watcher-drivers team https://launchpad.net/~watcher-drivers membership and ownership. during the TC sessions we discussed that that the <project>-coresec teams should be owned by the https://launchpad.net/~openstack-admins team https://etherpad.opendev.org/p/r.0f25532f564fb786a89cfe1de39b004b#L123 watcher does not currently have a sperate watcher-coresec team in launchpadd only a a watcher-drivers team i also think that the watcher driver team should be owned by the https://launchpad.net/~openstack-adminsteam. https://launchpad.net/~watcher-drivers is currently owned by https://launchpad.net/~david-tardivel and the only other member with admin rights is https://launchpad.net/~li-canwei2 Can i ask that one of the existing admin either grant my membership request and delegate admin rights to me or add the https://launchpad.net/~openstack-admins team as admins and make them the owner of the team? licanwei, david-tardivel, would either of ye be willing and able to make those changes in launchpad? i also think it would be prudent to add other active member (the current liaisons) as admins/moderators of the watcher-driver team but i can do that once i have access or https://launchpad.net/~openstack-adminscan. having all launchpad teams owned by https://launchpad.net/~openstack-adminsteam mitigates the risk of loosing access by the current admins becoming inactive, but it would be nice to not need to escalation to them for simple tasks like moderation of the group. that is why i want to add the other liaisons to the admins of the team. I am asking for this access for 2 reasons: Fist to add https://launchpad.net/~openstack-adminsas admins of the team and the launchpad project, Second so that i can create new launchpad series for current releases to do blueprint and bug tracking. at present because we do not have launchpad series fro 2025.1 we cannot properly track bugs/blueprints for the current cycle. In the future if there are no objections form the existing contributors i would also like to create a separate open bug team with less project wide permission so that anyone can contribute to bug triage without needing access to the drivers team. this is in lien with how other project like nova work for example https://launchpad.net/~nova-bugs i also think we should be creating a separate watcher-coresec team to allow dan as the security liaison and the vulnerability management team to properly manage security reports. once we have access to the watcher-drivers team we should be able to update the launchpad project to make that possible. Regards sean.
---- On Mon, 04 Nov 2024 10:01:05 -0800 Sean Mooney wrote ---
Hi folks o/
Following up form the PTG discussion https://etherpad.opendev.org/p/r.79644f8f3cd04686c4f45c10aa35d8ac#L65 and the recently merged governance patch https://github.com/openstack/governance/commit/1e547ae39f9913dc9cfd9c755b24e...
I wanted to raise the topic of the watcher-drivers team https://launchpad.net/~watcher-drivers membership and ownership.
during the TC sessions we discussed that that the -coresec teams should be owned by the https://launchpad.net/~openstack-admins
team https://etherpad.opendev.org/p/r.0f25532f564fb786a89cfe1de39b004b#L123
watcher does not currently have a sperate watcher-coresec team in launchpadd only a a watcher-drivers team
i also think that the watcher driver team should be owned by the https://launchpad.net/~openstack-adminsteam.
https://launchpad.net/~watcher-drivers is currently owned by https://launchpad.net/~david-tardivel
and the only other member with admin rights is https://launchpad.net/~li-canwei2
Can i ask that one of the existing admin either grant my membership request and delegate admin rights to me or add the https://launchpad.net/~openstack-admins team as admins and make them the owner of the team?
licanwei, david-tardivel, would either of ye be willing and able to make those changes in launchpad?
i also think it would be prudent to add other active member (the current liaisons) as admins/moderators of the watcher-driver team but i can do that once i have access or https://launchpad.net/~openstack-adminscan. having all launchpad teams owned by https://launchpad.net/~openstack-adminsteam mitigates the risk of loosing access by the current admins becoming inactive, but it would be nice to not need to escalation to them for simple tasks like moderation of the group. that is why i want to add the other liaisons to the admins of the team.
+1, Like any other project LP driver team, 'OpenStack Administrators' can be the owner and watcher core member can be added as admin. -gmann
I am asking for this access for 2 reasons:
Fist to add https://launchpad.net/~openstack-adminsas admins of the team and the launchpad project, Second so that i can create new launchpad series for current releases to do blueprint and bug tracking.
at present because we do not have launchpad series fro 2025.1 we cannot properly track bugs/blueprints for the current cycle.
In the future if there are no objections form the existing contributors i would also like to create a separate open bug team with less project wide permission so that anyone can contribute to bug triage without needing access to the drivers team. this is in lien with how other project like nova work for example https://launchpad.net/~nova-bugs
i also think we should be creating a separate watcher-coresec team to allow dan as the security liaison and the vulnerability management team to properly manage security reports. once we have access to the watcher-drivers team we should be able to update the launchpad project to make that possible.
Regards
sean.
---- On Mon, 04 Nov 2024 10:25:42 -0800 Ghanshyam Mann wrote ---
---- On Mon, 04 Nov 2024 10:01:05 -0800 Sean Mooney wrote ---
Hi folks o/
Following up form the PTG discussion https://etherpad.opendev.org/p/r.79644f8f3cd04686c4f45c10aa35d8ac#L65 and the recently merged governance patch https://github.com/openstack/governance/commit/1e547ae39f9913dc9cfd9c755b24e...
I wanted to raise the topic of the watcher-drivers team https://launchpad.net/~watcher-drivers membership and ownership.
during the TC sessions we discussed that that the -coresec teams should be owned by the https://launchpad.net/~openstack-admins
team https://etherpad.opendev.org/p/r.0f25532f564fb786a89cfe1de39b004b#L123
watcher does not currently have a sperate watcher-coresec team in launchpadd only a a watcher-drivers team
i also think that the watcher driver team should be owned by the https://launchpad.net/~openstack-adminsteam.
https://launchpad.net/~watcher-drivers is currently owned by https://launchpad.net/~david-tardivel
and the only other member with admin rights is https://launchpad.net/~li-canwei2
Can i ask that one of the existing admin either grant my membership request and delegate admin rights to me or add the https://launchpad.net/~openstack-admins team as admins and make them the owner of the team?
licanwei, david-tardivel, would either of ye be willing and able to make those changes in launchpad?
i also think it would be prudent to add other active member (the current liaisons) as admins/moderators of the watcher-driver team but i can do that once i have access or https://launchpad.net/~openstack-adminscan. having all launchpad teams owned by https://launchpad.net/~openstack-adminsteam mitigates the risk of loosing access by the current admins becoming inactive, but it would be nice to not need to escalation to them for simple tasks like moderation of the group. that is why i want to add the other liaisons to the admins of the team.
+1, Like any other project LP driver team, 'OpenStack Administrators' can be the owner and watcher core member can be added as admin.
'OpenStack Administrators' is now an admin in watcher-driver[1]. I did some cleanup to remove inactive members there and also made chenker (previous PTL and current an active member of the core team) as admin. Once the other new members are finalized for this group, let either of the 'OpenStack Administrators'[2] know or chenker can also add them now. [1] https://launchpad.net/~watcher-drivers/+members [2] https://launchpad.net/~openstack-admins/+members#active -gmann
-gmann
I am asking for this access for 2 reasons:
Fist to add https://launchpad.net/~openstack-adminsas admins of the team and the launchpad project, Second so that i can create new launchpad series for current releases to do blueprint and bug tracking.
at present because we do not have launchpad series fro 2025.1 we cannot properly track bugs/blueprints for the current cycle.
In the future if there are no objections form the existing contributors i would also like to create a separate open bug team with less project wide permission so that anyone can contribute to bug triage without needing access to the drivers team. this is in lien with how other project like nova work for example https://launchpad.net/~nova-bugs
i also think we should be creating a separate watcher-coresec team to allow dan as the security liaison and the vulnerability management team to properly manage security reports. once we have access to the watcher-drivers team we should be able to update the launchpad project to make that possible.
Regards
sean.
On 2024-11-20 10:43:22 -0800 (-0800), Ghanshyam Mann wrote: [...]
'OpenStack Administrators' is now an admin in watcher-driver[1]. [...]
Thanks! The openstack-administrators team only needed to own watcher-drivers, which it now does, so I have removed it as a member of the watcher-drivers team (if o-a were a member of every team it owns, the flood of notifications for everything to which those teams are subscribed would be overwhelming). -- Jeremy Stanley
hi everyone. the watcher projects launchpad groups changes are now complete. OpenStack-admin is now the owner of each of the watcher teams I have created 2 additional teams for bug triage and we create a new watcher-tempest-plugin project to allow issues and bugs to be filed against that separately. I have created the launchpad series on all projects with branches for 2025.1 and each of the stable branches the older series have been marked as obsolete. as such all of the changes discussed in the ptg and on the list should not be in effect. thanks for the help with completing this. regards sean On Wed, Nov 20, 2024 at 7:33 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2024-11-20 10:43:22 -0800 (-0800), Ghanshyam Mann wrote: [...]
'OpenStack Administrators' is now an admin in watcher-driver[1]. [...]
Thanks! The openstack-administrators team only needed to own watcher-drivers, which it now does, so I have removed it as a member of the watcher-drivers team (if o-a were a member of every team it owns, the flood of notifications for everything to which those teams are subscribed would be overwhelming). -- Jeremy Stanley
participants (3)
-
Ghanshyam Mann
-
Jeremy Stanley
-
Sean Mooney