- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
Re: Why not host new libraries at Lift?
Tue, 2009-09-15, 20:22
I found that the Lift license terms created a barrier to contribution when I discussed them with my lawyers. I suspect other corporate contributors will face objections too. Here's what I heard:
* The apache, bsd, and gpl licenses and contributor agreements are well studied. Less well understood terms need to be studied afresh, which is expensive and invites caution.
* Assignment is harder to swallow than licensing. Assignment doesn't keep all of the contributor's future options open. (to relicense the contribution under different terms to others, perhaps the option to sue license breakers, etc.).
I trust David to do the right thing with the code I assign to worldwide conferencing llc, and I understand the argument that assignment-style contribution may be a better model for the future of open source. But I'd suggest something easier to digest for incubating libraries, probably apache contribution and licensing terms.
Cheers,
Lee
* The apache, bsd, and gpl licenses and contributor agreements are well studied. Less well understood terms need to be studied afresh, which is expensive and invites caution.
* Assignment is harder to swallow than licensing. Assignment doesn't keep all of the contributor's future options open. (to relicense the contribution under different terms to others, perhaps the option to sue license breakers, etc.).
I trust David to do the right thing with the code I assign to worldwide conferencing llc, and I understand the argument that assignment-style contribution may be a better model for the future of open source. But I'd suggest something easier to digest for incubating libraries, probably apache contribution and licensing terms.
Cheers,
Lee
