From: "ibrahim via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] licence question
Date: Sat, 29 Jan 2022 16:43:01 -0500 [thread overview]
Message-ID: <16434925810.eeA3aBF.311885@composer.9fans.topicbox.com> (raw)
In-Reply-To: <8290453C-6FF6-4D5A-B6E0-F603F3C47B33@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
On Saturday, 29 January 2022, at 10:18 PM, Steve Simon wrote:
> Someone doesn’t like GPLs, can we not just accept this and not tell them they are wrong.
And if they wish not to release the source for their work, again that is their decision.
Thanks for your support. I mean it.
I don't get the argumentations here. Everyone was happy that plan9 was relicensed as MIT last year. If no one is allowed to make closed source distributions of plan9 based systems than why were all unhappy with the prior licenses. Years ago plan9 was licensed as GPL. 9front kept licensing with MIT. If you expect everybody to make their products and systems fully open sourced than you should have sticked with the GPL license. I admired the determination of 9front taking this step for years. Now I'm really surprised about some remarks in this thread. BSD or MIT licensed software encourages the use of such software in closed source products. GPL restricts this.
I'm also willing to support those projects with code I thing will be of value for others and giving them also the right to use this code open sourced or closed source as they prefer and allowed by applying the mit licence for my parts.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T3e07bfdf263a83c8-M300d0dce4e0019b8b17fae4a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2063 bytes --]
next prev parent reply other threads:[~2022-01-29 21:43 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
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 [this message]
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=16434925810.eeA3aBF.311885@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).