[530] in SIPB bug reports
Re: One more thing....
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Sun May 14 02:40:58 1989
Date: Sun, 14 May 89 02:40:48 EDT
From: Theodore Ts'o <tytso@ATHENA.MIT.EDU>
To: Jonathan I. Kamens <jik@ATHENA.MIT.EDU>
Cc: bug-sipb@ATHENA.MIT.EDU, sipb@ATHENA.MIT.EDU
In-Reply-To: Jonathan I. Kamens's message of Sun, 14 May 89 02:15:27 EDT,
Reply-To: tytso@athena.mit.edu
Date: Sun, 14 May 89 02:15:27 EDT
From: Jonathan I. Kamens <jik@ATHENA.MIT.EDU>
Sender: jik@PIT-MANAGER.MIT.EDU
I have not "started dictating what members can and can not do," give
me a break. It is not I who says that sources that are only readable
to gsipbbin should only be read by gsipbbin people, it is the *fact*
that gsipbbin exists that says this.
Sorry, this is a blatent lie. People in gsipbbin have access to *write*
to the sipb sources. *Everyone* has read access to the sources. Look
at the copyright. It says that anyone can copy these sources. It
doesn't say "shred before reading".
This analogy is flawed in so many ways that I won't bother to list all
of them. However, let me just point out that if I were in charge of
Kerberos and one of my *employees* copied the sources and/or tried to
make a replacement program which "broke [my] inadequate
implementation," I would fire him. How does that analogy strike you?
SIPB does not employ me, and *you* are not my employer. If I find a
copy of xlock on the net on my free time, or write a real one that
doesn't use the xtoolkit, neither you nor SIPB has a right to stop me.
- Ted
