There are multiple reasons why having a roadmap is good thing:
It shows project has future and gives an idea what the future might look like.
Organizes the effort and invites other to really around.
Provides accountability into how good last year was (eg. Did we achieve the goals we planned and why not?)
What should roadmap include or not include?
I wouldn't worry too much to have a "perfect" roadmap, but rather a place where one can see the directions which we want to explore. It can serve as inspiration to somebody looking what to work in Nix.
Items in roadmap can be:
areas to explore (eg. ipfs, trustix, ...)
technical goals (eg. separate nix the language from nix the command line)
non-technical goals (eg. we want to grow contributors)
I think most interesting roadmap is something that can be done in next year (or maybe two). Of course we can also write about longer term goals, but that is much harder to do.
There is no guarantee that items on the roadmap are going to get done. What it does it shows intent what we would work if we would have the resources.
Why
There are multiple reasons why having a roadmap is good thing:
What should roadmap include or not include?
I wouldn't worry too much to have a "perfect" roadmap, but rather a place where one can see the directions which we want to explore. It can serve as inspiration to somebody looking what to work in Nix.
Items in roadmap can be:
I think most interesting roadmap is something that can be done in next year (or maybe two). Of course we can also write about longer term goals, but that is much harder to do.
There is no guarantee that items on the roadmap are going to get done. What it does it shows intent what we would work if we would have the resources.