I believe the investment on keeping Qt up to date on the n900 to be the best way to keep our "devices" alive. We need to make sure that whenever Nokia decides to work on Qt4.8 that the n900 will get that too. More important even is to keep the qt mobility "backends" for the n900 alive and kicking.

Just one example of something that the developers in the community could work on: enhancing the qt mobility contacts backend to support "contacts grouping", "custom fields", "field labels" and some other features that Qt Mobility can support but the backend for the n900 can't. We are bound to see "contact front ends" written in Qt (for meego or not), enhancing our backend would allow us to greatly enhance the "phone side" of the n900 by back porting them.

First, second or last... probably not as important as continuing to be "an easy/viable target" for qt application developers. I am sure that if we had qt4.6 on diablo we would have seen many more applications ported to it. And with meego we will have even more qt applications floating around. The autobuilder will also be critical.

If you are, I am right there with you. If we don't believe that there can be a future for maemo after 6 months I can't see much of the point.