Hi, ext JD Zheng wrote: > As far as I understand, UI/UX part is basically the most important > component(s) that MeeGo is creating by itself, but now it sounds like > MeeGo will NOT design UX by MeeGo community, at least not most, instead, > it will incorporate UX components from "upsteam" like Intel UX or Nokia > UX or others.
You seem to be mixing streams. MeeGo is upstream and whatever implementation Nokia, Intel and others do based on MeeGo will be downstreams. I agree that currently, before the MeeGo UXs have been published, the waters are not clear but have no doubt about the role the MeeGo project will have maintaining and pushing its reference UX. Then MeeGo downstreams will probably customize their own UXs. Some of those customizations will be limited to preferences, themes, graphics and other details actually not contesting the upstream UX development. Some might be heavier customizations but still without having the vendor willing to challenge the upstream plans. But of course it is expected that the vendors bringing MeeGo based UXs to real users will have opinions and enhancement plans, and some of them will directly contribute or contest the upstream plans. As it usually happens. > My question is whether MeeGo will have its own UX teams/projects to > develop UX by itself or decide which UX will be chosen as MeeGo > *official* UX. Each MeeGo platform and application component needs to have teams and collaboration channels publicly documented. Anybody should be able to go to the right place and convince the right people with words, mockups, code... Anybody should have a chance to become a maintainer or responsible of an area based on own merits. -- Quim Gil open source advocate MeeGo Devices @ Nokia _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
