Skip to content

Conversation

mariolenz
Copy link
Contributor

@mariolenz mariolenz commented Aug 23, 2025

This is based on the Ansible 12 roadmap, but updated according to #2997. There are two major differences to the Ansible 12 roadmap:

  1. I've dropped the planned major changes section, because I think it's not really useful. If you think we should keep it, please join this discussion.
  2. I've changed links to docs.ansible.com to ansible.readthedocs.io. I thought it might be a good idea because of this announcement.

edit:
https://forum.ansible.com/t/44367

@ansible-documentation-bot ansible-documentation-bot bot added the sc_approval This PR requires approval from the Ansible Community Steering Committee label Aug 23, 2025
Copy link
Collaborator

@felixfontein felixfontein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for doing this!

@mariolenz
Copy link
Contributor Author

Thanks for reviewing and your suggestions @felixfontein!

@leogallego
Copy link
Contributor

leogallego commented Sep 9, 2025

@mariolenz We might need to double check with @oraNod , but I think the move of docs doesn't require to change URLs, and actually it might be counter-productive.

The docs.ansible.com subdomain will point to ansible.readthedocs.io through a CNAME probably (or something) for resolution, but the URL will stay docs.ansible.com, and actually, the readthedocs one is going away:

From the announcement in the forum

You do not need to update bookmarks or links to documentation in collection READMEs or other places where you might point to docs.ansible.com.

After the migration, the ansible.readthedocs.io subdomain will change to docs.ansible.com and the landing pages will be at the root level with each project, including core and the package, added as a subproject. After the change, you will have the following structure:

@oraNod
Copy link
Contributor

oraNod commented Sep 9, 2025

Thanks for pinging me here @leogallego I think this got lost in the avalanche of stuff when I returned from PTO. You're correct that there is no need to change subdomains or take any action. I also responded with some more details in a separate thread here: ansible-community/antsibull-build#675

Apologies if this read the docs migration is causing some confusion or extra churn!

@mariolenz
Copy link
Contributor Author

Actually I would link directly to https://docs.ansible.com/ansible/devel/community/steering/community_steering_committee.html#creating-community-topic here using the RST label

Good point @felixfontein! Should we do the same with the ansible-core 2.20 Roadmap? It's already linked like this under Release schedule.

It looks like we already had this mismatch in the Ansible 12 roadmap: First link to a URL, then to a RST label. But I guess it makes more sense like this.

Copy link
Collaborator

@felixfontein felixfontein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Links look good to me!

@mariolenz
Copy link
Contributor Author

@leogallego @oraNod FYI The links to ansible.readthedocs.io have been replaced with using RST labels. I've also reverted the last one (in the header) back to docs.ansible.com here again.

Does this look OK to you?

@oraNod
Copy link
Contributor

oraNod commented Sep 10, 2025

@leogallego @oraNod FYI The links to ansible.readthedocs.io have been replaced with using RST labels. I've also reverted the last one (in the header) back to docs.ansible.com here again.

Does this look OK to you?

Thanks @mariolenz Looks good to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sc_approval This PR requires approval from the Ansible Community Steering Committee
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants