GitLab

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 and community 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 delete packages from a package group: https://docs.gitlab.com/ee/user/permissions.html#project-members-permissions
• Only Owners can move packages between package groups: https://docs.gitlab.com/ee/user/permissions.html#project-members-permissions
• Create repo via push or alternative way must be able to succeed with project visibility public. related to:
  • https://gitlab.com/gitlab-org/gitlab-foss/-/issues/43524
  • https://gitlab.com/gitlab-org/gitlab-foss/-/issues/26388
  • https://gitlab.com/gitlab-org/gitlab-foss/-/issues/63564
  • https://gitlab.com/gitlab-org/gitlab-foss/-/blob/91c12da9033805d54c32f6081103d0d139dd22b7/app/services/projects/create_from_push_service.rb#L32
  • https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/services/projects/create_service.rb