[1479] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: [Alex T Prengel] Addendum to Transcript man page

daemon@ATHENA.MIT.EDU (Alex T Prengel)
Mon Aug 31 16:50:44 1998

To: Greg Hudson <ghudson@MIT.EDU>
Cc: alexp@MIT.EDU, release-team@MIT.EDU
In-Reply-To: Your message of "Sat, 29 Aug 1998 17:10:47 EDT."
             <199808292110.RAA07843@anubis.grey17.org> 
Date: Mon, 31 Aug 1998 16:50:37 EDT
From: Alex T Prengel <alexp@MIT.EDU>


>        * First, I would really like to see changes of this nature
>          requested with the release cycle taken into account--that
>          is, requested during the spring if any kind of rapid
>          resolution is important.

That's fine- I didn't do it previously because no one requested this.
If I can just put a text README somewhere, that's fine with me (see below).

>        * I don't understand your explanation referencing "a summary
>          of some license obligations," apparently irrespective of
>          particular pieces of software.  I would think that how we
>          handle Adobe software is only restricted by our license with
>          Adobe

It is- but concerning responsibility for compliance, there are two
components- 1. obligations that MIT (the licensee) has exclusive
control over, and responsibility for, like paying them, granting access
to the software, and lots of other stuff.

2. obligations that MIT end-users inherit, but that are partially or
entirely in their control- things like "reverse engineering" the
software, copying it elsewhere and so on...

End-users don't need to know of things in category 1. but they should be aware
of those in category 2 (at least according to the MIT lawyers, and I agree
with them for the most part), which is the point of "a summary of some 
license obligations".

> I would be surprised to find that our license
>          with Adobe qrequires modifications to their own man pages.

It doesn't! As I tried (perhaps too obscurely) to explain, we decided
this, as a means of getting the message out to users for an application
that wasn't in a locker but comes with a man page. I'd be perfectly happy
to plop it into some directory as an ASCII README, if a suitable directory
exists- that's what I do in lockers (via the README.athena file). 


home help back first fref pref prev next nref lref last post