What is the difference between gitlab team and gitlab group?

Question

I am using Gitlab 5.0 to manage git repositories and I have never used github before Gitlab.

When I create a group, I see a new directory with this group name in / home / git / repositories. But nothing is done with the team. In addition, with the group, I can create a project for the group, and the assignments (for users of this group) are done automatically.

I do not see other differences between the group and the team , and I would like to understand this.

Thanks in advance and sorry for the bad English (I'm French),

Answer 1

GitLab 6.0 (August 2013, 22d)

See commit 3bc4845 :

Function: Replace teams with group members

We introduce group membership in 6.0 as a replacement for teams.
The old mix of groups and teams was confusing for many people.
And when the team members where they were changed, this did not affect the permissions of the project.

In GitLab 6.0, you can add members to a group with a permission level for each member .
These group members will have access to the projects in this group.
Any changes for team members will be immediately reflected in the project permissions.
You can even have multiple owners for a group, which greatly simplifies administration.

---

Why do Team links still exist in GitLab 7? e.g. Filter by Command

• The " team " now (GitLab 6.x-> 7.x 2015) seems to be a limited project (see, for example, features/project/team_management.feature and app/models/project_team.rb or spec/models/project_team_spec.rb ).
  A project can be part of a group : see " Gitlab API for all projects under a group ."

• A " group " refers to users and can group several projects (see features/groups.feature , app/models/group.rb , app/models/members/group_member.rb )

As a user, you are the first member of the group and have roles ("Reporter", "Developer", ...) associated with the project (which makes you a member of this project, part of the "team" for this project).
No role, means "not a member of the team for the project."
See db/migrate/20140914145549_migrate_to_new_members_model.rb .

---

The answer to this question is GitLab 5.x (until August 2013, 22d)

• The group is intended for grouping projects similar to a folder (git repositories)
• The team is designed to group resources (people).

These concepts have been refined in GitLab 4.2 .

This allows you to manage authorization in a more convenient way, given permissions for a group of projects in one operation and / or by granting permission to the group of people referred to by their team.

GitLab 5.x is no longer used by Gitolite, but prior to 5.0 commands and groups come from Gitolite , and its gitolite.conf configuration file .
Here, the team and groups were announced and connected to provide access to the permission.
Even without gitolith, the idea remains: managing authorization through association between teams (people) and groups (projects).