Blocking Issues and Features for GNOME Migration to GitLab

As part of GNOME's evaluation to migrate over to GitLab they've identified a handful of bugs (and features) that are currently blocking the start of the migration. Below is the list of said bugs.

Migration Blockers

1. https://gitlab.com/gitlab-org/gitlab-ce/issues/24945 This is needed for the central translation user account and validation. This is a blocker of the pilot program.
2. https://gitlab.com/gitlab-org/gitlab-ce/issues/31847 This prevents the FF workflow GNOME would like to work with.

Minor Issues

1. https://gitlab.com/gitlab-org/gitlab-ce/issues/33770 Needed for the migration tool.
2. https://gitlab.com/gitlab-org/gitlab-ce/issues/34284 Needed for GNOME's IRC bots.

Feature Requests

1. https://gitlab.com/gitlab-org/gitlab-ce/issues/27031 GNOME needs it since they have many milestones and labels already due to the history of the projects.
2. https://gitlab.com/gitlab-org/gitlab-ce/issues/20076 Make fast forward merge requests a CE feature

cc/ @JobV

added meta label

changed the description

cc @victorwu @mydigitalself

changed title from Blocking Bugs for GNOME Migration to GitLab to Blocking Bugs and Features for GNOME Migration to GitLab

changed the description

@eliran.mesika : Can you make sure we've captured everything we need for GNOME on this issue? I.e. we've captured all the requirements we've chatted to them about.

cc @smcgivern

@smcgivern : I don't think we have an issue for moving FF to CE right? Can you confirm?

added Discussion Platform labels

changed milestone to %Next 2-3 months

marked this issue as related to #24945 (closed)

marked this issue as related to #31847 (moved)

marked this issue as related to #33770 (closed)

marked this issue as related to #34284 (moved)

marked this issue as related to #27031 (moved)

@victorwu I think it's one of our most popular issues! https://gitlab.com/gitlab-org/gitlab-ce/issues/20076

Ah yes. Moving a popular feature to CE would of course be a popular issue. Updating here. Thanks.

changed the description

marked this issue as related to #20076 (closed)

Hi all,

Great to hear the news about GNOME - particularly as it sounds like they plan to use a ff-only workflow that sounds very similar to the one my company has been using on gitlab for almost a year now. I hope no one minds me commenting in this way, but it seems likely GNOME will run into the same issues that frustrate our users; could I suggest these issues might be relevant too:

https://gitlab.com/gitlab-org/gitlab-ee/issues/1774 (the title for this one could be misleading; a better summary might be 'when rebase operation fails users are not told the rebase has failed or why'.

https://gitlab.com/gitlab-org/gitlab-ee/issues/895 (this is a really frustrating usability issue)

Hope that's helpful.

Actually maybe I got the wrong idea and GNOME don't intend to use the 'rebase' feature within GitLab? If not those two aren't relevent and you can ignore me. :-)

changed title from Blocking Bugs and Features for GNOME Migration to GitLab to Blocking Issues and Features for GNOME Migration to GitLab

changed the description

@victorwu these are all the issues they noted to me, yes.

@eliran.mesika how's this going? I saw this was linked from the GNOME GitLab :)

@connorshea trying to move the issues along within the respective ones.

mentioned in issue #31847 (moved)

@connorshea @eliran.mesika : This is our meta issue to track the GNOME blockers.

We are working on https://gitlab.com/gitlab-org/gitlab-ce/issues/20076 for 10.1

@smcgivern : I think we can roughly plan to get https://gitlab.com/gitlab-org/gitlab-ce/issues/31847 going for 10.2. Does that sound about right to you? Then we'll be really close to wrapping all the requests here.

@victorwu yes, with the caveat that 10.2 is interrupted a little because of the summit.

mentioned in issue #34284 (moved)

@victorwu:

1. Will https://gitlab.com/gitlab-org/gitlab-ce/issues/24945 make 10.1?
2. What is the plan for https://gitlab.com/gitlab-org/gitlab-ce/issues/34284?

Regarding #31847 (moved), my plan with GNOME is to announce their adoption of GitLab in November so assuming we'll be on plan there any delays will be very problematic as that FF will be part of the message as well as needs of the community.

@victorwu @JobV some clarifications from GNOME: critical projects won't be able to move until https://gitlab.com/gitlab-org/gitlab-ce/issues/24945 and https://gitlab.com/gitlab-org/gitlab-ce/issues/31847 will be resolved. This means our announcement won't happen until the critical projects have been migrated to GitLab. Can we prioritize these two issues accordingly?

FYI, GNOME has a dedicated issues for bugs or missing features/details they are keeping on their new instance: https://gitlab.gnome.org/GNOME/Infrastructure/issues/8

changed the description

@eliran.mesika : https://gitlab.com/gitlab-org/gitlab-ce/issues/24945 is a Platform issue. @mydigitalself : Could you speak to it? It has a 10.1 milestone. That means it is planned for 10.1 release @eliran.mesika .

Regarding #31847 (moved) and #34284 (moved), the earliest we would consider these is for 10.2, since 10.1 scope is already established. Perhaps we can try to get at least one of them for 10.2. But I can't say for sure now.

@victorwu it would be great if we can scope #31847 (moved) for 10.2.

#24945 (closed) is being driven by a community member, so the timing is somewhat out of our control at the moment, trying to chase it up.

@rymai can you have someone help drive that issue ^ forward? It's quite important.

mentioned in merge request gitlab-workhorse!185 (closed)

@JobV Sure thing, it seems #24945 (closed) (migration blocker) / https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/13264 (and prerequisite MRs) are on a good track now. I've also started working on #34284 (moved) (minor issue) / https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14308 and I expect it to be ready for %10.1.

mentioned in issue csoriano/testGitLab#1 (closed)

mentioned in issue #38639 (closed)

mentioned in issue #36239

moved to gitlab#11137

Hey!

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.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

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?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

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?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue