# Bullhorn content quality improvement proposals **URL:** \ **Category:** Project Discussions\ **Tags:** cfgmgmgtcamp, community, newsletter, community-wg\ **Created:** [February 11, 2026, 3:20pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321 "2026-02-11T15:20:44Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Sutapa](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sutapa/32/4230_2.png) [@Sutapa](https://forum.ansible.com/u/Sutapa)\ **Post date:** [February 11, 2026, 3:20pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/1 "2026-02-11T15:20:44Z")
Hi, this is a followup from previous discussion at ConfigMgmtCamp. I discussed with @gundalow please let me know if you find this useful. **Proposal: Improving Bullhorn Content Quality** I propose presenting Bullhorn content in a more story-driven format. This would follow a predefined structure using elements like charts, maps, links, infographic, and tables to present information in a clearer and more engaging way. Such a format would make the content easier to understand, more visually appealing, and better suited for sharing on social media. We can experiment on this format and if successful, create a template for future posts. **Execution** To implement this, we would need to design and adopt a structure along with clear usage guidelines. The structure can be shaped with input from Ansible contributors to reflect how they want to consume Bullhorn content. **Benefits** **to** **the Community/** **Audience** This approach would help readers quickly grasp the essence of an event or update. Even non-users could get a concise overview of the topic and its practical impact, which could also support broader promotion and outreach. **Technical benefits for the Ansible ecosystem** • Provides a consistent, structured format for presenting technical updates across Bullhorn editions • Makes release notes, collection updates, deprecations, and roadmap items easier to track and understand. I’ve prepared a full fledged post which shows my experience attending Ansible track in CfgMgmtCamp this year. While the structure can be modified/discussed/tweaked, I hope this will spark some discussion on how we can make the content more useful/appealing. > **[ConfigMgmtCamp and the Ansible Community](https://storymaps.arcgis.com/stories/151449710108465f9a65344d2cf6803b)** > > a community-driven conference where people passionate about DevOps, automation, and open-source infrastructure come together to learn ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [February 12, 2026, 9:21am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/2 "2026-02-12T09:21:36Z")
Hi @Sutapa , Mixed feelings here. Without seeing what exactly the new format is going to look like, it is hard for me to have any opinion on the change. As of the current format, it serves my needs as-is: I get the announcements, not all of them I want/need to know deeply, but I will have seen them and they usually have links to topics in the forum if I want to know more. And of course the news of releases of Ansible (core and ACP) and collections is very welcome. I am struggling to envision what the story-driven format would look like: if it means the same information with more narrative around it, personally I would not be very keen, but TBH I am not sure. Just my $0.02 ---
**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\ **Post date:** [February 12, 2026, 4:29pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/3 "2026-02-12T16:29:58Z")
@Sutapa Thanks for continuing this discussion. I think one thing that might help is copying a recent Bullhorn entry from #News & Announcements > Newsletter and replying to this thread with what it could look like. ---
**Author:** ![Sutapa](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sutapa/32/4230_2.png) [@Sutapa](https://forum.ansible.com/u/Sutapa)\ **Post date:** [February 12, 2026, 5:56pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/4 "2026-02-12T17:56:57Z")
## Major new releases 🏆 | Major release version | New release version | Forum Thread | | --- | --- | --- | | Ansible-core 2.19 | Ansible-core v2.19.6 | [New Release: ansible-core v2.19.6](https://forum.ansible.com/t/new-release-ansible-core-v2-19-6/45216) | | Ansible-core 2.20 | Ansible-core v2.20.2 | [New Release: ansible-core v2.20.2](https://forum.ansible.com/t/new-release-ansible-core-v2-20-2/45217) | | Ansible-core 2.18 | Ansible-core v2.18.13 | [New Release: ansible-core v2.18.13](https://forum.ansible.com/t/new-release-ansible-core-v2-18-13/45215) | | Ansible-core 2.16 | Ansible-core v2.16.16 | [New Release: ansible-core v2.16.16](https://forum.ansible.com/t/new-release-ansible-core-v2-16-16/45214) | ### Ansible Community Package [↗](https://github.com/ansible-collections) The `Ansible` package includes `ansible-core` and is a batteries-included package that provides a curated set of Ansible collections. See the [Ansible roadmaps](https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html) for future release plans. #### Ansible package 13 | Ansible package | command | Release Notes | Ansible 13 Porting Guide | contributor | | --- | --- | --- | --- | --- | | 13.3.0 | python3 -m pip install ansible==13.3.0 --user | (ansible-build-data/13/CHANGELOG-v13.md at 13.3.0 · ansible-community/ansible-build-data · GitHub) | (Ansible 13 Porting Guide — Ansible Community Documentation) | Felix Fontein | ## Collection updates 1. community.general release - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) shared > 12.3.0 ([community.general/CHANGELOG.md at stable-12 · ansible-collections/community.general · GitHub](https://github.com/ansible-collections/community.general/blob/stable-12/CHANGELOG.md#v12-3-0)) has new features, bugfixes, and a new filter module. > 11.4.4 ([community.general/CHANGELOG.md at stable-11 · ansible-collections/community.general · GitHub](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4)) has only bugfixes. 1. community.routeros pre-release - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) said > community.routeros 3.17.0-a1 ([community.routeros/CHANGELOG.md at main · ansible-collections/community.routeros · GitHub](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-17-0-a1)) has been released. This is a pre-release with a huge amount of chnages for the `api_modify` and `api_info` modules, and we need help testing them! Please take a look at the forum post about this release ([Community.routeros: 3.17.0-a1 pre-release with many new and updated paths is ready for intensive testing!](https://forum.ansible.com/t/45228))! 1. community.eda collection announcement - [pinotree](https://matrix.to/#/@pinotree:matrix.org) contributed > A new [community.eda](https://galaxy.ansible.com/ui/repo/published/community/eda/) collection is available; see the announcement & plans for it: [New community.eda collection](https://forum.ansible.com/t/new-community-eda-collection/45222) 1. infra.aap\_configuration release - [Sean Sullivan](https://matrix.to/#/@ssulliva:matrix.org) contributed > infra.aap\_configuration 4.2.1 has been released. > This Ansible collection allows for easy interaction with Ansible Automation Platform via Ansible roles using the supported collections modules. > Visit [GitHub - redhat-cop/infra.aap\_configuration: A collection of roles to manage Ansible Automation Platform 2.5+ with code](https://github.com/redhat-cop/aap_configuration/) For more information and updates. 1. Certified collections updates - [samccann](https://matrix.to/#/@samccann:ansible.im) shared > Certified collections updated this week: > > - [cisco.nxos:11.1.3](https://catalog.redhat.com/software/collection/cisco/nxos?sc_cid=RHCTE0250000461626) > - [redhat.edge\_manager:1.4.0](https://catalog.redhat.com/software/collection/redhat/edge_manager?sc_cid=RHCTE0250000461626) > - [dellemc.enterprise\_sonic:4.1.0](https://catalog.redhat.com/software/collection/dellemc/enterprise_sonic?sc_cid=RHCTE0250000461626) > - [splunk.enterprise:1.0.0](https://catalog.redhat.com/software/collection/splunk/enterprise?sc_cid=RHCTE0250000461626) > - [azure.azcollection:3.14.0](https://catalog.redhat.com/software/collection/azure/azcollection?sc_cid=RHCTE0250000461626) 1. infra.controller\_configuration release - [Sean Sullivan](https://matrix.to/#/@ssulliva:matrix.org) said > infra.controller\_configuration 3.2.1 has been released. > This Ansible collection allows for easy interaction with an AWX or Ansible Controller server via Ansible roles using the AWX/Controller collection modules. > Visit [GitHub - redhat-cop/infra.controller\_configuration: ansible collection for standardizing configuring AAP 2.4 and earlier](https://github.com/redhat-cop/infra.controller_configuration/) For more information and updates. 1. community.routeros release - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) said > community.routeros 3.16.0 ([community.routeros/CHANGELOG.md at main · ansible-collections/community.routeros · GitHub](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-16-0)) is out with new features for the API modules. 1. community.openwrt release - [russoz (Alex Z)](https://matrix.to/#/@russoz:matrix.org) shared > The [community.openwrt](https://galaxy.ansible.com/ui/repo/published/community/openwrt/) version 1.0.0 has been released! See the [announcement post in the forum](https://forum.ansible.com/t/announcing-community-openwrt-1-0-0/45212). > > This version comes with integration tests for all modules, a couple of bugfixes and more. @russoz : please see this sort of layout would be more interesting? cc @gundalow ---
**Author:** ![russoz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/russoz/32/127_2.png) [@russoz](https://forum.ansible.com/u/russoz)\ **Post date:** [February 15, 2026, 9:53am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/5 "2026-02-15T09:53:12Z")
Hi, Well, that seems more cosmetic than anything else - but it does look better than before. Maybe I read too much into “more story-driven format”? ---
**Author:** ![kks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kks/32/10352_2.png) [@kks](https://forum.ansible.com/u/kks)\ **Post date:** [February 15, 2026, 10:32am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/6 "2026-02-15T10:32:18Z")
> [@Sutapa](#): > > Major new releases Maybe sort this table by one column? At the moment hard to find version I am interested in. Also date column might be nice. ---
**Author:** ![kks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kks/32/10352_2.png) [@kks](https://forum.ansible.com/u/kks)\ **Post date:** [February 15, 2026, 10:50am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/7 "2026-02-15T10:50:13Z")
> [@Sutapa](#): > > The `Ansible` package includes `ansible-core` and is a batteries-included package that provides a curated set of Ansible collections. See the [Ansible roadmaps](https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html) for future release plans. > [@kks](#): > > The [`ansible==13.3.0`](https://pypi.org/project/ansible/) community package includes [`ansible-core==2.20.0`](https://pypi.org/project/ansible-core/) and is a batteries-included package that provides a curated set of Ansible collections. See the [Ansible roadmaps](https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html) for future release plans. Second version looks a bit more informative to me. Maybe links to github, rather than pypi should be included. > [@Sutapa](#): > > 1. community.general release > > - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) shared > > > 12.3.0 ([community.general/CHANGELOG.md at stable-12 · ansible-collections/community.general · GitHub](https://github.com/ansible-collections/community.general/blob/stable-12/CHANGELOG.md#v12-3-0)) has new features, bugfixes, and a new filter module. > > 11.4.4 ([community.general/CHANGELOG.md at stable-11 · ansible-collections/community.general · GitHub](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4)) has only bugfixes. > [@kks](#): > > 1. community.general releases > > - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) shared > > > [12.3.0](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=12.3.0) ([CHANGELOG.md](https://github.com/ansible-collections/community.general/blob/stable-12/CHANGELOG.md#v12-3-0)) is a regular feature and bugfix release with 70+ minor changes, six bugfixes, and one new filter module. > > [11.4.4](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=11.4.4) ([CHANGELOG.md](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4)) is a regular bugfix release that has two bugfixes. Just my opinion, but second one looks less cluttered and bit more informative. I mean 70+ minor changes (i was tired counting)! This is impressive and requires a shout out! Other collection updates also can be rewritten similar way. And I agree these changes look very nice and are definetely positive improvements. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [February 15, 2026, 11:18am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/8 "2026-02-15T11:18:32Z")
> [@kks](#): > > > [@Sutapa](#): > > > > The `Ansible` package includes `ansible-core` and is a batteries-included package that provides a curated set of Ansible collections. See the [Ansible roadmaps](https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html) for future release plans. > > > [@](#): > > > > The [`ansible==13.3.0`](https://pypi.org/project/ansible/) community package includes [`ansible-core==2.20.0`](https://pypi.org/project/ansible-core/) and is a batteries-included package that provides a curated set of Ansible collections. See the [Ansible roadmaps](https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html) for future release plans. > > Second version looks a bit more informative to me. Maybe links to github, rather than pypi should be included. If anyone wants to adjust it, the announcement comes from here: [antsibull-build/src/antsibull\_build/data/ansible-matrix-announcement.j2 at main · ansible-community/antsibull-build · GitHub](https://github.com/ansible-community/antsibull-build/blob/main/src/antsibull_build/data/ansible-matrix-announcement.j2) And the variables it can use from here: [antsibull-build/src/antsibull\_build/announcements.py at 3e2718d02a98a71ab6764705a4d4bed4dc883b9d · ansible-community/antsibull-build · GitHub](https://github.com/ansible-community/antsibull-build/blob/3e2718d02a98a71ab6764705a4d4bed4dc883b9d/src/antsibull_build/announcements.py#L83-L97) I’m not sure whether GitHub links are helpful, since the only repository we could sensibly link to is [GitHub - ansible-community/ansible-build-data: Holds generated but persistent results from building the Ansible community package](https://github.com/ansible-community/ansible-build-data/), which is already reachable from the PyPI page and isn’t of much use to most users. In any case, _replacing_ PyPI links by GitHub links is something we should definitely not do. Also `ansible==specific version` doesn’t include `ansible-core==another specific version`, but `ansible-core>=another specific version, **Author:** ![kks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kks/32/10352_2.png) [@kks](https://forum.ansible.com/u/kks)\ **Post date:** [February 15, 2026, 11:27am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/9 "2026-02-15T11:27:49Z") > [@felixfontein](#): > > but `ansible-core>=another specific` Thanks for correction, I was not sure what is included, I just found refference to the version number in build-data repo. ---
**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\ **Post date:** [February 15, 2026, 12:38pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/10 "2026-02-15T12:38:12Z")
One minor suggestion, the [Collection updates section](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/4#p-137823-collection-updates-4), might look better if it contained sub-headings in place of the ordered list. ---
**Author:** ![Sutapa](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sutapa/32/4230_2.png) [@Sutapa](https://forum.ansible.com/u/Sutapa)\ **Post date:** [February 17, 2026, 6:53pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/11 "2026-02-17T18:53:03Z")
Sub-headings as in name/title of the collection that we are highlighting? If so, I am preparing another reply tomorrow that takes into account the suggestions/comments I have got so far. ---
**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\ **Post date:** [February 17, 2026, 8:58pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/12 "2026-02-17T20:58:10Z")
I think the following: > [@Sutapa](#): > > ## Collection updates > > 1. community.general release > > - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) shared > > > 12.3.0 ([community.general/CHANGELOG.md at stable-12 · ansible-collections/community.general · GitHub](https://github.com/ansible-collections/community.general/blob/stable-12/CHANGELOG.md#v12-3-0)) has new features, bugfixes, and a new filter module. > > 11.4.4 ([community.general/CHANGELOG.md at stable-11 · ansible-collections/community.general · GitHub](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4)) has only bugfixes. > > 1. community.routeros pre-release > > - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) said > > > community.routeros 3.17.0-a1 ([community.routeros/CHANGELOG.md at main · ansible-collections/community.routeros · GitHub](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-17-0-a1)) has been released. This is a pre-release with a huge amount of chnages for the `api_modify` and `api_info` modules, and we need help testing them! Please take a look at the forum post about this release ([Community.routeros: 3.17.0-a1 pre-release with many new and updated paths is ready for intensive testing!](https://forum.ansible.com/t/45228))! Would look better like this: ## Collection updates ### 1. community.general release - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) shared > 12.3.0 ([community.general/CHANGELOG.md at stable-12 · ansible-collections/community.general · GitHub](https://github.com/ansible-collections/community.general/blob/stable-12/CHANGELOG.md#v12-3-0)) has new features, bugfixes, and a new filter module. > 11.4.4 ([community.general/CHANGELOG.md at stable-11 · ansible-collections/community.general · GitHub](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4)) has only bugfixes. ### 2. community.routeros pre-release - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) said > community.routeros 3.17.0-a1 ([community.routeros/CHANGELOG.md at main · ansible-collections/community.routeros · GitHub](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-17-0-a1)) has been released. This is a pre-release with a huge amount of chnages for the `api_modify` and `api_info` modules, and we need help testing them! Please take a look at the forum post about this release ([Community.routeros: 3.17.0-a1 pre-release with many new and updated paths is ready for intensive testing!](https://forum.ansible.com/t/45228))! It also has the advantage that heading have fragment IDs and anchor links whereas ordered lists don’t. ---
**Author:** ![Sutapa](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sutapa/32/4230_2.png) [@Sutapa](https://forum.ansible.com/u/Sutapa)\ **Post date:** [February 18, 2026, 11:39am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/13 "2026-02-18T11:39:21Z")
## Major new releases 🏆 | Major release version | New release version | Forum Thread | Release Date | | --- | --- | --- | --- | | Ansible-core 2.20 | Ansible-core v2.20.2 | [New Release: ansible-core v2.20.2](https://forum.ansible.com/t/new-release-ansible-core-v2-20-2/45217) | Jan 30, 2026 | | Ansible-core 2.19 | Ansible-core v2.19.6 | [New Release: ansible-core v2.19.6](https://forum.ansible.com/t/new-release-ansible-core-v2-19-6/45216) | Jan 30, 2026 | | Ansible-core 2.18 | Ansible-core v2.18.13 | [New Release: ansible-core v2.18.13](https://forum.ansible.com/t/new-release-ansible-core-v2-18-13/45215) | Jan 30, 2026 | | Ansible-core 2.16 | Ansible-core v2.16.16 | [New Release: ansible-core v2.16.16](https://forum.ansible.com/t/new-release-ansible-core-v2-16-16/45214) | Jan 30, 2026 | ### Ansible Community Package [↗](https://github.com/ansible-collections) The Ansible package includes ansible-core and is a batteries-included package that provides a curated set of Ansible collections. See the [Ansible roadmaps](https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html) for future release plans. #### Ansible package 13 | Ansible package | command | Release Notes | Ansible 13 Porting Guide | contributor | | --- | --- | --- | --- | --- | | 13.3.0 | python3 -m pip install ansible==13.3.0 --user | (ansible-build-data/13/CHANGELOG-v13.md at 13.3.0 · ansible-community/ansible-build-data · GitHub) | (Ansible 13 Porting Guide — Ansible Community Documentation) | Felix Fontein | ## Collection updates ### community.general - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) shared > [12.3.0](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=12.3.0) ([CHANGELOG.md](https://github.com/ansible-collections/community.general/blob/stable-12/CHANGELOG.md#v12-3-0)) is a regular feature and bugfix release with 70+ minor changes, six bugfixes, and one new filter module. > [11.4.4](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=11.4.4) ([CHANGELOG.md](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4)) is a regular bugfix release. * * * ### community.routeros - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) said > [community.routeros 3.17.0-a1](https://galaxy.ansible.com/ui/repo/published/community/routeros/?version=3.17.0-a1) ([CHANGELOG.md](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-17-0-a1)) has been released. This is a pre-release with a huge amount of changes for the api\_modify and api\_info modules, and we need help testing them! Please take a look at the forum post about this release ([Community.routeros: 3.17.0-a1 pre-release with many new and updated paths is ready for intensive testing!](https://forum.ansible.com/t/45228))! > [community.routeros 3.16.0](https://github.com/ansible-collections/community.routeros/releases/tag/3.16.0) ([CHANGELOG.md](https://github.com/ansible-collections/community.routeros/blob/main/CHANGELOG.md#v3-16-0)) is a release with features for the API modules. * * * ### community.eda - [pinotree](https://matrix.to/#/@pinotree:matrix.org) contributed > A new [community.eda](https://galaxy.ansible.com/ui/repo/published/community/eda/) collection is available; see the announcement & plans for it: [New community.eda collection](https://forum.ansible.com/t/new-community-eda-collection/45222) * * * ### infra.aap\_configuration - [Sean Sullivan](https://matrix.to/#/@ssulliva:matrix.org) contributed > [infra.aap\_configuration 4.2.1](https://github.com/redhat-cop/infra.aap_configuration/releases/tag/4.2.1) has been released. > This Ansible collection allows for easy interaction with Ansible Automation Platform via Ansible roles using the supported collections modules. > Visit [GitHub - redhat-cop/infra.aap\_configuration](https://github.com/redhat-cop/aap_configuration/) for more information and updates. * * * ### infra.controller\_configuration - [Sean Sullivan](https://matrix.to/#/@ssulliva:matrix.org) said > [infra.controller\_configuration 3.2.1](https://github.com/redhat-cop/infra.controller_configuration/releases/tag/3.2.1) has been released. > This Ansible collection allows for easy interaction with an AWX or Ansible Controller server via Ansible roles using the AWX/Controller collection modules. > Visit [GitHub - redhat-cop/infra.controller\_configuration](https://github.com/redhat-cop/infra.controller_configuration/) for more information and updates. * * * ### community.openwrt - [russoz (Alex Z)](https://matrix.to/#/@russoz:matrix.org) shared > [The community.openwrt version 1.0.0](https://galaxy.ansible.com/ui/repo/published/community/openwrt/?version=1.0.0) has been released! See the [announcement post in the forum](https://forum.ansible.com/t/45212). > This version comes with integration tests for all modules, a couple of bugfixes, and more. ### Certified collections updates - [samccann](https://matrix.to/#/@samccann:ansible.im) shared > Certified collections updated this week: > > - [cisco.nxos:11.1.3](https://catalog.redhat.com/software/collection/cisco/nxos?sc_cid=RHCTE0250000461626) > - [redhat.edge\_manager:1.4.0](https://catalog.redhat.com/software/collection/redhat/edge_manager?sc_cid=RHCTE0250000461626) > - [dellemc.enterprise\_sonic:4.1.0](https://catalog.redhat.com/software/collection/dellemc/enterprise_sonic?sc_cid=RHCTE0250000461626) > - [splunk.enterprise:1.0.0](https://catalog.redhat.com/software/collection/splunk/enterprise?sc_cid=RHCTE0250000461626) > - [azure.azcollection:3.14.0](https://catalog.redhat.com/software/collection/azure/azcollection?sc_cid=RHCTE0250000461626) * * * @kks @chris @gundalow please take a look and let me know what you think of this version. ---
**Author:** ![chris](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/chris/32/293_2.png) [@chris](https://forum.ansible.com/u/chris)\ **Post date:** [February 18, 2026, 12:02pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/14 "2026-02-18T12:02:02Z")
Looks good to me, thanks! ---
**Author:** ![kks](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kks/32/10352_2.png) [@kks](https://forum.ansible.com/u/kks)\ **Post date:** [February 18, 2026, 12:04pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/15 "2026-02-18T12:04:13Z")
Looks great! ---
**Author:** ![Sutapa](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sutapa/32/4230_2.png) [@Sutapa](https://forum.ansible.com/u/Sutapa)\ **Post date:** [February 23, 2026, 9:01am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/16 "2026-02-23T09:01:16Z")
Hi @samccann and @anwesha, I’ve been focusing on improving the content quality of the Bullhorn release, and I would really appreciate it if you could take a look and share your feedback. Please also let me know if there’s anything else I can contribute to or help with. Thank you! ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 23, 2026, 3:31pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/17 "2026-02-23T15:31:20Z")
I’m no native speaker, but “major new releases” sounds a little bit unfortunate to me. At first, I confused this with “new major releases” and than realized that this is not about _major releases_ at all. I suggest to substitute the “major” with something else (main, important, published…) or simply drop it completely (“New releases”). What do you think? ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [February 23, 2026, 4:57pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/18 "2026-02-23T16:57:30Z")
> [@Sutapa](#): > > - [Felix Fontein](https://matrix.to/#/@felixfontein:matrix.org) shared > > > [12.3.0](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=12.3.0) ([CHANGELOG.md](https://github.com/ansible-collections/community.general/blob/stable-12/CHANGELOG.md#v12-3-0)) is a regular feature and bugfix release with 70+ minor changes, six bugfixes, and one new filter module. > > [11.4.4](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=11.4.4) ([CHANGELOG.md](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4)) is a regular bugfix release. > > * * * (I was looking at this again since I’ll be writing a new one for this quite soon 🙂 ) For accessibility reasons link titles should kind of identify what they link to. Neither “12.3.0”/“11.4.4” nor “CHANGELOG.md” is thus a great title. The main reason I was using `community.general 12.3.0` as the link title to the changelog was to avoid these issues. If we also want a Galaxy link, how abount something like this? > [community.general 12.3.0](https://github.com/ansible-collections/community.general/blob/stable-12/CHANGELOG.md#v12-3-0) is a regular feature and bugfix release with 70+ minor changes, six bugfixes, and one new filter module ([community.general 12.3.0 on Galaxy](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=12.3.0)). > [community.general 11.4.4](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4) is a regular bugfix release ([community.general 11.4.4 on Galaxy](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=11.4.4)). ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [February 23, 2026, 5:24pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/19 "2026-02-23T17:24:28Z")
How about linking to galaxy first, and then to the release notes? Like: > [community.general 12.3.0](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=12.3.0) is a regular feature and bugfix release with 70+ minor changes, six bugfixes, and one new filter module ([Release Notes](https://github.com/ansible-collections/community.general/blob/stable-12/CHANGELOG.md#v12-3-0)). > [community.general 11.4.4](https://galaxy.ansible.com/ui/repo/published/community/general/content/?version=11.4.4) is a regular bugfix release ([Release Notes](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4)). I don’t know if this would be a good idea, but thought it might be worth to throw into the discussion. Anyway, if link titles should kind of identify what they link to I think it would be a good idea to use `Release Notes`. The file is CHANGELOG.md but if you look at it the title is Release Notes. ---
**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\ **Post date:** [February 23, 2026, 5:41pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/20 "2026-02-23T17:41:04Z")
I wondering who actually needs the Galaxy links? You only need it if you want to download the collection tarball from there directly IMO. I think the changelog is more useful, that’s why I put it first. [Next page](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321.md?page=2)