OStatic

Bugs, system conflicts, and errant bits of code add unique challenges to the technical area of open source development. They also affect a project's community -- and as any community manager can tell you, developing a healthy community is often more difficult (and has higher stakes) than rogue code.

Management is tough all round, but managing open source projects is different still. Most developers are giving their time because the project interests them, and non-developers join because they find the project useful, and they want to share their enthusiasm. But a community not being any one remotely homogenous group means that passions sometimes run high, and it's not always easy to keep a project's community -- it's life -- moving forward.

It may have just gotten easier. Ubuntu's Community Manager, Jono Bacon, announced his upcoming book, The Art of Community will be available later this year.

The New York Times ran a piece this Sunday featuring Canonical CEO Mark Shuttleworth. Though a majority of the piece was biographical, and the rest wasn't exactly the picture of accuracy in its portrayal of Ubuntu (or Linux in general), there were a few interesting figures.

It gives pause to wonder how, in this economy, and in an ever-changing industry, profit still gets much better press than growth.

The Ubuntu team has revealed the schedule and events for its next Developer Week. Ubuntu Developer Week events are traditionally held online to introduce new developers (or new to Ubuntu developers) to the Ubuntu development process.

The next Developer Week is slated for January 19th through the 23rd. Events start daily at 16:00 UTC, and occur hourly until 20:00 UTC. The first two scheduled events for Monday (at 16:00-18:00 UTC) are introductory events that will be conducted in several languages.

Open source software is inextricably tied to the idea of giving it away. Projects open their code for a number of reasons -- to better the codebase, or to allow others to bend an application to their own needs. Maybe the reasons are entirely altruistic, or maybe the altruism is the happy side effect of more project-centric decisions.

Of course, the open source approach doesn't just help code, or simply act as the framework for strong applications. The desired end result of any application is to improve the life of the user in some way. It sounds like hyperbole, perhaps, but if an application isn't making work in some way easier (or play more fun), it's not an application you'd want to use again.