Tales of software craftsmanship

Tales of software craftsmanship

Running KDE SC on the next big thing

A week ago I got a Tegra 2 based 10.1″ Android tablet called Point of View Mobii Tegra. Its brand is just badge engineering, the same device is sold throughout the world under a variety of other names, including Advent Vega, Smartbook Surfer 360, WSL Xvision and Dreambook ePad P10, and apparently it is based on a reference design by Nvidia. The hardware is quite fast but the bundled Android software feels, well, a bit weird. I say “weird” simply because Android 2.2 is an operating environment for handsets rather than for tablets, and while it’s fast and it does the job, it is hardly the best tool for the job: compared to a smartphone’s 3 or 4 inches, 10 inches of touch screen provide a lot more space for all sorts of touch-friendly widgets and a call for a somewhat different user experience. This is especially noticeable when looking at common widget placements on the screen: Android often expects you to hold a smartphone with one hand, and places relevant widgets close to where your thumb should be. These kind of assumptions fail miserably when running Android on a 10″ tablet.

Anyway, like a true fan of KDE my priority was trying to figure out if there’s a way to get KDE SC running on it in some form. This was remarkably easy, thanks to the efforts of some MoDaCo community members, who provided an Ubuntu-based rootfs and a kernel. All I had to do was figuring out how to flash the device with Nvidia’s tools the right way. After that it was just a matter of installing some KDE software from Ubuntu’s armel packages.

My PoV Mobii Tegra (Advent Vega) running KDE SC 4.6

So the point of this post isn’t technical, it really didn’t take much to have a KDE desktop running on the Tegra tablet. It’s just a bit of proof that it can be done.  The user experience with the regular Plasma Desktop is surprisingly fast but overall not very good, and Plasma Netbook doesn’t make it much better. The UI feels too small and is not well suited for use with fingers. I suppose it would work somewhat better with a stylus, but that’s not what these kind of tablets are about. I haven’t had the chance to try Plasma Mobile yet, but even if it brought a huge improvement, I would also need finger-friendly apps.

Right now I can see that there’s a vacuum in the tablet market as far as operating environments are concerned. Android is obviously late to the party and WebOS and MeeGo even more so. Could this be an opportunity for KDE?

A sensible beginning might be designing a set of finger-friendly widgets and a Plasma workspace optimized for 10″ and 7″ tablets, and defining a list of UI guidelines for tablet-friendly KDE apps.

The importance of mentorship in Google Summer of Code

I’ve been asked by Lydia, the ultimate social media ninja of KDE and Amarok’s community manager to put together a brief post about my opinions on the importance of mentorship and organization in a student outreach program such as Google Summer of Code based on my experience as a GSoC student. I’ve been a GSoC student twice and a volunteer Summer of KDE student the year before that, so I hope I can provide some insight from a student’s point of view. The KDE GSoC admins&mentors team has done a terrific job so far, and I’m very satisfied with their performance. Thank you, GSoC admins&mentors!

I have tried to gather a list of situations where as a GSoC student I could greatly benefit from good mentorship:

  • Planning. While I surely did have a vision and a somewhat clear direction where I wanted to take my project, I wasn’t always sure about the details of the implementation, and specifically how and where to tie my stuff in with the existing codebase. My mentor helped me a lot with planning and design, and we shared a design document in Google Docs that was to be kept up to date for the duration of the GSoC program. I believe that while the strong motivation of a student pushes the project forward, the direction has to be overseen and frequently discussed with the mentor to make the student’s project useful for the organization and to avoid rookie mistakes when laying out the design.
  • Code review. When I started with GSoC I was very much a noob about Qt and I didn’t have a lot of coding experience. Regular code review by my mentor and the other team members was very important to improve the quality of my output. I believe that at least occasional code reviews in the first weeks of the GSoC program (unrelated to the final review before merging the branch) can straighten out important details before they become serious issues later on.
  • Team interaction. When I started with GSoC I didn’t know anybody in the Amarok team. I didn’t know anything about the social structure and most importantly, I didn’t know which team member I should poke about specific parts of the codebase. In those times it was very important for me to have someone (mentor, community manager) to ask questions such as “Who has knowledge about this bit of code? Can I make change X on code Y or would that make person Z angry?”. I did ask those questions pretty often.
  • Technical questions. The life of a GSoC student can be pretty intense, between coursework, exams and coding. For this reason, while my output was quite consistent, coding could happen at any time of the day. I’m very grateful that my mentor Nikolaj Hald Nielsen was almost always available to answer my questions, and when he wasn’t, there was a clearly appointed second-in-command I could go to. This is perhaps the most important entry in this list. Rules such as “the whole team will mentor you” or “ask in the IRC channel and someone will answer” just won’t do with first time students! I know I wasn’t very comfortable with asking just any question in IRC, especially if I felt that the answer could be something that “anybody ought to know”. Sometimes I just needed a confirmation to make sure I was doing the right thing.

