@scottalanmiller said in Opinions: Ansible vs. SaltStack:
@pmoncho said in Opinions: Ansible vs. SaltStack:
@scottalanmiller
What would be the sense of purchasing a solid open source project like SaltStack?
Being OS, VMware can add their own developers to the project and still integrate it with their products without the cost of purchasing the company.
Control of commits is the primary one. Marketing is the second.  And often, but it depends on the project, ability to have a closed source copy used somewhere.
As a software company, it's super common that you maintain a closed source secondary license so that you, as the owners, are not bound to the open source limitations or requirements that other people are.   No idea if VMware is going to do this, or if they can (there are licensing factors in the past that determine this), but it's a possible reason.
This was my original thought of why but then I figured, if they want to close source it, someone could just fork the latest version and then most will then migrate to the open source version.
Fifth, keeping it from falling into someone else's control.  Remember IBM did this with Ansible, too.  So there is a trend.
Makes sense.  I guess the last thing one would want is for a competitor to buy a product deeply ingrained in your own software.
And sixth... revenue. SS brings in money, and you can make way more money as the actual project than as someone who just supports a project. If the later worked just as well, I'd make as much money as IBM does supporting Linux, but owning Red Hat gives them a slight edge 
I didn't think there would be much SS revenue from a product like SaltStack or similar apps.  Apparently I don't see all the power of SaltStack itself.