From: Wesley Parish <wobblygong@gmail.com>
To: Steve Nickolas <usotsuki@buric.co>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] man Macro Package and pdfmark
Date: Wed, 19 Feb 2020 10:29:15 +1300 [thread overview]
Message-ID: <CACNPpeaeeXi_A13Nf0+oB8BHsQau5QTporX7CdhCXf2JTOBjZA@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.02.2002181332010.54311@frieza.hoshinet.org>
IIRC, there was a meeting of various (FOSS) luminaries in the early or
mid-90s discussing rebranding Free Software (as in the FSF definition)
as it was far too easily misinterpreted as meaning
non-/anti-commercial. "Open Systems" had been around forever as a
description of how the Unix "ecosystem" worked - you had a common set
of APIs based on an originally common source base, and a common set of
communication protocols, that worked on a wide array of computer
systems, from real-time to supercomputers to mainframes and beyond.
With all due respect to Clem Cole, I don't recall ever seeing "open
source" used as a description of the Unix "ecosystem" during the 90s.
It was in the air with the (minimal) charges Prentice-Hall charged for
the Minix 0.x and 1.x disks and source; not dissimilar in that sense
to the charges the FSF were charging for their tapes at the time.
But all the Unix-y ads I can recall from the 90s talked about Open
Systems, and never Open Source. That came in following Linux and *BSD
radiation. But this is probably COFF's Harbour stuff ...
Wesley Parish
On 2/19/20, Steve Nickolas <usotsuki@buric.co> wrote:
> On Tue, 18 Feb 2020, Theodore Y. Ts'o wrote:
>
>> On Tue, Feb 18, 2020 at 10:43:06AM -0500, Steve Nickolas wrote:
>>> On Tue, 18 Feb 2020, arnold@skeeve.com wrote:
>>>
>>>> I don't like your use of "open source"; it is way out of skew with
>>>> how it's used today.
>>>
>>> Wasn't it always *intended* to mean the same thing as "Free Software" ?
>>
>> No, although the differences in practice are small. "Free Software"
>> was defined by Stallman as meeting his "Four Freedoms". Open
>> Source(tm) was derived from the Debian Free Software Guidelines, and
>> while the set of licenses which meet the "Free Software" definition
>> and those that meet the "Open Source(tm) definition mostly identical,
>> there are a few exceptions.
>>
>> I refer folks to the Wikipedia entry for more details:
>>
>> https://en.wikipedia.org/wiki/The_Free_Software_Definition
>>
>> It is true that the most of the people who use Open Source instead of
>> Free Software are doing so mostly for branding reasons (e.g., Open
>> Source is considered less likely to scare the suits), but technically
>> they aren't the same. And it is certainly true that way AT&T
>> distributed ditroff certainly isn't compliant with the Open Source
>> Definition (OSD).
>>
>> Whether or not it meets Clem's "open source" (small o, small s),
>> depends on his definition, which appears to be, "functionally, since
>> everyone back then had an AT&T source license, we're all good".
>>
>> - Ted
>>
>
> I always understood "open source" to mean this: you have access to the
> code, you can share it, you can modify it, and any combination of the
> above (including commercial exploitation; basically a restatement of
> Stallman's freedoms in simpler words).
>
> As any phrase gets skewed to mean something other than it was intended,
> when most people say "open source", they seem to only mean what I call
> "source-available" - i.e., that there is *some* means by which a mere
> mortal can gain access to the source, but there is no guarantee that they
> can actually DO anything with the source without getting sued into
> oblivion. I usually say if the code doesn't offer the necessary freedom
> to make use of it. it's not "open source", it's just source.
>
> (For the record: I shifted from the GNU side to the BSD side of the debate
> about 20 years ago. But I hold no ill will toward people on the GNU
> side.)
>
> -uso.
>
next prev parent reply other threads:[~2020-02-18 21:29 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 15:20 Doug McIlroy
2020-02-17 16:47 ` Clem Cole
2020-02-17 18:09 ` Thomas Paulsen
2020-02-17 18:39 ` Jon Steinhart
2020-02-17 21:16 ` Thomas Paulsen
2020-02-17 22:50 ` Thomas Paulsen
2020-02-17 23:22 ` Warner Losh
2020-02-18 0:56 ` Bakul Shah
2020-02-18 3:33 ` Dave Horsfall
2020-02-18 7:27 ` Thomas Paulsen
2020-02-18 0:03 ` Richard Salz
2020-02-18 0:17 ` Jon Steinhart
2020-02-18 0:54 ` Larry McVoy
2020-02-18 1:05 ` Bakul Shah
2020-02-18 7:40 ` Greg A. Woods
2020-02-18 7:45 ` arnold
2020-02-18 20:24 ` Greg A. Woods
2020-02-18 11:22 ` Rich Morin
2020-02-18 12:28 ` arnold
2020-02-18 12:49 ` U'll Be King of the Stars
2020-02-18 13:23 ` arnold
2020-02-18 15:11 ` Clem Cole
2020-02-18 15:28 ` arnold
2020-02-18 15:36 ` Larry McVoy
2020-02-18 15:43 ` Steve Nickolas
2020-02-18 15:52 ` Clem Cole
2020-02-18 16:40 ` Theodore Y. Ts'o
2020-02-18 18:39 ` Steve Nickolas
2020-02-18 21:26 ` Dave Horsfall
2020-02-18 21:29 ` Wesley Parish [this message]
2020-02-19 4:52 ` [TUHS] Open source or free software? (was: man Macro Package and pdfmark) Greg 'groggy' Lehey
2020-02-18 15:48 ` [TUHS] man Macro Package and pdfmark Clem Cole
2020-02-18 16:02 ` Chet Ramey
2020-02-18 16:28 ` Clem Cole
2020-02-18 17:49 ` Thomas Paulsen
2020-02-18 21:46 ` Rich Morin
2020-02-18 16:47 ` Henry Bent
2020-02-18 20:22 ` Greg A. Woods
2020-02-19 4:44 ` Larry McVoy
2020-02-19 18:01 ` Earl Baugh
2020-02-19 18:12 ` Emile Bye
2020-02-19 20:18 ` Michael Huff
2020-02-19 20:34 ` Jon Steinhart
2020-02-19 21:09 ` Henry Bent
2020-02-20 7:27 ` arnold
2020-02-20 7:43 ` Rich Morin
2020-02-20 13:15 ` Dan Cross
2020-02-20 16:23 ` Larry McVoy
2020-02-20 16:34 ` Arthur Krewat
2020-02-20 17:06 ` Al Kossow
2020-02-20 17:24 ` Bakul Shah
2020-02-20 17:48 ` Rich Morin
2020-02-20 20:10 ` Bakul Shah
2020-02-20 20:18 ` Rich Morin
2020-02-20 16:48 ` Nemo
2020-02-20 17:00 ` Larry McVoy
2020-02-20 19:16 ` Dave Horsfall
2020-02-20 23:45 ` Doug McIntyre
2020-02-21 0:18 ` Warner Losh
2020-02-21 1:14 ` Nemo Nusquam
2020-02-21 8:19 ` Thomas Paulsen
2020-02-21 8:17 ` Thomas Paulsen
2020-02-21 10:17 ` arnold
2020-02-21 10:37 ` Ed Bradford
2020-02-21 18:34 ` Heinz Lycklama
2020-02-21 18:59 ` Warner Losh
2020-02-21 21:10 ` Dave Horsfall
2020-02-21 21:46 ` David Barto
2020-02-22 6:48 ` Ed Bradford
2020-02-22 10:42 ` Al Kossow
2020-02-22 11:01 ` Ed Bradford
2020-02-22 16:38 ` Warner Losh
2020-02-22 18:11 ` arnold
2020-02-22 23:41 ` [TUHS] Mini-UNIX Warren Toomey
2020-02-22 11:08 ` [TUHS] man Macro Package and pdfmark Ed Bradford
2020-02-22 16:40 ` Warner Losh
2020-02-22 16:46 ` Clem Cole
2020-02-22 17:51 ` Heinz Lycklama
2020-02-17 18:55 Noel Chiappa
2020-02-17 20:13 ` Clem Cole
2020-02-17 21:06 ` CHARLES KESTER
2020-02-18 0:36 ` Dave Horsfall
2020-02-18 13:13 Don Hopkins
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=CACNPpeaeeXi_A13Nf0+oB8BHsQau5QTporX7CdhCXf2JTOBjZA@mail.gmail.com \
--to=wobblygong@gmail.com \
--cc=tuhs@tuhs.org \
--cc=usotsuki@buric.co \
/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).