> o bandwidth > > o ability to carry a complete mirror - e.g about 15G of disk space > to cover every apache project ? plus the daily updates that entails. > > o ability to refresh more than daily - perhaps to implement a ssh > based signalling system similar to that in use by gnome and other > projects, to pull updates when they are in place on the master site > > o ability to act as a propagation server - e.g running rsync for > other downstream mirrors > > o responsiveness of admin contact required to deal with mirror > issues
I'll second all of Jason's points. > > C) Restrict the number of mirrors in each country to say 4 > > 4 might be a bit small, but i guess there might be some policy there. in the > US it might make sense to have 15 mirrors. in australia 6. in Tibet, 2. it > would be a (clearly understood) function of network and demand (number of > internet users) in that region. I think 4 is pretty arbitrary ... how do we keep the 4 best mirrors? I don't think you should have a million mirrors; keep it as several high-quality mirrors ... of course how do you make sure they are high quality?
