From: Larry McVoy <lm@mcvoy.com>
To: Warner Losh <imp@bsdimp.com>
Cc: Marc Donner <marc.donner@gmail.com>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Thoughts on Licenses
Date: Sat, 2 Jul 2022 14:02:44 -0700 [thread overview]
Message-ID: <20220702210244.GU11191@mcvoy.com> (raw)
In-Reply-To: <CANCZdfoLquqHT6WYeK_eyk=NMVd-aQX_13yD2DeE-ArwQCibmw@mail.gmail.com>
If I were looking for licenses "Copyrights+Licenses" would make me
find, "metadata" I wouldn't think to look in.
But I'm an old retired dude without many brain cells left.
On Sat, Jul 02, 2022 at 02:57:31PM -0600, Warner Losh wrote:
> Before we go inventing our own thing, let's just add spdx tags and
> metadata..... there already is a standard for this.
>
> Warner
>
> On Sat, Jul 2, 2022, 1:09 PM Marc Donner <marc.donner@gmail.com> wrote:
>
> > I would call that top level directory "metadata" ... the licensing stuff
> > is quite relevant to the owner and operator of the system, but not directly
> > relevant to any of its actual content or function.
> > =====
> > nygeek.net
> > mindthegapdialogs.com/home <https://www.mindthegapdialogs.com/home>
> >
> >
> > On Sat, Jul 2, 2022 at 2:17 PM Clem Cole <clemc@ccc.com> 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?
> >>
> >
--
---
Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2022-07-02 21:03 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 [this message]
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] ` <F579710B-5568-431D-92CC-88D49C3D9BE6@gmail.com>
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
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=20220702210244.GU11191@mcvoy.com \
--to=lm@mcvoy.com \
--cc=imp@bsdimp.com \
--cc=marc.donner@gmail.com \
--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).