On Do, 2011-03-31 at 14:38 +0100, [email protected] wrote: > Hi, > > > -----Original Message----- > > From: [email protected] [mailto:[email protected]] > > On Behalf Of ext Patrick Ohly > > Sent: Wednesday, March 30, 2011 9:57 AM > > To: [email protected] > > Cc: [email protected] > > Subject: Re: [MeeGo-dev] migration (back) to EDS - contacts and > > calendar > > > > * In the past, meego.com was a dumping ground for technology > > developed and used elsewhere. Often it wasn't properly tested > > there. I have heard arguments that this testing can't be done > > without the apps in MeeGo using the middleware. IMHO this is > > just a lame excuse for not doing proper QA on middleware > > compoments, and leads to situations as with > > Dialer/libcommhistory were an app developer would have to stop > > working on his main task to investigate problems in someone > > else's code. Not cool. > > If no bugs were filed and no questions asked by mail, any efforts made > to take that technology into use are indistinguishable from not even > trying.
Trust me, I have tried. I filed bugs and exchanged emails. When that didn't help because my peers didn't have time to reply, I escalated to managers and participated in meetings, just to get some attention to these problems. A lot of work for very little gain, and I don't think any app developers deserves to be blamed for not investing a similar effort when running into issues. > I hope collaborative processes in MeeGo will be more transparent in the > future. I hope so too. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
