public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Costa <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: Collaboration Tool Proposal
Date: Thu, 26 Feb 2004 22:03:36 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>


On Feb 26, 2004, at 6:12 PM, Josh Berkus wrote:
>
> Why do we want to replace GBorg?
>
> GBorg was pretty good collab tool technology for 2000.
> Heck, it's still not a bad tool. Unfortunately, since the
> demise of Great Bridge, it's had only one maintainer (for
> whose efforts we are very grateful), meaning
> that little or no progressive development has taken place.
> For example, GBorg still lacks both project and bug search
> features, and based on our community is unlikely to develop
> these things.
>

+1 for me. I think the bug tracking is a must.  I have some experience 
with bugs on php.net
(http://bugs.php.net/) and the excellent platform makes the volunteers 
work much easier.

>
> Why GForge?
>
> GForge runs on PostgreSQL and their team are enthusiastic PG
> users.  Most other collab tools run on other databases and would
>

Again +1, they run PostgreSQL their project is made for postgresql (and 
this is rare in the PHP world) it makes sense to me.
>
>
>
> But I don't want to migrate my project!
>
> See above.  You'd have at least a year to procrastinate about it,
> and may be able to get someone else to do most of the
> migration work for you.
>
I would be glad to help, gforge is a PHP based project so I could try 
something out. I don't think that
we (or better said gborg developers) should be scared about the move. 
It is always a pain to migrate but, if it is worth the effort (and in 
this case
we could all benefit from a more structured system) we have to do it.

The suggestion is to move slowly, so, worth a shoot.

Cheers
David Costa

view thread (62+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Collaboration Tool Proposal
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox