This message was deleted.
# office-hourss
Slackbot
05/25/2023, 6:11 PMThis message was deleted.
b
binford2k
05/25/2023, 6:20 PMthis is bleeding over from the other thread lol
binford2k
05/25/2023, 6:20 PMI would like to do this. It depends on designing some kind of RBAC to grant those permissions
b
bastelfreak
05/25/2023, 6:21 PMI'm fine with admin perms
🤣 1
lol 1
bastelfreak
05/25/2023, 6:21 PMI take whatever you got! 😄
bastelfreak
05/25/2023, 6:22 PMyeah would be nice if there's some sort of RBAC and vox pupuli PMC could approve modules that got migrated to the vox pupuli namespace, but not others (and deprecate modules that got moved to Vox)
b
binford2k
05/25/2023, 6:24 PMpersonally, I'd also love to have something like a "migration request"
binford2k
05/25/2023, 6:24 PMthat would send the request via email to the original owner and give them a click to approve migration workflow
b
bastelfreak
05/25/2023, 6:26 PMoh yeah
l
Lumiere
05/25/2023, 6:27 PMthat'd be great for the voluntary ones, it's the ones where the owner has dropped off the face of the planet
b
binford2k
05/25/2023, 6:49 PMimho, that would trigger the "informational" notice that you proposed on the other thread. So users would already see a better maintained alternative.
binford2k
05/25/2023, 6:50 PMthe question then remains of how to manage "forcible" migrations and whether those should even exist.
b
bastelfreak
05/25/2023, 6:52 PMwe had a few situations where Vox Pupuli had to fork a repo. We try to avoid it, but sometimes the owner is just missing and there's a high demand for the module