---- 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.