Ansible 10 roadmap

[mariolenz]

Adding the Ansible 10 roadmap.

[samccann]

There are two items from https://forum.ansible.com/t/notes-for-the-ansible-10-roadmap/1751 that we should include here as well. Probably as general notes?

[mariolenz]

There are two items from https://forum.ansible.com/t/notes-for-the-ansible-10-roadmap/1751 that we should include here as well. Probably as general notes?

I was hoping @samccann would propose something 😇

But yes, I was also thinking about a (general) note as probably the best solution.

[samccann]

I was hoping @samccann would propose something 😇

@samccann hasn't woken up from her holiday stupor yet :-)

[mariolenz]

@felixfontein @samccann I've added a new commit, my suggested change was pretty large. Maybe it's easier for you to comment now.

I think you can see here how it looks at the moment.

[samccann]

Reposting from matrix:
Footnotes in tables can make it super difficult for folks with screen readers and other assistive tech to navigate. imagine the case where you have a table with a footnote and its in the middle of the table. when you hit that footnote you then jump to the section below the table and then have to navigate back up, which is annoying and risks those users missing information.
there are things you can do in HTML to make it more friendly but looking at the source I feel like users would run into the navigation pain. the footnote is a simple anchor that jumps to the bottom of the table.
an easy fix here might be to remove the anchor and add some text like "Refer to the notes below the table for more

[felixfontein]

The thing about footnotes in tables is something we should fix in another PR, not this one. We always used footnotes in tables for roadmaps so far (compare https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_9.html#release-schedule down to https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_3_0.html#release-schedule; only https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_2_10.html#release-schedule used neither table nor footnotes, but I don't think we want to go back there ;) )

[mariolenz]

I agree with @felixfontein. If footnotes are a problem, we already have this. Let's not discuss or try to solve it here.

If accessibility (for folks with screen readers and other assistive tech) is really an issue, I think this should be a separate discussion. After all, there might be more problems than just the footnotes... I really don't know, I have no experience there at all 🤷

[mariolenz]

@felixfontein @samccann Apart from the footnote / accessibility issue (which I think we should discuss somewhere else) does this look OK to you?

At least we would have a start on the Ansible 10 roadmap. We can change it and improve things later, no problem.

@anweshadas What do you think about the roadmap I've proposed?

[felixfontein]

The schedule and the text looks good to me!

[samccann]

If it's ready to merge, can you take it out of draft and remove WIP from the title pls?

[felixfontein]

Draft and WIP have to stay until this has been approved by SC vote.

[felixfontein]

The vote happens here: https://forum.ansible.com/t/vote-ends-on-2024-01-27-notes-for-the-ansible-10-roadmap/1751/4

[mariolenz]

@gotmax23 I've added the note.

Don't forget to vote if this looks OK to you now :-)

[gotmax23]

Ah, I thought I already had voted. I just did!

[gotmax23]

Thanks for working on this

[mariolenz]

The vote on the proposed roadmap has been accepted so I'll un-draft this PR.

[gotmax23]

Thanks @mariolenz!

[patchback]

Backport to stable-2.16: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.16/20fc39b366762506209c7c2dc38b7ef999fbecc4/pr-994

Backported as #1097

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.