Gerade rotierend:
Und am Mittwoch abend dann live:
Freu.
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.
This list is of course not complete. Also see LibgnomeMustDie.
Feel encouraged to add your issues.
NOT COMPLETED (”Reopened”) now that we also check external deps and the Mobile set:
DONE.
COMPLETED.
NOT COMPLETED.
NOT COMPLETED (Progress compared to 2.27.1: 22->15).
Please share experiences and knowledge.
NOT COMPLETED (Progress compared to 2.27.1: 15->12).
Please share experiences and knowledge.
NOT COMPLETED (Reopened):
NOT COMPLETED. Evolution schedule currently under discussion.
A Git branch is available.
IN PROGRESS. WebKitGTK+ has been proposed as an external dependency.
See d-d-l for the status.
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.
NOT COMPLETED.
According to “jhbuild rdepends hal –direct” the following modules still depend on HAL:
Not yet covered in the stats but required to fix are also:
Nice to fix:
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.
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.
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 maemo.org 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 maemo.org Brainstorm for feature requests that deal with a broader scope.
Today I have released a GNOME release schedule proposal for 2.27 and 2.29 (please keep discussion streamlined on desktop-devel mailing list instead of e.g. the comments section of this blog).
GNOME 2.30 will be GNOME 3.0 (if it’s considered to be ready in an early 2.29 stage - else 2.32 will become 3.0), as proposed by the GNOME release team at GUADEC 2008 (Remember some blog entries and press coverage?).
All the additional stuff (”additional” compared to former schedules) listed in the proposal is technical and under the hood, as this schedule proposal also covers streamlining of the platform by getting rid of deprecated modules.
Note that such a “boring” platform cleanup is not meant to completely define GNOME 3. This schedule proposal is just a proposal for being a part of what will be called GNOME 3.
By purpose, the schedule proposal does not cover any potential UI changes, any potential redefinition of GNOME, any blingbling UI, any complete rewrites from scratch or any implementations of a semi-working kitchen sink. If you are interested in such fields and topics, I am not the person to talk to. Please see other more generic threads about GNOME 3, especially Vincent’s d-d-l posting and blog post and Lucas’ blog post.
Also, this plan does not cover by purpose stuff like gnome-shell vs. gnome-panel, gnome-zeitgeist, or Vala, PolicyKit, PackageKit, etc. Discussing them is recommended, but
On the other hand, gconf vs dconf is also not yet covered by this plan, but definitely crucial to discuss.
So… if you are also interested in cleaning up your favourite desktop and getting it to the next level: Join the discussion (e.g. about the future of GNOME’s a11y), or take a look at the status overview and provide patches in GNOME Bugzilla. Help is highly welcome, especially when it comes to getting rid of libgnome and libgnomeui. Code needs to be written here. Soon.
I didn’t blog about our beautiful 2.26.0 release as I’ve been busy with relocating and job, but I must mention my heros for 2.25 - those brave folks that provided a lot of patches to clean up and helped on the way to GNOME 3. This is definitely not a complete list, but names like Thomas Andersen, Cosimo Cecchi, Luis Menina, Maxim Ermilov and Saleem Abdulrasool come to my mind. Thanks guys, you rock!
There’s currently only 5 open non-moreinfo Apps/Platform tickets left with version field set to a version earlier than 4.0.
That’s quite cool because it means that there’s nearly no non-updated bugs left about Bora or earlier - stuff that’s not being worked on anymore anyway. Having an up-to-date bug database is important to see what issues are still relevant, so help is welcome to check whether tickets filed against Chinook still apply to the latest Diablo version (5.2008.43-7) by simply adding a comment and updating the version field.
But even more helpful is to check if tickets still apply to Fremantle. This can be done for some Platform issues by using the Fremantle SDK alpha.
There’s currently 38 open Platform tickets with the version field set to Fremantle, but this also means that there’s 267 open Platform tickets with version field not set to Fremantle.
The maemo.org Bugsquad is waiting for you - even if it’s only one small bug that you check, it definitely helps improving the platform and is appreciated! 
Very late to blog about this, but some people might have seen that I’ve created a few more Target Milestones (5.0-alpha, 5.0pre-alpha) instead of the generic “Fremantle” one when the Alpha SDK was released. This should make everything a bit more transparent by having exacter information on when a bug was exactly fixed.
More news to come in the next weeks, e.g. a schedule for 2.27.
“Und wenn Du schon mal Deine neue Mitbewohnerin sehen willst, schau Dir kurz das neueste Musikvideo Deiner Lieblingsband an.”
Waschmaschine kaputt. Jacke kaputt. Fahrradschloß kaputt. Das erfreut die Volkswirtschaft, denn dann wird gekauft!
Das T-Shirt zum Song.
(gefunden im Blog der sehr geschätzten la_rayis.)
Auf der Suche nach weiteren Aktionen neben Atombombenexplosionen und hustý Lichtzeichenanlagen gefunden: Violated subconsciousness (Znásilněný Podvědomí). Schon einige Jahre alt, but still Ztohoven at its very best.
Sicherheitsdienstmann 1 am Eingang sagt Sicherheitsdienstmann 2, dass er mich nicht untersuchen brauche, da ich doch Mitarbeiter sei. Mir neu. Falls jemand Waffeln oder Drogeln in die örtliche Großraumdiskothek schmuggeln möchte: Bitte Kommentar hinterlassen.
Ja. Und allgemein Menschen, die den Mut haben, dies zu fragen (und es scheinen mehr zu werden) anstelle von “Wie geht’s”, “Wie heißt du”, “Was machst Du”. Denn was interessiert’s mich?
