Hi, Glen Gray wrote: > You're confusing a product release with openness. 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.
I'd like there to be a clear distinction between meego-the-code-project and meego-the-distribution. Openness for a distribution means a clear path for packaging & distributing one's software. Openness for a code project means, as you suggest, code available to download, build & deploy, and a clear path for proposing changes back upstream. We have a way to go for both, but perhaps thinking of these as two different things will help identify the top priorities in openness short-term? Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
