-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
doc: Move roadmap in from the wiki #20122
doc: Move roadmap in from the wiki #20122
Conversation
This copies the version of 2020-05-29, with only the header line added.
7ad8f42
to
b5b7826
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack. Don't forget to remove the wiki page after this gets merged :)
Do we want to add outdated items or take this PR as an opportunity to clean up the list? |
This PR is just the technical migration; removal etc I'd prefer to handle in separate PRs. (And I've even changed the wiki already -- it points to a 404 page but just for a few hours). |
No, let's get this in as is first. Then we can work in parallel on changing it with multiple PRs. |
fully agree |
This moves the road map from the wiki (which has little visibility) to a place where it is visible.
While technically this adds hurdles to changes (PR instead of just-edit), practically this should be better because people know the process, and experience shows that people are hesitant to edit the wiki b/c they can't get it ACKed.
Testing procedure
Way forward
(This was discussed during the 2023.11 VMA)
We can start shaping this up more as a collection of topics and people's/groups' concrete sub-roadmaps. This PR just increases the roadmap's visibility, and increases the visibility of roadmap adjustments.