GPL isn't, but a NDA would require that the documentation, or* Han Boetes [070213 23:00]:
It seems a little lame to write code under a license like the GPL if
you have to sign a NDA to do so. I mean, what takes precedence, and
who decides? Does the Linux Driver Development team lack courage to
demand open documentation for their drivers so that they can release
them properly under the terms of the GPL, or are they actually that
deluded that they think that this can work?
The problems would be similar if one signed a NDA, and then released
code with a BSD license. GPL, however, _requires_ that the code be
shared, and so I imagine it will be more problematic. Seriously,
how do you resolve the dilemma ethically?
Thankfully, there are people like Theo, and the OpenBSD developers,
who see this problem more clearly than most. Keep up the good work,
and fighting the good fight.
In the meantime, I'm going to work on an e-mail to send to Greg
Kroah-Hartman expressing my concerns regarding the Linux Driver
Development team's recent decision.
--
W. Steven Schneider
| Linus Torvalds | Linux 2.6.27-rc5 |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Trent Piepho | Re: [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
git: | |
| Christoph Hellwig | Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2] |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
