[Xorp-hackers] valgrind: selector.cc: Reading free'd memory

J.T. Conklin jtc at acorntoolworks.com
Wed Sep 30 18:17:48 PDT 2009


Hi Ben, Bruce,

Ben Greear <greearb at candelatech.com> writes:
> On 09/30/2009 01:51 PM, Bruce Simpson wrote:
>> As far as I know, not all of the code in the corporate branch is under
>> the GPL, some of it is subject to NDA -- so no, not all of that source
>> would be publicly visible.
>
> Well, anything that links with any of the (external SVN) code in
> Xorp becomes GPL.  They may have a private copy of some XRL logic
> that allows them to link proprietary protocols, I suppose...
>
> They would NOT be allowed to pull changes from the external SVN tree
> into their internal tree and not treat that code as GPL.
>
> That said, the GPL only takes affect when you sell/distribute the
> source outside your domain..so until they ship something, they are
> not in any violation regardless of other issues.

My understanding is that XORP Inc. holds the copyright of (most of)
the code in their corporate repo, which enabled the change of license
terms from BSD to GPL in the first place. In theory, this allows them
the flexibility to release their commercial product under a different,
non-GPL, license.

However, there are no copyright assignment or copyright disclaimer
required for community enhancements or bug fixes (as there is for
FSF/GNU projects).  IANAL, but I believe copyright of those would be
considered retained by author/contributor, with implied distribution
rights granted under the GPL.  So I would tend to agree that changes
taken from the community SVN repo going forward would remove any
flexibility to distribute the corporate product under non-GPL terms.

    --jtc

-- 
J.T. Conklin



More information about the Xorp-hackers mailing list