🚀 go-pugleaf

Gerben Vos (gerben@cs.vu.nl) wrote:
> Yes, but it would be better if there were more solutions. This can of course
> be solved by having more mirrors of Stuttgart and HENSA, but it is better
> to do it in this way. It will mean less work for you, since you can share
> the maintenance load with others, and duplicate work is avoided.

I think the src.doc-mirror has good download rates for people who come
from outside Germany while German downloaders usually have a good
connection to Stuttgart. Hensa is another problem, however.

The maintenance load is shared anyway: I personally don't care about
uploading communication-stuff (freenet, etc.) because Demon has all
this stuff anyway - and Stuttgart has a Demon-mirror :)

> It also means you give up some control. That shouldn't be a problem, unless
> of course the co-maintainers aren't suited to their task, so there must be
> a way to remove them without making the whole co-operation system going down.

The only way would be to split it up by sections - Demon does the
communication section, another server does grfx&sound, etc.

> An aminet-like solution also scales better if Acorns ever become more popular,
> which we all hope, of course.

One way to distribute the AcorNet would be to use the AFS-structure,
which is not the fastest solution, but is easy to access and saves
much harddisc space!

> A problem may be that HENSA's structure is a bit unsuitable for the purpose,
> since it only works if you have a bunch of search interfaces available, and
> most sites don't have that.

I don't like Hensas structure. You usually only find things if you
exactly know what you are looking for. If you just want to browse
a bit through what's available e.g. in the grfx section, you'll have
to look through all available files.

> I would suggest the ftp.uni-stuttgart.de directory structure or something
> similar as a starting point, and divide the work along directory lines,
> with people specialising in different kinds of programs. But then, i have
> no experience in organising things like this.

OK, that's what I meant above, but it's still a bit clumsy. Some
things may not fit in exactly one section, so there are duplicates. On
the other hand there will always be some people who don't know where
to upload their stuff, so the maintainers will have to move around the
wrong uploaded things. 

The organization would be a difficult point - who is able to
coordinate the whole thing? Two people want to maintain the grfx
stuff - who will decide which one gets the job? One maintainer is a
complete fool - who is *able* to take him away his job? You know, the
Internet is not a democracy, it's an anarchy :)

Bye,
Jochen

--
                      ------------------------------------
                      EMail:   jscharrl@ba-stuttgart.de
                         or:   acorn1@ftp.uni-stuttgart.de
                      ------------------------------------