OStatic

Today, the Linux Foundation released its updated study of mainline kernel development. The report examines the slight variations in release frequency, the lines of code submitted, deleted and modified since the April 2008 study, new trends in subsystem patch signoff, and the remarkable diversity (and, perhaps, adversity outside the realm of kernel development) of the companies contributing to the kernel.

While the study is obviously pertinent to those working in kernel development, it covers so many aspects of the development process that everyone working with open source software -- developers, community managers, and even non-IT managerial roles -- can find something directly related to their positions.

It's also (perhaps surprisingly) engaging reading for those interested in the Linux kernel but a little foggy on how the kernel relates to the rest of the operating environment or how changes are approved and applied to the kernel tree.

Earlier this week, the Qt Labs at Nokia announced a new project, QtMobility. QtMobility's primary goal is to offer a new set of Qt API development tools for mobile device applications.

While this will certainly make life easier for developers working with the Qt framework on specific Nokia devices, one of the best (and intentional) fringe benefits is that the new API tools are cross-platform. A single application, then, can be built and maintained for any supported Qt platform -- regardless of the mobile device model or manufacturer.

Video editing software for Linux is, to put it nicely, quirky. Some editors only work with specific file formats, some work nicely for basic video editing but can be wildly temperamental on seemingly identical machines, and some are powerful to the point of overkill for the average user.

PiTiVi is a non-linear video editor based on the GStreamer multimedia framework. After hearing some positive comments, and seeing development efforts really picking up on the project, I decided to take it for a spin. It is very much in development, but not in the traditional sense. It feels very stable, and the interface isn't confusing or a hindrance. It is, at the moment, very basic when it comes to functionality. There are not plugins or extensions currently available (though feature requests are welcome). However, the project has taken the time to plan its path forward -- and with the basics down, I can't see why real headway won't come quickly.

The Ubuntu Project may have just unleashed a legion of Jackalopes upon the world, but is well aware that time waits for no animal, real or cryptozoological. This is why the first alpha version of Ubuntu 9.10, the Karmic Koala, is now available for brave testers everywhere.

Keep in mind that this is the first alpha, just opened for development. This means not only that it should be kept far, far away from production machines, but that many of the nifty new features that will be in the final Karmic release aren't there at all yet, never mind perfected. Currently, however, there is a new kernel based on the 2.6.30 release, and the latest development version (2.27.1) of the GNOME desktop environment. Applications are being updated (and added) quickly, and there's definitely a wild ride (and a lot of bug-squashing fun) ahead for interested testers.

At OSCON last year, Jaspersoft revealed that work was underway to re-vamp JasperForge, its developer community platform. Jaspersoft's goal was to ensure that the Forge could support its community into the future by integrating new collaboration and networking tools, while enhancing the Forge's existing features.

Today, Jaspersoft has announced that the JasperForge upgrade has moved into high gear, with all of its new features and enhancements in place and operational.

In my travels, I discovered David Zeuthen's informative peek at DeviceKit (and its use with and in lieu of HAL) in the upcoming release of Fedora 11.

Zeuthen says that while the new storage device handling stack is implemented in Fedora's GNOME 2.26 desktop configuration, it should be appearing in its entirety in the upstream GNOME 2.28 release. The DeviceKit daemon modernizes and adds to many of the features and functions of the tried and true HAL daemon.

I blame the souls at Ars Technica just as much as the diabolical (though creative) minds at Miro for the ear-drum shattering, make-your-teeth-ache squeal I just unleashed upon the world. Miro's new fundraising campaign -- where for $4 a month, one can adopt a line of code -- has got to be one of the most innovative, creative, and inviting fundraising efforts an open source software project could ever dream up.

While I still take stock in the notion that perhaps open source projects could benefit from spinning their requests for monetary contributions as investments rather than donations, the Miro team has hit on (figuratively, anyway) real gold with this effort. Adopting a line of code (as if it were a whale, or, even, say, a penguin) and giving a little to the adoptee in return -- a blog widget, an adoption certificate, and a picture of your fostered line -- has a low impact on the project's resources, can garner some great returns, and is just fun.

I'm betting it'll turn out to be effective in other ways, as well.

I've noticed, as I get older, time seems to go exponentially faster. Unfortunately, this meant high school lasted an eternity, and I'm burning through my thirties at warp speed. Some events make me more aware of this than others -- it seems like it was only last week that Fedora 10 made its first mark upon the world.

But no, another release cycle has nearly come full circle, and today the Fedora Project announced the Preview Release of Fedora 11 (codenamed Leonidas). This preview will be followed by a release candidate (scheduled for a May 12 appearance), with the final version hitting the streets on May 26.

So what new features can we expect to see in Fedora 11?

Late yesterday afternoon, Canonical let loose the release candidate disk images for Ubuntu 9.04 (Jaunty Jackalope). Canonical warns that while a release candidate is about as stable as one can get with a testing release, it is still a testing release, and users should hold off installing Jaunty on essential systems.

The good news, of course, is that those clamoring to install Jaunty on their essential systems haven't long to wait. The finalized, stable Jaunty release will appear on mirrors worldwide April 23rd.

As news of Openmoko's harsh but realistic look at the road ahead ripples through the open source and mobile technology sectors, there will be, beyond a doubt, much speculation on how the project's challenges could have been minimized and its successes built upon. Perhaps Openmoko's attempt to bring a completely open mobile phone to the world was Quixotic. Perhaps it was a good idea that simply launched at a bad time. Perhaps it was (and still is) a very workable idea -- or maybe it will always have an extremely niche appeal. Openmoko's pulling away from FreeRunner phones (and looking toward its Plan B ) might well work out just as Michael Lauer writes on his blog -- not at all as a death sentence, nor as any sort of indication that free platforms don't work (or aren't desired) on mobile phones.