On Thu, 7 May 2015, Dave Taht wrote:
I am going to butt out of this until I get a legal opinion on commit:
5734509c0545ebd95a5b8e3f22a911c1a39ffa1b
This will take a few days.
In the interim, I am satisfied that I understand the terms under which
any future work I may perform in quagga will be under.
Glad to hear it helped clarify things for you. I'd be interested in the
outcome of the above, so far as you can share.
For the convenience of others, the commit Dave is talking about is:
http://git.savannah.gnu.org/cgit/quagga.git/commit/?id=5734509c0545ebd95a5b8e3f22a911c1a39ffa1b
Which imported the quagga-babeld code (fully attributed, as per the
original sources - which I think is clear to anyone viewing the commit
either via the above URL or via gitk). With the following commit message
(referring to the work done in the import - not the code; for me, Quagga
commit messages *always* refer to the work of the commit, not the code,
even if those tend to be same in description/author for many of the more
run-of-the-mill commits):
author Paul Jakma <[email protected]> 2011-12-25 16:52:09 (GMT)
committer Paul Jakma <[email protected]> 2012-03-25 16:06:51 (GMT)
babeld: Initial import, for Babel routing protocol.
* Initial import of the Babel routing protocol, ported to Quagga.
* LICENCE: Update the original LICENCE file to include all known potentially
applicable copyright claims. Ask that any future contributors to babeld/
grant MIT/X11 licence to their work.
* *.{c,h}: Add GPL headers, in according with the SFLC guidance on
dealing with potentially mixed GPL/other licensed work, at:
https://www.softwarefreedom.org/resources/2007/gpl-non-gpl-collaboration.html
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
"The human brain is like an enormous fish -- it is flat and slimy and
has gills through which it can see."
-- Monty Python
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
