- Commercial Open Source
Must meet requirements of the OSI OSS Definition. Just has a commercial entity behind it that offers support etc.
- FOSS - Free Software
Must meet requirements of the OSI OSS Definition. May have a commercial entity behind it, may not, key is that it is free or can be free
- Community Source
- Developer Source
This DOES NOT meet the OSI OSS Definition. But it sure beats the heck out of commercial proprietary. Examples of this model are Caucho, Some Jive Software products - including their new Clearspace (some of their products are FOSS), and Atlassian. Although I'd prefer FOSS, these are typically very innovative and open companies (e.g., publicly accessible enhancement requests/defects/forums) who take their customers very seriously. Typically customers of these companies are fanatical about using these products. I think that the fact that getting access to the source upon purchase sans escrow account is a big statement - it says that the company is proud of their code and has no problem with you seeing it and extending it as you wish.
- Shared Source
This is a MSFT thing - better than nothing I suppose. I want to be able to see the source.
If it's proprietary it might as well be free.
- Commercial Proprietary + Escrow
If it is proprietary, I might as well have the source in escrow so if you go out of business I am not completely screwed. I hope you included a build script and instructions . . .
- Commercial Proprietary
This is of course my least favorite. As Matt Asay says:
Let us be clear. Whatever the merits of proprietary software, they are purely vendor-favoring. There is no customer reason to make software proprietary. None. There is no customer benefit that attaches to proprietary software. There is only a vendor's ability to temporarily monopolize a piece of software and thereby profit from it.