14 ms·

No, the problem is the dual-license strategy combined with changing business models. If it had been pure GPL from the start, anyone who couldn't work with that

No, the problem is the dual-license strategy combined with changing business models. If it had been pure GPL from the start, anyone who couldn't work with that would never have used it in the first place. But because they sold licenses for closed source use, now there are customers using it who may be stuck choosing from three unpleasant options--keep using unmaintained code (if the license even allows that), find a way to use GPLed code, or find a new database. It's not really any different from what would happen if a proprietary software vendor went out of business or killed a product, since that's effectively exactly what happened. The fact that the code also exists in GPL form is largely irrelevant and I don't know why you're focusing on it. Without the dual-license strategy available, BSD software doesn't really HAVE an economic model other than charity (nor does pure GPL of course--just look at RMS--but at least GPL gives you the warm feeling of knowing that no one will be purely freeloading off your generosity).

antirez 17y ago
I don't think so. BSD business models: * Services: training, consultancy, ... and MOST important: * Closed source "PRO" versions. This has a number of declinations. For instance only add "enterprise" features in the closed source fork, or alternatively develop an important feature for the closed source fork and release it for the open source one after N months, and so forth. A plugin system can also work: develop a number of closed source plugins about features that are not so general to enter in the real release but that many people think they absolutely need, and sell this plugins. Note that here you are not undervaluing the open source fork as this are stuff that anyway you don't think are so general to be included.
- prodigal_erik 17y ago
  Why did you omit work for hire? New features aren't free software when they haven't been created yet, even if you open them at release.
deleted 17y ago
[deleted]

antirez 17y ago

I don't think so. BSD business models: * Services: training, consultancy, ... and MOST important: * Closed source "PRO" versions. This has a number of declinations. For instance only add "enterprise" features in the closed source fork, or alternatively develop an important feature for the closed source fork and release it for the open source one after N months, and so forth. A plugin system can also work: develop a number of closed source plugins about features that are not so general to enter in the real release but that many people think they absolutely need, and sell this plugins. Note that here you are not undervaluing the open source fork as this are stuff that anyway you don't think are so general to be included.

prodigal_erik 17y ago
Why did you omit work for hire? New features aren't free software when they haven't been created yet, even if you open them at release.

deleted 17y ago

[deleted]