From: Alex deVries <adevries@thepuffingroup.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HP releasing docs...
Date: Wed, 15 Dec 1999 03:25:31 -0500 [thread overview]
Message-ID: <3857507B.3248918E@thepuffingroup.com> (raw)
In-Reply-To: E11y4LG-0000tV-00@the-village.bc.nu
Alan Cox wrote:
> If
> its carrying on as an open public port and HP are willing to open all
> their document access and like to other folks I dont see a problem.
Having HP opening up documents is probably more difficult than most of
you realize, and in the same way that other hardware vendors can't
release documents on portions of hardware for fear of releasing
competitive information, HP is limited as well. Expecting HP to open up
*all* documentation is unrealistic.
Also, releasing the documentation isn't just pressing the magic button
labelled "Release Publicly" in red. The docs have to be found,
screened, edited, reformatted etc.
Ideally, though, developers will have access to all the hardware they're
porting to.
What's second best is to be able to do development of certain portions
under NDA. This can be used when the docs for the hardware *can't* be
released, or when they're not ready to be released. Advanced viewing
helps out a lot.
The Puffin Group's set up to do this, although we haven't generated any
useable code in this situation yet. Signing such NDAs has helped us
with quite a few other ways though, in terms of planning. The open
source linker would never have happened, for instance.
NDA's aren't quite the evil they're made out to be, having them has
really given us a better insight into how to do parisc-linux.
- Alex
--
Alex deVries
Vice President of Engineering
The Puffin Group
next prev parent reply other threads:[~1999-12-15 8:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-15 1:22 [parisc-linux] Puffin sells out! John David Anglin
1999-12-15 2:39 ` Alan Cox
1999-12-15 7:00 ` Eric Molitor
1999-12-16 5:47 ` Alex deVries
1999-12-19 17:43 ` Philipp Rumpf
1999-12-15 8:25 ` Alex deVries [this message]
1999-12-15 13:17 ` [parisc-linux] HP releasing docs Alan Cox
1999-12-16 23:09 ` Alex deVries
1999-12-19 19:19 ` Eric Molitor
1999-12-19 19:10 ` Alan Cox
1999-12-19 20:16 ` John David Anglin
1999-12-15 8:04 ` [parisc-linux] Puffin sells out! Alex deVries
1999-12-15 16:25 ` John David Anglin
[not found] ` <19991214215358.A31893@thepuffingroup.com>
1999-12-15 18:36 ` Jack Perdue
1999-12-15 20:36 ` Matthew Wilcox
1999-12-15 20:56 ` John David Anglin
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=3857507B.3248918E@thepuffingroup.com \
--to=adevries@thepuffingroup.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@thepuffingroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.