3 ms·
Scaring away those companies might be a plus, especially in this case.
by gojomo 13y ago
Scaring away those companies might be a plus, especially in this case.
- viraptor 13y agoIt's not that simple unfortunately. Here's an example of what could happen: A is under the shit licence, B depends on A, lots of people use B. Among those people is a big corporation, which needs their licences verified and they decide the shit licence is not acceptable. They'll talk to B about making A optional, replacing it, of will create an internal fork of it. If there's a business case for it, it will happen. And no one else gains anything from those solutions. If you use a known licence at least there's a chance that those companies will at some point contribute back instead of sitting on their internal patches. I'm in that situation now with a couple of projects, but I have to patch them locally only. I will not spend days with legal to approve a licence, sign a contributor agreement, or some other form of ownership transfer. Both the project and its users lose that way.
- plorkyeran 13y agoLawyers contacting you to ask if you're willing to relicense would be an amusing way for it to backfire, though.