Five last-minute gifts for open source fans (Dec 23, 2011)

10 Last-Minute Gift Ideas For Linux Geeks (Dec 21, 2010)

12 Ubuntu Derivatives You Should Consider (Nov 22, 2010)

Fact or Fiction? Top 8 Linux Myths Debunked (Sep 10, 2010)

Top 5 Mistakes Made by Linux First-Timers (Oct 14, 2010)

Linux Barbies Battle the Command Line (Mar 28, 2009)

I *did* cherry pick a little bit, but generally speaking, I've seen cotton candy less fluffy than this.

I'll tell you what needs to happen. All these grateful and passionate Users need to band together and organize a conference.

Once that happens, invite all the Developers to 'come down from their cloud' to visit and participate in this conference.

The list of workshops you'll want to develop will include 'The life of a Bug; From Discovery to Patch', 'Version Control for Laypeople', and a three parter on 'How Open Source Works'.

Get off your cloud? How about 'get off your duff'?

Just like Shuttleworth started Canonical to address userspace conditions, someone needs to get going on the meatspace support structure. Even older than your xfree86.conf file are the arguments 'Devs don't understand Users' and 'Sales doesn't understand Engineering'.

Now, how about stepping up to the plate?

Sorry SuperMicro, but you could use a bigger umbrella.

So, Dell: Buy SuperMicro

Also, Dell, you need to make some serious inroads in the backend service arena. There are several dozen cloud service and storage business starting up every week. Buy two or three of each. Three billion Dollars should go pretty far in this arena.

Split the software and services from the hardware. While you're at it, buy or invest heavily in implementation and sales engineer forces.

Once all the divisions are established, take some of the leftover funds and run a few Super Bowl ads around Dell Ver. 2.0, where directly offered services come with the requisite backing (whether cloud or otherwise)

Assignee: Halliburton Energy Services Inc.

I'd like to run this through my legalese relationship parser to generate some relational diagrams between the methods and the claims.

Something tells me there are some sploits to be found..

Propose a ridiculous answer, then suggest it is the common response?

How about this:

If the content is published without copyright, the license requirements should allow for physical replication, as the original digital version is protected and version controlled.

Life of a hard copy? As long as the information is relevant.

Life of a digital copy? As long as the information is relevant, with the added feature of perpetual evolution.

Let's imagine a world without an oxygen fueled brain...

Ah! It's a simple world because there is distinct lack of brains, due to a lack of oxygen!

Without managing blood flow and fuel supply according to its needs? Way simple!

Let's emulate all of nature, eliminating all the things we deem 'irrelevant' to the simulation.. What gets left out? Whales? Plankton? Ants? Yeast? Pollen?

How complete is your implementation? Outcome not what you expected?

You're looking at a shiny red hammer when you get automagic wireless configuration, stuff that 'just works', and easy and relatively complete package management.

You're looking into a stocked toolbox when you have a need to recognize and capitalize on the full scope of those packages - not just the tool to address the majority of what needs to be done.

I should have put a premium on /maturity/ when comparing the two..

My mistake!

The *best* is my *favorite*.

Favouritism is only that. Best is Best. Period.

Mass audiences are incapable of finding appeal in Debian. ..for good reason.

What appeal could they find in a well organized toolbox, when all they really want is a shiny red hammer?

MS would rather step over them all to where they estimate things will go rather than resign to being an late starting also-ran.

If those guys are all occupied with WebKit, it frees MS to do something bold.