I don't truly understand what this says. Possibly it will become
clearer when the legal minds get to work on it.
Possibly community contributions may need to be dual-licensed from
the beginning, so that they're under LGPL, but Traversal is also allowed to
merge them with proprietary Verilog files that go into the ASIC build. Or
maybe LGPL allows both uses of outside contributions as long as the source
files are statically linked but not actually merged; I haven't really
studied LGPL the way I have GPL.
The "community" might be defined as everybody who isn't an employee
or officer of Traversal.
One way of licensing Traversal-created source code that would
satisfy the community would be to issue it from the beginning under an
irrevocable LGPL, but have that license take effect on a specific date far
enough in the future to satisfy the investors. That raises the question of
putting the source code in some sort of escrow so that trade secret
protection is preserved while assuring the community that it will eventually
be published even in case of business failure. What's the rental on a safe
deposit box for 5 years? I could probably foot the bill for that myself.
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
