Archive for June, 2009


Monday, June 22nd, 2009

Gerade rotierend:

Und am Mittwoch abend dann live:


GNOME 3 status.

Saturday, June 20th, 2009

This is an update about cleaning up the GNOME stack for GNOME 3. This has also been posted to the desktop-devel mailing list.

This status report refers to the aims listed in the 2.27/2.29 schedule and the automatic statistics available (which now also covers the Mobile section, hence results can be worse than last time).

Maintainers: I have listed available PATCHES AWAITING REVIEW.
Please take a look if your module is listed and review/commit NOW so the changes can receive enough testing for 2.28.

THE PROBLEMS: What migration paths are missing?

This list is of course not complete. Also see LibgnomeMustDie.
Feel encouraged to add your issues.

ZERO modules with Glib-Deprecated-Symbols

NOT COMPLETED (“Reopened”) now that we also check external deps and the Mobile set:

  • Still to do: gconf-dbus, evolution-data-server-dbus.
  • External deps to do: dbus-glib, hal, libnotify, mono. PATCHES available: dbus-glib, libnotify. FIXED: farsight2, libnice, poppler.

Officially ANNOUNCE libglade as deprecated in favor of GtkBuilder


Less than 35 modules depending on libglade.


  • low: 25
  • average: 5 (dasher, gnome-media, gnome-panel, gok, zenity)
  • complex: 2 (gnome-control-center, evolution)
  • PATCHES awaiting review/commit: gnome-control-center, gdm, gnome-nettool, gnome-mag, gnome-media, gnome-menus, gnome-panel, gnome-session, gnome-system-tools, gtkhtml, sound-juicer, zenity, tracker. Maintainers please review/commit.

Clear a11y plan and schedule for 3.0


Less than 12 modules depending on libgnome

NOT COMPLETED (Progress compared to 2.27.1: 22->15).

  • low: 10
  • average: 4 (Evolution, gnome-media, yelp, anjuta)
  • complex: 1 (gok)

Please share experiences and knowledge.

Less than 12 modules depending on libgnomeui

NOT COMPLETED (Progress compared to 2.27.1: 15->12).

  • low: 9
  • average: 2 (Evolution-Exchange, gnome-panel)
  • complex: 1 (Evolution)

Please share experiences and knowledge.

ZERO modules dependening on gnome-vfs


  • average: 1 (gst-plugins-base)


  • low: 8
  • average: 7 (gnome-control-center, evolution, gedit, metacity, glade3, gconf-dbus)
  • complex: 2 (gnome-games, gnome-media)
  • PATCHES awaiting review/commit: gnome-control-center, gedit, metacity, yelp, glade3, policykit-gnome

Evolution-Data-Server must be migrated to D-Bus by default

NOT COMPLETED. Evolution schedule currently under discussion.
A Git branch is available.

WebKit status report for 2.27.5

IN PROGRESS. WebKitGTK+ has been proposed as an external dependency.
See d-d-l for the status.

Evolution to get rid of Bonobo by 2.27.3

NOT COMPLETED and postponed for 2.29.1.
See KillBonobo for the status. Testing and reporting bugs is HIGHLY welcome. See Matthew’s blog for more information.

Complete migration from HAL to DeviceKit-* by 2.27.3

According to “jhbuild rdepends hal –direct” the following modules still depend on HAL:

More important stuff to take a look at:

Not yet covered in the stats but required to fix are also:

Nice to fix:

GNOME Showstoppers

For GNOME 2.26/2.28, I have posted a Showstopper Review earlier this week. Feel free to take a look, test & help out, get things done.

Other activity

Kudos to the progress that has been made so far!
Getting rid of Popt is basically DONE.
ZERO modules dependening on Esound is DONE.
ZERO modules dependening on Gnomeprint is DONE.
The Website revamp front is rocking, and the Documentation team also has some great momentum currently.

Mozilla/Maemo Danish Weekend

Sunday, June 7th, 2009

Haven’t seen much blogging about the Mozilla/Maemo Danish Weekend yet – here we go.

After meeting at the airport with Lauri Võsandi (who works on Bittorrent support in Canola as part of Google’s Summer of Code) and quickly getting a shower in the hotel, we went to the café of the IT University (the host of this event). Nice to see some familiar faces again plus those that you have only seen pictures of before. That evening I mostly had discussions about technology and politics (hey, there were also “real” Danish students around and not only Mozilla or Maemo hackers – there seems to be a life out there!).

Saturday was opened by Mozilla’s William and Nokia’s Quim in the one lecture room that we had. Many people though also spent their time in the large hall room (lovely architecture!) for sitting, hacking and discussing together. There were talks about Fennec (Mozilla’s browser for smaller devices), Canola, Fremantle Stars and Mer.

Coffee, tea, great sandwiches for lunch and sweets for the afternoon were provided (though the coffee was removed one hour before lunch – this decreased productivity for many people). ;-)

In the evening after picking up some All you can eat we met in a bar in the center to have some beers.

On Sunday we had about 25 quick lightning talks, sometimes just a few words explaining “I work on/I can help you with…” but very helpful. It was also a pleasure to talk to some Mozilla folks that were curious about how it is to deal with a big company that (slowly) moves to Open Source.

All in all, a very good and helpful weekend.

Work related on that weekend I introduced an “upstream” keyword in Bugzilla (had that in mind for some time now), discussed the clutter blocker with Niels and Soumya, fixed some database sanity check issues, triaged lots of bugs, and started to concentrate more in triaging bugs & feature requests for Fremantle. So if you are subscribed/have voted for requests that interest you you might have received some “Fixed in Fremantle” bugmail but especially for feature requests I have often set the Version field to Fremantle which basically means “This is not fixed yet”.

Still thinking about how to deal with bug reports about API documentation (which is directly handled by the corresponding package developers and not by the Documentation folks) – I more and more tend to add a “docs” keyword and to keep those bugs in the corresponding (code) product instead of moving them to the “Developer Platform > Documentation” product so they remain visible for the developers. Comments?

Looking forward to the soon-to-come Brainstorm for feature requests that deal with a broader scope.