On 3/15/07, Kingsley Idehen <kide...@openlinksw.com> wrote:
> OK, so ODS is a packaging facility. A platform :-)
OK... I think. I'll just go play with it to more get a better feel for it.
> I'm still not entirely clear on the non-commercial use clause that I > assume is going to be added to the license for VOS. For example, if I > were to build the next Craigslist and offer it's use for free, where > would that fall? It should be no different to using MySQL in this regard.
But MySQL under the GPL does allow commercial use (hence, a.o. all those ISPs using it). It just doesn't allow you to distribute proprietary apps with MySQL. The two angles are entirely different. Again, the Linux kernel serves as an example: you cannot create a derivative proprietary product from the linux kernel since it is GPL. But you are allowed, without any financial or license-auditing strings attached, commercial use of the linux kernel (and MySQL), even when embedded in a GPLed application you intend to exploit commercially (routers with embedded Linux, for example). And with MySQL and Linux you are even allowed to build applications that are both proprietary and intended for commercial use -- as long as it is for in-company use only.
I'd not be using it commercially, but the visitors might be. And what > if I decide it's getting too expensive for me to run out of pocket, > would users be allowed to contribute to the hosting cost? In such a > context, what exactly does "commercial use" mean? > > This might be an interesting case to put before the FSF. At the very > least it'll help to clearly draft the licensing language. This isn't a problem.
I'd say it's at least grey-area material, and I'd not want to put anyone in grey-area situations. Given the scenario above, I would benefit from the users contributing since they would en passant be paying for hosting my own site. Splitting hairs, maybe, but I'm just trying to demonstrate the dilemma I see. Emile
