GNOME Bugzilla – Bug 713334
Zeitgeist integration
Last modified: 2018-10-28 22:26:06 UTC
---- Reported by adam@yorba.org 2012-04-17 15:59:00 -0700 ---- Original Redmine bug id: 5077 Original URL: http://redmine.yorba.org/issues/5077 Searchable id: yorba-bug-5077 Original author: Adam Dingle Original description: It might be useful to integrate Geary and Zeitgeist: http://live.gnome.org/Zeitgeist Apparently there's a Thunderbird plugin for Zeitgeist that we could look at for some ideas. ---- Additional Comments From geary-maint@gnome.bugs 2012-04-23 10:22:00 -0700 ---- ### History #### #1 Updated by Adam Dingle over 1 year ago Seif Lotfy from the Zeitgeist team has expressed interest in working on this. We first need to decide which of the following we want: * Geary depends on Zeitgeist * Geary optionally depends on Zeitgeist (we have a configure --enable-zeitgeist option) * Geary has a plugin which integrates with Zeitgeist Note that Zeitgeist is installed by default in Ubuntu, and has recently been proposed as a GNOME module: http://mail.gnome.org/archives/desktop-devel-list/2012-April/msg00031.html #### #2 Updated by Christian Dywan over 1 year ago I would personally tend towards built-in support because I've come to rely on zeitgeist and it takes care of details such as blacklisting and a format other applications can read without Geary-specific API. If it's in the engine, future engine API users could also use it implicitly without extra effort. #### #3 Updated by Adam Dingle over 1 year ago It turns out that Fedora 17 doesn't install Zeitgeist by default. Ubuntu does. I would rather not depend on Zeitgeist until it is universally adopted by major distros. So I think we should use an --enable-zeitgeist configure option for now. Later, we can move Zeitgeist support into a plugin or simply bake it into the Geary core if Zeitgeist becomes more universally adopted. --- Bug imported by chaz@yorba.org 2013-11-21 20:20 UTC --- This bug was previously known as _bug_ 5077 at http://redmine.yorba.org/show_bug.cgi?id=5077 Unknown Component Using default product and component set in Parameters Unknown version " in product geary. Setting version to "!unspecified". Unknown milestone "unknown in product geary. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
This would have to be a plugin, so depending on Bug 714883.
I just wrote up a tracking bug for the plugin system over at gitlab that collects all of the requirements for feature requests that should be implemented as plugins in the one place, so closing this bug in favour of that ticket: https://gitlab.gnome.org/GNOME/geary/issues/155