This thread hits on a number of discussions that have been happening for years- 
rather than trying to recap them here, I wrote a blog post about it: 
http://blog.rolpdog.com/2020/03/why-no-ansible-controller-for-windows.html

On another note: it bothers me that there's perception that Ansible is a "Red 
Hat only" project. It's true that those of us that are paid by Red Hat to work 
on Ansible have to pick and choose carefully where we spend our time, and that 
the concerns of paying customers (including keeping the underlying codebase 
reasonably stable) often take priority over shiny things. At the end of the 
day, Red Hat can't possibly capital-S-support everything, and we have to be 
really careful about large contributions or projects that are potentially 
destabilizing (especially when they involve things we currently have no way to 
test).

One of the major purposes of the move to collections is to get us out of the 
community's way in this regard. Rather than applying overly-harsh filters to 
all contributions in the name of capital-S-supportability and releasing at a 
relatively slow cadence, community-owned collections will be able to apply 
whatever quality rules they like, apply whatever compatibility policies they 
like, and release on whatever schedule they like, while still having a way to 
be part of a "batteries included" community Ansible distribution. For the 
collections that are capital-S-supported by Red Hat, the requirements for 
getting contributions accepted will still remain pretty high, but anyone is 
free to release their own version of that content themselves with whatever 
changes they like, while still enjoying the stability of the core Ansible 
engine itself.

We're also working to further plugin-ify and democratize even more of the 
"guts" of the Ansible engine in future releases. That doesn't directly address 
this case, but a number of others around first-class target support for many 
things that aren't Windows or POSIX, and will also probably knock down a few 
more of the barriers to a hypothetical native-Windows Ansible.

-Matt Davis (@nitzmahone)

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/67dba41d-f27b-40f0-ac3a-b49ccd3f19ad%40googlegroups.com.

Reply via email to