In this post, I’m going to explore some of the community data for the last few years, and show why that suggests that drastic action is needed (and as we now know, that action is Collections).
To some degree, this is just retrospective justification - we are already doing Collections. But I wanted to try and show what trajectory the community was on, if we did nothing. Honestly though, I also wanted to practice some of my forecasting techniques… :)
Time for another post in my showcase of the tooling I’m building for the Ansible community. This time: events! Specifically, Meetup.com events. Read on…
Communities produce huge amounts of work, when motivated to do so, and Ansible
is no exception - and as Ansible’s community is huge, so is the volume of
content! Let’s take a look at the Ansible modules contained in
/lib/ansible/modules
and try to see how we can view the community output.
Last month I was at the lovely EdinbR meetup to present my guide to self-hosting the amazing Shiny server. Some kind folks have been asking for the notes so that they can do it themselves, which seems fair, so here it is!
The Why Let’s start with my slides before we get to the how-to. There are fantastic resources for hosting Shiny out there, so why would you roll your own?
In this post, I take a look at how people contribute to Ansible Modules, through the lens of how that might help us with Collections.
Welcome! This is the first part of a series of blogs I’m going to write, about the Ansible community and the work we’re doing to help improve it through appropriate use of data.
Some thoughts on Twitter, Mastodon, work, and the future….