From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: reference to Linux Foundation NDA program obsolete?
Date: Sun, 24 May 2020 07:33:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2005240722560.5201@felia> (raw)
Hi Jonathan,
while reading the process documentation, I noticed this reference to the
Linux Foundation NDA program in Documentation/process/3.Early-stage.rst:
-->
That said, there are also cases where a company legitimately cannot
disclose its plans early in the development process. Companies with
experienced kernel developers may choose to proceed in an open-loop manner
on the assumption that they will be able to avoid serious integration
problems later. For companies without that sort of in-house expertise,
the best option is often to hire an outside developer to review the plans
undera non-disclosure agreement. The Linux Foundation operates an NDA
program designed to help with this sort of situation; more information can
be found at:
http://www.linuxfoundation.org/en/NDA_program
This kind of review is often enough to avoid serious problems later on
without requiring public disclosure of the project.
<--
The link is dead; internet search only showed some references from
meeting minutes in 2008, but nothing more since then.
Has this LF NDA program simply been phased out?
If so, I will provide a clean-up patch to remove this historic reference.
Lukas
next reply other threads:[~2020-05-24 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 5:33 Lukas Bulwahn [this message]
2020-05-25 15:41 ` reference to Linux Foundation NDA program obsolete? Jonathan Corbet
2020-05-25 17:46 ` Lukas Bulwahn
2020-06-03 20:33 ` Jonathan Corbet
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=alpine.DEB.2.21.2005240722560.5201@felia \
--to=lukas.bulwahn@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).