public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Stan Shebs <shebs@apple.com>
Cc: xconq7 <xconq7@sources.redhat.com>
Subject: Re: New Home for Xconq Project?
Date: Fri, 12 Nov 2004 17:37:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0411121213400.28513-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <4194473D.7060300@apple.com>

Hi Stan,

Thanks for weighing in.

On Thu, 11 Nov 2004, Stan Shebs wrote:
> >   Over the past few months I have had some discussions with various 
> > people about whether the Xconq project should be moved to a new host. 
> 
> It's certainly worth a serious look. The main advantage of the RH
> sources site is that it's managed by professionals who immediately
> have people all over them if things stop working; it's the same
> machine as hosts GCC, and you can imagine the urgency when the GCC
> sources are no longer available. 

I seem to recall that one of the outages was for more than 10 
hours. Presumably this was hardware-related, but it raises 
questions about clustering, redundancy, and whatnot....

>Many sites with that level of
> activity wish they only went down twice in a year!

This is true.

> I'm not really up-to-date on the alternate hosting options though.
> Sourceforge was pretty abysmal when I tried to check out a project
> some months ago; most cvs updates simply failed to complete and timed
> out. 

Good to note.

>Savannah used to have a problem with its admins disappearing
> without telling anybody, dunno if that's gotten better. They also
> tend to be more ideological about freeness, although I don't think
> that's an issue for any part of Xconq.

Yeah. They also had a significant security breach back near the 
end of last year, IIRC. The only reason why I might favor them is 
that their set of tools is more familiar to me. Sourceforge (which 
I investigated a few nights ago) does things differently (which 
does not imply that their way is inferior): their trackers and 
file release system, to name a couple of examples.

However, Sourceforge is at least an order of magnitude larger 
than Savannah, I think.

I will see about putting my development branch of the Xconq 
sources on Sourceforge in the way of making a trial of it. If 
things go well, then we could move the Xconq mainline branch 
there at a later point, if we wanted to.

  Thanks,
    Eric

  reply	other threads:[~2004-11-12 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 15:54 Eric McDonald
2004-11-11  2:11 ` D. Cooper Stevenson
2004-11-11  3:42   ` Elijah Meeks
2004-11-12 17:28 ` Stan Shebs
2004-11-12 17:37   ` Eric McDonald [this message]
2004-11-13  1:19     ` D. Cooper Stevenson
2004-11-13 22:52       ` Eric McDonald

Reply instructions:

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

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

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.44.0411121213400.28513-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=shebs@apple.com \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).