MeeGo's "big reveal" mentality hurting the project?
Carsten Munk, maemo.org distmaster and MeeGo contributor, has asked a question many have been thinking: does the desire for a large splash - a "big reveal" as Carsten puts it - hamper, now and in the future, the openness and viability of the MeeGo project? This desire is understandable for closed product launches, but was always the biggest impediment to true community collaboration on Maemo itself. However, the noises made by both Nokia and Intel - both of whom have a lot of experience now with open source development - at the launch of MeeGo were promising. Carsten doesn't think they're walking the walk, though: We're not working in the open like we're supposed to - even though as has been said - Intel, Nokia and we all know how to do it! But when there's a big reveal mentality active, the mode of the people participating switches to internal/private development, even if you are only tangentially related to the object/UX being revealed. Carsten poses three questions to MeeGo's Technical Steering Group:
Has this mentality been hurting the project to date?
How will they prevent it continuing after the user interface is unveiled?
How will they prevent it the next time the commercial requirements of a "big reveal" occur?