> Let me rephrase this question: Who on this list would be willing to step > forward and help maintain Qt Jambi?
You might need to start with "who on this list is *capable* of helping to maintain Qt Jambi?" Judging by the activity on this list, there's hardly anyone involved with Qt Jambi - a few dozen names maybe? Of those, almost all are users. It's only the Trolltech guys who actually know the in depth technicalities about the project. I don't think anyone else in the community is likely to be able to fill the void those guys will leave behind when they get moved on. I suppose the starting point might be for the Trolls to write some in-depth white papers about how it all works so some other people can pick it up and work with it. Is that happening? Even if it does, it won't help with Qt 4.6 very much. Who is going to know the in depth details of the 4.6 implementation updates, to the point they can say "...this affects Qt Jambi in this way, so we'll need to reimplement this part of Qt Jambi using this technique..."? Only the Trolls. Retaining and updating that level of knowledge is a full time job. I think that's the point Nokia don't understand. They've done the usual "let's open it up and let the FOSS community do the work for us" thing, without realising that large, complex projects still need money, and therefore business, behind them. That's fine if you're a kernel supporting a market for servers, or a DB supporting a market for applications, or an IDE supporting a market for developers. But a toolkit/language combo with hardly any users? It's not going to happen. Wishing and hoping that my arguments are shot down in flames and I'm comprehensively proved wrong... _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
