# Bullhorn content quality improvement proposals

**URL:** <https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321>\
**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:** 8\
**Page:** 2

<div class="post-metadata">

**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, 6:01pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/21 "2026-02-23T18:01:05Z")

</div>

Good point. So why not get rid of the link to galaxy? Like:

> [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 11.4.4](https://github.com/ansible-collections/community.general/blob/stable-11/CHANGELOG.md#v11-4-4) is a regular bugfix release.

I guess that people who download the tarball directly from galaxy don’t need a direct link, they are probably savvy enough to find it themselves.

_edit_: Which looks pretty close to what has been announced in [Bullhorn 217](https://forum.ansible.com/t/the-bullhorn-217/45240#p-137427-collection-updates-9).

---

<div class="post-metadata">

**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, 7:09pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/22 "2026-02-23T19:09:20Z")

</div>

@kks suggested to link to Galaxy as well, maybe he can say why he suggested that before we decide (or not) to remove it 🙂

---

<div class="post-metadata">

**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 23, 2026, 8:37pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/23 "2026-02-23T20:37:08Z")

</div>

I’ve suggested link to galaxy to have a link to the docs. Not all collections have docs on docs.ansible.

---

<div class="post-metadata">

**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 24, 2026, 4:17pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/24 "2026-02-24T16:17:22Z")

</div>

@kks FYI I think the documentation on galaxy is [broken](https://forum.ansible.com/t/3496) when collections use docs fragments from another collection.

Nevertheless, I think you have a valid point there. I guess it’s a good argument to link to galaxy.

---

<div class="post-metadata">

**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 24, 2026, 4:49pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/25 "2026-02-24T16:49:37Z")

</div>

> [@mariolenz](#):
>
> I think the documentation on galaxy is [broken](https://forum.ansible.com/t/3496)

…In so many ways…

Could not agree more.

---

<div class="post-metadata">

**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 24, 2026, 4:49pm UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/26 "2026-02-24T16:49:51Z")

</div>

> [@mariolenz](#):
>
> 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.

Any ideas on this?

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [October 5, 2026, 9:46am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/27 "2026-10-05T09:46:24Z")

</div>

Hi @Sutapa - The configuration for the NewsBot is located here: [ansible.im/bots at main · ansible-community/ansible.im · GitHub](https://github.com/ansible-community/ansible.im/tree/main/bots)

The templates which would require changes for this proposed new formatting:

- [ansible.im/bots/newsbot-project.md at main · ansible-community/ansible.im · GitHub](https://github.com/ansible-community/ansible.im/blob/main/bots/newsbot-project.md)
- [ansible.im/bots/newsbot-report.md at main · ansible-community/ansible.im · GitHub](https://github.com/ansible-community/ansible.im/blob/main/bots/newsbot-report.md)
- [ansible.im/bots/newsbot-section.md at main · ansible-community/ansible.im · GitHub](https://github.com/ansible-community/ansible.im/blob/main/bots/newsbot-section.md)

The templating engine is: [minijinja - Rust](https://docs.rs/minijinja/latest/minijinja/)

---

<div class="post-metadata">

**Author:** ![dbrennand](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/dbrennand/32/7830_2.png) [@dbrennand](https://forum.ansible.com/u/dbrennand)\
**Post date:** [October 23, 2026, 7:52am UTC](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321/28 "2026-10-23T07:52:27Z")

</div>

Hi again, some bits have moved around this week: [GitHub - ansible-community/newsbot: Configuration, newsletter template, and container image for the Ansible Community Newsbot. · GitHub](https://github.com/ansible-community/newsbot) - All the config is located here now.

[Previous page](https://forum.ansible.com/t/bullhorn-content-quality-improvement-proposals/45321.md?page=1)
