Re: [Fab-user] add recipes section to the Fabric web page?

[Jeff Forcier]

On Fri, Oct 17, 2008 at 12:29 PM, Jordi Funollet <address@hidden> wrote:
> Jeff Forcier dixit:
>
> What about Trac with the Git backend? Does it has any problems?
>

I'll outline my research here (been looking into this for a couple
weeks now in my spare time):

* Trac with GitPlugin: pretty darn slow, even with caching turned on.
It's still experimental, buggy, not worked on much, and when I took a
look at the source it was pretty bleh; Trac feels very Java-ish
internally, and certainly not easy to hack.
* Redmine: not bad, much faster than GitPlugin (altho I ran it on
different hardware, both were VMs of one stripe or another, so
probably comparable), has all the basic Trac niceties such as easy
linking between commit messages, commits, tickets and so forth. Decent
interface. Feels less mature than Trac, but that's because, well, it
is. My main issue is that it's Rails and I'd *prefer* not to load up
that whole environment stack on my VPS on top of Django and the other
stuff I've got running there. Not an enormous complaint, of course,
just my preferences at work. (I know both Django and Rails now so I'm
not horribly biased :))
* GitHub + Lighthouse: pretty, but integration probably not as tight
as I'd like in terms of aforementioned links between
commits/tickets/etc. Plus, Lighthouse costs $25 and up for an account
capable of being open to the public, which is obviously necessary
here. GitHub by itself is great for a mirror and decent UI for the
source, and we'll obviously keep hosting a mirror of Fabric there --
but it doesn't do any issue tracking on its own.
* Gitorious: open source, but same as GitHub -- no issue tracking.
* There are a few other source browsers such as cgit, which are nice,
but, again, no issue tracking :(
* There's a django-vcs project that is very new, but should be
relatively easy to get the basic features up and running, and tie it
to django-issues. Both projects are being done by the same group of
people so integration should be pretty easy. Django makes rapid
development easy :)

So, at the end of all that, as I said it comes down to Redmine or a
Django implementation of the same general ideas. Given that Fabric
isn't currently *lacking* anything (NonGNU.org has a ticket tracker
and I think gitweb; and then there's GitHub for nice source browsing)
I personally have no problem waiting a month or so to get
django-vcs/django-issues up to speed, then setting those up on my VPS
and starting to migrate us there.

-Jeff