Re: [ANNOUNCE] codeBeamer MR - Easy ACL for Git

From: Sitaram Chamarty <sitaramc@gmail.com>
Date: Nov 23, 2009, 16:28 UTC
Message-ID: <2e24e5b90911230828h199ae1ccv50d1fbdf50c91296@mail.gmail.com>
In-Reply-To: <4B0A5720.6020804@intland.com>

On Mon, Nov 23, 2009 at 3:04 PM, Intland Software <marketing@intland.com> wrote:

Show 9 quoted lines

> Sitaram Chamarty wrote:
>>
>> Intland: do you have a page that describes your role based ACL stuff a
>> little more?
>
>   This is a good starting point in our Knowledge Base, to read more about
> the permission model used in MR:
>
>   https://codebeamer.com/cb/wiki/11121

Thanks; I've read through that and the link to "Working Sets".

Modulo a bunch of *big* differences [*] in scale and scope between gitolite and MR, I'm fairly certain that working sets (groups of projects), user roles, user groups, etc., can all be done using gitolite's group mechanism and its delegation feature.

It won't be as refined and nuanced as in MR, but in the main, maintainable access control, which is the main point of all those features, can be done.

-- 
Sitaram


[*] these big differences are:

  - gitolite config is all in one text file versus whatever MR uses
    internally
  - gitolite only deals with the git repo for each project; MR does with
    all sorts of stuff outside the actual code repo
  - gitolite has no UI for the end user, MR clearly does, and the user
    can do a lot of stuff by themselves (like create new projects)
  - possibly many more I missed