From owner-freebsd-git@FreeBSD.ORG Fri Mar 20 20:45:55 2015 Return-Path: Delivered-To: freebsd-git@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A4F2573; Fri, 20 Mar 2015 20:45:55 +0000 (UTC) Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 07639995; Fri, 20 Mar 2015 20:45:55 +0000 (UTC) Received: by lagg8 with SMTP id g8so96120323lag.1; Fri, 20 Mar 2015 13:45:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=qNGPU+XCajHL1ompfEWSpb6syNtvm3ru4jXIhnNYkZo=; b=Qc15iM6RevCo9MJSJTlkVc7qfzdzJPBTulT5bSKD5YIuIN38f0i1PpBZdmDbJ/65c5 z9REfoixONW9L/Uj8HORIhUZ2LSzh5hDVOAqpvoVSWxjfLCZzY9t+jKBtqttCkFVJcRC k4WTKGDdDRCrxsDC4ThWKKecacH7Mf1OJPrNuLcJh65wSHIdKK2bXfTiEZH5xZ2V/Vag oYtAOdu2ovTsTNgPfyHi6T00mGTJrjjgRUhi57BT/J59Pzk1FSvjqC7AO8FEefTrQih5 lAFO9IXIzKMAkXctgEW4ePU8z8sBERR/d2DduwcCSrbYrNDG1feRZC+CqzROGlSnKO+G mfkQ== MIME-Version: 1.0 X-Received: by 10.152.163.2 with SMTP id ye2mr50996694lab.89.1426884353219; Fri, 20 Mar 2015 13:45:53 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.82.164 with HTTP; Fri, 20 Mar 2015 13:45:53 -0700 (PDT) In-Reply-To: <550A561D.4030109@freebsd.org> References: <550A561D.4030109@freebsd.org> Date: Fri, 20 Mar 2015 13:45:53 -0700 X-Google-Sender-Auth: r48lXjG4QRYrvizdpODxptZDv5U Message-ID: Subject: Re: Installing Gitlab on FreeBSD From: Craig Rodrigues To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-git@freebsd.org X-BeenThere: freebsd-git@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion of git use in the FreeBSD project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Mar 2015 20:45:55 -0000 On Wed, Mar 18, 2015 at 9:52 PM, Alfred Perlstein wrote: > > > We use it here at Norse on FreeBSD. Had some issues with earlier > versions. Our current deploy had some issues with process limits and > timeouts associated with the gargantuan size of the FreeBSD ports and src > repos. > > We were able to fix this by increasing a bunch of timeouts. I can ask our > ops lead about it to get some information. > Can you get your ops ninja to post any tips/tricks to this thread which I created: https://forums.freebsd.org/threads/howto-install-gitlab-on-freebsd.50920/ I want there to be more info for how to run Gitlab on FreeBSD, since a lot of the existing docs are very Linux-centric. In your experience at Norse, how does Gitlab compare against Github? Is it better, worse, or mostly the same? How good is the Gitlab project at fixing things and being responsive to feedback? What I am beginning to realize is that if you compare an individual feature of Github, like wiki, bug tracker, code review, there are better alternatives for each component, i.e. better wiki, better bug tracker, better code review tool. However, the value of Github is that everything is integrated. So, when I do a pull request on Github, and then commit, everything is integrated and linked. For FreeBSD, we have chosen nice tools, like Bugzilla (bug tracker), Phabricator (code review), MoinMoin (wiki) Subversion (code repository). Each of these things works nicely on its own, but to tie all those things together into a modern development environment requires a lot of work. There seem to be a few enthusiastic volunteers who are tying this together to make things work, but we definitely have rough edges. I'm wondering if the FreeBSD project would be better off going with one of these integrated solutions. I understand that the FreeBSD project likes to be independent and run its own infrastructure, but that is a lot of work, and I think we are missing out on a lot of innovation happening in other software projects that are taking care of all this stuff. -- Craig