OStatic

There was an interesting write up on Forbes.com this week discussing who contributes most to open source projects -- and why. Even though many open source projects have a commercial or institutional component that contributes some degree of direction (or funding) to software development, and even though many businesses and institutions use open source software regularly, the vast majority of contributions to these projects come from individuals.

Forbes' Dan Woods, after hearing Alfresco's Matt Asay and Eclipse's Ian Skerrett speak of this contributor gap, concluded that there must be something very different about how institutions contribute.

Ben Kepes at Cloud Ave. offers some interesting analysis of a question Yuuguu CEO Anish Kapoor recently tackled on his company's blog: Has software as a service (SaaS) killed open source as a business model?

The question raised, of course, is why these concepts are at odds at all -- why are they mutually exclusive? They aren't, per se (SaaS companies can -- and do -- offer their code under open licenses), but Kapoor imagines that for some companies, SaaS takes a bit of the shine from open source. Kepes counters that while this might be the case, SaaS has a fair bit to gain from the open source model.

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.

Google's Summer of Code (SoC) Program has united students interested in open source with projects and mentors for several years now. The intiative's goal is to foster interest in open source software while exposing students to real-world software development processes. It's easy to see, based on how enthusiastically some projects embrace the annual event, that the students aren't the only ones who benefit from the program.

This week, both KDE and GNOME announced that development teams under their respective umbrellas wishing to submit project ideas and mentor students this summer were able to do so.

This also means interested students can get a sneak peek at potential projects and mentors. The list of projects (and mentors) won't be finalized until mid-March, but seeing as students only have two weeks to submit their applications, an advance project screening might prove helpful.

Compiz, the project that brought spectacular desktop effects to Linux, acknowledged earlier this year it was grappling with organizational difficulties. Kristian Lyngstol, a long-time Compiz developer, said in a passionate but level-headed post to the development list that the project faced a grim future if it continued on its present path. Lyngstol proposed that strong leadership, and a clearly defined roadmap would retain existing developers, make the development process simpler, and even attract new developers.

Lyngstol said it would still be a rough ride, but that this would give the project a fighting chance. This week, after much discussion and numerous conference calls, an official statement was issued detailing where Compiz would move next. While the newly formed council predicts the 0.9 release will still be quite volatile, and the roadmap is subject to some change, its focus now is to maintain and improve the project's overall health.

Perhaps it's inevitable -- people react strongly to hyperbole, it gets them talking, it makes them curious, it's a quick way of making a subject hot. For years, every new MP3 player was met with speculation -- would it be an iPod Killer? Perhaps ASUS didn't release new hardware quickly enough before solid competition entered the market, but for a few months last year the term Eee Killer was thrown about. Yet, despite the bounty on their heads, iPods and Eees still exist, as do alternative devices.

As Microsoft allowed people to take an early version of Windows 7 out for a test ride, the -Killer suffix re-emerged. It's not an OS X-Killer. It's a Linux-Killer. I'm sure this is due in large part to the robust netbook market and Apple's absence there. It's interesting that suddenly Linux is seen as competition. It's also intriguing that this is portrayed as the nail in the coffin, and not an opportunity.

By way of Glyn Moody's Open Enterprise blog comes word that Mozilla's Creative Director John Slater is gearing up to better organize and expand Mozilla's visual design community through the Mozilla Creative Collective.

The Mozilla Creative Collective hopes to harness the enthusiasm and talent that made the Spread Firefox campaign such a success. Slater plans on running regular challenges on the MCC site, as well as integrating a job board to unite artists with projects in need of design work.

The Debian team has tangled with more than its fair share of demons during the development cycle of the 5.0 Lenny release. Lenny, which was loosely scheduled for release in September 2008, was delayed due to the number of release-critical bugs that were awaiting patches. As the year came to a close, Lenny faced other challenges, including team management shake-ups and a vote on how to handle Lenny's inclusion of non-free binary blobs to best meet the Debian Free Software Guidelines.

On February 1st, Lenny's second release candidate was announced, as well as the release's deep freeze status. Lenny is scheduled for general release over the weekend of February 14th.