Re: Openmoko on Design

Jay Vaughan wrote: >> I have a MIDI keyboard I can bring with me to LinuxWorld, and a USB/ >> MIDI >> interface. > > Well I spent some time hacking on it this weekend and I've gotten a > basic MIDI parser/librarian/sequencer setup on the Freerunner now .. > great fun to play back tracks to

Re: Openmoko on Design

> I have a MIDI keyboard I can bring with me to LinuxWorld, and a USB/ > MIDI > interface. Well I spent some time hacking on it this weekend and I've gotten a basic MIDI parser/librarian/sequencer setup on the Freerunner now .. great fun to play back tracks to my 19" rack using the Freerunner

Re: Openmoko on Design

I have a MIDI keyboard I can bring with me to LinuxWorld, and a USB/MIDI interface. If your synth is ready in time I'd love to show it. M Jay Vaughan wrote: >> 7) Maybe run some simple synth applications on the FR, using the USB >> host mode to connect it to a MIDI keyboard. > > > this is w

Re: Openmoko on Design

On Wed, Jul 30, 2008 at 11:28:13AM +0800, Marek Lindner wrote: > On Wednesday, 30. July 2008 10:18:33 Al Johnson wrote: > > I agree with everything you say here. The keyboard should just appear when > > I want it and disappear when I don't. The absence of a manual override > > means that whenever i

Re: Openmoko on Design

> 7) Maybe run some simple synth applications on the FR, using the USB > host mode to connect it to a MIDI keyboard. this is what i'm doing this weekend .. ;) ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http

Re: Openmoko on Design

On Thu, Jul 31, 2008 at 4:27 AM, Ken Restivo <[EMAIL PROTECTED]> wrote: > On Wed, Jul 30, 2008 at 11:38:07AM +0800, John Lee wrote: > > On Wed, Jul 30, 2008 at 01:47:29AM +0100, Al Johnson wrote: > > > I'll snip most of it to keep the length reasonable. > > > > same here :) > > > > > On Tuesday 29

Re: [openmoko-announce] Openmoko on Design

Ken Restivo <[EMAIL PROTECTED]> wrote: > It seems to me from my former-product-mananger perspective that > OpenMoko doesn't really want to be in the software business. why would they do ASU/FSO then? i don't buy this. > I'm sensing a business model that has OpenMoko focussing on selling > gene

Re: [openmoko-announce] Openmoko on Design

> It seems to me from my former-product-mananger perspective that OpenMoko > doesn't really want to be in the software business. > > I'm sensing a business model that has OpenMoko focussing on selling > general-purpose computing hardware (like Dell or ASUS). but in a handheld > format, and let

Re: Openmoko on Design

On Wed, Jul 30, 2008 at 11:38:07AM +0800, John Lee wrote: > On Wed, Jul 30, 2008 at 01:47:29AM +0100, Al Johnson wrote: > > I'll snip most of it to keep the length reasonable. > > same here :) > > > On Tuesday 29 July 2008, William Lai wrote: > > > > > > It already is. > > > We've offered a coupl

Re: [openmoko-announce] Openmoko on Design

On Mon, Jul 28, 2008 at 10:31:55PM +0200, Jay Vaughan wrote: > > Sorry to hear it doesn't work for you. But like I said, we each have > > our > > own ways of understanding and making meanings. > > You are free to create your own meanings. > > > I just can't see how you honestly believe all this

Re: Openmoko on Design

Marek Lindner wrote: > On Thursday, 31. July 2008 05:24:45 Josh Monson wrote: >> Or is Sean saying that this would be an option if it was in the form of >> a package, so if the package was built (by the community) then you would >> have the choice to toggle or not to toggle? I am assuming that >> f

Re: Openmoko on Design

On Thursday, 31. July 2008 05:24:45 Josh Monson wrote: > Or is Sean saying that this would be an option if it was in the form of > a package, so if the package was built (by the community) then you would > have the choice to toggle or not to toggle? I am assuming that > functionality was removed so

Re: Openmoko on Design

Open Source is more than that, do you all propose OM to sell their Software bound to the Hardware? I fear you thing too much in the old fashined way of MObile COmmunication. The Freerunner is a piece of Hardware *YOU DECIDE* what software you want to run on it FSO ASU 2007.1 2007.2, SHR, ASDF or s

