Hello, Sorry I am not a TU, and shouldn't really respond to said thread, but I have a question/problem I would like to bring up. If you enable the merge request functionality of Gitlab, what will stop the hundreds (potential thousands) of people who want to contribute to the official repositories? I know a lot of people will look at this and say "Isn't this a good thing?" but, until now the TUs have maintained the official repositories, and I am aware it was part of the goal of migrating to git, allowing for more community contributions, not just from Arch Staff however the opening of the merge request feature could cause thousands of people spamming the endpoints. If you only want TUs to be able to open them, how will you enforce this? If you want everyone to open merge requests and to contribute to official repositories, the TU's will no longer be maintaining the official repositories, instead will be reviewing and merging thousands of merge requests which simply bump the version of the package. This is a major issue within Alpine Linux, where merge/pull requests are free to be open by anyone in the community, but then you get tons of people demanding you merge their version bump, even though it is untested. So, in conclusion there is two issues which needs to be considered. If merge requests are Arch Staff only, then you will have thousands of merge requests which need to be closed, you will need some way of validating whether a user can or cant open said merge request (unless gitlab provides this?) or patch gitlab to distinguish between staff and community user. If merge requests are open to all, then you will potentially have thousands of package bumps to review, and test, and build. Your job will shift from maintainers of the official repositories to patch reviewers, or you will need to have some users who look through all the issues and automatically close package bumps. Again not a TU, this was a concern I had back during the migration from svn to git, however I remember being told (I believe by Jelle) that the migration was just the VCS and that issues/MR will be disabled until further notice. Is this the day(s) that will open the arch repository to the arch community? Or am I overreacting? Thank you! Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev