brett.hooker wrote:
"I have invested $5k in building a business website that includes a commercial extension. I have over a years worth of activity in this website, and my entire product catalogue. My 3PD is now scaling down his business and moving into a different line of work because he can't scale his niche solution to a sustainable level on a pure-play GPL model. I can't afford to migrate off my current investment. What do I do?"
I think they're more likely to say "my 3PD says he's scaling down his business and I don't understand why", but that's beside the point. :-)
brett.hooker wrote:
A1) Go to JoomLance to find other developer who will support your site
A2) Work with your 3PD to help them explore alternative revenue models that allow their niche solution to be GPL and commercially sustainable (paid doc, support, upgrades etc).
You'd have to check the proprietary licence terms for A1 to see if that is possible. Probably yes, but you'd need to check.
A2 is a better bet but I can't see many end-users actually doing that. This is where we, the Core Team and the Community, need to put our efforts into educating 3PD's about sustainable GPL-compliant business models. The Core Team is trying as hard as we can to do that, but there are only a few of us and not enough hours in the day.
One solid piece of advice that you can convey is that there is no rush to do anything. All the reputable 3PD's have said that they will continue to support their existing customers even though some may have decided to withdraw from future sales. You might have to pay for that support where previously it might have been free, but I doubt that many commercial end-users will worry too much about that.
I hope that some end-users may learn the lesson I learnt over 2 decades ago; that with proprietary software comes an element of "lock-in" that you need to cost into your future business plan. And that can be far, far higher than the cost of buying a licence. That's the main reason I got into open source development in the first place.
Regards,
Chris.