Glad to you brought this to my attention. My proprietary vs OSS essay promoting hybrids was going to change OSS to shared source to avoid confusion of established OSS definitions. Now, I suddenly find Microsoft has a brand of intiatives called Shared Source. They had to pick the most generic, intuitive thing I could come up with. This will probably cause confusion at some point. (sighs)

Might get away with it but maybe need alternatives. If not "open source" or "shared source," what's a generic phrase for software that includes the source but not necessarily OSS principles.

hybrids are sometimes referred to as "open core projects".

A free software (often copyleft) core with addons, which usually means that contributions to the core are riddled with CLAs or other hurdles, if possible at all.

See mysql, openoffice (pre-Apache), ...

I'll try to remember that. Although, my model allows for entirely proprietary software with source available for review, extension, whatever. Any combo of source availability, freedom, or paid so long as a review is possible. I explained more in this essay:

http://pastebin.com/eRGtedU4

Why not focus on the specific properties you want? Something like "auditable source", which also implies a reproducible build.

Another good one. Thanks.

> If not "open source" or "shared source," what's a generic phrase for software that includes the source but not necessarily OSS principles.

"Published source"?

Appreciate the suggestion.

"transparent source"?

I like the word "transparent" especially as my main application area is countering subversion or fixing problems. Great idea. :)

I like Openly Developed.

Thanks for the suggestion.