Teams collaborate more easily when they can find the work, understand its purpose, and contribute without relying on someone else's memory. The Source and collaboration pillar brings those conditions together: projects with clear ownership, reviews that hold up under pressure, project setups teams can build on, and contribution paths that work for people outside the owning team.
A GitLab project can connect planning, source code, merge requests, pipelines, releases, and day-to-day responsibility. Keeping related work together makes a change easier to follow. Separate projects make sense when people need different access, release schedules, or operating responsibilities, but each split adds dependencies and handoffs to manage.
A recent change can show where collaboration gets difficult. Repeated handoffs across projects may call for a different project arrangement. A change that bypassed review points to the review and branch permissions. These are different problems, even when both leave the team waiting.
The first contribution is another revealing example. A supported project setup helps a new team get started and maintain what it inherits. A contribution path for other teams helps people improve existing work without depending on private instructions or unnecessary access.
The checklist offers questions you can discuss using your own projects and recent changes.
Design principles
Understand the reasoning behind the pillar's guidance and the choices that matter for your team.
- 01
Keep planning, code, delivery, and day-to-day ownership together unless access, release, or legal needs call for separate projects.
- 02
Protect important branches, require the right reviewers, and keep the reason, discussion, checks, approval, and result with the merge request.
- 03
Provide supported templates and components, clear shared rules, and a practical way to request an exception.
- 04
Use clear project information, ownership, templates, and reusable components so contributors don't depend on private team knowledge.
Recommendations
Explore practical ways to improve in this area, including when each approach fits and what to watch for.
Help contributors find a project, prepare a change, get a review, and adopt the result without depending on private team knowledge.
Help teams complete their first contribution, understand what they can adapt, and keep their project setup current.
Organize projects around ownership, access, and release needs, and preserve the surrounding work when projects move.
Help teams review important changes independently and keep the reason, discussion, checks, and approval with the merge request.
Checklist
Look at your current setup and recent work to see where you're meeting the pillar's goals and what you'd like to improve.
Open the checklist→