For a lot of programmers, writing an application is fun, but writing its manual is not. Adding new features, refining the product, and responding to users' input are all more rewarding than writing instructions on how to use the software. However, good documentation is necessary to have happy, informed users who can contribute meaningfully to future development. A few months ago, Gilbert Ashley, the author of src2pkg (Slackware's "magic package maker") invited me and two other people to help him manage the user documentation for his program. The process we used to create the src2pkg wiki may be a useful example for other free and open source software (FOSS) application developers.

Clay Shirky's book on what information technology is doing to our world, Here Comes Everybody: The Power of Organizing without Organizations, has important things to say to anyone interested in open source software (OSS). His thoughts on the evolving effects of the technological revolution we are all living in make for a fun way to spend a few hours.

Which path should you follow? Should you take advantage of Ubuntu's package manager and use it to upgrade your system to the latest 8.04 Hardy Heron release, or should you download a CD or DVD ISO image and do a clean install? Common wisdom says that doing a clean install is the better, safer course of action. There may be a little extra work involved configuring everything once the latest and greatest is installed, but that's nothing compared to the pain of an update gone wrong, according to traditional thinking. But that cautious approach may no longer be necessary.

SqlSync lets you compare two databases to see which tuples have been added, removed, and changed. You can also use SqlSync to make one database a clone of another and maintain its contents to be that way. One benefit of using SqlSync to perform synchronization is that you can perform heterogeneous syncs -- for example, from MySQL to PostgreSQL.

I use Tomboy, an open source notetaking app, to cull and organize the hundreds of bits of information I track, and to prioritize it on to-do lists on the fly. When we first reviewed Tomboy 0.3.5, it had some obvious flaws. The project has had a number of updates since then, and the newest version, 0.10.0, really makes the grade.

Slackware Linux has stood strong for more than a decade by refusing to compromise. There was a time when people used to say, "If you want to learn Linux and learn it well, give Slackware a try." Attila Craciun, a Romanian software developer and Linux enthusiast, has ported the Slackware tree to the AMD64 architecture to create the Bluewhite64 distro. We spoke with him to find out about Bluewhite64, where it came from, and where it's going.

If Creative Commons (CC) has any say in the matter, the Web will soon have a standard machine-readable notation for licenses. Named the Creative Commons Rights Expression Language (ccREL), the notation has been under development for the last few years, partly with the cooperation of the World Wide Web Consortium (W3). It is described in a paper by four Creative Commons employees and published by Communia, a European site that explores the relationship between technology and the public domain. Creative Commons plans future presentations of ccREL, and is also actively explaining the need for it -- which is what CC's Chief Technology Officer, Nathan Yergler, was doing when Linux.com caught up with him at the recent Open Web Conference in Vancouver.