GNOME migration to GitLab

Hello all,

@eliran.mesika and me discussed it would be better to move here our priorities at GNOME so you can track them better. I will keep the noise as low as possible and I'll add here only those issues that have a general impact as a whole in GNOME. The issues are ordered by impact and not by time priority (thanks GitLab team that fixed most of those already), except when '(time critical)' it's written alongside the issue. Issues in each section are also ordered by impact.

High

• Duplicated issues handling. It's missing a richer UI experience. It's very important to us, since we usually deal more with duplicates than actual new issues - https://gitlab.com/gitlab-org/gitlab-ce/issues/39751.
• Be able to rebase MR's of non-dev contributors. https://gitlab.com/gitlab-org/gitlab-ce/issues/22292 (time critical). Time critical because of the notorious increase of upcoming external contributions from Google Summer of Code & Outreachy interns starting on March.
• Diffs bigger than 100kb cannot be reviewed - gitlab-org/gitlab#17609 (closed)

Medium

• Commit by commit review improvements:
  • Mark as reviewed per commit - gitlab-org/gitlab#14556
  • Able to go back/forward in commits while in the changes tab after clicking a commit - https://gitlab.com/gitlab-org/gitlab-ce/issues/39380
  • Ability to review commit messages - gitlab-org/gitlab#19691
• Figure out a workflow for merge requests that needs modifications to be done by the maintainer - https://gitlab.com/gitlab-org/gitlab-ce/issues/39756. One solution @connorshea pointed out is https://gitlab.com/gitlab-org/gitlab-ce/issues/32952 and it's indeed what we need, as it will allow to overcome other difficulties we have found.
  • Set by default "Allow edits by maintainers" in MRs. Otherwise we need to always say so in the MRs - gitlab-org/gitlab#23308 (closed)
• Allow reporters to set labels. We are missing a replacement for "components" of a project in Bugzilla, allowing labels to be set by the reporter it's a first step towards a replacement - gitlab-org/gitlab#15384
• Include cause in closing bug notification email - https://gitlab.com/gitlab-org/gitlab-ce/issues/42852

Minor

• Stock responses for comments (like need backtrace, etc.). - gitlab-org/gitlab#14328 (closed)
• And, not, or operands for search - https://gitlab.com/gitlab-org/gitlab-ce/issues/27747.
• Identifying better our instance as official GNOME. Custom color palette (it will make our designers happy) - gitlab-org/gitlab#20173
• Add "filter by name" for group labels, similar to what we have per project - https://gitlab.com/gitlab-org/gitlab-ce/issues/27031
• Allow to disable group mentions - https://gitlab.com/gitlab-org/gitlab-ce/issues/43686

Nice to have

Issues that are not regressions from what we had before but that we would appreciate to have.

• Ability to merge only part of the merge request - gitlab-org/gitlab#19238
• Allow permissions for wiki separated from developer permission - gitlab-org/gitlab#15443. This blocks the eventual usage of the GitLab wiki.
• Internal error when editing a issue description with task list (Akismet)- https://gitlab.com/gitlab-org/gitlab-ce/issues/38639.
• Have a good workflow for translators, it can involve labels that scale well (for having a label per language without cluttering much the UI) - Scalability of labels: https://gitlab.com/gitlab-org/gitlab-ce/issues/21902
• Issues templates are not discoverable enough - gitlab-org/gitlab#21485. This blocks eventual usage of the templates feature, since it's maintenance across all projects is too big for it not being used enough. Although Bugzilla had this feature we didn't use it, hence the 'nice to have' status.
• CI for every commit instead of just last commit - gitlab-org/gitlab#15007