Purpose:

GNOME Activity Journal is not a File Browser but an Activity Browser.

It uses the Zeitgeist Framework to display what you did and introduces a
better way of quickly finding the things that you were doing.

 

Target: desktop

 

Dependencies:

Zeitgeist (external)

PyGTK

Python 2.5

Cairo

DBus

Pango

 

Resource usage:

Bug tracker: http://bugs.launchpad.net/gnome-activity-journal 

VCS: http://code.launchpad.net/gnome-activity-journal 

Releases: http://launchpad.net/gnome-activity-journal/+download 

 

We are waiting on GNOME git approval for a new repository at which point all
resources will be moved to the GNOME Infrastructure.

 

Adoption:

Packages (at least) for Debian/Ubuntu, Fedora, openSuSE

 

GNOME-ness, community:

GNOME Activity Journal is a pure community effort with the only commercial
backing being our last GSoC project and the Zeitgeist Hackfest in Bolzano
2009. Right now, we are 2 core maintainers, 4 developers, and 2 designers.
We've striven to be open and visible in our development. This has also led
to a steady inflow of new contributors.

 

Other notes:

...

 

Status and future:

The Journal is able to display all events of applications currently
supported by Zeitgeist, such as:

- Totem 

- gedit

- eog

- Banshee

- Rhythmbox

- Tomboy

- Firefox

- git

- bzr

- Telepathy

- vim

- ... Anything that pushes into Recently Used

We will provide a data-providers setup and management tool with our next
release.

 

We are working to solve the performance issues on startup, caused by the
amount of data that is being requested over DBus from Zeitgeist. Our next
release should provide a proper solution.

 

There is a more detailed plan attached to our 0.3.4 release announcement
[1].

 

--

On behalf of the GNOME Activity Journal team,

Thorsten

 

[1] https://lists.launchpad.net/gnome-zeitgeist-users/msg00048.html 

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Reply via email to