It's not only viable, it's often required.  Many software programs eventually fade out of existence and organizations move to another.  Otherwise I'd still be supporting a Netware 2.2 network running DOS clients with WordPerfect and Lotus 123.  There are still quite a few DNN 3.x sites out there.  Even more that have grown individually from the I Buy Spy code.  And even if 4.92 was the last DNN version available publicly, you'd still have the full source and several years before you had to change.

Jeff

I think I'm feeling a bit better about this.

I was a bit worried after reading Joe's post initially as the word SugarCRM scared me. But after reviewing the other three products Joe mentioned I can maybe see some light at the end of the tunnel. I guess it all depends on which business model DNN chooses. If they go the Alfreso/Liferay route where the Pro/Enterprise versions are the same as the community version but with support added I think we will all benefit.  However, if they go the SugarCRM/Hypric route where the community editions have roughly half the features of the Pro/Enterprise editions we're doomed.

All indications seem to point to DNN choosing the Alfreso/Liferay type business model which I think is a very smart choice. If you look at SugarCRM where the forks (Vtiger is a fork of Sugar) that popped up after their business model choice are consistantly gaining market share I'd have to think that Sugar's user base is eroding rather than growing. While a large user base doesn't automatically equate to profits if you look at some of the products mentioned in Jeff's post having a very small or eroding user base does generally equate to extinction.

Greg

Jumping into the future and assuming our worst DNN fear gets real where the pro version gets updated and supported while the community one rusts. What if some volunteers decide to fork the community version and decide to update it on their own, is this "legal" and permitted? Assuming they use a different name.