Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Grant Taylor via COFF <coff@minnie.tuhs.org>
To: coff@minnie.tuhs.org
Subject: Re: [COFF] [TUHS] 386BSD released
Date: Fri, 16 Jul 2021 12:02:39 -0600	[thread overview]
Message-ID: <0afc6119-2900-1e72-618a-004549234cb2@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <YPDn3XRqRQ4a2UKl@mit.edu>


[-- Attachment #1.1: Type: text/plain, Size: 2858 bytes --]

On 7/15/21 7:58 PM, Theodore Y. Ts'o wrote:
> Requiring physical presence to get patches integrated.... doesn't 
> scale.

I believe I understand the spirit of what you are saying.  However I 
have a question:

Was the need / requirement for your physical presence motivated by (a 
lack of) technology?  Or was it more an interview of you / your team to 
determine if your contributions were desired or not?  I see a huge 
difference behind raw code and the team (trust ability / intentions) 
behind the code.  May people can do work required for a job remotely, 
yet must apply and interview for said job in person.

So, what was the real gate / blocker?  Technology to accept the code? 
Or meeting / getting to know the person / representative of the people 
behind the code?

> ... that is not what most people associate with the term "Open Source" 
> today.

I think this touches on the crux of the issue for me.

Does the ability to see the source code (in and of itself) constitute a 
license to use said source code (or compilations there of)?

My opinion is that no, the ability to see the source code is not the 
same thing as a license to use said source code.  There are many 
examples where visibility of source code and licensing to use it are two 
completely independent things.

There are many freely available programs with licenses to run them which 
do not provide any access to source code.  You probably only need to 
look as far as your Downloads folder for an example of such software / 
licenses.

There are many freely available programs with licenses and source code. 
The Linux kernel is a quintessential example.

There are fewer examples of programs where you can see the source code 
but do not have a license to run said program.  I know that Microsoft 
has made (parts of) Windows source code available to various 
institutions.  I'm confident that there are other examples.

So to me, there are two circles with some overlap between them, forming 
three broad categories that software can fall into.

Closed Source / Open License
Open License / Open Source
Open Source / Closed License

I believe that many people think of "Open Source" as being the middle 
overlap where both the License and the Source are open.  This may be 
accurate more of the time than it is not.  However I think that assuming 
it to /always/ be the case is ... unsafe.

After all, look at the terminology:  Open /Source/.  Emphasis on the 
word "Source" as short for source code.  Nothing about source code in 
and of itself implies a /license/ to use it.  Sure, there is quite 
likely an ability to use the source code (if you have all of it).  But 
the ability to do something does not mean that it's proper or legal, 
much less proper, to do so.



-- 
Grant. . . .
unix || die


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4013 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

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

  parent reply	other threads:[~2021-07-16 18:15 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 [this message]
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
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=0afc6119-2900-1e72-618a-004549234cb2@spamtrap.tnetconsulting.net \
    --to=coff@minnie.tuhs.org \
    --cc=gtaylor@tnetconsulting.net \
    --subject='Re: [COFF] [TUHS] 386BSD released' \
    /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

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).