| |||||||||||||
Akademy: Defensive publicationsAkademy: Defensive publicationsPosted Jul 9, 2012 16:42 UTC (Mon) by k3ninho (subscriber, #50375)In reply to: Akademy: Defensive publications by armijn Parent article: Akademy: Defensive publications
> ... [W]e believe it would be best if the "inventors" (the kernel developers who came up with the ideas) would be the best person to write and submit defensive publication.
But you'll take a description of what the code actually *does*, with a reference to the git commits which brought it into the public knowledge space, as a good second-class documentation of 'we had this problem, we solved it in this way; it enables features X, Y and Z', right?
K3n.
(Log in to post comments)
Akademy: Defensive publications Posted Jul 11, 2012 11:12 UTC (Wed) by armijn (subscriber, #3653) [Link]
As long as the main document describes all the ideas and the references are just that (references to more information, but not needed to understand the "innovation"): absolutely.
|
|||||||||||||