On Monday 22 August 2005 18:56, Jack Carroll wrote: > 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.
Is there any reason why we would want to permit linking the software model with proprietary software? I don't see why it shouldn't just be the GPL rather than the LGPL... > The "community" might be defined as everybody who isn't an employee > or officer of Traversal. Well, I don't really see the problem. If you create a fork of the code and publish it under the GPL, then you're a publisher of open source software, and thus by definition member of the open source community. Lourens
pgpWStr6fWfje.pgp
Description: PGP signature
_______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