Re: Openmoko on Design

> People need to stop biting the hand that feeds you. he bit the other hand, actually. *scnr* ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community

Re: Openmoko on Design

Scott wrote: > Sean Moss-Pultz wrote: >> On 7/30/08 Daniel Benoy wrote: >>> Also, would the openmoko design team be willing to consider a toggle >>> in the configuration menu between manual and automatic? >> >> What we want is for people to add their own configuration options to >> menus in the

Re: illume keyboard button (was Openmoko on Design)

wait until i get to changing how it works. > Dear community and OM Powers That Be, > > I have read the "Openmoko on Design" thread with a certain alienation. > I'll try to resist the temptation to pick up one of the many flame > baits, but even after sleeping it over

Re: Openmoko on Design

Sean Moss-Pultz wrote: On 7/30/08 Daniel Benoy wrote: Also, would the openmoko design team be willing to consider a toggle in the configuration menu between manual and automatic? What we want is for people to add their own configuration options to menus in the form of packages installable fr

RE: Openmoko on Design

1:21 AM To: List for Openmoko community discussion Cc: [EMAIL PROTECTED] Subject: Re: Openmoko on Design > If you go read Morse Peckham's book > http://www.amazon.com/Mans-Rage-Chaos-Biology-Behavior/dp/080520142 > You will understand how museuems and gallery's function; and, Se

Re: illume keyboard button (was Openmoko on Design)

On Wednesday 30 July 2008 15:01:52 Andreas Bogk wrote: > http://gitweb.openembedded.net/?p=org.openembedded.dev.git;a=blob;f=package >s/openmoko-projects/illume/configure-keyboard.patch;h=589fe53f38afc59be95a13 >ed67a9f9d1fc452148;hb=HEAD > > They re-enabled the feature in their branch, and went o

illume keyboard button (was Openmoko on Design)

Dear community and OM Powers That Be, I have read the "Openmoko on Design" thread with a certain alienation. I'll try to resist the temptation to pick up one of the many flame baits, but even after sleeping it over for a night, I feel inclined to comment on the issue here. Firs

Re: Openmoko on Design

> Yeah it was a misunderstanding then. That's exactly what I was > referring > to. Too many emails :-) > Only a joke Jay. Nothing personal. > okay, so please consider this .. i have a customer with the potential to place an order for 1,000 phones. when do you propose i go to them and close

Re: Openmoko on Design

On 7/30/08 arne anka wrote: > >> Yes Jay. That is exactly the goal of this company. Sell 1,000 > phones. > >> >> They we all can retire. > > > > > > wtf? you're ridiculing a single order of 1,000 phones being > placed at > > > one time by an enthusiastic customer? sheesh. what sort of CEO > a

Re: Openmoko on Design

On 7/30/08 Jay Vaughan wrote: > > Yes Jay. That is exactly the goal of this company. Sell 1,000 > phones. > > > They we all can retire. > > > -Sean > > > wtf? you're ridiculing a single order of 1,000 phones being placed > at > one time by an enthusiastic customer? sheesh. what sort of C

Re: Openmoko on Design

>> Yes Jay. That is exactly the goal of this company. Sell 1,000 phones. >> They we all can retire. > > wtf? you're ridiculing a single order of 1,000 phones being placed at > one time by an enthusiastic customer? sheesh. what sort of CEO are > you? chill. only a misunderstanding probably -- y

Re: Openmoko on Design

> Yes Jay. That is exactly the goal of this company. Sell 1,000 phones. > They we all can retire. > -Sean wtf? you're ridiculing a single order of 1,000 phones being placed at one time by an enthusiastic customer? sheesh. what sort of CEO are you? *all* orders, large and small, are wort

Re: Openmoko on Design

> On 7/30/08 Jay Vaughan wrote: >> > If you go read Morse Peckham's book >> > > >> http://www.amazon.com/Mans-Rage-Chaos-Biology-Behavior/dp/080520142 >> > > You will understand how museuems and gallery's function; and, >> Sean's >> > > words >> > > will strike you more deeply. >> >> >> Its all wel

Re: Openmoko on Design

On 7/30/08 Jay Vaughan wrote: > > If you go read Morse Peckham's book > > > > http://www.amazon.com/Mans-Rage-Chaos-Biology-Behavior/dp/080520142 > > > You will understand how museuems and gallery's function; and, > Sean's > > > words > > > will strike you more deeply. > > > Its all well and

