This week in Ansible Community
Issue #125, 2023-12-18 (Past Issues)
Welcome to The Bullhorn, our newsletter for the Ansible Community. If you have any questions or content you’d like to share, you’re welcome to chat with us in the Ansible Social room on Matrix, and mention newsbot to have your news item tagged for review for the next weekly issue!
KEY DATES 
cybette shared
- 2023-12-20: Community WG meeting, 19:00 UTC
- 2023-12-21: Bullhorn #126 content deadline, 18:00 UTC (last issue for 2023)
- 2024-01-02: DaWGs meeting, 16:00 UTC
- 2024-01-29: ETA for Ansible-Core 2.16.3, 2.15.9, and 2.14.14
- 2024-01-30: ETA for Ansible 9.2.0 release
MAJOR NEW RELEASES 
Ansible-Core 
The ansible-core package contains the base engine and a small subset of modules and plugins. To see what’s planned for the next release, look at the ansible-core roadmaps.
cybette said
PROJECT UPDATES 
Oranod shared
Hi all! As the holiday season grows near I thought it would be nice to give a quick round up of the progress on the Ansible community website.
I think it’s worth starting out by saying that choosing Nikola as the static site generator was a superb choice! The Ansible community voted on it and so far Nikola has exceeded all our expectations. So thanks again to our great community!
As for the site itself we’ve implemented the wireframe for the homepage layout (big thanks to the wonderful Tina Yip for her work), tested extensively for WCAG compliance, migrated a number of blog posts with help from the community writers, and added a number of resource pages. We’ve also added a bunch of CI checks for the website and are building a container image now too.
Please feel free to take a look and create an issue in the website repo or you can reply to this forum post where we have been discussing the website. It shouldn’t be too much longer until you see the change on “ansible.com”!
COLLECTION UPDATES 
mariolenz said
It looks like the inspur.sm collection is effectively unmaintained. According to the current community guidelines for collections, we consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: inspur.sm for more information or to announce that you’re interested in taking over the maintenance of (a fork of)
inspur.sm.At least one month after this announcement appears here and in the collection’s issue tracker, the Ansible Community Steering Committee will vote on whether this collection is considered unmaintained and will be removed, or whether it will be kept. If it will be removed, this will happen earliest in Ansible 11. Please note that you can still manually install the collection with
ansible-galaxy collection install inspur.smeven when it has been removed from Ansible.
resmo contributed
vultr.cloud 1.12.0 has been released with a new object storage module and bugfixes. See the changelog for more details.
PROPOSALS - DISCUSS AND VOTE! 
Oranod contributed
In a previous edition of the Bullhorn I asked for feedback about redirecting the ecosystem page from “docs.ansible.com”. The motivation has been to find the right place for this page to live, a canonical home where users expect to find it.
It seems that the Ansible ecosystem documentation is not the right place. So thanks to the power of community in figuring that out.
The good news is that it seems likely we can move the ecosystem page to the Ansible community website so that it’s available from “ansible.com/ecosystem”. This will give us a lot more flexibility with the content that can go on the page itself - but it also establishes a first-class place for the ecosystem when the new site goes live.
Feel free to take a look at the preview build, comment on the PR, or check out the forum discussion.
gotmax23 shared
The Steering Committee is discussing extending the Ansible 9 release cycle from 6 months to 1 year. See the forum topic for more information, and feel free to chime in! We are especially interested in hearing from collection maintainers.
THAT’S ALL FOR NOW!
Have any questions you’d like to ask, or issues you’d like to see covered? Please ask in #social:ansible.com! See you next time!