On Mon, 2008-09-08 at 17:26 +0800, Yang, Lei A wrote: > Hi, Jimmy, > > I am Moblin QA engineer in SH. I am investigating the component "Content > Manger" from QA perspective. > > I reviewed your test design doc and log some questions here: > > 1) The Tracker is an open source project. Are we going to merge/integrate the > latest version of “Tracker” into Moblin 2.0 in future? I found each of > “tracker” components is going to be modified in the doc. And I am afraid the > merge/integration will become very hard. >
Yes, we'll try to keep to the latest version, if there's a need, but the current version 0.6.6 is pretty stable. The modification to the tracker component is very light, only adding 2-3 methods, we are not doing any heavy changing of the component at all. > 2) When multiple tags of content files will be added? How are the tags > updated by user? > Multi-tagging is added. There are 2 sets of "tags", 1 is metadata extracted by Tracker like image size, mimetype, duration, etc, and those cannot be updated through user. User can add and remove keywords to the files using the interface we expose (or through Tracker) for their application-specific tagging. > 3) D-Bus searching interface will not be exposed to application developers, > right? (P3, Sec4, Sub-Sec3) > Furthermore, which part of interfaces will be exposed to application > developers and which part will not? > It will be still exposed (but through Tracker), not content manager. Other application might still interact with Tracker, in fact, all other Tracker-aware applications (like Deskbar, Nemo) communicates with Tracker through D-BUS, otherwise, those application will break. Content Manager will be just another lib that runs on top of tracker that expose easier-to-use APIs. The intention is that Moblin applications should call the Content Manager's interface. The D-BUS interface in the design doc is what Tracker exposes. The Content Manager is just a C library. > 4) Whether “the sample test app” (P3, Sec4, Sub-Sec4) is looked as the part > of formal release? Namely, do developers expect QA test sample test app as > product? I do not think the sample test app will need to be QAed, it is just sand-boxing app that shows people how to use it. > > 5) How about your unit test plan? Do you want to use any automatic unit test > framework? > I don't have a unit test plan yet, this is something that we can discuss in the QA session that May and I will be setting up this week. > Thanks, > Lei Yang > > > > > > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jimmy Huang > Sent: 2008年9月4日 8:42 > To: dev > Subject: [Moblin Dev] (Re-attached) Content Manager Design Draft Attachedfor > Review > > (Re-attached with doc) > > Hi, All, > > I completed a design document draft of Content Manager for Moblin 2.0, > which is part of the Application and Framework infrastructure. It is > based on Meta Tracker (Trackerd) and SQLite. > > Please review the document and provide feedbacks, or comments are > welcome. Thanks. > > Content Manager project is hosted here: > > http://test.moblin.org/projects/content-manager > > Jimmy > _______________________________________________ dev mailing list [email protected] https://www.moblin.org/mailman/listinfo/dev
