gitlab团队和gitlab组有什么区别? [英] What are the differences between gitlab team and gitlab group?

问题描述

我正在使用Gitlab 5.0来管理我的git存储库，并且在Gitlab之前从未使用过github.

I'm using Gitlab 5.0 to manage my git repositories and I've never used github before Gitlab.

当我创建一个组时，在/home/git/repositories中看到一个具有该组名的新目录. 但是，对于团队而言，这是没有完成的. 另外，对于组，我可以为该组创建一个项目，并且分配(针对该组的用户)是自动完成的.

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

我看不到组和团队之间的任何其他区别，我想理解这一点.

I can't see any other differences between group and team and I would like to understand that.

在此先感谢您，英语不好(我是法语)，

Thank you in advance and sorry for the bad English (I'm french),

推荐答案

GitLab 6.0(2013年8月，22d)

GitLab 6.0 (August 2013, 22d)

请参见提交3bc4845 :

我们在6.0版中引入了组成员身份，以代替团队.
小组和团队的旧组合让很多人感到困惑.
而当团队的成员发生变化时，这并没有反映在项目权限中.

We introduce group membership in 6.0 as a replacement for teams.
The old combination of groups and teams was confusing for a lot of people.
And when the members of a team where changed, this wasn't reflected in the project permissions.

在GitLab 6.0中，您可以将成员添加到具有每个成员权限级别的组中..
这些小组成员将有权访问该小组中的项目.
对组成员的任何更改将立即反映在项目权限中.
您甚至可以为一个组拥有多个所有者，从而大大简化了管理.

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

---

那么，为什么在GitLab 7中仍然存在对Teams的引用?例如按团队过滤"

Why do references to Teams still exist in GitLab 7 then? e.g. "Filter by Team"

• "团队"似乎现在(GitLab 6.x-> 7.x 2015)似乎仅限于项目(例如，参见 features/project/team_management.feature 和项目可以成为小组的一部分:请参阅"适用于组下所有项目的Gitlab API ".

  • "Team" seems now (GitLab 6.x->7.x 2015) seems limited to a 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 group".

    "组"引用用户，并且可以对多个项目进行分组(请参阅 )

    "Group" references users, and can group multiple projects, (See features/groups.feature, app/models/group.rb, app/models/members/group_member.rb)

    作为用户，您首先是组的成员，并且具有与项目相关的角色("Reporter"，"Developer"，...)(这使您成为成员)该项目的团队"的一部分).
    没有角色，表示不是项目团队的成员".
    参见 db/migrate/20140914145549_migrate_to_new_members_model.rb .

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

    GitLab 5.x的答案(2013年8月之前，22d)

    Answer for GitLab 5.x (before August 2013, 22d)

    • 分组用于对项目进行分组，类似于文件夹(git存储库)
    • 团队用于对资源(人员)进行分组
    • Group is for grouping projects, similar to a folder (git repositories)
    • Team is for grouping resources (people)

    GitLab 4.2 .

    这允许您以更方便的方式管理授权，在一个操作中授予一组项目的权限和/或授予其团队引用的一组人员的权限.

    That allows you to manage authorization in a more convenient way, given permissions to a group of projects in one operation, and/or given permission to a group of people, referenced by their team.

    GitLab 5.x不再使用Gitolite，但在5.0之前，团队和小组来自 Gitolite 及其 gitolite.conf配置文件 .
    在此声明并关联团队和组以便授予权限访问权限.
    即使没有甘蔗糖，这个想法仍然存在:通过团队(人员)和团队(项目组)之间的关联来管理授权.

    GitLab 5.x no longer used Gitolite, but before 5.0, teams and groups are coming from Gitolite, and its gitolite.conf configuration file.
    This is where team and groups were declared and associated in order to grant permission access.
    Even without gitolite, the idea persists: managing the authorization through association between teams (of people) and groups (of projects).

    这篇关于gitlab团队和gitlab组有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！