I have the same problem, I don't feel to be called a developper. I'am a network guy (Open source first, but network).<br><br>So I propose that all members of the Open Moko mailing lists may have a priority on purchassing a phone for testing/troubleshooting (of course) if theire is some devices left after develpppers. :):):)
<br><br><br>Best regards, and congratulation to the all team, step one is almost completed !!!!<br>Foucault (In a hurry to free his phone)<br><br><br><div><span class="gmail_quote">On 2/12/07, <b class="gmail_sendername">
Ryan Kline</b> <<a href="mailto:radryan214@gmail.com">radryan214@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">You have 845 people subscribed to this list who all support what you do 100%. Delays just make us want one more.<span class="q"><div><br></div><div><i>>All interested developers can purchase Neos starting late March.
</i></div></span><div><div>Do you have to be a developer to purchase in March? I am going to try to learn GTK+, but I doubt I will call myself a developer by then.</div><div><br></div><div>Keep up the great work.</div><span class="sg">
<div><br></div><div>-ryan</div></span><div><span class="e" id="q_110b65a72c8e3f7d_4"><div><br><div><div>On Feb 12, 2007, at 3:17 AM, Sean Moss-Pultz wrote:</div><br><blockquote type="cite"><div style="margin: 0px;">Dear Community,
</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">We, the OpenMoko Team, have promised exciting news about our project</div><div style="margin: 0px;">today. We have some information that we think you will like very much,
</div><div style="margin: 0px;">but also have some news we like less. Let us first address the</div><div style="margin: 0px;">unpleasant part, before turning to the more cheerful part of this</div><div style="margin: 0px;">
announcement.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">After we announced OpenMoko last November, we were flooded with emails.</div><div style="margin: 0px;">Most were absolutely encouraging, thanking us for undertaking this
</div><div style="margin: 0px;">project. And out of the many thousands of emails, only two requests came</div><div style="margin: 0px;">again and again: "Where's bluetooth?" And, "Why doesn't it have WiFi?"
</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">(We really do read _everything_ you write.)</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Originally, bluetooth was in our product spec, however, this was left
</div><div style="margin: 0px;">out of our schematics in an early stage. At the time we were really</div><div style="margin: 0px;">hurting for resources internally, so we did not push. Making changes to</div><div style="margin: 0px;">
a product while in the R&D stages can be quite painful. But after all</div><div style="margin: 0px;">the incredible demand, post-November, we felt it had to be done.</div><div style="margin: 0px; min-height: 14px;"><br>
</div><div style="margin: 0px;">We had a string of bad luck that really hurt our productivity. Each</div><div style="margin: 0px;">hardware revision takes at least one month of time. Each month without</div><div style="margin: 0px;">
stable hardware means serious delays for software.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">One time we received the wrong memory from our vendors and we failed to</div><div style="margin: 0px;">
catch this before production. Another time some key components ran out</div><div style="margin: 0px;">of supply. And as if all that wasn't bad enough, our baseband leader's</div><div style="margin: 0px;">mom died leaving a gaping wound in both his heart and our hardware
</div><div style="margin: 0px;">team.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">But we moved on. Little by little our hardware started to come together.</div><div style="margin: 0px;">
Around the middle of January we thought we finally found a stable</div><div style="margin: 0px;">revision. At this point, our software was seriously behind schedule, but</div><div style="margin: 0px;">as Alan Cox once said, "Free Software is always late."
</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">January's announcement bought us more time to fix some hardware issues</div><div style="margin: 0px;">still plaguing us. We also modified the position of the bluetooth module
</div><div style="margin: 0px;">to make way for a JTAG port (we're trying our best to be hacker</div><div style="margin: 0px;">friendly). This required our vendor to design a special FPC to connect</div><div style="margin: 0px;">
the module to our board. Something on the order of 3 weeks would be</div><div style="margin: 0px;">required to complete this "simple" task.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">
One thousand little Murphy's seems to be what we have running around</div><div style="margin: 0px;">teasing this project. Less than a 7% yield rate is all that we got out<span> </span></div><div style="margin: 0px;">of this new cable; not even enough to meet our Phase 0 demand. Needless
<span> </span></div><div style="margin: 0px;">to say, it was an incredibly depressing day for all of us.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">"Tormented" is really the only word that we can think of now to describe
</div><div style="margin: 0px;">how we are feeling as a team, forced with making this decision: Do we <span> </span></div><div style="margin: 0px;">delay again, wait for the hardware and software to be ready, or do we</div>
<div style="margin: 0px;">just open up now as promised without reaching our key milestone?</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Each of us, in different ways, have struggled with this decision for
</div><div style="margin: 0px;">the past five days. We're all extremely demanding of ourselves when it</div><div style="margin: 0px;">comes to the quality of our work. Nearly every minute of our waking</div><div style="margin: 0px;">
lives have been spent on this project. So to be at this state, now, is</div><div style="margin: 0px;">really hard on us.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Mickey Lauer, one of our core developers sent an email, only a few hours
</div><div style="margin: 0px;">ago, that put things back into perspective for us. He said,</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;"><span> </span>"A lot of people will be disappointed by the state of the
</div><div style="margin: 0px;"><span> </span>software, but -- I may be a dreamer -- I prefer rough and truly</div><div style="margin: 0px;"><span> </span>open solutions (where I have the chance to help shaping the</div>
<div style="margin: 0px;"><span> </span>future) over cool, but already finished and closed solutions</div><div style="margin: 0px;"><span> </span>(where all I can do is take the platform as it is or NOT.)"</div><div style="margin: 0px; min-height: 14px;">
<br></div><div style="margin: 0px;">As planned, we are going to open this project up at this point. Within<span> </span></div><div style="margin: 0px;">three days of this announcement you will all have access to our source
<span> </span></div><div style="margin: 0px;">code, Wiki, and Bugzilla.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Hopefully you can understand why we're at this less-than-ideal state.
</div><div style="margin: 0px;">But more importantly, we hope you understand that opening our code now,</div><div style="margin: 0px;">and letting you join us in making this dream of an open phone platform</div><div style="margin: 0px;">
come true, is more important for us than mere appearances.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Regarding our Neo1973 hardware, we will send out the first batch of</div><div style="margin: 0px;">
phase 0 phones out around the end of this month. Sorry for not being</div><div style="margin: 0px;">able to give an absolute date. Next week is Chinese New Year (we're in</div><div style="margin: 0px;">Asia remember) and _everyone_ stops working for a full week. Having our
</div><div style="margin: 0px;">newly designed FPC built before is really wishful thinking.</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">All interested developers can purchase Neos starting late March. Please
<span> </span></div><div style="margin: 0px;">understand that phase 0 is a system of "checks and balances," so it</div><div style="margin: 0px;">simply cannot be rushed. We want to get the framework right, the first
</div><div style="margin: 0px;">time around. Hopefully you all can live with the slight delays in our</div><div style="margin: 0px;">schedule. We're all super excited to be cranking again and eagerly await</div><div style="margin: 0px;">
sending you hardware so you can join us in the party ;-)<span> </span></div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Finally, we will offer Neos to end users sometime in September of this
</div><div style="margin: 0px;">year. People everywhere will finally begin to understand the real power</div><div style="margin: 0px;">of an open phone with a strong community behind it. Within this</div><div style="margin: 0px;">
relationship between humans and Neos, a new kind of device will emerge.</div><div style="margin: 0px;">"Freed Phones", will have the potential to forever change the way people</div><div style="margin: 0px;">think of technology. This is the challenge that drives us. And it awaits
</div><div style="margin: 0px;">each an every one of you, along with our full support. <span> </span></div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">
Now, "Free Your Phone."</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">Sincerely,</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px;">The OpenMoko Team
</div><div style="margin: 0px; min-height: 14px;"><br></div><div style="margin: 0px; min-height: 14px;"><br></div> </blockquote></div><br></div></span></div></div></div><br>_______________________________________________<br>
OpenMoko community mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://lists.openmoko.org/mailman/listinfo/community" target="_blank">
https://lists.openmoko.org/mailman/listinfo/community</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Mail : <a href="mailto:foucault@thaumiers.com">foucault@thaumiers.com</a><br>Photos : Updated 22 mai 2006<br>
<a href="http://foucault.debonneval.free.fr/mGallery/">http://foucault.debonneval.free.fr/mGallery/</a><br>FreePhone : +33 (0) 871 73 53 96