That's probably a good Idea, but I still like to point out, you cannot
tell anyone what to do.
You can put up a list of what's important/required and I'm likely to
pick something from it from time to time.
You can ask me to do something and I might be like *sigh*, well ok...
(halfassed attempt to help out)
Or you can tell me to do something, and I might be like... sorry, got no
time. Very busy, RL issues, you know... ;p
That's the way we all work, isn't it? We do it for the fun. If it's no
fun we don't do it or not do it very enthusiastically, which means
halfassed and ineffective. Of cause success is fun. But we all decide
for ourselves what is success and how we can achieve success.
If I don't like to fix some winetests, but like to fix amd64 branch
instead, or implement mode switching, do you want to keep me from doing
that? Probably not.
So a roadmap might point out what is important to be done and what is
not. But it cannot make people work on a specific part at a specific time.
Timo