To sum it up, I believe that KDE has a great admins&mentors team, and I can testify that also because of this doing GSoC for KDE was a very rewarding experience.

However, it has come to my attention (also during this year’s Google Code-in) that for the fairly small admins&mentors team a large scale student outreach program such as GSoC creates a huge workload.

KDE contributors are encouraged to help with the organization to make the recently announced GSoC 2011 the most successful GSoC ever: feel free to add your ideas to our GSoC 2011 ideas page, and if there’s an area of KDE you know well, why not be a mentor this year?

The KDE GSoC team is looking for good mentors with lots of cool ideas, and especially if you’re a former GSoC student and you’re not a student any more, you might be the perfect candidate to become a GSoC 2011 mentor. To apply as a mentor visit #kde-soc on Freenode.

Amarok 2.4 “Slipstream”

On behalf of the Amarok team I’m pleased to announce that Amarok 2.4 codename “Slipstream” has just been released.

This release finally brings some of the Google Summer of Code stuff we have been blogging about a few months ago, many new features, as well as many performance and usability improvements. We are especially proud of the new, completely rewritten and much more reliable collection scanner, and I’m personally very happy to be able to show/hide the menu bar again 🙂

Check out our release announcement to learn what we’ve been up to for the past few months.


What to do with an old Nokia N810?

Nitdroid Donut showing Planet KDE

Like quite a few KDE community members who attended Akademy 2008, I got a Nokia N810 internet tablet. Sadly, shortly after we got the devices we stopped receiving OS updates and the Maemo Diablo platform was basically abandoned in favor of a bigger better faster and quite different Maemo Fremantle, to be used on the N900 with the hope of eventually having a community supported port for the N810. Unfortunately, the Mer project, which aimed to bring as much Fremantle as possible to the N810, was cancelled back in 2009, leaving N810 owners with a nice piece of hardware and a dead software stack.

Don’t get me wrong: while the browser is still slow as molasses and the battery drains quite quickly when WiFi is on, Maemo Diablo works, but it’s not moving and in 2011 it’s not fun any more. Lately I’ve been using it just as a music player and rarely for quick note taking or Skype over WiFi.

So thanks to the efforts of the Nitdroid project, I installed an Android 1.6 Donut build on my N810, hoping to get something fun to tinker with. Even though Donut is old, it might still have been an improvement over Maemo Diablo. From what I’ve picked up, the Nitdroid project is focusing on the N900, and I can testify that Android on the N810 is unusably slow.

I have managed to open Planet KDE on my third attempt, the first two times stuff just crashed randomly:

As for MeeGo, a fellow Amarok developer says it’s slow even on the N900, so does it even make sense to try running it on the N810?

What are my options if I want a fun, fairly recent and at least a bit usable system on my N810?

I know people even managed to run KDE on it, but is it fast enough to be usable?

What do you use your N810 tablets for in 2011?

Amarok 2.4 Beta 1 “Closer”

Unsurprisingly, this fall has been a busy time for the Amarok squad: we had several heaps of code to merge from this year’s Google Summer of Code projects, and we cooked up lots of new features. All the stuff that our GSoC students blogged about months ago and much more will finally be released in January 2011 in Amarok 2.4.

But first, to make Amarok 2.4 rock-solid we would like to ask you, our users, for some help.

We have just released Amarok 2.4 Beta 1, codename “Closer”. In the hope that this release brings us all closer to creating the perfect music player, get it, play with it, test it, and if you find something that needs to be fixed please do send us bug reports at bugs.kde.org.

If the next few weeks are holidays for you, the Amarok team wishes you a happy holiday season!

The About dialog goes social – now for all of KDE!

Remember a year ago when I blogged about the Social About dialog? The dialog in Amarok that replaces the dull old About dialog with something more colorful?

Last Wednesday, after an almost complete rewrite and a few days of review, I committed my KDElibs port of the Social About dialog to trunk, to be released with KDE SC 4.6.

What does this mean for end users?

The Social About dialog is a small built-in Social Desktop client, available in any KDE application. Its purpose is to bridge the apparent gap between users and developers by providing an additional communication channel right inside the application. As a user, you will be able to see some more information about the project’s contributors, and directly access a contributor’s online presence as exposed by openDesktop.org or another provider which implements the Open Collaboration Services (OCS) API, as chosen by the authors of the app.

