Comments on: Managing Software

By: Jim

Jim — Fri, 27 Oct 2006 05:21:25 +0000

Just dropped in to mention I’m back now. If you like roses, read Billy’s last post about his Dad’s.

Congrats on the five years! You are a cute couple. And too, for the house sale.

I programed a long time ago. Mine were used in house (NASA) but it gave me a good feeling to see it take wings. Just like a good blog.
..
..

By: micah

micah — Wed, 25 Oct 2006 06:00:45 +0000

Use your python skills to add the feature to trac that a lot of other people want, namely making it so you can setup one trac instance for multiple projects.

Don’t spend your time coding something else from scratch, when you can improve something else that has a lot of the functionality that you already need. An improvement that a lot of others would find valuable (including myself).

By: Bjorn Bringert

Bjorn Bringert — Tue, 24 Oct 2006 17:21:51 +0000

I got tired of making releases and keeping homepages up to date for all my Haskell projects, so I wrote a program to do it:

[url]http://www.cs.chalmers.se/~bringert/darcs/hask-home/doc/[/url]

It assumes that you use darcs, Cabal, haddock, and probably makes some other assumptions too.

By: Adam Turoff

Adam Turoff — Tue, 24 Oct 2006 15:17:39 +0000

Google Code is a good choice.

If you want to host everything locally though, don’t give up on Trac. Sure, each little project will have its own trac instance, which should take maybe a few minutes to set up. Also, it triages bug reporting — little chance a bug coming from outside can be misreported against the wrong project.

For your sanity though, just funnel all the bug reports to a single mailing list. You can still close a bug with a commit message, so it’s not to heinous. One thing you lose is unified bug reports across projects, which arguably isn’t a huge feature in the first place.

By: John Goerzen

John Goerzen — Tue, 24 Oct 2006 14:15:33 +0000

But they all share a single Subversion repository. That’s not all that ideal, but with darcs, it would be much worse. I have some projects that really are too large for this to work with.

By: Paul Tötterman

Paul Tötterman — Tue, 24 Oct 2006 11:30:51 +0000

I’d also recommend google code. For me sourceforge is slow. It crawls. But google code is fast. Although if you like to use darcs and not subversion, then it might not be worth it.

Trac is what we use at work. We have all projects in the same repository. We use components for projects and send mail about all changes to a mailing list that most of us subscribe. RSS is not a bad option either, I just prefer mutt.

As others have stated, downloads in trac is solvable. And trac improves at an amazing rate.

By: Neil Mitchell

Neil Mitchell — Tue, 24 Oct 2006 11:08:08 +0000

Use Google Code for bug tracking, Google Pages for websites and downloads, and keep the darcs repo’s whereever you have them now.

By: Jan Hudec

Jan Hudec — Tue, 24 Oct 2006 08:25:13 +0000

Also it’s not really necessary to have one trac instance for each project. http://trac-hacks.org is a trac hosts many trac plugins in a single instance. Each plugin only gets it’s own component. For small projects it would be a reasonable way.

By: Jan Hudec

Jan Hudec — Tue, 24 Oct 2006 08:20:53 +0000

There are tons of plugins for trac. As far as I recall, one of them is somewhat sane download manager.

By: Eric Kow

Eric Kow — Tue, 24 Oct 2006 05:46:39 +0000

Re: the bugtracker on trac, I use the RSS feeds for the timeline to aggregrate all incoming wiki/bugtracker/commits. That might make it somewhat less annoying.

Also, it might still be worthwhile to have multiple repos for a single trac instance. Trac will only be able to manage one of them (with the timeline and fancy source browser), but there is nothing stopping you from using the same bugtracker and wiki for them all.