OStatic

There's been some intriguing discussion going on in the KDE community. Developer Aaron Siego ponders how the open source community can recognize and help struggling projects before the situation becomes critical.

Seigo says two of the more common reasons development efforts are put aside are technical issues with upstream projects and non-project demands that developers face. The first scenario is (sometimes) forseeable, but one person's life changing event can throw a small development team into a tailspin.

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.

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.

The Linux Plumbers Conference may have ended last Friday, but the discussions -- and one discussion in particular -- will be analyzed, deconstructed, and argued for quite a bit longer.

Greg Kroah-Hartman's assertion is that Canonical doesn't contribute significantly to kernel development and the packages that make up the core of a Linux system. Canonical CTO Matt Zimmerman responded to this assertion. It seems at that point, much of the community, developers and users alike, took to examining their particular parts of the open source elephant.

Herein lies the problem.