Web app-like experience for issues and merge requests pages

Background

• GitLab is a web app. It is not a website.
• We should educate users and move them toward web app-like experiences, and move away from website experiences.
• In websites, you typically have web forms. The object model that we reinforce to users is that they do CRUD on objects, such as issues, merge requests, etc. Each time you manage an object, you have to do it all at once. This model is clunky. It is slow. It is not efficient. It slows down idea to production because people cannot make quick, small changes.
• In a web app, the focus is on user flows. The user shouldn't care about the underlying objects in the system, and when/how they persist.
• In a web app, when you make a change, the change should be instantaneous, at least as felt/experienced by the user. The user should not care about objects in the database. The user should not care about persistence.

Issues

• Making UI elements real-time
• https://gitlab.com/gitlab-org/gitlab-ce/issues/34261
• https://gitlab.com/gitlab-org/gitlab-ce/issues/33874
• https://gitlab.com/gitlab-org/gitlab-ce/issues/34258
• https://gitlab.com/gitlab-org/gitlab-ce/issues/33873
• Inline title/description editing for merge requests
• Inline approvals management for merge requests
• Inline squash / rebase management for merge requests
• New merge request without a web form

changed milestone to %Backlog

@sarrahvesselov : Here's an issue grouping many of the existing ideas. Feel free to give feedback / provide UX direction, etc. No immediate action required at this point. But something I'm interested in moving toward.

mentioned in issue #33874 (closed)

Will do @victorwu, thanks for looping me in

moved to gitlab#10664

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