Re: Openmoko on Design

> If you go read Morse Peckham's book > http://www.amazon.com/Mans-Rage-Chaos-Biology-Behavior/dp/080520142 > You will understand how museuems and gallery's function; and, Sean's > words > will strike you more deeply. Its all well and good when you're dealing with art students, but when you h

Re: [openmoko-announce] Openmoko on Design

> About Jay, I apologize if I attached personally it, but he was > attaching > a lot of person of this ML, and it was not too much nice. > I don't believe I attacked any one person specifically, personally, but okay .. lets move on. There is code to be written and new things to be talked ab

Re: [openmoko-announce] Openmoko on Design

> you seem very passionate about your concerns. If you are going to > linux > world I'd be happy to meet and discuss things. > Or if you can make a list of specific problems I can try to > explain or > address your concerns. [reply off-list] ; -- Jay Vaughan

Re: Openmoko on Design

On 7/30/08 Daniel Benoy wrote: > Also, would the openmoko design team be willing to consider a toggle > in the configuration menu between manual and automatic? What we want is for people to add their own configuration options to menus in the form of packages installable from the "Installer". Th

Re: [openmoko-announce] Openmoko on Design

On Wednesday 30 July 2008 04:37:20 Christopher White wrote: Hi Cristopher, let me to understand why you are so in angry. > My frustration comes off as anger because I just can't seem to figure > out where to go at times. I know I signed up for a tough road, and I am > not afraid to rollup my sle

Re: Openmoko on Design

On 7/29/08 david varnes wrote: > On Tue, Jul 29, 2008 at 4:22 AM, Sean Moss-Pultz <[EMAIL PROTECTED]> > wrote: > [snip] > > > > > > Think of our products as museums. We're building the environment. > > I re-read Sean's post a couple of time (like a few people I am > guessing :-) > For some of

Re: Openmoko on Design

On 7/29/08 ian douglas wrote: > I feel that Sean has just given us (or perhaps just reiterated what > should have already been known), as a community, the means to empower > ourselves to help on *everything* about the Openmoko project as a > whole. > We wanted an open platform, and it's been given

Re: [openmoko-announce] Openmoko on Design

On 7/29/08 Stroller wrote: > Initially I was > really angry about the whole removal-of-the-keyboard-button-by- > shadowy-designers thing, and I've come to realise it's irrelevant and > > that I was stupid to get upset about it. Please don't think it's irrelevant. It's anything but. This is t

Re: Openmoko on Design

Scott wrote: > Charles, > > While that is a means of bringing the keyboard button back, thats just > too damn hard! And I have to do that all over again if I upgrade! > > Needs to be a simple configuration setting. Agreed, but I was just replying to that part: > if you HAVE to leave them out c

Re: Openmoko on Design

On Wed, Jul 30, 2008 at 01:47:29AM +0100, Al Johnson wrote: > I'll snip most of it to keep the length reasonable. same here :) > On Tuesday 29 July 2008, William Lai wrote: > > > > It already is. > > We've offered a couple of different solutions to community requests that > > were declined by, we

Re: Openmoko on Design

On Wednesday, 30. July 2008 10:18:33 Al Johnson wrote: > I agree with everything you say here. The keyboard should just appear when > I want it and disappear when I don't. The absence of a manual override > means that whenever it gets it wrong I can't correct it, the worst case > being when I need

Re: [openmoko-announce] Openmoko on Design

Hi Michele, > Cristopher, let me to understand why you are so in angry. Forgive me if I came across as very angry. I actually am not. I am frustrated, but I do not find fault with anyone in this regard. > Like you I sent my 350 Eur postcard (= 2 month of my house rent) for a > phone that I was

Re: Openmoko on Design

On Wednesday 30 July 2008, Marek Lindner wrote: > On Wednesday, 30. July 2008 04:57:27 Chris Wright wrote: > > Something as simple as a keyboard button -- well, users were > > complaining about its lack very quickly. If the design team were also > > users, then they would have insisted that the err

Re: Openmoko on Design

On Tue, 29 Jul 2008 20:56:23 -0400 Daniel Benoy <[EMAIL PROTECTED]> babbled: > Is it feasible to have illume detect that an application isn't > capable/interested in sending the signal to bring up the keyboard? with the matchbox protocol - it is not possible. with the new protocol i put in (whic

