Git packaging migration
There are a few issues on the gitlab side of things which needs to be solved for any git migration to take place. Some of them are [arch-dev-public]
discussion worthy, but I think just having a list of issues which we'd need to decide on is a good idea.
I'll add more to the list as we go along.
-
Access restrictions for packages
andcommunity
groups. -
Pull-requests and issues should be toggle-able by maintainers.(This is either globally on or off, not a per package thing) -
Package deletions should be instant, and not linger for X number of days. (I believe this is the case today) - to be discussed, most likely a none issue: the archiving feature would be a better option otherwise protected branches/tags can be circumvented and history be rewritten (and malicious things hidden) by deleting and recreating a package
-
Only Owners can move packages between package groups: https://docs.gitlab.com/ee/user/permissions.html#project-members-permissions
Edited by Levente Polyak