On Mo, 2011-04-04 at 09:10 +0100, Patrick Ohly wrote:
> On Fr, 2011-04-01 at 10:57 +0100, Mathias Hasselmann wrote:
> > Am Dienstag, den 29.03.2011, 16:35 +0200 schrieb Patrick Ohly:
> > > Let's be more specific about identifying work which needs to be done.
> > > I've put together some thoughts here:
> > > http://wiki.meego.com/Architecture/planning/evolution-data-server
> > > http://wiki.meego.com/Architecture/planning/evolution-data-server/QtContacts_storage_plugin
> > > http://wiki.meego.com/Architecture/planning/evolution-data-server/eds-improvements
> > > 
> > 
> > Hi Patrick,
> > 
> > Thanks alot for those wiki pages.
> > 
> > Good approach to collect rationales in the public. Will you take care of
> > updating the pages, or shall we do this together somehow?
> 
> I'll do another pass over the pages today (after catching up with
> email), but then they could also be maintained together.

Changes:

Calendar - removed part about past experience with it, added
KCalCore-EDS (empty place holder at the moment)

Contact - removed the offending (and unintentional) "clue code" comment
on QtContacts-Tracker ;-), clarified libfolks and moved it from "opens"
to "plan"

Email - clarified that QtMobility/QtMessaging remains the main app API,
added "rewrite QtMobility Messaging to use Camel, rewrite mail app to
use QtMobility" as another option

EDS improvements - clarified the change tracking/view part

I would have loved to link to the public information about each
component mentioned in the Wiki, but that would take too much time right
now. If anyone wants to make the pages nicer, feel free to add links.

-- 
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
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to