kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: FMDF <fmdefrancesco@gmail.com>
To: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Does Linux (Torvald's tree) infringe GPLv2 and contain proprietary binary blobs?
Date: Fri, 11 Mar 2022 04:09:24 +0100	[thread overview]
Message-ID: <CAPj211sn8LmNfCbU=VJbmE=MVEOu=q-nZY9XhXEiJTvimJKS8g@mail.gmail.com> (raw)
In-Reply-To: <CAPj211t_d1u4DYYv19B5FajhAVjTkwP1bkYfAq8HJcD5nVM5Gw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2039 bytes --]

On Fri, 11 Mar 2022, 03:48 FMDF, <fmdefrancesco@gmail.com> wrote:

> Hi Everyone,
>
> Let me explain why I'm posting such an unusual question and why I really
> _NEED_ reliable answers and (above all) reliable links to official
> documents...
>
> In Wikipedia there is an article called "Linux kernel" at
> https://en.wikipedia.org/wiki/Linux_kernel.
>
> According to XTools I'm the first of more than 1500 editors. I'm the one
> who contributed the most. I'm proud of it, despite it still needs lots of
> additional  relevant information and perhaps it also needs the removal of
> other not so relevant and/or redundant info.
>
> It's a "Class B" article (something that has been peer-reviewed by
> thousands of people and considered two grades less than the top Wikipedia's
> articles).
>
> Unfortunately, there have been several attempts to state that Linux is
> _not_ a free and open source kernel and that it contains proprietary binary
> blobs.
>
> I'm asking for help to remove those fake information, mainly sponsored and
> backed by the FSF and by the Linux libre project (or something like that).
>
> Can someone please provide reliable sources that I can use when reverting
> the above-mentioned false information? Unfortunately, I cannot simply
> revert them by just saying that the Linux Community won't ever accept non
> GPLv2 complaint
>

Sorry, "complaint" --> "compliant".

code.
>

> There is a strict rule that says "No original research": mostly everything
> must be supported by links to third party reliable documentation (web,
> books, and so on).
>

It simply means that I cannot tell, for instance, that the Maintainers of
the subsystems I have submitted patches to (first of all, Greg
Kroah-Hartman) won't ever accept unsigned code and/or proprietary binary
blobs, just because any  personal experience with working with the
Community is not considered a  "reliable and authoritative source of
information".

Thanks,

Fabio M. De Francesco

Again, can someone please help?
>
> Thanks,
>
> Fabio M. De Francesco
>

[-- Attachment #1.2: Type: text/html, Size: 3795 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2022-03-11  3:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  2:48 Does Linux (Torvald's tree) infringe GPLv2 and contain proprietary binary blobs? FMDF
2022-03-11  3:09 ` FMDF [this message]
2022-03-11 14:14 ` Konstantin Ryabitsev
2022-03-11 14:24 ` Robert Joslyn

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='CAPj211sn8LmNfCbU=VJbmE=MVEOu=q-nZY9XhXEiJTvimJKS8g@mail.gmail.com' \
    --to=fmdefrancesco@gmail.com \
    --cc=kernelnewbies@kernelnewbies.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).