I on the other hand for reasons listed below think we /need/ a roadmap. But lets first define what a roadmap is, before explaining why Drupal needs one. A roadmap – in contrast what people believe- is not a rigid layout of the plans for the period ahead. Neither is it a braindump of thing we want or a list of formal deliverables.
A roadmap doesn’t come with a receipt and there is no money back either. A roadmap is an abstract flexible projection of the predictable –makeable?- future to get developers and (potential) users aligned within a certain timebox. Strictly speaking Drupal has a roadmap. A roadmap might even be: we don’t need no stinkin roadmap, hence we already do have a roadmap.Planet Drupal]
Bryan Ruby is the owner and editor for CMS Report. He founded CMSReport.com in 2006 on the belief that information technologists, website owners, and web developers desired visiting sites where they could learn about content management systems without the sales pitch. Besides this site, you can follow Bryan at Google+ and Twitter.