Looking back at the time when I wasn’t a KDE dev I can distinctly remember that I used to perceive KDE contributors as a reclusive and elite clique of people somewhere far away, with mad skills, encircled by an aura of awesomeness. While I can testify that a lot of KDE people really do have superpowers, I’d hardly call them reclusive. To quash that misconception, I’m giving you, the user, a way to get to know the people behind the project. You might even be surprised to find out that there’s an active bunch of KDE hackers in your very city or that the authors of your favorite KDE app share your taste in music.

The Social About dialog replaces the old “About Project” dialog and exposes the Social Desktop features if all of the following conditions are met:

  • You are running KDE 4.6 or later
  • You have a working internet connection
  • The contributors of the application you are using have chosen to add their usernames for an OCS provider such as openDesktop.org.

The new Social About dialog, as it appears in a test application using KDElibs trunk.

For every contributor who wishes to share his OCS data the dialog shows fields such as location, blog, homepage and social network profiles including Facebook, LinkedIn, Last.fm, Twitter and several others.

If there’s no internet connectivity or if a contributor does not wish to expose his data on the dialog, the appearance of an item will be very similar to how it was in the old offline about dialog.

What does this mean for application developers?

The general idea is to convey the message that the project is developed by real people, with another channel of user-developer interaction right inside the app.

This is a drop-in replacement for the old KAboutDialog. Obviously if you don’t touch anything in your KAboutData the dialog will be very similar to how it used to be, aside from some minor cosmetic differences i.e. you need to opt-in to use it. The dialog will also be in offline mode if KDElibs is built with the mobile profile (which is expected to remove the Attica dependency). By default, the Open Collaboration Services provider is openDesktop.org, and the contributor’s usernames can simply be appended to the KAboutData::addAuthor and addCredit calls.

In Amarok the experience has been positive, and there have been no instances of abuse (such as bug reporting in the wrong place or harassment) that I know of that could be attributed to the communication channels exposed by the Social About dialog.

If you already have a profile on openDesktop.org (or another OCS provider), don’t forget to update it before adding your username 😉

Why was this an almost complete rewrite?

For several reasons. At the time I wrote Amarok’s Social About dialog, Attica (the library that talks to the Open Collaboration Services API used by openDesktop.org and other providers) was still a moving target, and I needed to throw away some of the code that used now deprecated and removed API elements. Also, Amarok’s Social About dialog couldn’t work as a drop-in replacement for the old KAboutDialog since the data structures used by Amarok’s Social About dialog were a hack designed to make the it work with an unmodified KAboutData and OCS usernames thrown on the side. Finally, the persons list in Amarok’s Social About dialog was just a bunch of widgets in a layout, and lacked many of the performance and reliability advantages offered by the new dialog which uses model/view.

I wish to thank Frederik Gladhorn for his useful suggestions and review, the Amarok team for their useful suggestions and support in surviving git-svn and the developers who reviewed my submission on KDE’s Review Board for their patience, attention to detail and help.

What’s missing?

Aside from some minor planned improvements under the hood, the most prominent missing interface elements are about a dozen icons that represent links provided by OCS, such as Facebook, Identi.ca, LinkedIn and other social network profiles. We already have some of those from Amarok’s Social About dialog, but I still have to check if inclusion in KDElibs would be possible because of licensing restrictions, and what do KDE artists have to say about the appearance of said icons in the context of Oxygen.

And obviously, we are missing the data, so if you are a contributor for a KDE application and you feel like joining the Social Desktop bandwagon, go ahead and add that username!

Amarok 2.3.2 Beta 1 “Sentinel”

While lots of new features are still pouring in from this year’s Google Summer of Code projects, it will take us a while to make sure they don’t crash and burn and hopefully release them some time later this fall. In the meantime, why don’t you help us weed out some bugs to make Amarok 2.3.2 the rock solid release we would like it to be?

To make the task easier, we have deployed a sentinel to look out for bugs: Amarok 2.3.2 Beta 1, codename “Sentinel” is out.

Since the last release in the 2.3 series the Amarok team has been working through the laziest days of summer to implement very much needed fixes, changes and even some new features, especially concerning filtering and podcasts. Read the full announcement here and don’t forget that to make Amarok 2.3.2 even better, bugs.kde.org is the place to be 🙂

A summer of transcoding for Amarok

It’s been GSoC season for over a month now and I haven’t blogged, so now I’m going to try to fix that. After last year’s Multilevel playlist sorting project, one of my proposals has been accepted again for GSoC 2010: I’m going to implement on-the-fly transcoding in Amarok.

