VLC migration to GitLab
# Background [VideoLAN](https://videolan.org) is a non-profit organization, developing popular multimedia applications, like VLC, x264 or dav1d. VideoLAN is also hosting other multimedia projects. [VideoLAN](https://videolan.org) has partially moved some projects to its own Gitlab instance, like for [VLC/Android](https://code.videolan.org/videolan/vlc-android/) or [VLC/iOS](https://code.videolan.org/videolan/vlc-ios/). [VideoLAN](https://videolan.org) has mandatory self-hosting requirements and cannot use SaaS versions of tools. The VideoLAN GitLab is hosted here: https://code.videolan.org/ # Product - Would be using Community Edition # Goals The main goals for this migration are: - simplify contributions for external users, - single login/application for all coding tasks, from bugs to reviews, to release, - less maintenance, - move to MR model. VideoLAN would like to kill: - trac *(bugtracker)*, - patchwork *(patch tracking)*, - wiki, - gitosis *(git user management)*, - git webview, - jenkins *(CI)*, - our documentation, and move all this to Gitlab. # High Priority / Blockers * **Custom Field**s -- The biggest issue is the lack of Custom Fields in the bug tracker: https://gitlab.com/gitlab-org/gitlab/issues/1906 # Medium Priority * ~~[Allow `not` filtering in issues](https://gitlab.com/gitlab-org/gitlab/issues/18059)~~ * [Allow to set global settings for merge requests mode](https://gitlab.com/gitlab-org/gitlab/issues/26540). * [Multiple Users delete](https://gitlab.com/gitlab-org/gitlab/issues/29666) for **spam** fighting! * ~~Similarly, [Allow changing the default value of the merge request contribution](https://gitlab.com/gitlab-org/gitlab/issues/23308)~~ * [Close a bug as duplicate, and adjust the flags/milestones in the same way](https://gitlab.com/gitlab-org/gitlab/issues/20036), * [Running pipeline on all commits](https://gitlab.com/gitlab-org/gitlab/issues/25148) * [Allow fork pipelines to run in parent project](https://gitlab.com/gitlab-org/gitlab/issues/11934) # Low * CI button shows even when CI is configured: https://gitlab.com/gitlab-org/gitlab/issues/35421. * Control over images in MD: https://gitlab.com/gitlab-org/gitlab/issues/15697 * Trademarks and Copyright symbols issue: https://gitlab.com/gitlab-org/gitlab/issues/17652. * [Make it possible to use `only` keyword with `artifacts` in `.gitlab-ci.yml`](https://gitlab.com/gitlab-org/gitlab/issues/16680) * [Add an 'Allowed to Force Push' option to the Protected branches](https://gitlab.com/gitlab-org/gitlab/issues/15611) Currently a branch has to be unprotected to be able to force-push, which creates a time-window in which the branch in unprotected which is not ideal from a security point of view. * [Assign a ticket to a closed milestone in the UI](https://gitlab.com/gitlab-org/gitlab/issues/38099). * Display tags in the commits logs gitlab-org/gitlab#14549 * [Tie pending stuck with a build timeout](https://gitlab.com/gitlab-org/gitlab/issues/24540) * https://gitlab.com/gitlab-org/gitlab/-/issues/17822 * # Nice to have * [Implement cross-server (federated) merge requests](https://gitlab.com/gitlab-org/gitlab/issues/14116) * ~~[View the history of changes on issues](https://gitlab.com/gitlab-org/gitlab/issues/10103)~~ * https://gitlab.com/gitlab-org/gitlab/-/issues/14972 * https://gitlab.com/gitlab-org/gitlab/-/issues/28268 * [Add groups concept to Gitlab CI](https://gitlab.com/gitlab-org/gitlab/issues/195828) * [Group Wikis](https://gitlab.com/gitlab-org/gitlab/-/issues/13195) ### Gitlab-CI issues - [x] The biggest issue on the CI side is: https://gitlab.com/gitlab-org/gitlab/-/issues/9713 or https://gitlab.com/gitlab-org/gitlab-ce/issues/23902
issue