From owner-freebsd-questions@FreeBSD.ORG Fri Jul 28 14:32:28 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FFFC16A4DE for ; Fri, 28 Jul 2006 14:32:28 +0000 (UTC) (envelope-from chris@Shenton.Org) Received: from Shenton.org (23.ebbed1.client.atlantech.net [209.190.235.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2359F43D4C for ; Fri, 28 Jul 2006 14:32:25 +0000 (GMT) (envelope-from chris@Shenton.Org) Received: (qmail 8610 invoked by uid 1001); 28 Jul 2006 14:32:24 -0000 From: Chris Shenton To: Greg Groth References: <44C4ED38.3000905@gregs-garage.com> Date: Fri, 28 Jul 2006 10:32:24 -0400 In-Reply-To: <44C4ED38.3000905@gregs-garage.com> (Greg Groth's message of "Mon, 24 Jul 2006 10:54:32 -0500") Message-ID: <86slkl7qbr.fsf@PECTOPAH.shenton.org> User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: Subversion web development question. 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: Fri, 28 Jul 2006 14:32:28 -0000 I'd definitely go with SVN for a code repo. I use a couple different SVN servers on various teams I work with at my clients. I also set one up for myself for code I'm working without other coders, mainly so I could get at it from home, on the road, or some client's site; a laptop or two, a desktop or two.... Very convenient. You might also consider integrating it with the Trac issue tracker . It has a very nice SVN repo code browser, takes bug/issue/feature tickets, offers a wiki (e.g., for writing project plans, docs, whatever). It's integrated in the sense that you can check in code into SVN and say in your log message something like fixes #37 and Track will notice and close the open ticket #37 for you. You can reference code within Trac too. It's lightweight and gets out of your way. I prefer it to other trackers and trouble ticket systems I've used like Remedy , Jira, and even the venerable RT. Even if all you use is Trac's code browser it's a win, but the other stuff is real helpful with no bloat. FWIW, it's all written in Python. (a language I prefer to PHP and Java)