community-topics VS docsite

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.

Before we add the redirect we'd like to get your feedback. Please leave a comment on the pull request or head over to the docs channel on Matrix and let us know your thoughts.

Hopefully you've noticed that the "docs.ansible.com" landing page has a different navigation. We've updated it to focus on user journeys so users can find support from Ansible docs more efficiently. There is still lots to do and we'd love to hear from you! Do you have ideas about new user journeys? Do you see any content gaps? Are there things you'd just like to change? Send a PR or open an issue in the ansible/docsite repo and help us keep building better content journeys for the community.

We've just refreshed the layout on docs.ansible.com to include quick and easy links for most visited doc pages. You can find the new "Quicklinks" section on the index, user, developer, and maintainer pages. We want to hear from you, especially if you have a killer suggestion for a quicklink, so open an issue in the ansible/docsite repo.

You might have noticed that "docs.ansible.com" has a different layout. That's because we've revamped it to focus on user journeys so that users find what they need from Ansible docs more efficiently. There is still lots to do and we'd love to hear from you! Do you have ideas about new user journeys? Do you see anything missing from the new docsite? Are there things you'd just like to change? Send a PR or open an issue in the ansible/docsite repo and help us make it even better.

Come join us and help build a new docsite! The community team has been working to update the Ansible documentation landing page based on a set of user journeys. Right now we're working on a prototype docsite to improve the navigation and user experience.

The community engineering team has put together a first set of user journeys for Ansible docsite personas and would like your feedback. You can find the user journeys in GitHub.

The ansible/docsite repo is now public, giving the Ansible community full access to all the html and navigation assets that go into docs.ansible.com. Fork the repo and start hacking.