Re: Openmoko on Design

On Wednesday, 30. July 2008 04:57:27 Chris Wright wrote: > Where I work, the design team is the same as the development team. May I ask where you work and what kind of consumer products you are creating ? > Something as simple as a keyboard button -- well, users were > complaining about its lack

Re: Openmoko on Design

Is it feasible to have illume detect that an application isn't capable/interested in sending the signal to bring up the keyboard? Also, would the openmoko design team be willing to consider a toggle in the configuration menu between manual and automatic? I have a portable bluetooth keyboard (S

Re: Openmoko on Design

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: Snipped > > 3) If the design department is

Re: Openmoko on Design

On Wed, 30 Jul 2008 01:05:35 +0800 Marek Lindner <[EMAIL PROTECTED]> babbled: > Do you mean that sentence: > "we are paid by openmoko to do what we are told to do by the design > department and that is what we then do." If that's the state of things for > paid developers, then community contri

RE: Openmoko on Design

Thanks marek. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marek Lindner Sent: Tuesday, July 29, 2008 10:06 AM To: List for Openmoko community discussion Subject: Re: Openmoko on Design On Tuesday, 29. July 2008 19:19:10 Al Johnson wrote

Re: Openmoko on Design

2008/7/29 Marek Lindner <[EMAIL PROTECTED]>: > On Tuesday, 29. July 2008 20:17:00 Chris Wright wrote: >> But you do have a design team, according to Rasterman. > > Of course we have. How do you think we are trying to get to a device that is > ready for end user ? And this is just the beginning. We

Re: Openmoko on Design

No bad intentions for snipping, Just trying to get to the facts: Brian C wrote: > > 1) Who is Openmoko's "design department"? That would be: William Lai - PM Regina Kim - Testing Wendy Hung - Testing > 2) Many in the community believed that Openmoko wanted the community to > contribute code

RE: Openmoko on Design

om: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david varnes Sent: Monday, July 28, 2008 5:32 PM To: [EMAIL PROTECTED]; List for Openmoko community discussion Subject: Re: Openmoko on Design On Tue, Jul 29, 2008 at 4:22 AM, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: [snip] > >

RE: Openmoko on Design

] [mailto:[EMAIL PROTECTED] On Behalf Of Jay Vaughan Sent: Monday, July 28, 2008 1:21 PM To: [EMAIL PROTECTED]; List for Openmoko community discussion Subject: Re: Openmoko on Design > Let's start simple. And grow. I know we can get there! Get where exactly? Got coordinates for that destinat

Re: Openmoko on Design

On Tuesday, 29. July 2008 20:17:00 Chris Wright wrote: > But you do have a design team, according to Rasterman. Of course we have. How do you think we are trying to get to a device that is ready for end user ? And this is just the beginning. We will work with more designers for the UI, the housi

Re: [openmoko-announce] Openmoko on Design

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cristopher, let me to understand why you are so in angry. Like you I sent my 350 Eur postcard (= 2 month of my house rent) for a phone that I was knowing was not software complete (and some possible hardware bug). OM wrote very well on the homepage t

Re: Openmoko on Design

Chris Wright wrote: > > > Still, nobody has mentioned why the design team can't be contacted or > identified. > Posted to the list a couple days ago: http://lists.openmoko.org/pipermail/community/2008-July/023806.html We can be contacted, just wasn't using an openmoko email at the time I wrot

RE: [openmoko-announce] Openmoko on Design

EMAIL PROTECTED] On Behalf Of Jay Vaughan Sent: Tuesday, July 29, 2008 7:53 AM To: List for Openmoko community discussion Subject: Re: [openmoko-announce] Openmoko on Design > I am no one to tell to you how to use your time, but I personally > thing that continuing to use your time to repeat how

Re: [openmoko-announce] Openmoko on Design

On Tue, 2008-07-29 at 16:02 +0200, Michele Renda wrote: > I think this require some hours hour man-time (let suppose 3-4 h) I'll agree that responding as Jay has takes considerable time, but I disagree with what a person can do. > In 3-4 hours a person can do: > > To learn a bit how to wri

