We want to hear from you! Help us gain insights into the state of the Ansible ecosystem.
Take the Ansible Project Survey 2024

Bullhorn #16

Ansible Bullhorn banner

The Bullhorn

A Newsletter for the Ansible Developer Community Issue #16, 2020-12-16 (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, please reach out to us at the-bullhorn@redhat.com, or comment on this GitHub issue.

KEY DATES

ACCEPTING NEW COLLECTIONS FOR ANSIBLE 3.0.0

The criteria for accepting new collections for Ansible 3.0.0 (releasing in February) have been approved.

If you would like your collection to be included in ansible-3.0.0, please try to make your collection conform to the requirements and then submit it as a discussion.

  • When you start the discussion, please include a link to the collection on galaxy, a link to the source code repository, a link to the issue tracker, and the GitHub IDs of collection owners that we should contact if there's a problem with the collection later.
  • We will review the new collection requests that have been submitted on a first-come, first-served basis. The earlier you submit your collection, the more likely you are to get it into 3.0.0.
  • The review may turn up things that need to be fixed which would delay acceptance.
  • 2021-01-27 is the date by which new collections must be reviewed and accepted, so get your collection in as early as possible! Submitting it close to the deadline may mean that there is not enough time for us to review and approve it resulting in it not being accepted.

The procedure for getting new collections in is highly likely to change for the Ansible 4.0.0 release (including who reviews, whether it remains first-come first-served, and so forth).

ANSIBLE-BASE 2.10.4 NOW GENERALLY AVAILABLE

The Ansible Core team announced the general release of Ansible-Base 2.10.4 on December 14th. This ansible-base package consists of only the Ansible execution engine, related tools (e.g. ansible-galaxy, ansible-test), and a very small set of built-in plugins, and is also bundled with the larger Ansible distribution. For more information on how to download, test, and report issues, read Rick Elrod’s announcement to the ansible-devel mailing list.

ANSIBLE 2.9.16 AND 2.8.18 RELEASED

The Ansible Core team announced the availability of Ansible 2.9.16 and Ansible 2.8.18 on December 14th, both of which are maintenance releases. Follow this link for Rick Elrod’s email to the ansible-devel mailing list, to obtain details on what’s new, installation instructions, and links to the full changelogs.

NEW/UPDATED COMMUNITY COLLECTIONS

ANSIBLE CONTIRBUTOR SURVEY DATA

Greg has started some deep dives into the data from the first 3 Contributor Summit surveys we ran during 2020. He's written up three whole posts on how the survey is designed, and what it has to say about burnout and contribution blockers in Ansible. Here's a teaser:

Screenshot

DIVERSITY & INCLUSION WORKING GROUP MEETING

The Diversity WG meetings will begin next year on January 7th at 19:00 UTC in IRC channel #ansible-diversity, and take place every other week. Submit agenda items in this GitHub issue.

ANSIBLE DOCUMENTATION SURVEY

We have created a one-page survey about the Ansible documentation. If you use docs.ansible.com, we’d love to hear your views! We’re hoping to learn whether different types of users need different types of documentation. We’re also interested in what the most common pain points are for documentation. The survey will be open until December 31st, 2020. Please fill out the survey and pass the word!

CONTENT FROM THE ANSIBLE COMMUNITY

Following up on his previous article about CI of the Ansible modules for VMware, Gonéri Le Bouder explains how to prepare the vSphere instances for the VMware CI.

SEASON'S GREETINGS

This will be the last issue of The Bullhorn for 2020. Thanks for all your support and contributions. Warm greetings from the Ansible Community Team, and see you in 2021!

FEEDBACK

Have any questions you’d like to ask, or issues you’d like to see covered? Please send us an email at the-bullhorn@redhat.com.