QuakeDev.com downtime and request for archival

[Error]

[motorsep]

[Error]

[goldenboy]

[leileilol]

[motorsep]

[frag.machine]

[leileilol]

[apolluwn]

I would be willing to take over the web/svn( or mercurial / git [if requested instead] ) hosting.

It appears that this is a fairly low bandwidth site, but, if not, you can provide me with anticipated usage (typical 95th). I doubt it will be a problem, however.

The move would be to either a dual opteron located in Dallas, TX, or a pentium d in Toronto, ON. Both are running FreeBSD with 100mbit links and are running most of the software on the quakedev server [except webmail software, phpmyadmin, awstats on the opteron].

We have additional servers scattered around in europe and russia, as well, but they would require remote hands in the case of disaster so I'd rather stick with NA ones.

Judging from the server specs on quakedev.com, the hardware and resources available on either of these servers should be quite adequate.

The site would continue to operate exactly as it does now. Dead, dying, whatever, I think plenty of solutions have been offered (edit) in the way of archiving what currently exists.

I'd like to keep as much of it intact as possible and would accept any new requests for hosting with the same terms. This would be done for free, as it is now, but I'd certainly graciously accept any donations by anyone generous enough to help cover some of the costs from time to time.

The servers certainly aren't going anywhere, but every little bit helps.

If anyone who can make a decision regarding this issue believes that this is a route they would like to take then I'd be more than happy to help.

I've certainly taken my fair share from the community, and would hate to see another quake site disappear into the void.

If anyone is interested, you can contact me at john(nospam)seventhsin.net, or my associate at brian(nospam)seventhsin.net and we can work out the details of the migration ( website transfers, database dumps, expected services [ftp access, shell access, mail, etc], or any other software that I'm unaware of).

It would also be worth discussing a solution for the actual domain... Which would be either transferring the domain, or just using our nameservers (although this isn't ideal for obvious reasons).

Regards,
John

[Entar]

[apolluwn]

Well, as for my offer, I haven't been contacted by anyone at this point...

I don't know if this was the most appropriate place to initiate contact, but it seemed the quakedev.com forums were relatively silent regarding the issue when I originally posted and, honestly, it seemed to be more of an issue here (probably because of the activity) rather than there...

After considering that, it did seem it was more appropriate to address it here, where it was being actively discussed, rather than contacting anyone individually since it really is up to those with the data and access to make the decision. This is certainly an issue that those with access should discuss amongst themselves as there may be a fair bit of work involved depending on how a migration would be handled.

I wouldn't want anyone to put work in that they felt has been addressed by other methods, or that they feel just isn't worth the effort since the main sites seem to be archived at this point.

[Baker]

[apolluwn]

[Error]

[apolluwn]