First of all: This is a stupid question.<p>Second:<p>The solution is simple, copy a tarball of the source to CD and throw it inside the casing of the missile. Add rocket fuel to compensate for the added weight.<p>EDIT:<p>Third:<p>That was an intentionally stupid answer.
Including a copy of the source with a missile reminds me of the "McDonnell-Douglas Warranty Card" joke that is probably nearly as old as the Internet itself:<p><a href="http://www.cartalk.com/content/mcdonnell-douglas-warranty-card" rel="nofollow">http://www.cartalk.com/content/mcdonnell-douglas-warranty-ca...</a>
The drones the original article talks about aren't missles, they aren't even predators or global hawks. They are the target practice drones the navy shoots with their own missiles for air to air combat exercises.
The GPL only states you have to release the source to people you distribute the code to, not directly make it publicly available. If the missiles work well enough when "delivered", there will be no one left eligible to demand access to the source!<p>Assuming that they are not selling them to someone rather than firing them at someone, of course.
Yes, the internet is good at selecting pedantic people for extended discussions of absurdities. However, this doesn't have much significance for whether GPL-style licensing provisions are preferable in the regular world.
Even if it is, the first sale doctrine would likely apply and so it would not require the permission of the copyright owner.<p>Whether this is the case or not depends on whether or not the Navy is making copies, or just passing along copies they received from a contractor.