I agree.

The problem as I see it is a combination of mistakes on Nokia's part vis-a-vis product development and release (IMO) combined with a lack of strategy on community software development.

We can't do much about Nokia's irregular schedule and poor choices (I still think it was a HUGE error not to have released a newer N800 iteration by now). And the best we can do on the official software front is identify and report on bugs (which this community does to a great extent).

But for reasons I still cannot put together we have not yet managed to create a cohesive community of developers. I believe Nokia has come up short there, too, in not providing the proper level of leadership (it's close, but not quite there). However, there is no real reason that a 100% community-led effort could not also be achieved.

There should always be solo software efforts IMO and I will not take anything away from the excellent work done by "coding cowboys". But as I and others have often noted, there is too much overlap and too many gaps between various projects. The solution is managment, although I realize many Linux coders shy away from what they perceive as restrictive bureaucratic hierarchies... so clear goals and communications are necessary.

I am hopeful that the council is one step toward solving the scattered software issue, because that's a BIG one. If we can build and sustain a continual flow of apps then many criticisms vanish. But it all comes down to leadership of one form or another. Without it we are individuals with isolated goals.