What I don’t like about using design.xwiki.org for Roadmaps is that it would be hijacking something that currently works, is relatively clean enough and is quite clear on its purpose.
Pages on design tend to be (by design, no pun intended ) very feature-oriented and with a limited lifecycle in mind (i.e. the feature is proposed, analyzed, refined, implemented and, finally, done and only kept for reference). It also targets mostly new features and, at most, improvements, but not bugs (which can also be part of roadmaps).
Roadmaps, on the other hand, are “living things”. You handle roadmaps for products/extensions which are made of multiple new features, improvements and/or bug fixes. You track the evolution (i.e. not its design, since that is pretty short lived and happens only at the beginning) and, when it’s done, it’s not really done, because you start again with the new version/iteration. Sure, you can break it in per-version roadmap pages (e.g. “Extension-X-v11.5-Roadmap” page), but that would just be a workaround.
In my mind, “Roadmap” is more related to “Development” (e.g. “dev” wiki which would not only contain dev tools, API and process, but also the progress; the example is “valid” because on dev we also declare the process of developing XS itself, not only how extension devs should develop work with the platform) than to “Design” (which is not really a concept that includes “progress of execution”, since that part usually comes - if, for argument’s sake, you think at the Waterfall model - after the design/analysis step ).
I also get that we can look at Roadmaps as something that covers all aspects of the development process (design, implementation, testing, etc.), for each iteration so it should be somewhere above all that, but, in any case, not mixed (location-wise) with one of the steps which it contains (in this case, the design step).
It probably does make sense from a purely pragmatic pov to have roadmap pages in the design wiki, but, to me at least, it just does not sound right to mix the 2 concepts.
After thinking a bit more on it, maybe the better alternative (potentially a bit more costly, but maybe cleaner, in the end) would be to look into some dedicated project management/planning tool that would allow us to nicely aggregate all the steps of the dev process and manage them more easily and maybe in a more modern approach than by writing something on a peace of paper (i.e. wiki page) :).
AFAIR, even Jira is supposed to be pretty good at managing Roadmaps (with/without plugins) for each project (so it would work for both XS and each individual extension) as it would technically make the most sense in our current situation (roadmaps are usually just an ordered list of jira issues and it would also enforce us to create jira issues for each task) and since we already heavily use it. I know this has been discussed before as well.
Other tools more dedicated than Jira (and possibly allowing to easily integrate the issue tracker) exist. Why not consider this approach instead of us coming up with our own custom solution (again) to a relatively common (and simple?) problem?
Hope the input is useful