What are the differences between gitlab team and gitlab group? -
i'm using gitlab 5.0 manage git repositories , i've never used github before gitlab.
when create group, see new directory group name in /home/git/repositories. team, no such thing done. also, group, can create project group , assignments (for users of group) done automatically.
i can't see other differences between group , team , understand that.
thank in advance , sorry bad english (i'm french),
gitlab 6.0 (august 2013, 22d)
see commit 3bc4845:
feature: replace teams group membership
we introduce group membership in 6.0 replacement teams.
old combination of groups , teams confusing lot of people.
, when members of team changed, wasn't reflected in project permissions.in gitlab 6.0 able add members group permission level each member.
these group members have access projects in group.
changes group members reflected in project permissions.
can have multiple owners group, simplifying administration.
why references teams still exist in gitlab 7 then? e.g. "filter team"
"team" seems (gitlab 6.x->7.x 2015) seems limited project (see example
features/project/team_management.feature
, ,app/models/project_team.rb
orspec/models/project_team_spec.rb
).
a project can part of group: see "gitlab api projects under group"."group" references users, , can group multiple projects, (see
features/groups.feature
,app/models/group.rb
,app/models/members/group_member.rb
)
as user, first member of group, , have roles ('reporter', 'developer', ...) associated project (which makes member of project, part of "team" project).
no role, means "not member of team project".
see db/migrate/20140914145549_migrate_to_new_members_model.rb
.
answer gitlab 5.x (before august 2013, 22d)
- group grouping projects, similar folder (git repositories)
- team grouping resources (people)
those notions have been refined in gitlab 4.2.
that allows manage authorization in more convenient way, given permissions group of projects in 1 operation, and/or given permission group of people, referenced team.
gitlab 5.x no longer used gitolite, before 5.0, teams , groups coming gitolite, , gitolite.conf
configuration file.
team , groups declared , associated in order grant permission access.
without gitolite, idea persists: managing authorization through association between teams (of people) , groups (of projects).
Comments
Post a Comment