{"thread":{"id":"25591","subject":"Re: Bugs in Gitosis","startedAt":"2010-10-29T10:52:58Z","lastAt":"2010-10-29T10:52:58Z","messageCount":1,"participants":["Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"154778","messageId":"AANLkTi=a=oD=8jNQmmWA_gYTjnOQKJUM=w8uVdx+N43u@mail.gmail.com","threadId":"25591","inReplyTo":"AANLkTinzLL-Sk1cMd_3WNogmgvr=x4gEh7LuS8guNYgB@mail.gmail.com","subject":"Re: Bugs in Gitosis","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2010-10-29T10:52:58Z","receivedAt":"2010-10-29T10:52:58Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"Hi Shawn,\n\nOn Fri, Oct 29, 2010 at 7:36 AM, Shawn Pearce <spearce@spearce.org> wrote:\n> On Oct 28, 2010 5:02 PM, \"Sitaram Chamarty\" <sitaramc@gmail.com> wrote:\n\n>> can do.  See\n>> http://github.com/sitaramc/gitolite/blob/pu/contrib/gerrit.mkd\n>> for a comparision\n>\n> There are a few inaccuracies in that document that I would like to correct.\n\nwell, updates I guess; I did update one part of it based on our IRC\nconv, but if there's more I'll put those in too.\n\n> For starters we now support regex patterns in branch access control rules.\n\nok; will update.\n\n> We also now allow $(username) in a pattern to mean the current user and thus\n> permit per-developer branches.\n\nRight; gitolite uses /USER/; it's only a syntax difference but I'll\nmention it somewhere.\n\n> We don't allow per-user access rules because in the corporate world its\n> usually a bad idea to have only one user with a particular set of\n> permissions. What happens when the user leaves the project or is hit by a\n> bus? Of course this also applies to most open projects too... :-)\n\nYou do the same thing in either case, no?  Take out the old guy's name\nfrom somewhere, put in the new guy's name?\n\nBut yeah, I'll amend this to say this is a subjective opinion :-)\n\n> We also allow importing a user's groups from an organization's LDAP server.\n> This can be useful when there are thousands of users on a single server and\n> the org wants to continue using their existing access controls.\n\nExcept in gitolite it's not an import; it's more like \"give me a\nprogram that, given a userid, returns a list of groups he belongs to\"\nand gitolite calls that if it's specified.\n\n> But after that, yes, that document is a good summary of the features that\n> both tools offer... and I know many companies really do salivate over the\n> branch level read access rules. It is difficult to do for Git, but it also\n> can be useful to have everything in a single location.\n\nProbably.  But where that restriction exists, I may have to show the\nauditors that the restriction holds, and that's a lot easier to do\nwhen they're in separate repos to begin with.\n\n-- \nSitaram\n"}]}