Case of the missing duck

In reference to Jean-François Fortin Tam and Luis de Bethencourt blog posts, I would like to post my side of the story.

The night before the incident (where the duck got lost), I was contacted by Vivia past midnight, after an awesome meal with the Collaborans. She asked me to contact JeFF and Rene if I see them and tell them to give the duck to Veronique.

Unfortunately by the time I met them, it was at the airport. At the canteen were discussing how to return the duck to Vivia (their intentions were good).

Later we met up with some Canonical folks and Emmanuelle Bassi while waiting for our plane. We were having some lengthy discussion and the duck was insightful as usual. I can’t remember who made a joke of frying him, but we found it very offensive but nevertheless the duck was still cheerful.

We then were on our way to board the plane, when suddenly we realized the duck was not amongst us. It was too late to go back. The only 2 who did not board the plane were Robert Ancell (Canonical) and Emmanuelle Bassi (GNOME Board & Mozilla)

Here is a a sketch of how it looks, sadly all ducks look the same to me.

The duck is very very missed…
Please help us find him

GNOME Clocks… almost there, help needed

GNOME Clocks has been in the works for 3 months now almost.  It is an implementation of the designs prepared by the GNOME Designers (see https://live.gnome.org/Design/Apps/Clock)

Together with Allan Day, we are mentoring the awesome Emily Gonyer for her SoC project as well as our free time superhero Eslam Mostafa. One of the nice (non-techie) things about GNOME Clocks is that it allowed us (the mentors) to identify patterns of healthy communication between designers and developers (I will be preparing a post about this soon).

The project is in a more or less good development state… Here are some screenshots of the current status.

Clocks view

Alarm view

Timer & Stopwatch views

We have been hanging around #gnome-clocks for a bit to make the development environment protective and focused for our new devs. Now I think we can move forward. You can find the code at http://git.gnome.org/browse/gnome-clocks

It is all written in python so it should be easy to just jump in and contribute to a “core app” for GNOME. We need some help with our bugs and most help with autofoo and hosting on jhbuild. So if you are up for it you can find me or allan on #gnome-design & #gnome-clocks and files bugs at https://bugzilla.gnome.org/buglist.cgi?quicksearch=product:%22clocks%22+

Have a nice weekend :D

A peek behind the Journal

After some silence, our research brain and user experience visionary Thorsten Prante is getting vocal again. For those of you who don’t know: he is mentoring Stefano’s current GSoC revamp of the activity journal.

In his post GSoC 2012 – Journal! Revamp!, he provides a nice list of example echos of the activity journal across the web from past to present before he goes on to explain why “in this project, beyond adding new features and types of activity footprints, we’re introducing a new way of showing the Activity Journal to its users.”

Zeitgeist: Playing with Berkeley DB

While doing some scaling optimization the Zeitgeist team decided to give Berkeley DB a try. But porting from SQLite to Berkeley is not easy. However thanks to the Berkeley SQL API porting one can use the SQLite queries. All we did was change the Makefile and add a new vapi (which is a straight copy of the sqlite3.vapi but with dbsql.h as a referenced header instead of sqlite3.h).

The results are not good though. But maybe its because we need to optimize the queries a bit more. Nevertheless you will find the code on freedesktop under the branchname berkeley tonight.

If you like a challenge, try to optimize the Berkeley optimization yourself, but be aware this is not for beginners and it may break you DB.

To build it make sure you get Berkeley db (on Debian and Ubuntu):

  • sudo apt-get install libdb-sql-dev
Get the latest Zeitgeist trunk code and create a new branch:
Download the following patch and apply (make sure you replace path to patch):
  • git am –signoff < /path/to/patch

Download the following vapi and place it into:

  • cp /path/to/vapi /usr/share/vala/vapi/dbsql.vapi
Configure and compile Zeitgeist:

  • sh autogen.sh –prefix=/usr/ –disable-fts && make

Now run it and make sure you are NOT using the default datapath:

  • ZEITGEIST_DATA_PATH=/home/seif/.local/share/zeitgeist-bdb/ src/zeitgeist-daemon –replace –log-level=debug –no-datahub

you will find a generate_events.py script in the zeitgeist tools folder as well as other benchmarking scripts. Feel free to poke around.

Zeitgeist in GNOME

Words can not express how happy the Zeitgeist team is to see our little project with the Empathy and Folks developers merged into GNOME and finally bring some neat Zeitgeist features to the user.

Thanks to everyone who has contributed to Zeitgeist, Folks and Empathy, including Collabora, Intel, Canonical and RedHat for their code and design contributions. I think the new design is very clean – check out Guillaume Desmottes blog post for screenshots.

P.S: Stay tuned for our next release (release within 2 weeks) which will log telepathy interaction events out of the box (as part of the datahub). If you want to start logging now check out our standalone logger from the datasources repo on freedesktop.

 

Zeitgeist scalability & efficiency bootcamp results

As Trever blogged yesterday, the Zeigeist team has been busy with tweaking the DB and the engine. During that process tools and benchmarks have been developed to make the tweaking and testing more interesting. Trever will be blogging about that tomorrow so make sure to check his blog.

Our end goal is  trying to scale the engine to be able to handle a few billion events just as fast as it can handle a few hundred thousand. While we are not there yet we managed to have some pretty nice stable results for the first iteration. A lot of results show more than 100% speed enhancement. In other words a lot of queries from our standard benchmarks now consume more than 50% less time to execute. Here are some graphs of our benchmarks.

Green indicates the 0.9 release

Yellow indicates the new trunk

Most notable performance enhancement is querying Zeitgeist with a specified timeframe (from data x to date y).

 

Same queries with an open timeframe also improved

 

We also have a copy of the Synapse queries benchmarked

The queries here are typical queries used to extract info from Zeitgeist. So right now the team is really happy with the initial results. For Synapse on my local DB (over a year old), all my synapse queries perform under 0.08 seconds. We still can get more out of this. The trick here was improving our indexes and our sql query generator.

Next month we will be going through another iteration.

 

 

On first interactions with open source communities…

I think it is safe to assume that as an open source project, striving to grow our community, we should make first interactions of new contributors with us a pleasant one.
So when commenting on a new contribution or attempt, we should try to either say something positive or don’t say anything.

  • If the contribution is  not useful then sugar coat you criticism. Because while the contribution might be bad, the person who did the contribution showed initiative to help out. We need to harvest this momentum and help integrate the person into the community.
  • If the contribution is useful then praise the developer. Making him feel useful. I learned from Lydia Pintscher to not only praise good contributors, but grant them autonomy to play around. This would allow them to master their craft, which will lead to them feeling like they have a purpose to stay.

What do you think?

Zeitgeist: Hello Freedesktop.org

For as long as Zeitgeist has existed it has been hosted on Launchpad. We made use of almost every Launchpad feature and grew to love Bazaar. The tight integration between Bazaar and Launchpad should be a taken as a grand example to the community, and the the team hacking on Launchpad and Bazaar has been always very responsive, supportive and above all incredibly approachable. The Zeitgeist team hosted all of its projects on Launchpad which made our development process very agile. I really need to thank the Launchpad team for hosting the project from its inception.

During the course of the last 3 and half years, Launchpad served us well and allowed us to handle:

  • ca. 748 unique bugs reported
  • ca. 231 merges
  • ca. 53 code contributions

We hope that many other great projects will find a valuable home on Launchpad. Without Launchpad, Zeitgeist would have not reached the level it has now.

But time changes and projects grow. The Zeitgeist team has a stable developer base of minimum 7 people putting several hours a week into Zeitgeist development and deployment. With these efforts comes the need of a vendor neutral platform hosted and serviced in a way that serves the interest of the project best.

Due to the deployment efforts being made to get Zeitgeist integrated with applications, our developers got more and more exposed to git. A stream of developers expressed their desire to work with us, however they were very uncomfortable or unfamiliar with bazaar and Launchpad, due to the popularity of git. That is something we do not understand in the core team, but still something we respect and will act on.

We couldn’t find a good direct replacement for Launchpad honestly, but since Bugzilla is something like the defacto standard for most people we decided to host Zeitgeist on Freedesktop.org (I must admit in-patch commenting in Bugzilla is sweeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeet).

We needed to wait until we finished the 0.9 release of Zeitgeist as well as narrow down the bugs to be less then 10 to make the transition as smooth as possible.

Now that Zeitgeist 0.9 is released, all our development will take place on Freedesktop.org and will be mirrored to launchpad, this means no code will be pushed directly to Launchpad, but rather Launchpad will pull from the git repositories. There the Zeitgeist Ubuntu guys (including me) will be syncing bugs and keeping everything intact. So bugs reported in Launchpad will be ported to FDO. But not the other way around.

We did not turn our backs on Launchpad, its just time for us to remove any barriers to getting the widest adoption of and contributions to Zeitgeist

On the road toward Zeigeist 1.0, FDO will be a great home for the project and we look forward to many great new contributions.

So please feel free to have a look at:
http://cgit.freedesktop.org/zeitgeist/

P.S: I would like to thank Trever Fisher and Manish Sinha for their efforts porting the code base.

Zeitgeist 0.9 and more…

Since the Zeitgeist team is kinda recovering from last month, and no one really feels like blogging, I am here to sum up what has been up the last 2 months. (Also I think a blog post from my side is long overdue)

Privacy Manager

A lot of users are scared of “logging”, and since Zeitgeist is considered an event logger, we ended up having some users trying to disable Zeitgeist all in all breaking Unity searching and so on.
Fact is, if you want searching to be sorted properly, the search provider needs to know what files you recently or frequently used. Also some people want to have some of their stuff logged and others things not (blacklisting folders).
Activity Log Manager which we already had developed in python last year has been ported to Vala. This nifty tool allows you to blacklist application, folders, mime-types from being logged as well as the option to delete parts of your log. The port to Vala happened so we can patch it into the Settings Manager to give it an more integrated feel with the System in Ubuntu and Dawati.
It has received very good reviews and there are some very interesting new development efforts/ideas in the make (right now one in a state of flux which I hope I can get out of soon).

Here are some screenshots of the current stand of ALM

(dialog for deleting history)

(dialog for blacklisting folders and file types)

(dialog for blacklisting applications)

Zeitgeist 0.9

Last year we started porting Zeitgeist from python to Vala. Mostly for the sake of easier deployment as well as improving startup time. As a side effect also memory consumption decreased and during the development more optimizations have been made.
It was a very intense operation sponsored by Collabora and Canonical as well as the awesome unpaid Zeitgeist developers.
So a big thanks goes to Collabora, Canonical, Michal Hruby, Siegfried Gevatter, Manish Sinha, Mikkel Kamstrup, Trever Fischer, Stefano Candori, Moritz Neeb, as well as everyone else who tested Zeitgeist, provided bug reports or contributed in any other way.

We released some alphas and a beta. But now the real deal is out. We still have some nice optimization in the queue that we will release with the next Zeitgeist version. So don’t hesitate to try it out.

Things I have been up to…

I have been absent from blogging a bit :(
So here are the highlights of the past month:

  • GNOME Clocks is shaping up nicely, a nice example of prototype becoming product. It is a very nice experience for me in developer <-> designer communication. Something that I have been working on with Allan Day, Jakub Steiner, Garret LeSage and Hylke Bons. (I will wrap up the code and push it up somewhere tomorrow). I will be giving a talk about this experience along with Allan Day (including prototyping) at FOSDEM.
  • The prototyping spirit within the GNOME design team is growing. After playing with  Jakub Steiner’s HTML/JS prototype I got inspired to play with HTML/JS too.
  • The Zeitgeist team set up a nice TODO list for the next release and beyond (blog post coming soon). Some awesome commit by Michal Hruby managed to reduce the memory consumption by a big chunk by “optimizing allocations of variants”. Our bug list for the next release has only 4 more bugs open so take a stab if you dare…
  • Thanks to Collabora, I got a N9. After ruining my SIM card trying to build a Micro-SIM I ended up running to O2 getting myself one from there that got activated after 30 minutes. Now I am playing around with QML again.
  • I started playing with Plasma Active and have very mixed feelings about it. Tech wise its pretty good, but I don’t find it intuitive enough like GNOME 3 or Unity on a tablet. I seem to be missing the concept of activities really.
  • I started getting into XBMC and now Ubuntu TV is announced… will be trying it out soon.
  • I am addicted to Every Detail Matters.