RE: [openmoko-announce] Openmoko on Design

] Openmoko on Design -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jay Vaughan wrote: > I'm glad OpenMoko has as many rabid fanboix as other projects, it > means there is hope yet .. Usually I am not too much disposed to moderation in a ML, but now I am started to think: In these t

Re: Openmoko on Design

On Tuesday, 29. July 2008 19:19:10 Al Johnson wrote: > Whether the term is 'key developer' or just 'a developer' is irrelevant. > The issue is the total lack of communication over removal of a function > many in the community, not to mention said developer, have good technical > reasons to see as a

Re: [openmoko-announce] Openmoko on Design

> I am no one to tell to you how to use your time, but I personally > thing > that continuing to use your time to repeat how many stupid things > Openmoko do, and complaining how many fanboy there are, is not the > best > way to help this project. Then do you what do you think is better! > I

Re: [openmoko-announce] Openmoko on Design

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jay Vaughan wrote: > I'm glad OpenMoko has as many rabid fanboix as other projects, it > means there is hope yet .. Usually I am not too much disposed to moderation in a ML, but now I am started to think: In these two days you wrote around 15 email

Re: Openmoko on Design

Charles, While that is a means of bringing the keyboard button back, thats just too damn hard! And I have to do that all over again if I upgrade! Needs to be a simple configuration setting. Scott Charles-Henri Gros wrote: You mean like this? http://wiki.openmoko.org/wiki/ASU_Keyboard_Togg

Re: [openmoko-announce] Openmoko on Design

>> This does not work. That is all. > As Sean already said. You are only speaking for yourself. > I am not alone in my view. > I am glad that OpenMoko is not just another half-open half-closed > effort > that once thought: "Oh look Linux. It doesn't cost a dime. Let's make > something that is

Re: [openmoko-announce] Openmoko on Design

