home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!spool.mu.edu!sdd.hp.com!uakari.primate.wisc.edu!ames!data.nas.nasa.gov!taligent!apple!motcsd!xhost92.csd.mot.com!ajv
- From: ajv@xhost92.csd.mot.com
- Newsgroups: gnu.misc.discuss
- Subject: Re: AT&T USL vs. BSDI/UCB, Mach3, OSF/1, GNU HURD, Linux
- Message-ID: <7100@motcsd.csd.mot.com>
- Date: 14 Sep 92 20:18:48 GMT
- References: <PCG.92Sep5151041@aberdb.aber.ac.uk> <BuG1v1.E5o@ddsw1.mcs.com> <PREECE.92Sep14004723@predator.urbana.mcd.mot.com>
- Sender: usenet@motcsd.csd.mot.com
- Distribution: gnu
- Lines: 20
-
- preece@urbana.mcd.mot.com (Scott E. Preece) writes:
-
- >I would be really surprised if the people who worked on BSD weren't
- >working under agreements with the University of California that
- >transferred the copyright on the work they did -- certainly when I
- >worked as a student for a college (we're not talking homework here,
- >we're talking about work done for pay) it was under that kind of
- >agreement.
-
- In California at least, there are interesting restrictions on how
- software can become the property of someone other than the writer.
- In particular, they have to have paid you AND provided a certain
- level of benefits--health insurance and so forth. Otherwise, the
- software remains the creator's property. When we wrote a simulation
- environment for UC Santa Cruz, we were notified by the Univeristy
- towards the end of the project that we (the team) were the joint owners
- of the software.
-
- Andy Valencia
- ajv@csd.mot.com
-