Re: [i3] Help: Code Review Software
- From: Michael Stapelberg <michael@xxxxxxxx>
- To: Discussions/Questions about the i3 window manager <i3-discuss@xxxxxxxxxxxxx>
- Date: Mon, 30 Jul 2012 20:19:22 +0200
Hi,
Quoting ablepharus (2012-07-26 14:25:55)
I would really like to write the desired Software and I would use django
for it. I would be ready for doing this alone, but of course I'd be
happy about some help. I have planned on writing such a service anyway,
without a target. I agree with the mentioned needs and restrictions.
That’s nice to hear. I’d be happy to betatest anything you come up with.
By the way, I evaluated barkeep briefly. Here are my observations:
• Deployment is horrible, as with most ruby projects :-/
• Documentation is really sparse, and the existing documentation
contained two errors (I opened an issue for one and fixed the other
one right away).
• The only distinction is between admin/normal users, that is, you
cannot specify who’s able to comment or approve commits (not that
approving has any effect, but…).
• Authentification is possible only via OAuth with a horrible user
experience. You are directly redirected to the configured OAuth
provider (e.g. google) without any message. This is the biggest
problem for my intended use. We really need to be able to create user
accounts automatically to hand them out after somebody uploads a
patch.
• barkeep only supports a post-commit workflow. This means I’d have to
build a site (and/or script) to upload patches and then have them be
committed to a new branch automatically. No big deal, but see the
points above — after all, it’s not really worth it I think.
I have to stress that barkeep really does it right in the user
interface. A list of commits, a nice diff and comments is really all I
want to have. I just think adjusting it is not that easy for now.
Best regards,
Michael
Other related posts:
