Hi, ext Glen Gray wrote: > > By openness I mean > code available, for me to download, compile and work on. Some code was > released for Day 1 as regards the base operating system but the project > is still largely being designed and developed behind closed doors. The > plan is for this to move to an open model which includes the MeeGo > community. What I'm asking for is timelines on when this will happen.
The plan is to have in few weeks a first complete MeeGo release followed by a roadmap to work on the next release. Once this is out the MeeGo project shouldn't have any obstacle to have all the daily work and routines in the open. There might still be some areas under the shadow, but always related to new developments e.g. imagine the arrival of a new cool UX category or key platform feature. Once they are released they go to open business as usual. All this is related to two main factors: - One that is quite unique now: two big teams having to sync on 1001 little things before going public & common. - One that will be around basically always: marketing factors making company X or even the MeeGo project itself to go for a sound release instead of an open development since the first line of code. -- Quim Gil open source advocate MeeGo Devices @ Nokia _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
