Bullhorn #47

Source

Ansible Bullhorn banner

A Newsletter for the Ansible Developer Community Issue #47, 2022-02-24 (Past Issues)

Welcome to The Bullhorn, our newsletter for the Ansible developer 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

GENERAL NEWS UPDATES

cybette contributed

Ansible turns 10! We appreciate all of you, contributors and users in the community, for the amazing growth and adoption of Ansible over the past decade. Happy Birthday to Ansible, and let's continue automating and innovating with Ansible for the next 10 years and beyond!

MAJOR NEW RELEASES

Ansible ↗

The Ansible package includes ansible-core and is a batteries-included package that provides a curated set of Ansible collections. See the Ansible roadmaps for future release plans.

dmsimard shared

ansible 5.4.0 has been released and includes minor updates from 24 Ansible collections! Read more about it in the announcement, the changelog or the porting guide.

COLLECTION UPDATES

felixfontein contributed

community.docker 2.2.0 has been released with new features and bugfixes. Version 1.10.5 has been released with bugfixes.

rrey said

community.grafana 1.3.2 has been released (changelog).

rainerleber said

community.sap 1.0.0 has been released (changelog).

felixfontein shared

community.crypto 2.2.2 has been released with some bugfixes, and community.crypto 1.9.12 has been released with backports of these fixes and some known issues, as some of these issues could not be fixed in some cases.

felixfontein contributed

community.general 4.5.0 (changelog) and 3.8.5 (changelog) have been released with new features (only 4.5.0) and bugfixes.

HELP WANTED

Rémi Rey contributed

The community.grafana collection is looking for help. There are major changes in Grafana 8 that requires adaptations in the modules. We are also looking for good souls to join the maintainers <3

PROPOSALS - FEEDBACK APPRECIATED!

Gwmngilfen said

Chatrooms Feedback

It is coming up on 6 months since the vote to adopt Matrix alongside IRC. At that time, I said we should treat this as an ongoing process, and I meant it! I am preparing a blogpost covering the adoption so far, data to show, nice wins, pain points, and so on.

I would love to hear from the community about how the last few months have felt for you! Are you a long-term community member, or perhaps someone who just joined? Are the rooms discoverable enough? Are some things causing issues? Good, bad, or just interesting, I'd like to hear it. Note that nothing I hear will be made public without consent - but I hope I can publish some comments, and gain an idea of the sentiment.

If you are comfortable having a direct chat, then message me (@gwmngilfen:ansible.im or gwmngilfen-work on Libera), otherwise please feel free to leave anonymous comments on this form. The feedback window will be open for about 2-3 weeks, as I plan to write the blogpost in mid-March. Thanks!

gundalow shared

Improving Ansible documentation by unversioning some guides

Today, we have multiple files that we only maintain in /devel/. Historically, we had problems keeping these files up to date in other branches (latest and older). The docs team chose to publish the following pages only to devel and put a stub page up in latest and earlier releases to point to devel:

While this has worked well to keep the relevant docs current, it can be a cause of confusion. One recent reader was confused that we were pointing them to a devel page which has the banner that says this is not a guaranteed stable branch.

We have another set of guides (the community and contributor guides) that are getting a significant overhaul in devel. These guides are not specific to any release (core or Ansible package), but because we publish only to versioned urls, we force these guides to be 'versioned'.

We'd really welcome feedback from users, contributors and folks that have helped with the documentation via ansible-community/community-topics#68.

gundalow contributed

Revamping the community and contributor documentation

We have docs in three places today for contributors: * ansible/ansible in the community folder * ansible/community-docs - more collection focused * ansible-collections/overview - has deeper collection contribution details

Since only the first one is published to docs.ansible.com, we need to find a way to publish the details from the other two repositories.

This is a complex issue, and will shape how we structure the wide range of Ansible Documentation in the future. We'd really like to get your thoughts, and to hear your ideas via community-topics#60.

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.

gundalow contributed

ansible-core is proposing adding Type Annotations

Since the ansible-core controller fully dropped support for older versions of Python, starting in ansible-core 2.12, new Python language features like inline type annotations have become available to us. Before we open the floodgates to type annotations being splattered across the ansible-core codebase, it's necessary to define some policy around how type annotations will be used, and especially how they will be validated.

If you have experience with Python's type annotations we'd like to hear how you think this could help, let us know your thoughts via ansible/proposals#202.

COMMUNITY EVENTS AND MEETUPS

cybette contributed

Join Ansible NOVA group in “Ansible NOVA March Spring Soiree!” on Thursday, March 24 at 16:30 EDT / 20:30 UTC. It'll be a virtual meetup and they are looking for speakers/content. Check the details and RSVP here.

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!

Powered by