GEustace@massey.ac.nz (Glen Eustace) (05/02/89)
Here at Massey University we are in the process of setting up a large LAN to support PCs and MACs. To date we have a Pyramid 9815 supporting PC-NFS and AUFS. Things appear to be progressing well, however we are concerned about what software we can ethically put on the server. To date we have been installing software for which we have purchased appropriate licensing or which is clearly marked as being in the Public Domain. Our problem is that there is a huge amount of software that is labelled SHAREWARE. We recently received about 150M of PC software from SIMTEL20, there is alot of very good SHAREWARE software included. If we put the software up on the server, are we liable for the registration? or are our users? Many PD software outlets include SHAREWARE software on their disks, bulletin boards etc., and treat it as though it were in the Public Domain. Our user community consists of about 1200 PC users, presently some 25 have been connected to the network. The dilema is that we can supply SHAREWARE to our users on disks and it then become their responsibility to register it. If we put it on the server, it would appear to be our responsibility. We can't afford to register every SHAREWARE package for 1200 users but we believe we have some obligation to our user community to ensure its availablity. I would love to hear what others think about SHAREWARE on LANS and how this problem can be addressed. There must be some solution that is fair to the SHAREWARE Authors, us as the Network Support service and our Users. ----------------------------------------------------------------------- Glen Eustace, Software Mgr, Comp.Cntr, Massey Uni, Palmerston Nth, N.Z. Janet/Greybook: G.Eustace@nz.ac.massey Phone: +64 63 69099 x7440 CSnet/ACSnet/Internet: G.Eustace@massey.ac.nz New Zealand = GMT+12 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
ciriello@lafcol.UUCP (Patrick Ciriello II) (05/04/89)
In article <48@massey.ac.nz>, GEustace@massey.ac.nz (Glen Eustace) writes: > [system descriptio] > > To date we have been installing software for which we have purchased > appropriate licensing or which is clearly marked as being in the > Public Domain. Our problem is that there is a huge amount of software > that is labelled SHAREWARE. > > [stuff deleted] > > I would love to hear what others think about SHAREWARE on LANS and how > this problem can be addressed. There must be some solution that is > fair to the SHAREWARE Authors, us as the Network Support service and > our Users. > ----------------------------------------------------------------------- > Glen Eustace, Software Mgr, Comp.Cntr, Massey Uni, Palmerston Nth, N.Z. > Janet/Greybook: G.Eustace@nz.ac.massey Phone: +64 63 69099 x7440 > CSnet/ACSnet/Internet: G.Eustace@massey.ac.nz New Zealand = GMT+12 A very interesting problem. I would think that, if the users RUN the program off the server, then they are not liable for registering the software. However, if they COPY the software, then that is the same as if you had put it on a disk for them, so the responsibility is completely theirs. This would be the same as if it were commercial software. The licence agreement for a network version is usually 2 or 3 times the cost of a single user licence. However, if the student wants his own copy, then he has to go out and buy it. Perhaps this is an issue that can be resovled quickly and easily by the developers of the SHAREWARE products. In you licnece agreement, include an option for Network licencing ... this way no one get's cheated. Pat ( the DRAGON that is WHITE ) Disclaimer: Let you yes be yes, and your no be no ...... the
ggray@wpi.wpi.edu (Gary Gray) (05/04/89)
In article <48@massey.ac.nz> GEustace@massey.ac.nz (Glen Eustace) writes: >Here at Massey University we are in the process of setting up a large [details of setup omitted] >Many PD software outlets include SHAREWARE software on their disks, >bulletin boards etc., and treat it as though it were in the Public Domain. PD software outlets can distribue shareware, but you still have to pay the owners for it. I have seen several places that "forget" to remind you that you need to pay the author to use the program. However, this distribution of software is quite legal, and is encouraged by shareware authors. >appear to be our responsibility. We can't afford to register every >SHAREWARE package for 1200 users but we believe we have some >obligation to our user community to ensure its availablity. Try to contact the authors/companies that made the shareware. I would be VERY surprised if they didn't have, or would not be willing to create a policy for use on servers. Sharware authors (at least in my experience) are quite flexible, and some, rather unfortunatly, are quite surprised when people actually pay for their product. Tell the authors of your situation, and how many people you estimate would use the software simultaneously. This is usually a good measure of how many copies they would want you to actually purchase. >----------------------------------------------------------------------- >Glen Eustace, Software Mgr, Comp.Cntr, Massey Uni, Palmerston Nth, N.Z. >Janet/Greybook: G.Eustace@nz.ac.massey Phone: +64 63 69099 x7440 >CSnet/ACSnet/Internet: G.Eustace@massey.ac.nz New Zealand = GMT+12 ><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> -- _____________________________________________________________________________ _ | / _ ar \/ ggray@wpi.bitnet | << generic clever and witty saying >> \_| ra / ggray@wpi.wpi.edu |
rmh@apple.com (Rick Holzgrafe) (05/05/89)
In article <48@massey.ac.nz> GEustace@massey.ac.nz (Glen Eustace) writes: > If we put [shareware] > up on the server, are we liable for the registration? or are our users? > > I would love to hear what others think about SHAREWARE on LANS and how > this problem can be addressed. There must be some solution that is > fair to the SHAREWARE Authors, us as the Network Support service and > our Users. I'm a shareware author. In general, the wider the distribution my product gets, the happier I am. If 1200 people on your network have a chance to see my gadget, and one or two percent of them actually buy it, I've made a tidy profit! You should probably group and label your shareware collection, so the users don't assume that it's already site-licensed. A big obvious READ ME file should do it, or a judiciously-named directory or folder. An interesting parallel: Jasmine hard drives come out of the box with a large library of shareware and public domain stuff. I don't know what warnings they send along with it; but a LOT of my shareware income comes from folks who say "I found it on my new Jasmine, and really liked it...". ========================================================================== Rick Holzgrafe | {sun,voder,nsc,mtxinu,dual}!apple!rmh Software Engineer | AppleLink HOLZGRAFE1 rmh@apple.com Apple Computer, Inc. | "All opinions expressed are mine, and do 20525 Mariani Ave. MS: 27-O | not necessarily represent those of my Cupertino, CA 95014 | employer, Apple Computer Inc."
warb@faatcrl.UUCP (Dan Warburton) (05/06/89)
Well, you could contact the Authors and make a deal for a site license. That seems to be the only fair way.
ellisond@gtephx.UUCP (Dell Ellison) (05/12/89)
In article <48@massey.ac.nz>, GEustace@massey.ac.nz (Glen Eustace) writes:
-> ...
-> To date we have been installing software for which we have purchased
-> appropriate licensing or which is clearly marked as being in the
-> Public Domain. Our problem is that there is a huge amount of software
-> that is labelled SHAREWARE.
->
-> We recently received about 150M of PC software from SIMTEL20, there is
-> alot of very good SHAREWARE software included. If we put the software
-> up on the server, are we liable for the registration? or are our users?
->
-> Many PD software outlets include SHAREWARE software on their disks,
-> bulletin boards etc., and treat it as though it were in the Public Domain.
->
-> Our user community consists of about 1200 PC users, presently some 25
-> have been connected to the network. The dilema is that we can supply
-> SHAREWARE to our users on disks and it then become their
-> responsibility to register it. If we put it on the server, it would
-> appear to be our responsibility. We can't afford to register every
-> SHAREWARE package for 1200 users but we believe we have some
-> obligation to our user community to ensure its availablity.
->
-> I would love to hear what others think about SHAREWARE on LANS and how
-> this problem can be addressed. There must be some solution that is
-> fair to the SHAREWARE Authors, us as the Network Support service and
-> our Users.
You don't have to pay for SHAREWARE unless you USE it! You're just
providing it!bergman@m2c.m2c.org (Michael Bergman) (05/12/89)
If I understand you correctly, the problem is that once the software is on your server, it will be available for use by people who won't actually "have" a copy--and are likely to think that you paid for it. Yet you can't afford to register it all yourself. Seems to me you want to make it available in the same way that it is usually available on a BBoard, that is, they can download a copy (or rcp or whatever) but *not* run from the server...so that they have to take possession of the software in order to use it. Is this feasible? I don't know anything about how your system is set up or what its capabilities are. -- --mike bergman (w) 75 North Drive, Westborough, MA 01581, USA +1 (508) 870-0312 UUCP: harvard!m2c!bergman INTERNET: bergman@m2c.org