See #53206 (moved) for the preface, this issue is the meant as tracker to list the issues affecting KDE. I will update the list with issues we're getting affected.
this feature is backported to the community edition? or not? Can someone clarify this to me?
The merge request referenced (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22158) only backports any CE changes that we made in EE. It doesn't backport the feature, only some Vue component and JS changes to make conflicts between CE & EE happen less often.
Hello, Is there any chance feature implemented in gitlab-org/gitlab-ee#1984 moved to gitlab-ce? It is one of most requested feature that people want and are annoyed due to lack of it, specially in larger code review.
Ah, optional approvals was discussed already, and we agreed that optional merge request approvals are fine for our use-case. (@bcooksley commented on one of issues, but I can't find out issue at moment).
In trying out GitLab myself for KDE projects, I have had a difficult time managing the volume of email I'm receiving. Phabricator, which we're migrating away from, has the ability to disable email notifications and instead see notifications in a web page instead (not just TODOs, but notifications of general activity). Even better is GitHub, which groups actions into the item they're affecting. With this style, if I'm following 50 Issues/Merge Requests, and each gets 10 comments, I see 50 items in my notification center, rather than getting 500 email or web-based notifications.
Our current use cases covers people sitting in front of their computers, with email being a key tool in their productivity workflow. That won't change for a while in our product and market. So whatever we add, would be secondary / supplemental to that.
The above doesn't describe the KDE community at all. The vast majority of KDE contributors are volunteers who can devote a few hours a week to the project, and are virtually never sitting in front of a computer all day handling emails as they come in. If KDE starts to feel like a job, many of these people will burn out. For that reason, we already have a problem with people filtering, auto-deleting, or ignoring emails. The more emails people get, the more acute this issue becomes.
I'd also like to nominate https://gitlab.com/gitlab-org/gitlab-ce/issues/60690 as a blocker. Without the Merge Request Reviews feature, every inline comment sends an email (instead of one email per review, which can include multiple comments), and inline comments do not show the updated context when the MR is changed in response to feedback.
Phab has these features, and losing them has impaired my ability to perform code reviews for the KDE projects that have already moved to GitLab.
I'm a very heavy user of Phabricator Tasks, and one of the things I like about the functionality is that it offers detailed relationships between tasks (e.g. child/parent). GitLab currently only offers "related to", which is not as detailed and would represent a loss of information when our Phab Tasks are imported into GitLab Issues.
@Pointedstick I've modified the issue description to include the Merge Request Reviews in blocker, and blocker/sub-task/tracking into nice-to-have category.
GitLab is moving all development for both GitLab Community Edition
and Enterprise Edition into a single codebase. The current
gitlab-ce repository will become a read-only mirror, without any
proprietary code. All development is moved to the current
gitlab-ee repository, which we will rename to just gitlab in the
coming weeks. As part of this migration, issues will be moved to the
current gitlab-ee project.
If you have any questions about all of this, please ask them in our
dedicated FAQ issue.
Using "gitlab" and "gitlab-ce" would be confusing, so we decided to
rename gitlab-ce to gitlab-foss to make the purpose of this FOSS
repository more clear
I created a merge requests for CE, and this got closed. What do I
need to do?
Everything in the ee/ directory is proprietary. Everything else is
free and open source software. If your merge request does not change
anything in the ee/ directory, the process of contributing changes
is the same as when using the gitlab-ce repository.
Will you accept merge requests on the gitlab-ce/gitlab-foss project
after it has been renamed?
No. Merge requests submitted to this project will be closed automatically.
Will I still be able to view old issues and merge requests in
gitlab-ce/gitlab-foss?
Yes.
How will this affect users of GitLab CE using Omnibus?
No changes will be necessary, as the packages built remain the same.
How will this affect users of GitLab CE that build from source?
Once the project has been renamed, you will need to change your Git
remotes to use this new URL. GitLab will take care of redirecting Git
operations so there is no hard deadline, but we recommend doing this
as soon as the projects have been renamed.
Where can I see a timeline of the remaining steps?