The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jay Logue via TUHS <>
To: Clem Cole <>,
Subject: [TUHS] Re: Thoughts on Licenses
Date: Sun, 3 Jul 2022 14:38:46 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 2532 bytes --]

I think it makes sense to place standalone documents like the Caldera 
license in a central location.  However I don't see a lot of value in 
placing copies of non-standalone license/copyright notices in a place 
other than their original locations, because all these texts have 
context ("/This /software is copyright ...."), which I think is 
important both historically and practically.

Perhaps it would be better to create an index of license/copyright 
notices that appear in the source tree, including pointers to their 
containing files. Extra points for an historical analysis of the 
evolution/commonality of license texts as they appear over time and 
across Unix versions.


On 7/2/2022 11:15 AM, Clem Cole wrote:
> As part of some of simh work, I've been immersed in some licensing 
> discussions.  Thanks for the V8-10, Plan-9 and Inferno notes - they 
> are relevant.
> Anyway, WRT to TUHS, I'm thinking that at least in the case of the 
> Unix style bits, I propose a small change to Waren's top-level 
> directory.   Add a new dir called something like 'Legal Docs' or 
> 'Copyrights+Licenses'.   Then move the Caldera document and Warren's 
> current note into that area.  Then add copies of anything we can 
> collect like the Dan Cross's V8-10, anything WRT to Plan9/Inferno or 
> anything we from the UNIX world - such as something Sun, DEC or HP or 
> like might have added.  Maybe add a subdirectory with the AT&T/USL 
> case details.   And maybe add a sub-directory with known FOSS licenses 
> used by the UNIX community and add a copy of the 3-clause BSD and 
> maybe even the two GPLs.
> Then update the README in the current top-level dir.   Adding to the 
> contents something like "/the IP contained on this website is covered 
> by different licenses depending on the specific IP.  Copies of these 
> can be found with the source code itself, but have also been all 
> collected together in the top-level directory: .../."
> I think these all have both historical values, as well as practical 
> values. As I said, I was not sure myself and I think other would be 
> less ignorant if they could find it all easily.   In the case of the 
> practical, a for instance, in an email with some lawyers last week, I 
> had pointed them at the Caldera document.  I'ld have loved to have 
> been able to say look in this directory.  The Caldera and later 
> Nokia Licenses are what we are considering as examples.
> Thoughts?

[-- Attachment #2: Type: text/html, Size: 4273 bytes --]

      parent reply	other threads:[~2022-07-03 21:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 18:15 [TUHS] " Clem Cole
2022-07-02 19:07 ` [TUHS] " Marc Donner
2022-07-02 20:57   ` Warner Losh
2022-07-02 21:02     ` Larry McVoy
2022-07-02 23:54       ` Clem Cole
2022-07-03  2:03         ` Warner Losh
2022-07-03  2:27           ` Larry McVoy
2022-07-03  8:11             ` steve jenkin
     [not found]             ` <>
2022-07-03 14:39               ` Larry McVoy
2022-07-03 14:59                 ` Clem Cole
2022-07-03 15:30                   ` Bakul Shah
2022-07-03 16:26                     ` Clem Cole
2022-07-03 16:55                       ` Kevin Bowling
2022-07-03 17:15                         ` Clem Cole
2022-07-03 17:48                       ` Bakul Shah
2022-07-03 19:48                         ` Clem Cole
2022-07-03 21:23                           ` Matthias Bruestle
2022-07-03 22:40                             ` Clem Cole
2022-07-04  3:01                               ` Norman Wilson
2022-07-04 12:33                             ` Paul Winalski
2022-07-03 21:38 ` Jay Logue via TUHS [this message]

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:

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

  git send-email \ \ \ \ \

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