The problem with traditional "roadmaps" is that they assume that you know exactly where you're going and how you're going to get there. The typical business roadmap also includes a schedule for getting there. None of those things align with the objective of being a community distro. We have a general vision of what we want the distro to be and how we want to accomplish that, but exactly how that plays out depends on what the community wants and how much they can contribute. The ability to pursue an important opportunity or idea when it arises is more important than ticking boxes for comparison shoppers.
With limited resources it's more important to be focused on what they community wants and needs than to create roadmaps that dictate a course that may not be appropriate. Wayland is a perfect example. Everyone has to support it because everyone else supports it and you have to check the boxes in the distro competition. Who cares? Nobody, really. Until it makes my desktop better without creating any fresh headaches, Xorg is fine thanks.
As for BDFL, every pack has a leader. The pack spots opportunities and communicates them, but it's the pack leader that says go or no go. There needs to be an executive authority. We've seen that community distros go terribly wrong when they become distro by committee. The squeaky wheel gets the grease and and corporate paid developers can get very squeaky. There needs to be a single decision point that will put the needs of the distro first. Only those who trust drobbins to do that should join the pack.