> It looks like Ansible is the tool from the Operations world for Developers and we need a tool that is built by Developers for Operations. That is how we think

> It looks like Ansible is the tool from the Operations world for Developers and we need a tool that is built by Developers for Operations. That is how we think a DevOps tool should feel. This... sounds like it would take the balance in the wrong direction. The idea of DevOps is a working together, and one of the reasons I like Ansible is that it strikes a decent balance between the world of 'hack together shell scripts and get things running' and 'let's build a well architected application'. Anyways, the number of PRs and issues is high, but it's par for the course for any popular open source software. Another community I'm involved in, Drupal, has thousands of open issues/patches, and we have so many longstanding bugs that we have a special name for them—DrupalWTFs. At least with Ansible you can monkey patch if absolutely necessary, and it's mostly possible to override core functionality through modules and roles. The core devs do need to do more work communicating vision, implementing community feedback, etc. Especially since the Red Hat acquisition, it'd be a good gesture to make it clear Ansible itself isn't just a sledgehammer meant to make Red Hat be 'DevOps' hip.