[jonknee]

> service companies are hard to scale, and unlikely to grow their value in a short time. This is not what your VCs have in mind, basically.

It depends on your services I suppose, but I don't think it would be especially hard to generate revenue by selling Nginx training and support. A conference, seminars, books, support contracts, etc.

Sadly just having an official company behind it will be enough to get approval to use Nginx in a lot of enterprises--sign a fat support contract so you can cover your ass and not think about it again.

[wildmXranat]

>Sadly just having an official company behind it will be enough to get approval to use Nginx in a lot of enterprises--sign a fat support contract so you can cover your ass and not think about it again.

I foresee that plugin writers and source contributors will slowly creep towards the consulting and support model, while the 'community' or 'core' version users will get scarcer documentation. That's fine by me, but signing that support contract will probably mean paying 2 grand for getting a tailored nginx.conf and an SOW document.

That's a good business opportunity overall, but at what cost to the community ?

[mfjordvald]

There are hardly any source contributors to begin with. Igor is notorious for being very slow to accept patches for anything but simple bug fixes, it's only recently that other people have gotten access to SVN, or that the SVN was even public.

Meanwhile the nginx wiki is completely community run and maintained. The nginx company would cripple itself if it ostracised the community behind it.

[SoupIce]

Almost no cost to the community, this option is far better than MySQL route.