Dries Buytaert wrote:
I'm very sceptic about roadmaps and long-term planning in the context of Drupal development. A roadmap is vaporware and creates pressure.
Perhaps the "roadmap" could be redefined as two things: 1. Things we hear a lot from users as something they really want to see. We already have surveys thanks to Kieran, and we know what the wish list is. If we do this polling once a year, we will have an idea of what the current needs are. 2. From the above wishlist, we can select features that someone in the development community has committed to writing within the next release, or a sponsor has committed funding. Call the first one "community wishlist", and the second one "roadmap". How about that? Would that reduce the vaporware aspect of it?