Hi all,
Following on from the Ansible Community Roadmap 2026 post, I’d like to share an update on some progress.
We’ve been organizing our work in a Red Hat Jira board and have defined work items from the roadmap as epics. There is still a bunch of work to fill those epics out and get all the tasks fully defined. However that’s not stopping us from digging in and getting started.
Our approach is going to be identifying a single epic as “critical” priority and then making that epic the focus of our sprints, which start and end on Thursdays and run for two weeks. We’ve just started sprint 12. Here is a screengrab:
As you can see @Andersson007 will be leading the effort to establish an AI policy. There’s already some discussion happening in Ansible AI Policy?
In this current sprint @Andersson007 @dbrennand and I are going to do some research on the Fedora AI policy as well as the pip-tools policy that @webknjaz shared in that thread. We’ll be sharing some updates about all that here in the forum shortly.
I also wanted to point out that @dbrennand will drive the effort around a unified strategy for collection testing. In this sprint he’s going to be getting up to speed on a few bits. He’s still new to Red Hat (just finished NHO!) but brings a ton of expertise and skill that will be invaluable to help establish a single, authoritative collection testing strategy as discussed at CfgMgmtCamp. I’m genuinely excited to see what Daniel is going to do here.
That’s it for now. Questions and comments are welcome. We’ll continue to keep folks up to date.
Minor footnote: I’d like to remind that the work items and updates I’ve shared here represent only a portion of the work that the Community and Partner Engineering team at Red Hat are doing. This is work that @Andersson007 @dbrennand and I are focusing on, as a dedicated group within the wider team, from our conversations at Contributor Summit in Ghent. Cheers!