From: Pavel Roskin <proski@gnu.org>
To: David Planella <david.planella@googlemail.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
johannes@sipsolutions.net, acx100-devel@lists.sourceforge.net,
gregkh@suse.de, greg@kroah.com, xazz.xazz@googlemail.com,
Andreas Mohr <andi@lisas.de>,
andim2@users.sourceforge.net
Subject: Re: The tiacx driver situation
Date: Mon, 04 Aug 2008 17:42:34 -0400 [thread overview]
Message-ID: <1217886154.9182.8.camel@dv> (raw)
In-Reply-To: <1d9d9b240808041147n5032160v252e1bc956c97902@mail.gmail.com>
On Mon, 2008-08-04 at 20:47 +0200, David Planella wrote:
> 3) Remove all public sources and start development from scratch,
> following clean-room procedures.
> This is the view I got from a short conversation with Johannes Berg on
> IRC, and would basically mean removing all sources and references to
> the current acx driver from the public domain and start completely
> from scratch, with two isolated development teams: one writing the
> specs and the other one doing the development separately. Most of you
> probably know this method from [5].
As I understand, the reverse engineering team should be able to use the
existing sources. But the new coding team should not. What matters is
that the new code is not derived from any proprietary code, but only
from the specification.
> I must say I find this the cleanest solution from an engineering and
> legal point of view, but I cannot help but feeling a bit unoptimistic
> about this taking off with the acx driver. There is not much of a
> community left, and all the people currently involved, although not
> many, would also have to leave the project, as they would have been
> "tainted" with the old sources.
That would be the reverse engineering team. But you'll need to find a
"virgin" coder :-)
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2008-08-04 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 18:47 The tiacx driver situation David Planella
2008-08-04 21:42 ` Pavel Roskin [this message]
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=1217886154.9182.8.camel@dv \
--to=proski@gnu.org \
--cc=acx100-devel@lists.sourceforge.net \
--cc=andi@lisas.de \
--cc=andim2@users.sourceforge.net \
--cc=david.planella@googlemail.com \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=xazz.xazz@googlemail.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 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).