MinuteElectron wrote: > Perhaps if you combined your resources into one toolserver all users > would be able to share these CPU cycles, rather than users having to > decide whether to use the one with more human resource tools (i.e. JIRA, > FishEye etc.) or one with more availability. That way users can get the > best of both worlds. > > MinuteElectron. >
That's probably rather impractical, in both technical and possibly legal terms (German copyright law and Polish copyright law?), and of course we have the issue of ultimate ownership of each server here... Hemlock is heavily overloaded - allowing local servers to exist for various purposes is a Good Thing, seeing as they prevent this load from being on hemlock. For the record, I fully support any local toolservers which are responsibly administered, and would support the use of subdomains under toolserver.org to help these. A storm seems to have been brewed in a teacup over this issue.... giving the subdomain does nobody any harm.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Toolserver-l mailing list [email protected] http://lists.wikimedia.org/mailman/listinfo/toolserver-l