I have to agree with Kalle & Jay, While i part of me would like to see a nailed down platform with a clear definition of tools, UI standards, platform support, documentation standards(one I've been yelling about recently) I also understand OM's struggle to produce a viable open source product

Re: Openmoko on Design

2008/7/29 Marek Lindner <[EMAIL PROTECTED]>: > > Hi, > >> At the same time we heard comments from a key developer who indicated >> that the decision was made above him by unnamed individuals with whom >> the community has no obvious means of communication, and who apparently >> don't even listen to

Re: Openmoko on Design

On Tuesday 29 July 2008, Marek Lindner wrote: > Hi, > > > At the same time we heard comments from a key developer who indicated > > that the decision was made above him by unnamed individuals with whom > > the community has no obvious means of communication, and who apparently > > don't even listen

Re: [openmoko-announce] Openmoko on Design

Hi, Jay Vaughan schrieb: > [snip] > > This does not work. That is all. As Sean already said. You are only speaking for yourself. I am glad that OpenMoko is not just another half-open half-closed effort that once thought: "Oh look Linux. It doesn't cost a dime. Let's make something that is flas

Re: Openmoko on Design

On 29 Jul 2008, at 09:23, Marcus Bauer wrote: > ... > Openmoko should concentrate on kernel and driver work, power > management > and working hardware and a basic set of apps. ... +1 As Openmoko push more open hardware out the door, people will come running to do cool stuff on it. It's the

Re: [openmoko-announce] Openmoko on Design

> If you need a benevolent dictator to lead, why not become one yourself? > If you need standards why not make them? This is not a responsibility > of the Openmoko team. They already gave us the damn thing to build it > all on. This really is the job of the community. Stop whining and start > doing

Re: Openmoko on Design

Hi, > At the same time we heard comments from a key developer who indicated > that the decision was made above him by unnamed individuals with whom > the community has no obvious means of communication, and who apparently > don't even listen to the reasonable technical arguments of key > develope

Re: Openmoko on Design

On Tue, 29 Jul 2008 10:23:41 +0200, Marcus Bauer <[EMAIL PROTECTED]> wrote: > No developer who is sane in his mind will want to marry a whole PIM API > just for sending an SMS. And FSO is essentially a newly invented, > unstable and immature PIM API. This is so much like Microsoft. > > And there

Re: Openmoko on Design

On Tue, 2008-07-29 at 00:35 -0700, Brian C wrote: [snip ] > So, I'll ask again: does > Openmoko intend to allow direct code contributions by community members > to core components of the ASU/FSO frameworks? It would be better to get rid of this whole framework concept and doing what Sean is cons

Re: Openmoko on Design

> A keyboard that always automatically knows when it is needed > sounds great in theory, but prior to that perfect keyboard being > implemented, what happened here was that users experienced a > degradation > in usability and had no obvious means of restoring the lost > functionality. They were

Re: Openmoko on Design

Sean Moss-Pultz wrote: > > Dear Community > > > Design. This is a long, careful response to Sean's "Openmoko on Design" post. If one goes back to the beginning of the "Terminal for ASU" thread, what you find is that several users were just getting thi

Re: Openmoko on Design

On Mon, 2008-07-28 at 17:14 -0700, ian douglas wrote: > And while Openmoko is working on their own framework, I have to agree > with many other voices: knowing which platform to develop for, as a > developer myself, is confusing. This is exactly the point. Openmoko should be like Ubuntu: integrat

Re: Openmoko on Design

Lisa wrote: > ~ Folks, > ~ I don't need a major design statement for my phone...I just want > a (mostly) working phone. There is a point where "taking one more thing > away" doesn't make it simpler any longer, it makes it hard to figure > out/work on. Not having a terminal in ASU ( the ge

Re: [openmoko-announce] Openmoko on Design

>> Jay, your negative posts on this ML do nothing but foster an >> unpleasant atmosphere > Actually I disagree a bit here. Jay is not trolling but just saying > where he's trying to come from. Thank you Kalle .. no, I'm not trolling, yes I am voicing a strong opinion, yes I do think the Freerunn

Re: [openmoko-announce] Openmoko on Design

> If you need a benevolent dictator to lead, why not become one > yourself? Because there is one already, he just doesn't have any power to make smart design decisions because of some new-age hippy-dippy faff. > If you need standards why not make them? This is not a responsibility > of the Op

Re: Openmoko on Design

> And while Openmoko is working on their own framework, I have to agree > with many other voices: knowing which platform to develop for, as a > developer myself, is confusing. I don't like the thought of having to > write multiple versions of an application that caters to GTK and Qt > separately, a

Re: [openmoko-announce] Openmoko on Design

> Jay, your negative posts on this ML do nothing but foster an > unpleasant atmosphere. Last I checked, no one put a gun to your head > and forced you to buy or design for the FR. If you're tired of > waiting for the device to become stable, sell the phone and check > back again in about a

Re: [openmoko-announce] Openmoko on Design

> I think my first project will be called MokoBingo! (with the > exclamation mark!)! It will check the mailing list on a regular basis > and the Freerunner will make a squeaky noise when any of the > following terms are encountered: heh heh .. please do this! :) ; -- Jay Vaughan __

Re: [openmoko-announce] Openmoko on Design

Nkoli wrote: > On Mon, Jul 28, 2008 at 5:22 PM, Jay Vaughan <[EMAIL PROTECTED] > > wrote: > > > Having worked in Open-Hardware for over 15 years now, I was, in fact, > expecting a much more coherent strategy for the software platform on > Freerunner than just

Re: [openmoko-announce] Openmoko on Design

> blab blab blab > > Jay Vaughan If you need a benevolent dictator to lead, why not become one yourself? If you need standards why not make them? This is not a responsibility of the Openmoko team. They already gave us the damn thing to build it all on. This really is the job of the community. Stop

Re: Openmoko on Design

On Tue, Jul 29, 2008 at 4:22 AM, Sean Moss-Pultz <[EMAIL PROTECTED]> wrote: [snip] > > Think of our products as museums. We're building the environment. I re-read Sean's post a couple of time (like a few people I am guessing :-) For some of us 'museum' may have an old/musty connotation. When I p

Re: Openmoko on Design

ezuall wrote: > Potential, that is the first word that comes to mind when I think about and > play with my freerunner. I spent months absolutely obsessively waiting for > the release, but when I first received it I was afraid. I agree, there's unlimited potential. To be honest, I was all hyped a

Re: [openmoko-announce] Openmoko on Design

On Mon, Jul 28, 2008 at 5:22 PM, Jay Vaughan <[EMAIL PROTECTED]> wrote: > > Having worked in Open-Hardware for over 15 years now, I was, in fact, > expecting a much more coherent strategy for the software platform on > Freerunner than just "let the community decide". Certainly, the > community as

Re: [openmoko-announce] Openmoko on Design

;blue sky". I don't want to sound negative (again!) because over the weekend I've had a bit of a revelation about Openmoko, and I'm feeling much more positive than I was a couple of days ago. I've just spent quite a bit of time trying to express that in a reply to "

Re: Openmoko on Design

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ~ Folks, ~ I don't need a major design statement for my phone...I just want a (mostly) working phone. There is a point where "taking one more thing away" doesn't make it simpler any longer, it makes it hard to figure out/work on. Not having a

Re: [openmoko-announce] Openmoko on Design

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jay Vaughan wrote: > It is *important* that such things as a usable GUI, which > looks nice, are presented very, very rapidly - there is no other way > for our projects to snowball than to attract the interest of those who > will use the hardware

Re: Openmoko on Design

y I wanted to and there is a lot of potential. Rock on freerunners! -- View this message in context: http://n2.nabble.com/Openmoko-on-Design-tp587159p587441.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko communi

Re: [openmoko-announce] Openmoko on Design

> I can't speak for anybody else, but what were you actually expecting > of > the Neo FR? A finished SDK that you can develop against to build your > app on? Having worked in Open-Hardware for over 15 years now, I was, in fact, expecting a much more coherent strategy for the software platform

Re: [openmoko-announce] Openmoko on Design

> Openmoko is trying to do what can: is trying to build a phone. It is > trying to build a running open hardware: It will not be perfect but it > will be open. You will know all the defect and compromise token to get > it. Then is your choose. And don't tell to me that OM hardware is > broken > b

Re: [openmoko-announce] Openmoko on Design

Jay Vaughan wrote, On 28/07/08 21:31: >> Sorry to hear it doesn't work for you. But like I said, we each have >> our >> own ways of understanding and making meanings. >> You are free to create your own meanings. >> > > > I just can't see how you honestly believe all this panty-waiste > d

Re: [openmoko-announce] Openmoko on Design

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jay Vaughan wrote: > Because at this point, it seems to me that you've just pissed in the > koolaid. Basically, you're just selling incomplete, mediocre hardware > in order to cash in on the "Open Community" meme, or what? Hi Jay. First person t

Re: Openmoko on Design

On Mon, 28 Jul 2008 22:21:28 +0200 Jay Vaughan <[EMAIL PROTECTED]> wrote: > > Let's start simple. And grow. I know we can get there! > > > Get where exactly? Got coordinates for that destination? Maybe Tango GPS can help trace the route? solar.george signature.asc Description: PGP signature

Re: [openmoko-announce] Openmoko on Design

> Sorry to hear it doesn't work for you. But like I said, we each have > our > own ways of understanding and making meanings. > You are free to create your own meanings. I just can't see how you honestly believe all this panty-waiste dilettante waffling about "not having a design because its

Re: [openmoko-announce] Openmoko on Design

On 7/29/08 Jay Vaughan wrote: > [snip] > > This does not work. That is all. Sorry to hear it doesn't work for you. But like I said, we each have our own ways of understanding and making meanings. You are free to create your own meanings. -Sean _

Re: Openmoko on Design

Hi Alex On 7/29/08 Alex Kavanagh wrote: > Thanks for an excellent post. It gives me an even better insight into > OpenMoko's vision. Glad it helps. We will be building from here in near future. I know things have been a bit chaotic in the past. But we're really starting to come together now.

Re: Openmoko on Design

> Let's start simple. And grow. I know we can get there! Get where exactly? Got coordinates for that destination? By the sounds of it, not really .. ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists

Re: Openmoko on Design

Thanks for an excellent post. It gives me an even better insight into OpenMoko's vision. Thanks for all of the hard work! Cheers Alex. Sean Moss-Pultz wrote, On 28/07/08 19:22: > Dear Community > > > Design. > > Many people seem to expect an explanation of "design" from Openmoko. > This isn't

Re: Openmoko on Design

On 7/29/08 Michele Renda wrote: > There is a lot of work to do, and OM can't all this alone. Exactly. This is really the essense of what I want to say. We need your help to organize our environment. We need to focus on this. Flashy design can come later if that's what's wanted. We are open. Th

Re: [openmoko-announce] Openmoko on Design

[snip] This does not work. That is all. ; -- Jay Vaughan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community

  1   2   >