Re: Tracker, Zeitgeist, Couchdb...where is the problem ?

On Tue, 2009-08-18 at 16:48 -0400, Matthias Clasen wrote:
> I think this recent discussion about tracker as a gnome module is
> somewhat backwards. I don't think it is leading us anywhere to talk
> about ontologies and rdf and events and timelines and metadata stores
> and kernel apis before we answer the first question:
> What is the user problem that we are solving here ?
> Can that be described in a paragraph ?
> And if it can, is it something that a 'regular' user would recognize
> as a problem he has on his computer ?
> Once we have the problem scoped out, we need to look at the user
> experience we want to aim for in solving it. Will it be a single
> search-for-everything dialog ? A query language ? Tagging everywhere ?
> After that, it might be possible to evaluate whether tracker,
> zeitgeist, couchdb or something else can be part of the
> implementation...
> Matthias


Tracker: Something which sounds cool. It for sure will help managed data
for middle-organized users and for sure will make a great videos (to be
honest - spinning cube had done much more PR then carefully designed
UI). I'd rather use it when (if?) it will be ready.

My only concern is a concept of centralized database which may get
corrupted (with ALL of metadata) [besides that it is not done yet]. I'd
much more'd like to see for example DBus API (or other) to support
notify signals about data etc. with tracker only caching the data to
query (so any time I can simply remove .tracker to rebuild the cache).
Of course - if tracker will provide library to
support .config/epiphany/bookmarks.trackerdb and integrate it with the
main cache - I'm fine (as long as I can remove one database lefting
others intact).

On the other hand it will not help probably most of the users which have
save-all-on-desktop mentality.
If there will be (Linux-specific) inotify extention to NFS - great.

CouchDB: I don't really think it is needed. I'm not convinced - how many
times do I need to change email client. Without proper definition of
storage (such as FirstName vs. firstName vs ...) it won't help and the
proper definition can be made w/out introducing networking (TCP/IP as
IPC is not nice hack IMHO unless you want RPC).


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]