[1476] in Release_7.7_team
forgot to cc release-tem
daemon@ATHENA.MIT.EDU (Alex T Prengel)
Sat Aug 29 14:32:00 1998
To: release-team@MIT.EDU
Cc: alexp@MIT.EDU
Date: Sat, 29 Aug 1998 14:31:56 EDT
From: Alex T Prengel <alexp@MIT.EDU>
------- Forwarded Message
Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po10.MIT.EDU (5.61/4.7) id AA02402; Sat, 29 Aug 98 14:29:09 EDT
Received: from DIT.MIT.EDU by MIT.EDU with SMTP
id AA15788; Sat, 29 Aug 98 14:29:07 EDT
Received: by dit.mit.edu (SMI-8.6/4.7) id OAA17279; Sat, 29 Aug 1998 14:29:04 -0400
Message-Id: <199808291829.OAA17279@dit.mit.edu>
To: Greg Hudson <ghudson@MIT.EDU>
Cc: alexp@MIT.EDU
Subject: Re: [Alex T Prengel] Addendum to Transcript man page
In-Reply-To: Your message of "Sat, 29 Aug 1998 13:31:32 EDT."
<199808291731.NAA07669@anubis.grey17.org>
Date: Sat, 29 Aug 1998 14:29:04 EDT
From: Alex T Prengel <alexp@MIT.EDU>
>If this kind of crap is going to come up every time we have to deal
>with Transcript, then I'm going to junk it for the 8.3 release in
>favor of nenscript or genscript. It's not worth the pain.
Greg,
It's not worth getting all upset about this... I certainly didn't intend
that in my request. Let me explain some background-
A long time ago, when I first started working at MIT, a policy
decision was made by MIT that a summary of some license obligations
relevant to end-users of Third Party software should be put online
"with the software". In 98% of the cases, this meant putting a file
at a locker top level called README.license (subsequently incorporated
into README.athena) that I wrote by extracting relevant parts of the
license- this was (and still is) an explicit part of my job. This may
be ignored by 99.9% of Athena users but it clears us of certain legal
liabilities. The software vendors didn't insist on this and probably
have no idea we are doing it. The MIT legal types did.
In a very few cases where there wasn't a locker (saber/codecenter and
transcript are the only ones that come to mind), it was decided to
tack the wording on to the end of the man page, for want of a better
way to deliver it. This was done for years and it didn't seem to be a
huge problem to anyone.
If you can suggest any better way that I can asssociate a README with
enscript, I'll be glad to do it. We don't need to put it in 20
different places because putting it in one or two for the "primary
apps" constitutes "reasonable efforts" for the legal types. It won't
serve its purpose if it's in some toally obscure directory that a user
would never look in though.
Alex
------- End of Forwarded Message
