# Suggesting updates to the Bullhorn boilerplate content **URL:** \ **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:** 7\ **Page:** 1
**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\ **Post date:** [June 28, 2024, 4:21pm UTC](https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839/1 "2024-06-28T16:21:16Z")
We were chatting a bit in the social matrix channel and I wanted to move the conversation here to take a deeper dive. Today the top of the Bullhorn has a Key Dates section. Historically, this listed just a couple of the weekly Working Group Meetings, and the estimated date of the next core and package releases. All of this is subject to human error (aka the bullhorn editor might pick an incorrect date) and also doesn’t list all the releases or working groups. So some ideas that came out of this early chat: - Let’s remove the release details in Key Dates - these two teams always update the bullhorn separately when a release happens. - Let’s stop manually adding working group meetings and meetups and instead point to the [Events - Ansible](http://forum.ansible.com/c/events/8) Calendar here in the forum instead. - Let’s also add a link to the [Ecosystem Releases - Ansible](http://forum.ansible.com/c/news/releases/18) to cover more than the two release types we’ve been adding. We can then encourage other projects to use that release category here to keep folks informed. **Note** - if a meetup or WG wants to also add a newsbot entry, they are welcome to. What I’m talking about here is ways to simplify the workload for the Bullhorn editor and use the forum as our ‘single source of truth’ instead. ---
**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\ **Post date:** [June 28, 2024, 4:24pm UTC](https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839/2 "2024-06-28T16:24:32Z")
So not all of the working group calendars show up here in Events. We’d have to add them. That would mean working groups that used the [shared ica](https://github.com/ansible-community/meetings)l would have to update their calendars in two locations. @gwmngilfen - does the Events calendar here recognize Daylight Savings time etc? If so, then the ical folks wouldn’t have to update Events here when that change happens (we do have to update in ical because the tooling works on UTC so every 6 months, we make the changes). [@Docs](https://forum.ansible.com/groups/docs) [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) [@network-wg](https://forum.ansible.com/groups/network-wg) - as the three teams still using ical, what are your thoughts here? ---
**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")
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. ---
**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:06pm UTC](https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839/4 "2024-06-28T21:06:08Z")
Should we move Project Updates above the Releases, they seem more important. ---
**Author:** ![gwmngilfen](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gwmngilfen/32/6_2.png) [@gwmngilfen](https://forum.ansible.com/u/gwmngilfen)\ **Post date:** [July 1, 2024, 9:04am UTC](https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839/5 "2024-07-01T09:04:05Z")
> [@samccann](#): > > @gwmngilfen - does the Events calendar here recognize Daylight Savings time etc? If so, then the ical folks wouldn’t have to update Events here when that change happens (we do have to update in ical because the tooling works on UTC so every 6 months, we make the changes). I think you’d have to test it. IIRC it stores the TZ it’s created in - so if that’s one with DST it should move. The calendar _renders_ in the browser’s local time, so you should get the correct time for you. ---
**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\ **Post date:** [July 1, 2024, 6:40pm UTC](https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839/6 "2024-07-01T18:40:31Z")
Okay I’ve updated [How to edit and release the Ansible Bullhorn](http://forum.ansible.com/t/how-to-edit-and-release-the-ansible-bullhorn/6543) with the ideas so far. This will make the Bullhorn editor’s job easier for sure, thanks! ---
**Author:** ![Leo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/leo/32/23_2.png) [@Leo](https://forum.ansible.com/u/Leo)\ **Post date:** [July 9, 2024, 7:53pm UTC](https://forum.ansible.com/t/suggesting-updates-to-the-bullhorn-boilerplate-content/6839/7 "2024-07-09T19:53:35Z")
Added a few details and fixes to the instructions for The Bullhorn. I missed the key dates update here so the last one included them but I won’t in the next one. I do think a key dates summary is useful but until we can automate it, I agree removing it is the easiest as those are shared below on the updates. Regarding the working group meetings and calendar, a reminder we had an rfe for Discourse to allow an ics export or source for importing into calendars, we might want to check status on that. Having the option to import to get alerts in our calendars should help with attendance. I know it helps me at least.