Hi, Many, many people have come out with offers of help for the htdig.org machine. First off, I'd like to thank everyone for the offers--keep in mind that mirroring is also welcome. ;-) This message is long but important. Please read it and comment as appropriate -- it will affect how the project goes forward. IMHO, I think the most logical choice is to have a short-term solution and a longer-term solution. Short-term, we need to buy some time to get a long-term solution in place. If Andrew can continue to keep the server up on his cable line, this obviously entails the fewest disruptions. Short-term, SourceForge has also said they'd host the box itself temporarily. Of course this would require some downtime for getting the box physically to them. For better or worse, my suggestion for a long-term solution is to migrate to SourceForge. A few points: * CVS - this will require people to either checkout the source again or modify their checkout to point to a new directory. This also requires anyone intending to commit to get a SourceForge account and use SSH. * FTP - no problem, ftp.htdig.org is *already* hosted by SourceForge. ;-) * Web - biggest catch here is that they don't have ht://Dig installed and we can't compile code. I've already requested it. I don't know if we could carry over dev.htdig.org, but this is a) Low volume b) IMHO Something we can migrate to www.htdig.org/dev/ * Bug tracking - Can't migrate current tracking system and I don't know about the SF one (e.g. can we follow up via e-mail?) * Mailing lists - We'll have to migrate the lists (again), but archives will be autogenerated. I don't see any big snafus here. But many of these services can be kept "in-house" or branched out at some future point if we decide against SF. -Geoff ------------------------------------ To unsubscribe from the htdig3-dev mailing list, send a message to [EMAIL PROTECTED] You will receive a message to confirm this.
