From: "Theodore Y. Ts'o" <firstname.lastname@example.org> To: Clem Cole <email@example.com> Cc: COFF <firstname.lastname@example.org> Subject: Re: [COFF] [TUHS] 386BSD released Date: Mon, 19 Jul 2021 20:55:31 -0400 [thread overview] Message-ID: <YPYfAzeqJJUCemail@example.com> (raw) In-Reply-To: <CAC20D2PqmbVcjSh3eMLCijLby_X=53+_a9rckBuj7OD4+eLQUw@mail.gmail.com> On Mon, Jul 19, 2021 at 04:08:34PM -0400, Clem Cole wrote: > > Your thinking would be reasonable *iff* AT&T had won the case, but the fact > is the ideas (IP) and even the source to the basic UNIX was open and > available. And yet, much is made by the *BSD's that the reason why Linux won and *BSD's lost the battle of mindshare was because of the AT&T lawsuit. The FUD caused by the copyright and the license *did* have an impact. Which is why I believe the Open Source Definition matters, and why it's important that we make a sharp distinction between "Source Available" and "Open Source". The license matters. Just making the code out there, but restricting under various clauses or "you have to be in the club" is not enough.  Or worse, in the case of Audacity, where the new copyright holders attempted to add spyware and then to stay out of trouble in the E.U. tried to restrict usage of the software to people over the age of 18 --- in violation of the GPL and the Open Source Definition. This is why insisting on this distinction is so important, and not letting people try to weasel out of saying, "the source is available but we can jerk you around and possibly add extra conditions, and possibly threaten to sue any competitors" is NOT OK. - Ted _______________________________________________ COFF mailing list COFF@minnie.tuhs.org https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2021-07-20 0:55 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <firstname.lastname@example.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 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 [this message] 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.email@example.com> [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=YPYfAzeqJJUCfirstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --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).