Openmoko on Design
openmoko at mazikeen.demon.co.uk
Wed Jul 30 02:47:29 CEST 2008
Many thanks for the direct answers. This is what I've been hoping for. I'll
snip most of it to keep the length reasonable.
On Tuesday 29 July 2008, William Lai wrote:
> No bad intentions for snipping,
> Just trying to get to the facts:
> Brian C wrote:
> > 3) If the design department is operating from a design document, has it
> > been made public? If so, where? If not, why not?
> Design doc uploaded (sometime in April)
> Posted by Ian Darwin in May
Just in case anyone wonders why it comes back not found, typo corrected
> Feature Plan tracking
> Bug Tracking:
> You get the point.
I think so. There's some documentation but nothing particularly detailed, and
details weren't set in stone as of Ian's post in May when the keyboard toggle
existed. It has been public, but perhaps not widely known about, for quite
some time. Comments in the bug tracker reference a discussion on the
openmoko-devel list which I assume to be one of these:
Big chunk of snippage...
> > If so, will such
> > community members also have a voice in underlying design decisions that
> > guide that/those framework(s)?
> It already is.
> We've offered a couple of different solutions to community requests that
> were declined by, well, engineering. One of them was:
> * create a package to be installed through installer adding manual
> qwerty button to illume theme.
The only suggestion I remember was that the community fork illume. Is this a
different take on the same suggestion, or a different suggestion? What was
the other option? And what was the objection to providing it as a
configuration option with the default being off, as proposed on this list?
More information about the community