From owner-freebsd-questions@FreeBSD.ORG Thu Dec 22 04:07:39 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A754106566B for ; Thu, 22 Dec 2011 04:07:39 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 196BB8FC12 for ; Thu, 22 Dec 2011 04:07:38 +0000 (UTC) Received: by lahl5 with SMTP id l5so4530876lah.13 for ; Wed, 21 Dec 2011 20:07:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=QXuIm8cZ9ULI51SQquXbBRX6yy4qDXchUNu6gSwCxkA=; b=bQF0Du9bnKKVk4Bb5i9LqHfP1ALqXq4Kro5K5kzmPelV24eyWHwb2iq82WUHzx2o77 hO4NJeG/NEJvZP13LTNTSulm6osZ9M/R0ZkPB/b/f6KtA2iJLLvjOe9tsyz33KRU/RVa rBQLreenkiIauQRwb0ojO6vivRHCDxmC8ygX8= MIME-Version: 1.0 Received: by 10.152.104.6 with SMTP id ga6mr7734096lab.45.1324526857741; Wed, 21 Dec 2011 20:07:37 -0800 (PST) Received: by 10.152.24.195 with HTTP; Wed, 21 Dec 2011 20:07:37 -0800 (PST) In-Reply-To: References: <4EF29AD7.5040807@herveybayaustralia.com.au> Date: Wed, 21 Dec 2011 23:07:37 -0500 Message-ID: From: Outback Dingo To: ss griffon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: Revision control advice X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2011 04:07:39 -0000 On Wed, Dec 21, 2011 at 10:24 PM, ss griffon wrot= e: > On Wed, Dec 21, 2011 at 7:49 PM, Da Rock > wrote: >> On 12/22/11 11:37, Chris Hill wrote: >>> >>> Hello list, >>> >>> I apologize for this posting being not-much-on-topic, but my other >>> resources have come to naught and I think you folks may have some exper= ience >>> in this area. >>> >>> I'm looking to set up some sort of revision control system at work. Sim= ple >>> enough, except that our situation is approximately the reverse of what = most >>> revision control systems are designed for. >>> >>> Unlike, e.g., FreeBSD kernel development, we have dozens or hundreds of >>> small, rapid-fire projects that are created at the rate of 3 to 20 per >>> month. They last a few days or a few months and are (usually) not devel= oped >>> afterward. Each project has one to three developers working on it, some= times >>> simultaneously. Usually it's one guy per project. >>> >>> Since my programmers are not necessarily UNIX-savvy, I'd like to deploy= a >>> web interface for them which will allow them to create new repositories >>> (projects) as well as the normal checkin, checkout, etc. I want to set = this >>> up once, and from there on have the programmers deal with managing thei= r own >>> repos. And heaven forfend exposing them to the horrors of the shell. >>> >>> I've built a test server (9.0-RC3, amd64) for experimenting with this >>> stuff. So far I've installed and played with: >>> =A0- fossil. I like the simplicity and light weight, but it doesn't see= m to >>> allow creation of new repos at all (let alone multiple ones) from the w= eb >>> interface, and the documentation is meager. I've pretty much given up o= n it. >>> =A0- subversion, which looks like the heavy hitter of RCSs, but it's no= t at >>> all clear to me how to handle the multiple-project scenario. Still work= ing >>> on it. >>> =A0- git looks promising, but I have not installed it yet. >>> >>> If anyone can point me to a tool that might be suitable, I would be mos= t >>> grateful. >> >> I'd suggest subversion. It allows individual files to be versioned, you = can >> setup a webdav interface, and there are other tools that can help mainta= in >> it. >> >> Forget the individual repositories. Setup a single repository and have >> directories for each project. in each directory you can then setup trunk= , >> branches, whatever, as per best practices in the Book. >> >> Designate a person or two to administer, and use directory level auth, o= r >> another alternative I haven't thought of. >> >> My 2c's anyway. HTH >> >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.= org" > > Yeah I would second what Mr Rock says. =A0Set up a single repo where > folders can be used for projects. =A0Since svn lets you checkout sub > folders of a repo, each developer can check out the folder that > corresponds to their project. =A0Also, Tortoise svn is a very nice > graphical utility that will allow your developers to manage there svn > folders without even needing a web interface (most non unix people > that I know like tortoise), so there is less maintenance for you :) > Finally, kudos to moving towards using version control, its an > important step for a software company. git or mercurial - best choices > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg"