Computer Old Farts Forum
 help / color / mirror / Atom feed
From: David Arnold <davida@pobox.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: coff@minnie.tuhs.org
Subject: Re: [COFF] [TUHS] 386BSD released
Date: Sun, 18 Jul 2021 13:42:11 +1000	[thread overview]
Message-ID: <57DB6C33-5CE1-4A06-B646-0E5C6707F866@pobox.com> (raw)
In-Reply-To: <b8dc9ac8-c75a-7d4b-dc88-e16f161b1ab7@spamtrap.tnetconsulting.net>




David Arnold
0487 183 494
> On 18 Jul 2021, at 13:30, Grant Taylor via COFF <coff@minnie.tuhs.org> wrote:
> 
> On 7/16/21 10:09 PM, Theodore Y. Ts'o wrote:
>> You can try to argue that it should have a different etymology
> 
> I'm not trying to argue anything.
> 
> If anything, I'm sharing what I think is a different / an alternate understanding.
> 
> I view "open source" (case insensitive) as having two different definitions, much like "hacker" has two almost diametrically opposed definitions depending which community you're in.
> 
> The dualism exists, and I believe that there's nothing that I can do to change that.  So why try?

That horse bolted when the Open Source folks claimed their definition..

“Open” was a widely used term at the time, with Open Systems in particular being a thing complete with history, corporate good will, conferences and magazines and so on.  It was particularly valuable as the respectable corporate face of Unix (vs the feared hairy hacker). 

The attempt to leverage/hijack that to make the hairy hackers’ Free Software corporately palatable has eclipsed the uncapitalized sense of the term.  Very few people distinguish the two, and so your meaning will often be lost. 




d


_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

  reply	other threads:[~2021-07-18  3:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7wtukxtgag.fsf@junk.nocrew.org>
     [not found] ` <CAKH6PiVCjo3YnTZUVYOCDeffQ6POVwGAQA1QMR9UinkfGn+AmQ@mail.gmail.com>
2021-07-15  6:33   ` Michael Kjörling
2021-07-15 20:44     ` Derek Fawcus
2021-07-15 15:07   ` Clem Cole
2021-07-15 19:33     ` 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-16 18:02           ` Grant Taylor via COFF
2021-07-17  4:09             ` Theodore Y. Ts'o
2021-07-17  6:30               ` [COFF] " Tom Ivar Helbekkmo via COFF
2021-07-17 12:37                 ` Theodore Y. Ts'o
2021-07-17 13:30                   ` Tom Ivar Helbekkmo via COFF
2021-07-18  3:29               ` [COFF] [TUHS] " Grant Taylor via COFF
2021-07-18  3:42                 ` David Arnold [this message]
2021-07-18  4:01                   ` Grant Taylor via COFF
2021-07-19 13:41                     ` Theodore Y. Ts'o
2021-07-19 14:50                       ` Clem Cole
2021-07-19 17:38                         ` Theodore Y. Ts'o
2021-07-19 19:33                           ` John P. Linderman
2021-07-19 20:21                             ` Clem Cole
2021-07-20  1:05                             ` Grant Taylor via COFF
2021-07-19 20:08                           ` Clem Cole
2021-07-20  0:55                             ` Theodore Y. Ts'o
2021-07-18  6:44                   ` Andy Kosela
2021-07-16 16:11         ` Jonathan Corbet
2021-07-15 23:02       ` joe mcguckin
     [not found] <alpine.BSF.2.21.9999.2107140824460.15723@aneurin.horsfall.org>
     [not found] ` <213a4c11-3ab2-4b4a-8d6b-b52105a19711@localhost>
     [not found]   ` <CAE49LGn-gY9eikkwUgS+i3p=ZQV+gk_3BJ5V4_6B4HPbdyRuZw@mail.gmail.com>
2021-07-14 15:01     ` Clem Cole
2021-07-14 17:40       ` Theodore Y. Ts'o
2021-07-14 17:50         ` Larry McVoy
2021-07-14 18:28         ` Clem Cole
2021-07-14 20:03         ` John Cowan

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=57DB6C33-5CE1-4A06-B646-0E5C6707F866@pobox.com \
    --to=davida@pobox.com \
    --cc=coff@minnie.tuhs.org \
    --cc=gtaylor@tnetconsulting.net \
    /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).