Am Montag, den 07.03.2011, 15:56 -0800 schrieb Arjan van de Ven: > On 3/7/2011 3:33 PM, [email protected] wrote: > > > > Let's define what we want, create a Meego-standardized test bench, make > > we can do many things that delay MeeGo moving forward. > We're not going to do that.
You won't move MeeGo forward by making arbitrary decision out of your guts. Without having numbers. Without discussion. With spreading food. With insulting people. Others tried that. They failed. It's an architecture's task to define architecture goals. Based on research. Based on numbers. You didn't present any numbers so far. You didn't define performance goals yes. Without such information it is impossible to meet your performance goals. We don't have mind reading machines yet. > Time has come and gone for this to be a discussion; this is a decision. The big question is: How could it come that far? Was this a lack of communication? A lack of leadership? Even more: What will be done to prevent such problems in the future? Actually: What makes you sure that EDS will solve this problems? WHERE ARE THE NUMBERS backing your decision? Did you roll dices? Or how did your decision process work? Ciao, Mathias -- Mathias Hasselmann <[email protected]> http://openismus.com/ _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
