FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

The lyris server on franklin goes incommunicado on a regular basis.  What
I do like about lyris though is I can respond via web in a pinch.

I use sourceforge for my other projects, and am generally satisfied with
it.  Using ssh to check in stuff is a pain, but overall it's pretty solid
and offers a pretty complete package.  Right now we have web hosting, list
hosting, cvs repository, and bug tracking (if it still worked), at 4
different sites.

Not to slight those folks that have donated resources, but I hate bugging
internetcds for new cvs accounts all the time.  They're doing it out of
kindness, but it's not their main focus.

The web hosting would stay with siscom.net since they donated the
domain, and they've been really good...and besides freetds.org is much
cooler than freetds.sourceforge.net ;-)

Brian

On Wed, 25 Jul 2001, Steve Langasek wrote:

> Brian,
> 
> On Wed, 25 Jul 2001, Brian Bruns wrote:
> 
> > This has come up in the past.  With iBiblio's persistant lyris problems
> > and LinuxCare no longer offering bug tracking, I had considered moving
> > some or all of FreeTDS to SourceForge or a similiar service.
> 
> > What does everyone think?
> 
> What persistent problems is iBiblio having?  I guess iBiblio hasn't held my
> attention very much lately given that everything under the sun has binary
> packages available now.
> 
> One advantage I see to putting FreeTDS on SourceForge is that there'll
> probably be fewer CVS problems to contend with.
> 
> Steve Langasek
> postmodern programmer
>