The Developer (GrokOpen - Colin Charles) Your popular OSS project gets corporate-backing & widespread community adoption. You create an enterprise supported version as it's easier to sell an "enterprise spin-off with support" that is better than the currently "stable" community edition. It flourishes as the money starts rolling in. Is one version better than the other? The community gets annoyed but you need resources to keep the releases coming and the code maintained. Just because it’s open source doesn’t mean it’s free. Forking happens. Rewind. What works? What doesn’t work? How do you manage the split personality nature well to keep management as well as the community happy. Learn from other successful models as well as the many failed experiments.