Data analyst @gregsutcliff has some extremely insightful data in his 'Ansible - State of the Community 2023' post: ansible.github.io/community/post… #ansible #opensource
Following up on some of the notes about the decline—as someone who's worked on both sides of the Red Hat fence, I think one big shift is IBM's purchase, and how that affected the community dynamics. Two big things happened (both percolated a while):
1. There was definitely a bit of a shift from the spunky 'get Ansible to do little things and grow into automated all the things' feel from the early days to 'Ansible is an enterprise application. It's not like python/shell scripting anymore.'
(Though it is... sorta) and
(Though it is... sorta) and
2. The shift to collections definitely alienated some users and contributors (and its long-term effects are still playing out).
Good reasons for the shift, but I think it focused a lot more on easing ansible core maintenance and corporate solutions strategy (1/2)
Good reasons for the shift, but I think it focused a lot more on easing ansible core maintenance and corporate solutions strategy (1/2)
And a little less on solving end user problems.
Like I said, good reasons but that shift definitely made the 'pip install ansible, automate a task within 10 minutes' thing less easy to do. That's how I learned Ansible originally. (2/2)
Like I said, good reasons but that shift definitely made the 'pip install ansible, automate a task within 10 minutes' thing less easy to do. That's how I learned Ansible originally. (2/2)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
