From: "ibrahim via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] licence question
Date: Sat, 29 Jan 2022 21:18:34 -0500 [thread overview]
Message-ID: <16435091140.eDE43962.999357@composer.9fans.topicbox.com> (raw)
In-Reply-To: <CAP6exYLFLrgDb7TRW+61GbOuCGaFfQuJdd12wBd=krD6cekH2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
On Sunday, 30 January 2022, at 2:45 AM, ron minnich wrote:
> The late jmk and I labored over a period of many months in 2013 to get
Plan 9 out under a BSD license. In the end, the copyright holder at
that time required that we distribute it, via UC Berkeley, under the
GPL. No choice. It was that or nothing. Those negotiations involved
many people, and it almost did not happen at all.
As far as I recall OpenBSD (Theo dR) was interested in BSD licensed compilers at that time and that didn't happen.
On Sunday, 30 January 2022, at 2:45 AM, ron minnich wrote:
> The p9f process was not a relicensing, it was a transfer of ownership
of the code. One condition of the transfer, was that the GPL was
explicitly named as a license we should not use. All agreed that the
MIT license was a good one.
Thanks for this choice and your efforts during those negotiations.
I only read about the expectations from BSD projects which were hoping to get an alternative Compiler for GCC. But that didn't happen at that time.
Thank you for clarifying things sorry if I made wrong assumptions.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T3e07bfdf263a83c8-M7727dcecedf37178853eb7de
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2061 bytes --]
next prev parent reply other threads:[~2022-01-30 2:18 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 22:43 ibrahim via 9fans
2022-01-27 22:48 ` hiro
2022-01-27 23:33 ` ibrahim via 9fans
2022-01-28 0:05 ` hiro
2022-01-28 0:42 ` ibrahim via 9fans
2022-01-28 0:46 ` ori
2022-01-28 1:14 ` ibrahim via 9fans
2022-01-28 3:23 ` Kurt H Maier via 9fans
2022-01-28 12:01 ` ibrahim via 9fans
2022-01-28 21:59 ` hiro
2022-01-29 13:03 ` ibrahim via 9fans
2022-01-29 13:24 ` hiro
2022-01-29 14:08 ` ibrahim via 9fans
2022-01-29 14:59 ` sirjofri
2022-01-29 18:11 ` Grant Defayette
2022-01-29 19:00 ` ibrahim via 9fans
2022-01-29 20:43 ` hiro
2022-01-29 21:32 ` ibrahim via 9fans
2022-01-29 21:42 ` hiro
2022-01-29 22:23 ` ibrahim via 9fans
2022-01-29 23:14 ` sirjofri
2022-01-29 23:27 ` hiro
2022-01-29 23:36 ` ibrahim via 9fans
2022-01-30 0:08 ` hiro
2022-01-30 1:45 ` ron minnich
2022-01-30 2:18 ` ibrahim via 9fans [this message]
2022-01-30 21:00 ` ron minnich
2022-02-01 15:08 ` ibrahim via 9fans
2022-02-01 17:06 ` Dan Cross
2022-01-29 22:14 ` Bakul Shah
2022-01-29 22:40 ` ibrahim via 9fans
2022-02-04 15:30 ` Kent R. Spillner
2022-02-04 16:17 ` Grant Defayette
2022-02-04 16:29 ` ibrahim via 9fans
2022-02-04 21:12 ` sirjofri
2022-02-04 17:48 ` Kurt H Maier via 9fans
2022-02-05 0:08 ` Frank D. Engel, Jr.
2022-02-05 16:47 ` hiro
2022-01-29 14:26 ` David Leimbach via 9fans
2022-02-01 14:12 ` Dan Cross
2022-02-01 22:47 ` hiro
2022-02-02 13:22 ` Wes Kussmaul
2022-02-02 16:25 ` ori
2022-02-02 18:22 ` ron minnich
2022-02-02 19:00 ` ibrahim via 9fans
2022-01-29 16:15 ` Wes Kussmaul
2022-01-29 16:56 ` Bakul Shah
2022-01-29 17:17 ` ori
2022-01-29 18:14 ` ibrahim via 9fans
2022-01-29 18:58 ` cinap_lenrek
2022-01-29 19:23 ` ibrahim via 9fans
2022-01-29 20:48 ` hiro
2022-01-29 21:18 ` Steve Simon
2022-01-29 21:34 ` hiro
2022-01-29 21:43 ` ibrahim via 9fans
2022-01-29 22:44 ` hiro
2022-01-29 23:26 ` ibrahim via 9fans
2022-01-30 7:55 ` tlaronde
2022-01-30 13:44 ` ibrahim via 9fans
2022-01-30 13:56 ` tlaronde
2022-01-28 3:14 ` Lucio De Re
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=16435091140.eDE43962.999357@composer.9fans.topicbox.com \
--to=9fans@9fans.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).