Have you considered embracing Linux in any of your articles? If you have, but have not acted on such thoughts, why is that? Is it the Linux learning curve? The "lack of benchmarks"? Simply the lack of resources on the part of your editors and product evaluators? After speaking with several editors from fellow publications, these seem to be most of the excuses at hand.

"While GNU Generation isn't the next Google Highly Open Participation Contest™ (GHOP), the two efforts have a lot in common. My name is Max Shinn and I am going into my junior year of high school. This summer, though, I'm interning with the Free Software Foundation (FSF). When I was participating in GHOP, I never imagined that I would be using that experience to start a similar project.

The reason I mention all this stems from an offer made by Ubuntu head honcho Mark Shuttleworth to put some of his staff to work on the Debian distro, to help Debian developers get ready for a proposed code freeze in December.

"It has been just over four months since the Free Music Archive launched as a destination for high-quality, freely licensed music [...] Today we are ecstatic to announce that CC has joined the FMA’s curatorial ranks! ..."

In a long posting on the Debian mailing list, Ubuntu sponsor Mark Shuttleworth sets out his position in the dispute over bringing a fixed development cycle to Debian's GNU/Linux distribution. Shuttleworth points out that he has long advocated a model of synchronisation between the various releases of Linux distributions which are based on the same versions of the same core components.

People doing everything in their browser scares me not because I think everyone should use the desktop but rather because I don't think the browser is the best user tool for doing all those things.

Richard Matthew Stallman, also known as The Last of the True Hackers, invited for a talk at FRHACK 01, an International IT Security Conference by hackers, for hackers - France, September 7-11, 2009 ...

Developers of open source software projects should be just as concerned about security as anyone developing a proprietary app. However, the nature of the two development processes can be very different at times, and debate still rages about which is inherently more secure -- a secret code kept by a company, or a public one that all eyes can see.