What could be done to improve the OM development process?

[Carsten Haitzler (The Rasterman)]

On Tue, 12 Aug 2008 18:05:14 -0400 Jeffery Davis <heavensblade23 at gmail.com>
babbled:

> Two thoughts...
> 
> 1. Instead of working on multiple concurrent software distributions, why 
> not try to rally everyone under one banner for a while?
> People are going to work on what they want to work on to some degree, 
> but an attempt should be made at least.  Choice is great
> and all, but in the beginning I'd rather have one option that works well 
> rather than three or four equally terrible options.  There's no need to
> go running off in different directions when people still can't receive 
> calls reliably, among other issues.

aaah - but this is what om wants! as per will's words (product management for
OM): "Everyone should fork. Everyone should create their own distribution"

( quoted from:
  From: onimas at gmail.com
  To: "List for Openmoko community discussion" <community at lists.openmoko.org>
  Subject: Re: Community contributions to core apps & features. (Was: Terminal
  forASU) Date: Sat, 26 Jul 2008 11:44:21 +0000
)

this is om's intention and desire.

> 2. Better communication between the development community and the end 
> user community.  I have yet to see anyone say they're pleased
> as punch with the keyboard.  When almost everyone is unhappy, closing 
> bugs as 'working as intended' is pigheaded.

rock | om engineers | hard place. om design specifies what keyboard it wants.
you are to fork and do your own thing if you don't like it.

if you trawl through the mail archives you'll know why. the keyboard has been
flamed about enough. i'm not going to touch it.

-- 
Carsten Haitzler (The Rasterman) <raster at openmoko.org>