Hacker News new | ask | show | jobs
by the8472 3074 days ago
Well, between and around AGPL and BSD there's a lot of configuration-space left unexplored.

How about an L-AGPL that so that the source of a component must be published without extending to the whole work?

Or maybe one that requires any changes made (patches) must be made available to the public under CC0, even if you only use it internally?

It's a pity that modified licenses are basically treated like plague spots, nobody wants to touch them. This conservationism prevents exploration of alternative development models.

1 comments

> How about an L-AGPL that so that the source of a component must be published without extending to the whole work?

Middle grounds exist though. The MPL is one that I like. It requires copyleft at the file level. However AFAIK it doesn't have the A in AGPL, i.e. it's pretty much like the BSD license if the software is a server application.

It certainly would be nice to have some more options.