Community Updates

From Openmoko

(Difference between revisions)
Jump to: navigation, search
 
(183 intermediate revisions by 46 users not shown)
Line 1: Line 1:
'''Community Updates'''
+
{{Languages}}
 +
This page gives you access to some regular updates released by the projects, OM or community. All communications channels of the Openmoko community are listed at the [[Community Resources]] page.
  
As we strive to make our development progress as open as possible, we do not provide delivery dates. Instead, we continuously report on the project status here and on our mailing list.  
+
The official Openmoko updates (discontinued early 2009) can be found in [[Weekly Engineering News]].
  
The status is usually updated at least twice a month, usually by Michael Shiloh ([[User:MichaelShiloh]]). Updates are also mailed to the community mailing list (see below for previous updates), and major updates are also sent to the announce list.
+
You can see the latest edition [[Community_Updates/current]]
  
You are invited to add questions or topics you think should be included in the Community Updates.
+
= Post launch series =
 +
* [[Community Updates/Draft]]
 +
* [[Community Updates/2011-12-01]]
 +
* [[Community Updates/2011-09-01]]
 +
* [[Community Updates/2011-05-01]]
 +
* [[Community Updates/2011-03-01]]
 +
* [[Community Updates/2011-02-01]]
 +
* [[Community Updates/2010-12-01]]
 +
* [[Community Updates/2010-11-01]]
 +
* [[Community Updates/2010-09-01]]
 +
* [[Community Updates/2010-08-01]]
 +
* [[Community Updates/2010-07-01]]
 +
* [[Community Updates/2010-06-01]]
 +
* [[Community Updates/2010-05-01]]
 +
* [[Community Updates/2010-04-01]]
 +
* [[Community Updates/2010-03-01]]
 +
* [[Community Updates/2010-02-10]]
 +
* [[Community Updates/2010-01-14]]
 +
* [[Community Updates/2009-12-31]]
 +
* [[Community Updates/2009-12-09]]
 +
* [[Community Updates/2009-11-25]]
 +
* [[Community Updates/2009-11-11]]
 +
* [[Community Updates/2009-10-28]]
 +
* [[Community Updates/2009-10-14]]
 +
* [[Community Updates/2009-09-30]]
 +
* [[Community Updates/2009-09-16]]
 +
* [[Community Updates/2009-09-02]]
 +
* [[Community Updates/2009-08-19]]
 +
* [[Community Updates/2009-08-06]]
 +
* [[Community Updates/2009-07-23]]
 +
* [[Community Updates/2009-07-09]]
 +
* [[Community Updates/2009-06-25]]
 +
* [[Community Updates/2009-05-22]]
 +
* [[Community Updates/2009-04-30]]
 +
* [[Community Updates/2009-04-17]]
 +
* [[Community Updates/2009-04-05]]
 +
* [[Community Updates/2009-03-20]]
 +
* [[Community Updates/2009-03-06]]
 +
* [[Community Updates/2009-02-20]]
 +
* [[Community Updates/2009-02-06]]
 +
* [[Community Updates/2009-01-23]]
 +
* [[Community Updates/2009-01-12]]
 +
* [[Community Updates/2008-12-29]]
 +
* [[Community Updates/2008-12-15]]
 +
* [[Community Updates/2008-12-01]]
 +
* [[Community Updates/2008-11-16]]
 +
* [[Community Updates/2008-11-02]]
 +
* [[Community Updates/2008-10-19]]
 +
* [[Community Updates/2008-10-03]]
 +
* [[Community Updates/2008-09-17]] - Activity since launch
  
==Current Status==
+
== Rules for community updates ==
 +
After May 22nd 2009 OM stopped working on community updates. These rules are here to make it possible for the community to keep the updates running.
  
===GTA02 hardware production and qualification===
+
The draft of the news will be listed here but not on the main page until it gets released. (example, see [[Community Updates/Draft]] ). Upon the release of the current updates a new page should be created. The news will be added there. On release, the link will be set on the main page. Detailed instructions below.
GTA02v3 is quite solid, but a flaw in power distribution required another revision. A very small number of GTA02v4 have been manufactured. Evaluation by internal OpenMoko engineers should start any day now (relative to October 31, 2007).
+
  
