05/25/2023, 6:11 PM
and can vox pupuli get permissions to mark other modules as migrated when they're now in our namespace?
05/25/2023, 6:20 PM
this is bleeding over from the other thread :lol:
I would like to do this. It depends on designing some kind of RBAC to grant those permissions
05/25/2023, 6:21 PM
I'm fine with admin perms
I take whatever you got! 😄
yeah 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)
05/25/2023, 6:24 PM
personally, I'd also love to have something like a "migration request"
that would send the request via email to the original owner and give them a click to approve migration workflow
05/25/2023, 6:26 PM
05/25/2023, 6:27 PM
that'd be great for the voluntary ones, it's the ones where the owner has dropped off the face of the planet
05/25/2023, 6:49 PM
imho, that would trigger the "informational" notice that you proposed on the other thread. So users would already see a better maintained alternative.
the question then remains of how to manage "forcible" migrations and whether those should even exist.
05/25/2023, 6:52 PM
we 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