From: Intland Software <marketing@intland.com>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] codeBeamer MR - Easy ACL for Git
Date: Thu, 19 Nov 2009 14:50:02 +0100 [thread overview]
Message-ID: <4B054D0A.5030802@intland.com> (raw)
In-Reply-To: <20091118120936.GL17748@machine.or.cz>
Petr Baudis wrote:
> I think a lot of people wonder now, how does this compare to existing
> solutions; from your announcement I thought it's something like
> Gitosis/Gitolite, but in fact it seems more similar to Gitorious or
> GitHub (if it was publicly available, of course); perhaps it would be
All right, some quick comparisons with codeBeamer Managed Repository (MR).
* MR against Gitosis
In terms of access control, MR has the concept of "role", and it makes our security model more fine grained. Permissions
can be set by role. One user account can have multiple roles. Roles are project-dependent. When you add a group to a
project, you can assign multiple roles to the group (which is equivalent with assigning those roles to each group member
one by one).
On the other hand, MR has a much broader scope than Gitosis. MR helps you to manage your repos, to track your
tasks/bugs/issues, to follow commit activities, to browse repos in the web, can be extended using its APIs, etc. (And
you don't have to install and maintain Git extensions for this.)
* MR against Gitolite
Pretty much the same applies here as well.
* MR against GitHub & Gitorious
Probably the most significant difference is that MR is available as free download, and can run behind your firewall.
MR was derived from the source code of our commercial product codeBeamer. CodeBeamer is a full-blown enterprise
collaboration solution, thus MR is likely to focus more on the enterprise needs, not on the "social" aspect.
next prev parent reply other threads:[~2009-11-19 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 8:33 [ANNOUNCE] codeBeamer MR - Easy ACL for Git Intland Software
2009-11-18 12:09 ` Petr Baudis
2009-11-18 13:19 ` Intland Software
2009-11-19 6:06 ` david
2009-11-19 10:06 ` Intland Software
2009-11-19 10:43 ` Jakub Narebski
2009-11-19 12:15 ` Aron Gombas
2009-11-19 11:39 ` Rakotomandimby Mihamina
2009-11-19 13:50 ` Intland Software [this message]
2009-11-19 14:01 ` Thomas Rast
[not found] ` <4B05588B.5080501@intland.com>
2009-11-19 15:22 ` Intland Software
2009-11-20 4:56 ` Sitaram Chamarty
2009-11-20 7:47 ` Petr Baudis
2009-11-20 8:24 ` Intland Software
2009-11-21 13:12 ` Sitaram Chamarty
2009-11-23 9:34 ` Intland Software
2009-11-23 16:28 ` Sitaram Chamarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B054D0A.5030802@intland.com \
--to=marketing@intland.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.