===gllin GPS driver for GTA01===
+
'''Adding news'''
We have received permission to distribute this driver in binary-only form, however the binary format is different from what we now use (OABI vs EABI in 2007.2 vs 2007.1 OpenMoko). There are various work-arounds (chroot, wrapper) but they raise legal questions. We are in the process of sorting out these legal issues.
+
# Don't expect someone else to add it, add it yourself and make it nice
 +
# Add links to blog posts, applications, mailing list posts that you think are worth to announce to the whole community
  
===The apparent lack of 850 MHz GSM support in USA+Canada (e.g. comment 24 on bug #256)===
+
'''Releasing'''
I think it's a combination hardware and software issue.
+
# If it's The Release Date and you notice the news has not been released, DO IT! Don't expect someone else to do it for you.
===Delivery of a GSM firmware update for the 3G SIM bug (#666)===
+
# When you release, move the content of Talk: page to the actual wikipage.
I believe the problem has been solved and we have permission to update the firmware, but there is a question as to how to legally update in the field.
+
# Add a link to the released update page to http://wiki.openmoko.org/index.php?title=Community_Updates
===The current Neo1973 is not FCC approved to operate in the 850Mhz band===
+
# Prepare the draft page for the next community news: captions, dates etc.. Releasing news on Thursdays every two weeks sound's good to me.
It would be illegal for FIC to sell the device in the US with it activated. BT and PCS is the only approved band currently.
+
# Send a post to the community mailing list with the link to the released news and the draft of the next news.
  
http://www.phonescoop.com/phones/fcc_query.php?gc=EUN&pc=GTA01BV4
+
= Ramp up to launch series =
  
==Questions or Topics you think are missing==
+
Even though Openmoko strives to keep the community informed of the development progress, Openmoko does not provide delivery dates. Instead, Openmoko Inc. reports and discusses the project on a day to day basis, using the [http://lists.openmoko.org/pipermail/community/ openmoko-community mailing list]. Developers will wish to follow the progress on the [http://lists.openmoko.org/pipermail/openmoko-kernel/ openmoko-kernel mailing list] and the [http://lists.openmoko.org/pipermail/devel/ devel mailing list]. Major updates notices are sent to the [http://lists.openmoko.org/pipermail/announce/ announce mailing list].
  
=== SMedia 3362 Documentation & OpenGL ES Drivers ===
+
As FreeRunners started shipping, that series of Community Updates mostly related to the expected release date has been taken over by a more community-oriented newsletter.
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and OpenMoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).  
+
  
Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation OpenMoko developers will be writing themselves, not the technical documentation SMedia have provided OpenMoko with. The OpenMoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)
+
* [http://lists.openmoko.org/pipermail/community/2008-June/019384.html 2008-06-14 - When it will be possible to buy Openmoko?]
 
+
* [http://lists.openmoko.org/pipermail/community/2008-June/018887.html 2008-06-10 - SMT is running!]
==Previous Community Updates==
+
* [http://lists.openmoko.org/pipermail/community/2008-June/018575.html 2008-06-05 - Cleared to start Mass production]
*[[September 28, 2007 Community Update]]
+
* [http://lists.openmoko.org/pipermail/community/2008-May/017531.html 2008-05-20 - Whats up with the freerunner mass production?]
*[[October 12, 2007 Community Update]]
+
* [http://lists.openmoko.org/pipermail/community/2008-April/015189.html 2008-04-14 - next costumers location]
*[[October 13, 2007 Community Update]]
+
* [http://lists.openmoko.org/pipermail/community/2008-April/015080.html 2008-04-11 - FreeRunner Pricing and PVT update]
*[[October 15, 2007 Community Update]]
+
* [http://lists.openmoko.org/pipermail/community/2008-April/014928.html 2008-04-07 - Any updates on the PVT status?]
*[[October 16, 2007 Community Update]]
+
* [http://lists.openmoko.org/pipermail/community/2008-March/014361.html 2008-03-25 - Production status Update]
*[[October 25, 2007 Community Update]]
+
* [http://lists.openmoko.org/pipermail/community/2008-February/013555.html 2008-02-25 - Community Update]
*[[October 31, 2007 Community Update]]
+
* [http://lists.openmoko.org/pipermail/community/2008-February/013356.html 2008-02-14 - Community Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-February/013280.html 2008-02-10 - Community Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-January/012821.html 2008-01-24 - Community Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-January/012499.html 2008-01-10 - Community Update]
 +
* [http://lists.openmoko.org/pipermail/community/2008-January/012357.html 2008-01-02 - Community Update]
  
 +
[[Category:Community Update| ]]
 
[[Category:Community]]
 
[[Category:Community]]

Latest revision as of 06:50, 25 November 2011

This page gives you access to some regular updates released by the projects, OM or community. All communications channels of the Openmoko community are listed at the Community Resources page.

The official Openmoko updates (discontinued early 2009) can be found in Weekly Engineering News.

You can see the latest edition Community_Updates/current

[edit] Post launch series

[edit] Rules for community updates

After May 22nd 2009 OM stopped working on community updates. These rules are here to make it possible for the community to keep the updates running.

The draft of the news will be listed here but not on the main page until it gets released. (example, see Community Updates/Draft ). Upon the release of the current updates a new page should be created. The news will be added there. On release, the link will be set on the main page. Detailed instructions below.

Adding news

  1. Don't expect someone else to add it, add it yourself and make it nice
  2. Add links to blog posts, applications, mailing list posts that you think are worth to announce to the whole community

Releasing

  1. If it's The Release Date and you notice the news has not been released, DO IT! Don't expect someone else to do it for you.
  2. When you release, move the content of Talk: page to the actual wikipage.
  3. Add a link to the released update page to http://wiki.openmoko.org/index.php?title=Community_Updates
  4. Prepare the draft page for the next community news: captions, dates etc.. Releasing news on Thursdays every two weeks sound's good to me.
  5. Send a post to the community mailing list with the link to the released news and the draft of the next news.

[edit] Ramp up to launch series

Even though Openmoko strives to keep the community informed of the development progress, Openmoko does not provide delivery dates. Instead, Openmoko Inc. reports and discusses the project on a day to day basis, using the openmoko-community mailing list. Developers will wish to follow the progress on the openmoko-kernel mailing list and the devel mailing list. Major updates notices are sent to the announce mailing list.

As FreeRunners started shipping, that series of Community Updates mostly related to the expected release date has been taken over by a more community-oriented newsletter.

Personal tools

Community Updates

As we strive to make our development progress as open as possible, we do not provide delivery dates. Instead, we continuously report on the project status here and on our mailing list.

The status is usually updated at least twice a month, usually by Michael Shiloh (User:MichaelShiloh). Updates are also mailed to the community mailing list (see below for previous updates), and major updates are also sent to the announce list.

You are invited to add questions or topics you think should be included in the Community Updates.

Current Status

GTA02 hardware production and qualification

GTA02v3 is quite solid, but a flaw in power distribution required another revision. A very small number of GTA02v4 have been manufactured. Evaluation by internal OpenMoko engineers should start any day now (relative to October 31, 2007).

gllin GPS driver for GTA01

We have received permission to distribute this driver in binary-only form, however the binary format is different from what we now use (OABI vs EABI in 2007.2 vs 2007.1 OpenMoko). There are various work-arounds (chroot, wrapper) but they raise legal questions. We are in the process of sorting out these legal issues.

The apparent lack of 850 MHz GSM support in USA+Canada (e.g. comment 24 on bug #256)

I think it's a combination hardware and software issue.

Delivery of a GSM firmware update for the 3G SIM bug (#666)

I believe the problem has been solved and we have permission to update the firmware, but there is a question as to how to legally update in the field.

The current Neo1973 is not FCC approved to operate in the 850Mhz band

It would be illegal for FIC to sell the device in the US with it activated. BT and PCS is the only approved band currently.

http://www.phonescoop.com/phones/fcc_query.php?gc=EUN&pc=GTA01BV4

Questions or Topics you think are missing

SMedia 3362 Documentation & OpenGL ES Drivers

There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and OpenMoko developers will not be writing one in the near future (although they have not ruled it out in the long-term).

Documentation for the SMedia 3362 has been promised (see this post). However, this refers to documentation OpenMoko developers will be writing themselves, not the technical documentation SMedia have provided OpenMoko with. The OpenMoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See this post for details)

Previous Community Updates