From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] GitLab Feature-Set / Was: devmanual moved to github
Date: Tue, 14 May 2013 09:59:57 -0400 [thread overview]
Message-ID: <CAGfcS_kkSrgxZyF1VAc-nZfv8hv9_kHoM4uE_dkvXk_UjDzAeA@mail.gmail.com> (raw)
In-Reply-To: <39106330.P4KaKQNKU3@sammi>
On Sun, May 12, 2013 at 3:18 PM, <sascha-ml@babbelbox.org> wrote:
> - It supports "Merge Requests", which are almost the same as PRs on Github,
> which allows user contributions to be reviewed quite easily.
So, out of curiosity I set this up on a VM and started playing with it.
It seemed like the UI for merge requests was limited to merges between
branches on the same repository. Github lets you make pull requests
between repositories. Logistically that is a BIG difference. With a
Github-like model users don't need write access of any kind to the
repository (they do their work in their own forks), but with Gitlab
you'd need to give write access (not sure if you can limit that to
only an incoming branch of some kind, which would be a free-for-all
area (which might also create problems as this is essentially an
arbitrary file hosting area)).
I could be missing something though - seems like a useful tool but it
might be more appropriate to closed teams than for public
contribution. If somebody knows of something I missed by all means
chime in.
Gerrit also requires letting the public push, but those pushes go to a
contained area and each commit is isolated.
Again, let me know if I missed something.
Rich
next prev parent reply other threads:[~2013-05-14 14:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 11:32 [gentoo-dev] devmanual moved to github Markos Chandras
2013-05-12 13:12 ` Rich Freeman
2013-05-12 13:27 ` Peter Stuge
2013-05-12 15:02 ` Ben de Groot
2013-05-12 15:15 ` Markos Chandras
2013-05-12 15:12 ` Diego Elio Pettenò
2013-05-12 15:02 ` [gentoo-dev] " Duncan
2013-05-12 13:15 ` Ulrich Mueller
2013-05-12 15:04 ` Markos Chandras
2013-05-12 15:17 ` Peter Stuge
2013-05-12 15:48 ` Ulrich Mueller
2013-05-12 15:54 ` Markos Chandras
2013-05-12 16:08 ` Rich Freeman
2013-05-12 16:12 ` Michael Palimaka
2013-05-14 15:44 ` William Hubbs
2013-05-14 17:51 ` Rich Freeman
2013-05-12 16:55 ` Ulrich Mueller
2013-05-12 16:04 ` Mike Gilbert
2013-05-12 17:20 ` Peter Stuge
2013-05-12 17:32 ` Michael Palimaka
2013-05-12 18:24 ` Peter Stuge
2013-05-12 18:31 ` Michael Palimaka
2013-05-12 22:12 ` Alexander Berntsen
2013-05-12 22:21 ` Peter Stuge
2013-05-12 22:24 ` Alexander Berntsen
2013-05-12 22:37 ` Peter Stuge
2013-05-13 7:09 ` Alexander Berntsen
2013-05-12 22:38 ` W. Trevor King
2013-05-13 6:32 ` Ralph Sennhauser
2013-05-13 7:07 ` Alexander Berntsen
2013-05-13 7:40 ` Ralph Sennhauser
2013-05-13 7:47 ` Alexander Berntsen
2013-05-13 13:28 ` Ciaran McCreesh
2013-05-14 15:55 ` William Hubbs
2013-05-13 12:38 ` Greg KH
2013-05-13 12:42 ` Alexander Berntsen
2013-05-13 21:59 ` Duncan
2013-05-12 17:33 ` Theo Chatzimichos
2013-05-12 18:22 ` Peter Stuge
2013-05-12 19:18 ` [gentoo-dev] GitLab Feature-Set / Was: " sascha-ml
2013-05-14 13:59 ` Rich Freeman [this message]
2013-05-14 14:19 ` Peter Stuge
2013-05-14 14:40 ` Rich Freeman
2013-05-13 3:38 ` [gentoo-dev] " Arun Raghavan
2013-05-12 15:13 ` Richard Yao
2013-05-12 15:38 ` Ulrich Mueller
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=CAGfcS_kkSrgxZyF1VAc-nZfv8hv9_kHoM4uE_dkvXk_UjDzAeA@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox