Hi Nicola, Just answering parts of the questions related to this thread. I'd like to take the N900 questions and answer in a different thread but first in the morning.
2010/7/7 Nicola Mfb <[email protected]>: > On Tue, Jul 6, 2010 at 9:13 PM, Carsten Munk <[email protected]> wrote: > Sorry if some questions seem hurting or stupid, but to the casual > reader it seems meego is *actually* internally driven, and is going > only to be a *base* OS strongly adapted to vendors needs to put their > closed components and providing unified api for developing partner > companies with the objective to sell more hardware and not an "open > revolution" as guessed from the meego faq. It is my strong belief that it isn't so - from everything I've seen, people do want the open source in MeeGo. Reality always pokes it's head in, which is why there are some closed parts of the N900 image (SGX drivers is one of them). But 99% open is better than 43%, like Maemo was. If you'd like to discuss this part, let us discuss this in the morning thread :) Do keep in mind that this thread is about developer involvement and ability to contribute and participate in the already open source MeeGo project. MeeGo is open source. The plea is about making it possible for people to participate or even just watch - giving the opportunity to them to contribute by having your team work in the open. > Would a random contributor be able to get answers to simple questions? > Many time you have "please respect peoples working under NDA" or in > the worst case the silence. Sometimes it is possible to get answers to questions, otherwise the hope is that open development will let you dig into old logs, archives, meeting logs, source code, etc, to let you find the answer yourself. And then you help document it for future questions. Best regards, Carsten Munk _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
