antsibull-docs VS community-topics

antsibull-docs 2.6.0 has been released with a fix for EXAMPLES parsing and error message improvements.

More than two years ago the Ansible Docs Working Group started discussing the use of semantic markup for Ansible plugin/module documentation. This resulted in a specification that has been implemented as proofs of concept both for ansible-doc and the validate-modules sanity test, as well as for antsibull-docs. From the docs perspective this will improve plugin, module, and now also role documentation a lot, and in particular separate markup from content. (Right now you have to use C(...) and I(...) for values and option names, which stand for 'code-style' and 'italics'.)

antsibull-core 2.0.0a1 has been released. This major release drops support for Python 3.6, 3.7, and 3.8 and deprecates some compatability code (full changelog). It also includes a new feature needed by antsibull-build. antsibull-core houses shared code used by antsibull-build and antsibull-docs. If you use either of these tools, please help us test this new release. It can be installed with pip install -U antsibull-core==2.0.0a1. Note that you'll need the latest version of antsibull and antsibull-docs to use antsibull-core 2.0.0a1.

antsibull-docs 1.3.0 (changelog) has been released with several new features for the docs build! The most important changes are that now booleans are rendered as true and false instead of yes and no (https://github.com/ansible-community/community-topics/issues/116), and that a proper parser is used for Ansible markup, which properly escapes for example backticks instead of simply inserting them into the RST files (https://github.com/ansible-community/antsibull-docs/issues/21).

If you are using the antsibull-docs or antsibull-lint collection-docs CLI command from the antsibull package, consider switching to using the new antsibull-docs 1.0.0 package instead! It is more stable and comes with less potential baggage to carry around.

There is a community vote on a new policy for community.general on which ansible-core versions will be supported in new major releases. Basically support for ansible-core versions will be dropped if they were EOL at least a few weeks before the major release. For the upcoming community.general 8.0.0, that means that it will drop support for ansible-core 2.11 and 2.12 and require at least ansible-core 2.13. Details can be found in the associated issue.

As mentioned in The Bullhorn #113, we've opened a community / steering committee vote on declaring ngine_io.exoscale an effectively unmaintained collection and remove it from the Ansible 10 community package. Since then, there has been a new release. As a result, the vote ended with the decision to keep the collection in the community package.

2023-07-12: Community WG meeting, 18:00 UTC (propose topics here)

Hi everyone. We're working on making Ansible community documentation a separate project to ansible/ansible. The purpose is to benefit the Ansible community by decoupling community doc initiatives from core release cycles. This change also removes the Ansible Core team as the gate for other doc related efforts that will meet community needs, such as putting source content for docs.ansible.com under the direct control of the Steering Committee. Overall this change is a first step towards providing greater access and ownership of docs.ansible.com to the Ansible community.

Looking for your feedback on making community docs a separate github project to ansible/ansible, starting with moving /docs from ansible/ansible to ansible/ansible-documentation. See this issue for details.

It looks like the netapp.elementsw collection is effectively unmaintained. According to the current community guidelines for collections, we consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: netapp.elementsw for more information or to announce that you're interested in taking over the maintenance of (a fork of) netapp.elementsw.

The netapp.aws collection is considered unmaintained and will be removed from Ansible 10 if no one starts maintaining it again before Ansible 10. See the removal process for details on how this works.

As mentioned in The Bullhorn #98, we consider netapp.aws an effectively unmaintained collection. Therefore, we've opened a community / steering committee vote on removing it from the Ansible 10 community package.

2023-05-10: Community WG meeting, 18:00 UTC (propose topics here)

Work continues combining several pytest plugins for ansible.