The Colemak community is generally regarded as the loudest among keyboard layouts. That adjective is not used in a positive way regarding communities (it's like, why do they talk so much, is it to compensate for a worse layout?), so i do not recommend more promoting than we already do. But we're, as far as I know, growing exponentially, so your worries are unfounded.

Also, as a user of all the operating systems you mention, including OpenBSD, I have to disagree about your latter statements too. It works great under Windows, great under GNU/Linux, great under *BSD and also OS X (which I'm using right now).

Yes, the size of the Colemak userbase is still small, compared to the Dvorak or Qwerty one, obviously. Also, Dvorak has been around for much, much, much longer and is also recognised as a layout by ANSI, which contributes to more people knowing about it. But for it's size, the Colemak community is extremely noisy, and we're on the upswing. I've converted two or three people in the four months I've used Colemak. That's at the very least one new person every two months. And if everyone is like me, that's a doubling of the userbase every two months. That'd mean that in December, there would be sixteen times as many users than in January. I suppose that's untrue, and after a while you deplete your reserve of potential converts, but to show you how rapidly it may grow.

What kind of glitches did you encounter in Ubuntu? (I suppose you're talking about the Xorg implementation here.) And how is the OS X implementation of Colemak bad? The only thing that's not working absolutely perfectly on my OS X is the backspace. Which works just as it should with Colemak, but when i switch back to QWERTY it still erases (when it should, according to someone, become a caps lock). But that's fine with me. Nobody should feel the need to use caps lock anyway (most useless function on the keyboard, residing at one of the most useful keys? No thanks) and to have the extra backspace on QWERTY too is not a bad thing.

Most of the implementation problems (on any platform) are limited to the Capslock->Backspace remap, just because many systems don't readily support/expect that mapping.  Other than that, Colemak is "just another" keyboard layout, and works just as well as any other.
It works perfectly for me on NetBSD (natively both on console and in X11) and on Windows (with pkl).

Stats being "basic support" required to promote Colemak?  Do you have any stats on Dvorak users, or users of any other keyboard layout?

iPad "hardware support" being critical for Colemak's success?  Sorry, doesn't make sense to me.  And if you buy such a locked-down device, it's what you get.  (and you can't touch-type on a touch-screen, anyway.)

You must be trolling...

OS X layout has been working so well for me that I don't even think about it.  DoubleCommand takes of the backspace without any glitch, I haven't missed not having a Caps Lock.

I'm still puzzled why on devices with virtual keyboards, I don't have complete control over the key layout.  It seems really stupid.

:-) I should just be able to press on the space bar long enough that all the keys start jiggling and then I drag them around with my finger to rearrange them the way I want :-)

come on Apple, get with it!

Screen keyboards have one thing going for them: You no longer need keychords (the simultaneous pressing of multiple keys, as with Shift or Control) -- the chief source of stress. 

To type uppercase B, you press Shift, drag finger to B, and release!  Try that on a "real" keyboard!  :-)

Wow, how slow is that? :-)

But the point was mostly (and you confirmed it with this example) that you have to look at the keyboard at all times.  Touch typing is impossible.

Yeah, that's that feature I keep accidentally triggering on Windows machines that prevents me from typing properly again until I restart the computer.

What if each virtual key gave a little different buzz,  so you could say that feels like a "B".    or at least T an N gave your index fingers an extra tingling.    I could see that happening....  some thing better, more nuanced than the haptic feedback methods used today.

I would rather try some form of Morse code blind. For instance two large panes (for dits and dahs) and a few buttons (at least space and backspace).

Rockbox, the firmware I use on my iPod, has morse code input as an option.  It's certainly faster than selecting letters with a scroll wheel. :-)

My dad's using Rockbox on his iPod, I'll have to try the morse code input there to see if it actually works. (My iPod is unfortunately a generation 6, so I can't try on my own.)

Now that we're drifting off-topic anyway, here's an innovative input method that requires a pointer device (or even just eye movement) only: Dasher.  You enter text by continuously zooming into boxes with letters, sized relatively to their likeliness to follow the previously entered letters.

WPM will suck, but for severely disabled people it can be a really useful (and fun!) way to produce text.  Try it, you'll get the hang of it after five minutes of practicing.