# Suggesting updates to the Bullhorn boilerplate content

**URL:** <https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839>\
**Category:** Project Discussions\
**Tags:** newsletter\
**Created:** [June 28, 2024, 4:21pm UTC](https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839 "2024-06-28T16:21:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**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:** [June 28, 2024, 9:04pm UTC](https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839/3 "2024-06-28T21:04:17Z")

</div>

Good to think about simplifying and automating something we do weekly.

## Community Meetings

We are establishing [The Forum as the default place for discussion](http://forum.ansible.com/t/proposal-consolidating-ansible-discussion-platforms/6812/), I think that also implies it should be The Source Of Truth.

So moving away from the [YAML/ICS files](https://github.com/ansible-community/meetings/tree/main/meetings) (which were always difficult to maintain) to Events in The Forum seems like it makes sense.

I think we’ve used the Forum for other events and know how to best use The Forum for Agenda, does that require people to have extra permissions to update the running Agenda?

## Releases

I think with a GitHub action that watches for `git tag` (ie a release) we can likely automatically create Forum posts with the correct `tags` for projects that want it. This would likely work well for projects that have well formatted changelogs, ie can be posted without further editing.

---

_[View the full topic](https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839)._