This direction is a work in progress, and everyone can contribute. Please comment and contribute in the linked issues and epics. Sharing your feedback directly on GitLab.com is the best way to contribute to our strategy and vision.
Source Code Management provides the core workflows and controls for teams to collaborate using Git to build great software, including protected branches, code owners, merge request approvals, and mirroring.
Building great software depends on teams working well together. Teams can rarely be divided into areas of complete independence. As cross-functional security, compliance and growth teams are formed, or new services and libraries are created, effective coordination and collaboration is need. This is true whether using a single monolithic repository, or spread across numerous smaller services and libraries.
Teams require the controls to protect production while making it easy for everyone contribute. This means providing more granular and dynamic controls so that low risk changes can be made easily, and only the highest risk changes require the strictest controls.
Building software we stand not only on the shoulders of the giants of Computer Science, but of our contemporaries: the authors and maintainers of open source software. Private companies have been beneficiaries, contributors, and authors of these projects, yet lack of controlled workflows prevent more upstream contributions.
Upstreaming contributions from private repository to a public upstream should simple and safe, even for conservative organizations. Whether the upstream repository is on the same GitLab server, is hosted on GitHub.com, or upstream contributions managed via a mailing list. GitLab should enable collaboration between isolated and firewalled teams.
In progress: Represent code owners in the database
In order to be able to Support selecting CODEOWNERS section to be a required approval rule
we should no longer access a project's
CODEOWNERS file each time we need to conduct an operation.
These queries do not scale well and get more expensive as data sets grow. Representing code owners
in the database will also allow us to invent new ways for initial setup of this feature, such as
while navigating files or navigating users.
In progress: Manage/reduce repository size
Managing & reducing repository storage is an important part of resource management/consumption of Git repositories. The ability to easily cleanup and receive feedback on related actions from the GitLab GUI is an important part of managing your source code.
Next: Forking improvements
Forking workflows are important for open source projects on public instances like GitLab.com, but they are also used for private projects on GitLab.com and elsewhere. There are a range of significant shortcomings in the forking workflow that should be resolved. Forking workflows should be fully supported in GitLab so that they can be used by open source projects and enterprises, public or private.
Many software products often consists of many services and/of components that are need to be integrated to ship complex applications, but for reasons of scale, access control and history, it may not be possible or advisable to have many hundreds of projects operating in the same Git repository and the same GitLab project.
Providing a top-level merge request that in turn actions lower-level merge requests in related projects can provide a central point of action to submit, review, approve, and merge changes into the main branch.
Limiting which branches a user can read in a Git repository is possible in a basic sense, by only advertising a subset of refs, but it is not possible to guarantee that unreachable objects will not be sent to the client. This means that branch read access controls would be very weak, since they could not prevent exfiltration of data they do not have permission to read.
Path-level read access controls
From a commit, Git expects all trees and blobs to be reachable. Although Git supports partial clone and spares checkout, which allow data to be excluded from fetch and checkout, Git expects to be able to fetch missing objects on demand. Deliberately excluding objects by path is likely to cause unexpected failures.
This category is currently at the Loveable maturity level (see our definitions of maturity levels).
However, specific aspects are not yet loveable:
For public open source projects, GitHub is our primary competitor, with millions of active users having chosen GitHub before the first version of GitLab ever existed.
In most source code management capabilities GitLab compares favorably to GitHub, the most notable exception being the maturity of forking workflows which GitHub pioneered. GitHub has a highly polished and fast product, which makes tasks like browsing and managing projects fast and easy.
For users of SVN (Apache Subversion) intending to migrate to Git, GitHub is a significant competitor, particularly because GitHub supports hosting SVN repositories.
Perforce competes with GitLab primarily on it's ability to support enormous repositories, however, Perforce also competes on the basis of being a Centralized Version Control System. This means that Perforce not only supports granular write permissions, but granular read permissions on a branch and file path basis. While fine grained read permissions are important to some customers, large monolithic repositories may be split into smaller repositories allowing read controls and easier management.
Large file support (see Gitaly direction) is an ongoing area of interest because it blocks certain segments of software development from using Git.
Similarly extremely large repository support (see Gitaly direction) is also an area of interest for the same reason.
The most frequent category of request is for improved support for finer grained controls, so that policies can be enforced at key points in the workflow, and more permissive permissions can be granted at other times.
Other items of frequent interest include: