[EMAIL PROTECTED] wrote: > We could look at > > o Upgrading Taz. RAID disks, more memory, faster CPUs, whatever.
This would work, but wouldn't do much for redundancy. Having said that, we might get more bang for buck if we didn't get a whole new box. > o Partitioning the load. Taz is handling a lot of stuff; perhaps > moving all of the Apache XML stuff (CVS, web server, mailing lists) > to their own machine would make sense. Or it could be split > based on function rather than project, with CVS, mail and web > serving on separate machines, but with each handling all of the > projects. > > o Some way of running local CVSs that mirror the main one on Taz. I like the mirroring idea -- sitting here in the UK access to the repository doesn't seem too slow, but it's a bit of a waste using transatlantic bandwidth when I don't need to. We have, for example, apache.org.uk (and plenty of other European mirrors of the main apache site). How does the Apache funding setup work? Do you have a budget, or rely on donations, or what? What's Taz's spec at the moment? Is there a web page I should be reading this stuff from instead of randomly posting to this list? ;) Unfortunately I can't offer to donate company bandwidth by running a mirror, but having just left academia I would have thought there'd be volunteers in the student community. Cheers, Mike.