Amarok is a music player and manager built around very general concepts of tracks and media sources. The collection tries to decouple the format from the data itself and presents the music as tracks (with metadata) rather than files. In other cases, music isn’t even stored in local files. These concepts, and others, allow one to truly rediscover music through seamless internet sources and media devices integration, and the user in fact doesn’t have to care where the actual data comes from. The many sources at one’s fingertips are accessible in a consistent way and playable from the playlist.

However, even in this day and age of stuff in the cloud, there are situations in which the user still has to worry about media formats, e.g. when acquiring new music, or copying existing music from one collection to another or from the collection to a portable music player. That’s where transcoding kicks in.

For example, one might have a quantity of Windows Media Audio files that should be transcoded to a more Free format in order to be usable in the future, or a quantity of Monkey’s Audio files, which, while lossless, are not well supported everywhere, especially in PMPs. And then of course, even if someone has a collection full of FLAC files, which is a reliable and Free codec, a conversion into a lossy format such as Ogg Vorbis or MP3 might be necessary for use with a PMP simply for reasons of storage capacity.

So my idea is this: whenever the user can copy files, give him or her the choice to either just copy, just transcode or transcode with custom options. That way, we cover both of the following use cases:

  • “I’m running late for a 4 hour train ride and I haven’t updated the music collection on my portable player, I need to quickly copy over my tunes while making sure they will compatible with the portable player”
  • “if I tweak the quality rating of the Vorbis encoder exactly the way I want it I’m going to save 1% of the space on my portable music player and still get the audio quality my sensitive ears deserve”.

The current situation is that the transcoding operation (in the strictest possible sense) works, so the next thing I have to do is integrate it nicely with Amarok’s existing collections framework. The current implementation uses FFmpeg, but I’ve placed FFmpeg-specific stuff in a wrapper class so something else could quite easily be used in the future if need arises.

The following screenshot represents the current state of the still quite unfinished transcoding GUI.

On a somewhat unrelated note, I’ve been to the  KDE Multimedia+Edu sprint in Randa, Switzerland.

It was a lot of fun and very productive too. I wish to thank the whole organizers team. Special thanks go to Mario Fux for his mad organizational skills, to the cooking team which I had the pleasure to share the kitchen with while preparing vegan stuff and to Knut Yrvin for arranging a much needed meeting with the Brisbane office of Nokia, Qt Development Frameworks regarding QtMultimedia and the future of Phonon. Finally, thanks Anne-Marie Mahfouf for a gift she gave me which allowed me to taste again something I like very much but haven’t been able to eat because of nickel allergy.

LikeBack in Amarok

Amarok 2.3.0 has just been released but the Amarok team is already working hard on the next release. Shortly after mainline opened for feature commits I pushed a feature that will hopefully result in the next Amarok release being based on user feedback even more than 2.3.0: LikeBack integration.

What is LikeBack?

Short answer: a client-server system for gathering context-related, anonymous and immediate user feedback.

Long answer: described in a blog post by Valerio Pilo, KMess developer.

Pics worth more than 1K words (hint: the icons in the top right corner):

As I’ve read, LikeBack was originally developed for BasKet Note Pads and ported to KDE4 by KMess developers.

In Amarok the LikeBack bar is enabled by default only for testing releases i.e. git builds and betas. When the user has a good or bad experience, or gets an idea for a feature, he can click on one of the icons in the top right and submit a message. With LikeBack we gather comments of the types “like” “dislike” and “feature idea”, single and short suggestions, not discussions or bug reports. Bugs are still handled through the usual dialog that takes the user to bugs.kde.org, a system much better suited for bug tracking than LikeBack: this also means that if we receive something like a bug report under the guise of a “dislike” through LikeBack, we will have to consider it invalid.

The feedback we have received so far (several dozen comments in half a week) is quite positive, no insults yet (yay!).

LikeBack is available in Amarok’s git mainline (and in git/nightly builds if your distro provides them) as of a few days ago (*not* in the 2.3.0 release), so feel free to give it a spin and let us know what you think, either through LikeBack or the usual channels.

Amarok 2.3.0 “Clear Light”

The Amarok team is always at work, aiming with every release to deliver the best music player on earth and beyond. For some it may be just great fun, for others it may be a sacred calling, but for all of us a release cycle is a journey with its ups and downs, that comes to an end with a release. Each release is a time when we unleash our brainchild into the wild, and take a moment to just feel proud about what we have achieved.

This is such a moment.

Today I’m happy to announce the immediate availability of Amarok 2.3.0 “Clear Light”, which brings countless improvements and fixes over Amarok 2.2.2, and lots of new features. This release is the result of extensive user feedback, and it contains many patches submitted by members of the greater Amarok and KDE community. Check out the release announcement and please digg it.