🚀 go-pugleaf

I'm sorry if I gave the impression that one might be less than
scrupulous in observing the terms of the contract.

What I was trying to say that a more useable gauge of how much a site
should pay could be based on something more tangible like some function
of the number of machines in the network, the number of registered
users and the level of hand-holding. Maybe even the number of manuals
supplied. (There are ways to make manuals too much hassle to
photocopy.) Just as an example. An honor system is nice of ArborText,
but makes sys admins nervous about whether they are in compliance with
the contract. How is he/she to know how many users on the average use
the software? There are usually more pressing things on the sys admin's
mind than counting users.

I have seen other attempts at dealing with sites with networks.
Waterloo, for example, has a logarithmic scale for Maple licenses.
(Double the number of machines and pay a constant increment.) I don't
know how well this works for them.

Oh well, I suppose as long as ArborText trusts the site.  This has
drifted too far from the subject of this newsgroup anyway. If you want
to comment further, change the newsgroup.

	Ken