OStatic

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.

Churning out an x.0 software release must be akin to becoming a new parent -- the event exudes promise, joy, and hope, yet is simultaneously humbling, exhausting, and terror-inducing. While it isn't realistically possible to plan out detailed roadmaps for your children's long-term future, it's crucial to do so for a software project. While whether the presence of a carefully planned roadmap makes progress more or less stressful depends largely on who you ask and at what point you're asking, a project with clearly outlined goals and direction has a much better shot at sustained developer interest and solid releases.

Many projects grapple with this, and as GNOME pushes towards its 3.0 milestone, the GNOME Release Team talks about the voyage to this point -- and how best to travel forward from where it currently stands.

Yesterday, the openSUSE Project announced that it will move to a fixed release schedule after November's release of openSUSE 11.2.

openSUSE developer Stephan Kulow said that the developers are considering an eight month release cycle at the moment, as they feel successfully producing an up-to-date and solid release in this time frame is more realistic than a six month cycle. However, the development team invites feedback on the openSUSE-Project mailing list.

I have a confession to make. Sometimes, even when you've been trained in the intricacies of searching every database known to man, you can still outright miss really obvious things in a simple Google search. When I was fresh out of library school, I resurrected one of the library's catalog terminals, an old Bondi Blue iMac, with Yellow Dog Linux and KDE. I spent days locking down the KDE desktop, so that if the browser displaying the catalog was somehow shut down (or crashed) it would automatically restart. I spent a few more days making sure that most patrons couldn't access anything but the browser (never underestimate the general public, or the havoc that stray keystrokes, however innocent, can bring).

It wasn't that the KDE Kiosk tool didn't exist at the time. I simply missed it. Yes, I was a bad systems librarian for missing it, and then spending days (happily, but still...) locking down the desktop and reinventing the wheel.

With the release of KDE 4, Kiosk sadly fell into a state of limbo. Now, however, KDE developer Ian Geiser wants to bring it back to life on KDE 4.

Digital Arts Online has a thorough break down of some of the snags the Firefox development team has encountered as it continues work on the browser's 3.1 release. TraceMonkey, the JavaScript engine that's responsible for the browser's performance boost, seems to be what's holding its actual release back.

According to the forum posts the article points to, both Firefox developers and those focusing specifically on TraceMonkey agree that a decision has to be made -- but whether it's better to release Firefox 3.1 without TraceMonkey, release Firefox with TraceMonkey disabled by default, or give the developers a set amount of time before making the decision at all -- might be a sticking point.

Every year or two, some hardware component comes down the line that truly takes my breath away. On the past few occasions, these bits of circuitry have all used open source software in some capacity, though whether that's due to my tendency to notice such things, or a measurable increase in hardware developments that feature open source technology is uncertain.

TMCnet introduced me to this year's take your breath away device, the Marvell SheevaPlug. This plug computer (it's designed to hang comfortably from a household wall socket) features a 1.22 GHz Kirkwood (Sheeva-based) processor, 512 MB DRAM, and a Gigabit ethernet connection. In addition to its onboard 512 MB Flash storage, the plug has a USB port for external storage. The hardware, the multiple Linux distributions it currently supports, and the API framework (called Raindrop ) that is currently being developed for running third party applications -- are all open source.

Why? Because, as Marvell's product manager, Raja Mukhopadhyay told TMCnet, ...[open source] is what we see going forward.