The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Clem Cole <clemc@ccc.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] [COFF]  386BSD released
Date: Wed, 14 Jul 2021 13:40:53 -0400	[thread overview]
Message-ID: <YO8hpZ4VYln+QxNb@mit.edu> (raw)
In-Reply-To: <CAC20D2NDPLZQ25GfYq7Yi1XQj9BEJJY0gLQB3nb5Z2bM66wM8A@mail.gmail.com>

On Wed, Jul 14, 2021 at 11:01:58AM -0400, Clem Cole wrote:
> By formal definition, the tarball and the rest of UNIX from Research is and
> always has been, '*Open Source*' in the sources were available.  *But they
> were licensed*.  This was fairly typical of much early software BTW.  The
> binary nature only came about with the minicomputers.

It may have been "Open Source" by your definition, but there is a very
specific definition of "Open Source(tm)" and it has always been, from
the beginning, defined to mean code licensed under terms which meet
the Open Source Definition[1] (OSD).  The AT&T license, for better or
for worse does not mean the terms of the OSD.

[1] https://opensource.org/osd

> The sources in the tarball were not '*Free and Open Source*' -- which
> becomes the crux of the issue.  [Sadly the OSS folks have confused this
> over the years and that important detail is lost].

Hardly.  "Free and Open Source" (FOSS) is a term which developed
*after* the the term "Open Source" was coined and trademarked.  That
term was not created by the "OSS folks", but by people who were trying
the solve a political problem.  The GPL meets the definition of the
Open Source Definition, so GPL-licensed software is "Open Source(tm)".
But Stallman objected to that usage, preferring his terminology "Free
Software" on the grounds that it came first.  So FOSS was a compromise
to keep the FSF partisan happy.

But to take this back to TUHS, sorry, no code which falls under AT&T
License can be called "Open Source(tm)".  If AT&T were still trying to
sell Unix under its original terms including the AT&T Unpublished
Trade Secret "all your student's minds belong to us" license, and
tried to claim that Unix was "Open Source", the Open Source Initiative
could sue AT&T for trademark infringement.

If you must, you could try to claim that AT&T was "Source Available"
--- which is a terminology I've seen some used.  But I think your
assumptions of how easily the AT&T License could be obtained, and how
"anyone who wanted it could get it" may be looking at the past with
rose-colored classes.

Cheers,

					- Ted

  reply	other threads:[~2021-07-14 17:41 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 22:28 [TUHS] " Dave Horsfall
2021-07-14  7:54 ` Michael Kjörling
2021-07-14  8:19   ` Angus Robinson
2021-07-14  8:32     ` Michael Kjörling
2021-07-14  9:07       ` Lars Brinkhoff
2021-07-14 14:09         ` Larry McVoy
2021-07-14 14:54           ` Warner Losh
2021-07-14 15:06             ` Richard Salz
2021-07-14 15:37             ` Steve Nickolas
2021-07-14 10:09       ` Tom Ivar Helbekkmo via TUHS
2021-07-14 10:39         ` arnold
2021-07-14 17:21         ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2021-07-14 17:32           ` Richard Salz
2021-07-14 15:01     ` Clem Cole
2021-07-14 17:40       ` Theodore Y. Ts'o [this message]
2021-07-14 17:50         ` [TUHS] [COFF] " Larry McVoy
2021-07-14 18:28         ` Clem Cole
2021-07-14 11:49   ` [TUHS] " Andy Kosela
2021-07-14 15:48     ` Theodore Y. Ts'o
2021-07-16  1:35   ` Dave Horsfall
2021-07-16  2:33     ` risner
2021-07-16  4:25       ` Theodore Y. Ts'o
2021-07-16  5:51         ` Bakul Shah
2021-07-16 13:00           ` Theodore Y. Ts'o
2021-07-16 13:56             ` Larry McVoy
2021-07-16 14:40               ` Clem Cole
2021-07-16 15:44                 ` Theodore Y. Ts'o
2021-07-16 16:11               ` Bakul Shah
2021-07-16 19:07               ` Kevin Bowling
2021-07-16 20:17                 ` Clem Cole
2021-07-16 20:24                   ` Richard Salz
2021-07-18 13:13                     ` arnold
2021-07-18 13:23                       ` Richard Salz
2021-07-18 13:43                       ` [TUHS] MtXinu calendar (was Re: 386BSD released) Al Kossow
2021-07-18 13:51                         ` Al Kossow
2021-07-18 16:44                         ` Al Kossow
2021-07-18 17:38                           ` John Cowan
2021-07-18 18:35                           ` Bakul Shah
2021-07-19  3:06                             ` Dan Stromberg
2021-07-18 19:00                           ` arnold
2021-07-18 21:48                             ` Deborah Scherrer
2021-07-18 20:06                           ` Lyle Bickley
2021-07-14 21:37 ` [TUHS] 386BSD released Bakul Shah
2021-07-16 21:22 ` Dave Horsfall
2021-07-15  2:21 Douglas McIlroy
2021-07-15 15:07 ` Clem Cole
2021-07-15 19:33   ` [TUHS] [COFF] " Theodore Y. Ts'o
2021-07-15 19:49     ` Adam Thornton
2021-07-15 20:29       ` Andy Kosela
2021-07-16  2:22       ` Theodore Y. Ts'o
2021-07-15 20:30     ` Clem Cole
2021-07-16  1:58       ` Theodore Y. Ts'o
2021-07-16  2:14         ` George Michaelson
2021-07-15 23:02     ` joe mcguckin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YO8hpZ4VYln+QxNb@mit.edu \
    --to=tytso@mit.edu \
    --cc=clemc@ccc.com \
    --cc=coff@tuhs.org \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).