Forgot your password?
typodupeerror

Comment: Re:More and more... (Score 1) 617

by sciurus0 (#33793682) Attached to: Take This GUI and Shove It

The config file format shouldn't need to be modified. Obviously they're already machine-readable! The problem is that people write myopic GUI config tools. They should be using something like augeas.

Augeas is a configuration editing tool. It parses configuration files in their native formats and transforms them into a tree. Configuration changes are made by manipulating this tree and saving it back into native config files.

Augeas is:
An API provided by a C library
A command line tool to manipulate configuration from the shell (and shell scripts)
Language bindings to do the same from your favorite scripting language
Canonical tree representations of common configuration files
A domain-specific language to describe configuration file formats

Augeas goals:
Manipulate configuration files safely, safer than the ad-hoc techniques generally used with grep, sed, awk and similar mechanisms in scripting languages
Provide a local configuration API for Linux
Make it easy to integrate new config files into the Augeas tree

Comment: Sean's speech at ESC about making a 3G devic (Score 4, Informative) 219

by sciurus0 (#27461307) Attached to: No More OpenMoko Phone

Reposting from http://lists.openmoko.org/pipermail/community/2009-April/044915.html

Sean's speech at ESC about making a 3G device:

Since I worked on the presentation with Sean for the days he was here in
SF, let me give you my view and sean's view. That way we won't get into
some version of the telephone game.

Sean discussed three things at OpenExpo.

1. Our successes.
2. Our mistakes.
3. Our challenges

I won't go over 1& 2 but I'll cover #3 since rasters perception has
a bit of color added to it. Only a tiny bit and he's entitled
to that color commentary, I'll just add what Sean and I, as authors
of the presentation, had as our message.

Our biggest challenge was to make a choice about how to spend the
balance of 2009.

There were two paths:
A: Fulfill our promises on FreeRunner and launch GTA03
B: Fulfill our promises on FreeRunner and launch project B.

We will talk more about project B in the coming months, but these
salient facts should be able to guide any budding executives out there.

1. GTA03 was in constant flux as a design.
2. GTA03 schedule was consequently always slipping.
3. The resources required for GTA03 are 3X those required for Project B.
4. We don't have 3X.

So, we picked plan B.

Now comes the question, what about GTA03? how do we get there? And when?
and what is it?

Well my basic argument was and is this:

First we attend to the issues that still remain with the GTA02. That's
why the VP of marketing ( of all people) is working on the buzz fix
problem. Second we complete project B. When we've done that, then we
get to eat dessert. Essentially, I made the same argument I heard so
many times on this list: "How do expect us to buy a GTA03 when you've
yet to deliver on all the promise of FreeRunner?" And I took the
arguments I heard from disty seriously, "how do you expect us to buy FR,
when GTA03 is right around the corner?" And I accepted the arguments I
heard from Engineers I respect who questioned the viability of the GTA03
in the market place. All of those arguments said "put a bullet in its
brain pan!"

    So, what about GTA03? As it was defined, it is dead. So how do we
get to a new GTA03? Two requirements: continue to improve GTA02; deliver
on project B. What is GTA03 and when do we get there? There are a number
of independent efforts out there that are pitching me ideas for GTA03.
I talked to sean a bit about this and I'd like to try to open up more
of the design process and the marketing process to the community.
Perhaps on a separate list. Some of these discussions have already started.

What can you do to help?
1. Move GTA02 code upstream.
2. Stay Involved.
3. Continue work on applications
4. Buy a FreeRunner.
5. Get involved in GTA03 discussions

Promising costs nothing, it's the delivering that kills you.

Working...