http://wiki.openmoko.org/api.php?action=feedcontributions&user=Ferric&feedformat=atomOpenmoko - User contributions [en]2013-05-24T03:43:46ZUser contributionsMediaWiki 1.19.6http://wiki.openmoko.org/wiki/User:FerricUser:Ferric2009-03-13T00:37:30Z<p>Ferric: </p>
<hr />
<div>Proud GTA01 owner in NY<br />
<br />
coordinates: http://ferric.net/</div>Ferrichttp://wiki.openmoko.org/wiki/SHR_DevelopmentSHR Development2008-07-23T18:08:22Z<p>Ferric: /* Before beginning */</p>
<hr />
<div>== Building openmoko-dialer3 ==<br />
Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp|Bobby]] before starting one), put instructions for working on the project here!<br />
<br />
=== Before beginning ===<br />
You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br />
<br />
* Note: if building FSO fails using MokoMakefile (zhone! or no dbus show up on the top of the newly booted image), try using this<br />
method: http://wiki.openmoko.org/wiki/FSO<br />
<br />
The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br />
<br />
You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br />
<br />
=== Set up your BBPATH ===<br />
<br />
export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br />
<br />
=== Set up the CACHE ===<br />
<br />
export CACHE=tmp/cache<br />
<br />
<br />
<br />
=== Set up your local.conf ===<br />
Cd to your selected build directory.<br />
<br />
Create a directory under your current directory called 'conf'.<br />
<br />
cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br />
<br />
Append the following lines to your local.conf:<br />
BBFILES += "$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb"<br />
SELECTED_OPTIMIZATION = "-Os -g"<br />
<br />
''Note: Spaces are important in your bitbake conf files! You must have spaces before & after the = or +=''<br />
<br />
=== Set up your openmoko.conf (if using 2007.2) ===<br />
<br />
edit $MOKO/openembedded/conf/distro/openmoko.conf<br />
<br />
and make sure that these Gtk+ options are set:<br />
<br />
# Select package versions we want to use.<br />
PREFERRED_PROVIDER_gtk+ = "gtk+-fastscaling"<br />
PREFERRED_VERSION_gtk+-fastscaling = "2.10.14"<br />
<br />
<br />
=== Add your cross-compiler to your PATH ===<br />
<br />
export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br />
<br />
=== Run bitbake ===<br />
<br />
bitbake openmoko-dialer3<br />
<br />
After the first time you build successfully, you can build with<br />
<br />
bitbake -b openmoko-dialog3_svn<br />
<br />
which is much faster.<br />
<br />
=== To recompile, and only recompile ===<br />
<br />
bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br />
<br />
=== Troubleshooting ===<br />
<br />
==== General ====<br />
One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Community]]<br />
[[Category:SHR]]<br />
[[Category:SHR Devel]]</div>Ferrichttp://wiki.openmoko.org/wiki/SHR_DevelopmentSHR Development2008-07-23T18:07:51Z<p>Ferric: /* Building openmoko-dialer3 */</p>
<hr />
<div>== Building openmoko-dialer3 ==<br />
Currently this is the only package of any size being developed for SHR, and it's the only one with any instructions. If you start another SHR project (please check with [[User:Wurp|Bobby]] before starting one), put instructions for working on the project here!<br />
<br />
=== Before beginning ===<br />
You must build openembedded before you can build SHR packages. The easiest way is to go to http://wiki.openmoko.org/wiki/Mokomakefile and build using the instructions for FSO.<br />
<br />
* Note: if building FSO fails using MokoMakefile (zhone! or no dbus show up on the top of the newly booted image), try using htis method: http://wiki.openmoko.org/wiki/FSO<br />
<br />
The rest of these instructions are written assuming that you used Mokomakefile and that the directory you downloaded the base Makefile into (using wget) is $MOKO.<br />
<br />
You must also download the SHR code using subversion. See http://projects.openmoko.org/projects/shr. We will refer to the directory to which you downloaded the project as $SHRSVN. (This directory should contain $SHRSVN/packages/openmoko-dialer3.bb)<br />
<br />
=== Set up your BBPATH ===<br />
<br />
export BBPATH=.:$MOKO/openembedded/:$MOKO/bitbake/:$MOKO/:$SHRSVN/trunk/packages/<br />
<br />
=== Set up the CACHE ===<br />
<br />
export CACHE=tmp/cache<br />
<br />
<br />
<br />
=== Set up your local.conf ===<br />
Cd to your selected build directory.<br />
<br />
Create a directory under your current directory called 'conf'.<br />
<br />
cp $MOKO/openembedded/conf/local.conf conf/local.conf.<br />
<br />
Append the following lines to your local.conf:<br />
BBFILES += "$SHRSVN/trunk/packages/*.bb $MOKO/openembedded/packages/*/*.bb"<br />
SELECTED_OPTIMIZATION = "-Os -g"<br />
<br />
''Note: Spaces are important in your bitbake conf files! You must have spaces before & after the = or +=''<br />
<br />
=== Set up your openmoko.conf (if using 2007.2) ===<br />
<br />
edit $MOKO/openembedded/conf/distro/openmoko.conf<br />
<br />
and make sure that these Gtk+ options are set:<br />
<br />
# Select package versions we want to use.<br />
PREFERRED_PROVIDER_gtk+ = "gtk+-fastscaling"<br />
PREFERRED_VERSION_gtk+-fastscaling = "2.10.14"<br />
<br />
<br />
=== Add your cross-compiler to your PATH ===<br />
<br />
export PATH=$MOKO/build/tmp/cross/bin/:$MOKO/build/tmp/staging/x86_64-linux/usr/bin:$PATH<br />
<br />
=== Run bitbake ===<br />
<br />
bitbake openmoko-dialer3<br />
<br />
After the first time you build successfully, you can build with<br />
<br />
bitbake -b openmoko-dialog3_svn<br />
<br />
which is much faster.<br />
<br />
=== To recompile, and only recompile ===<br />
<br />
bitbake -c compile -b $SHRSVN/trunk/packages/openmoko-dialer3.bb<br />
<br />
=== Troubleshooting ===<br />
<br />
==== General ====<br />
One thing to try is to unset all environment variables not listed in this page. LIBPATH and INCLUDE can be particularly troublesome.<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Community]]<br />
[[Category:SHR]]<br />
[[Category:SHR Devel]]</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-09T00:25:59Z<p>Ferric: /* Tasks & status */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* [[User:Ferric|ferric]]<br />
* [[User:Paulproteus|paulproteus]]<br />
* [[User:Ainulindale|Ainulindale]]<br />
* [[User:jluis|Jose Luis]]<br />
* [[User:Kevin_Dean|Kevin Dean]]<br />
* [[User:Cb22|cb22]]<br />
* [[User:Jeremy-list|Jeremy List]]<br />
* mwester<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|Have server CPU time and disk space; just need to talk about git branches<br />
|[[User:Paulproteus|paulproteus]]<br />
|<br />
|2008-07-03<br />
|-<br />
|phonekit to ophoned adapter<br />
|Not started<br />
|[[User:Ainulindale|Ainulindale]]<br />
|[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br />
|2008-07-08<br />
|-<br />
|Test & label good SHR releases<br />
|Awaiting builds<br />
|[[User:Kevin_Dean|Kevin Dean]]<br />
|Nobody<br />
|2008-07-05<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|-<br />
|Identify differences between FSO & 2007.2 that need investigation<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|-<br />
|Switch FSO to use the matchbox window manager (as does 2007.2)<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|}<br />
<br />
Completed tasks:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Resolution<br />
|When resolved<br />
|-<br />
|Set up launcher (home) page and document how to add new apps to it<br />
|The launcher will be the apps tab of openmoko-today2<br />
|2008-07-08<br />
|-<br />
|Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br />
|Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br />
|2008-07-08<br />
|-<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...<br />
<br />
== Project links ==<br />
[http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br />
<br />
== IRC conversation about how we're using revision control ==<br />
From 2007-07-07<br />
<pre><br />
12:36 < wurp2> Everything *new* goes on OM projects site<br />
12:36 < Ainulindale> I totally agree<br />
12:36 < wurp2> Updates to 2007.2 apps go back into the home svn<br />
12:36 < Ainulindale> paulproteus: no, you're an external cabal all by yourself<br />
:-)<br />
12:36 < cb22> anyone planning on drawing up a roadmap?<br />
12:36 < paulproteus> cb22, We can do that in Trac in fact.<br />
12:36 < wurp2> And changes to the underlying release go as patches into our OE<br />
branch, yes?<br />
12:36 < paulproteus> (or on the wiki page)<br />
12:36 < paulproteus> wurp2, Right<br />
12:36 < paulproteus> mwester, Sanity-check my terminology where I mess things<br />
up!<br />
12:37 < Ainulindale> hmmm fuzzy for me but what should go in OM and what should<br />
go in OE ?<br />
12:37 <@mwester> Sure<br />
12:37 <@mwester> What do you mean by OM?<br />
12:37 < paulproteus> Ainulindale, New software we write goes in the<br />
projects.openmoko.org.<br />
12:37 <@mwester> right.<br />
12:37 < Ainulindale> Ok so the wrapper for example<br />
12:37 < wurp2> Anything stand-alone goes in OM (projects.openmoko.org)<br />
12:37 < wurp2> yeah<br />
12:37 <@mwester> So we will use projects.openmoko.org for as much as we can,<br />
and OE to build the distro.<br />
12:37 < Ainulindale> Sounds right to me<br />
12:37 < wurp2> Great!<br />
12:38 <@mwester> We *will not* use the OM git repo, as that is owned and<br />
controlled by Openmoko the company...<br />
</pre><br />
<br />
== Reference Material ==<br />
* [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br />
* [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Community]]</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-09T00:25:20Z<p>Ferric: /* Tasks & status */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* [[User:Ferric|ferric]]<br />
* [[User:Paulproteus|paulproteus]]<br />
* [[User:Ainulindale|Ainulindale]]<br />
* [[User:jluis|Jose Luis]]<br />
* [[User:Kevin_Dean|Kevin Dean]]<br />
* [[User:Cb22|cb22]]<br />
* [[User:Jeremy-list|Jeremy List]]<br />
* mwester<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|Have server CPU time and disk space; just need to talk about git branches<br />
|[[User:Paulproteus|paulproteus]]<br />
|<br />
|2008-07-03<br />
|-<br />
|phonekit to ophoned adapter<br />
|Not started<br />
|[[User:Ainulindale|Ainulindale]]<br />
|[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br />
|2008-07-08<br />
|-<br />
|Test & label good SHR releases<br />
|Awaiting builds<br />
|[[User:Kevin_Dean|Kevin Dean]]<br />
|Nobody<br />
|2008-07-05<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|-<br />
|Identify differences between FSO & 2007.2 that need investigation<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|-<br />
|Switch FSO to use the matchbox window manager (as does 2007.2)<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|}<br />
<br />
Completed tasks:<br />
{|<br />
|+<br />
|Task<br />
|Resolution<br />
|When resolved<br />
|-<br />
|Set up launcher (home) page and document how to add new apps to it<br />
|The launcher will be the apps tab of openmoko-today2<br />
|2008-07-08<br />
|-<br />
|Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br />
|Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br />
|2008-07-08<br />
|-<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...<br />
<br />
== Project links ==<br />
[http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br />
<br />
== IRC conversation about how we're using revision control ==<br />
From 2007-07-07<br />
<pre><br />
12:36 < wurp2> Everything *new* goes on OM projects site<br />
12:36 < Ainulindale> I totally agree<br />
12:36 < wurp2> Updates to 2007.2 apps go back into the home svn<br />
12:36 < Ainulindale> paulproteus: no, you're an external cabal all by yourself<br />
:-)<br />
12:36 < cb22> anyone planning on drawing up a roadmap?<br />
12:36 < paulproteus> cb22, We can do that in Trac in fact.<br />
12:36 < wurp2> And changes to the underlying release go as patches into our OE<br />
branch, yes?<br />
12:36 < paulproteus> (or on the wiki page)<br />
12:36 < paulproteus> wurp2, Right<br />
12:36 < paulproteus> mwester, Sanity-check my terminology where I mess things<br />
up!<br />
12:37 < Ainulindale> hmmm fuzzy for me but what should go in OM and what should<br />
go in OE ?<br />
12:37 <@mwester> Sure<br />
12:37 <@mwester> What do you mean by OM?<br />
12:37 < paulproteus> Ainulindale, New software we write goes in the<br />
projects.openmoko.org.<br />
12:37 <@mwester> right.<br />
12:37 < Ainulindale> Ok so the wrapper for example<br />
12:37 < wurp2> Anything stand-alone goes in OM (projects.openmoko.org)<br />
12:37 < wurp2> yeah<br />
12:37 <@mwester> So we will use projects.openmoko.org for as much as we can,<br />
and OE to build the distro.<br />
12:37 < Ainulindale> Sounds right to me<br />
12:37 < wurp2> Great!<br />
12:38 <@mwester> We *will not* use the OM git repo, as that is owned and<br />
controlled by Openmoko the company...<br />
</pre><br />
<br />
== Reference Material ==<br />
* [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br />
* [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Community]]</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-09T00:24:46Z<p>Ferric: /* Tasks & status */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* [[User:Ferric|ferric]]<br />
* [[User:Paulproteus|paulproteus]]<br />
* [[User:Ainulindale|Ainulindale]]<br />
* [[User:jluis|Jose Luis]]<br />
* [[User:Kevin_Dean|Kevin Dean]]<br />
* [[User:Cb22|cb22]]<br />
* [[User:Jeremy-list|Jeremy List]]<br />
* mwester<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|Have server CPU time and disk space; just need to talk about git branches<br />
|[[User:Paulproteus|paulproteus]]<br />
|<br />
|2008-07-03<br />
|-<br />
|phonekit to ophoned adapter<br />
|Not started<br />
|[[User:Ainulindale|Ainulindale]]<br />
|[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br />
|2008-07-08<br />
|-<br />
|Test & label good SHR releases<br />
|Awaiting builds<br />
|[[User:Kevin_Dean|Kevin Dean]]<br />
|Nobody<br />
|2008-07-05<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|-<br />
|Identify differences between FSO & 2007.2 that need investigation<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|-<br />
|Switch FSO to use the matchbox window manager (as does 2007.2)<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|}<br />
<br />
Completed tasks:<br />
{|<br />
|+<br />
|Task<br />
|Resolution<br />
|When resolved<br />
|-<br />
|Set up launcher (home) page and document how to add new apps to it<br />
|The launcher will be the apps tab of openmoko-today2<br />
|2008-07-08<br />
|-<br />
|Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br />
|Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br />
|[[User:Ferric|ferric]]<br />
|N/A<br />
|2008-07-08<br />
|-<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...<br />
<br />
== Project links ==<br />
[http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br />
<br />
== IRC conversation about how we're using revision control ==<br />
From 2007-07-07<br />
<pre><br />
12:36 < wurp2> Everything *new* goes on OM projects site<br />
12:36 < Ainulindale> I totally agree<br />
12:36 < wurp2> Updates to 2007.2 apps go back into the home svn<br />
12:36 < Ainulindale> paulproteus: no, you're an external cabal all by yourself<br />
:-)<br />
12:36 < cb22> anyone planning on drawing up a roadmap?<br />
12:36 < paulproteus> cb22, We can do that in Trac in fact.<br />
12:36 < wurp2> And changes to the underlying release go as patches into our OE<br />
branch, yes?<br />
12:36 < paulproteus> (or on the wiki page)<br />
12:36 < paulproteus> wurp2, Right<br />
12:36 < paulproteus> mwester, Sanity-check my terminology where I mess things<br />
up!<br />
12:37 < Ainulindale> hmmm fuzzy for me but what should go in OM and what should<br />
go in OE ?<br />
12:37 <@mwester> Sure<br />
12:37 <@mwester> What do you mean by OM?<br />
12:37 < paulproteus> Ainulindale, New software we write goes in the<br />
projects.openmoko.org.<br />
12:37 <@mwester> right.<br />
12:37 < Ainulindale> Ok so the wrapper for example<br />
12:37 < wurp2> Anything stand-alone goes in OM (projects.openmoko.org)<br />
12:37 < wurp2> yeah<br />
12:37 <@mwester> So we will use projects.openmoko.org for as much as we can,<br />
and OE to build the distro.<br />
12:37 < Ainulindale> Sounds right to me<br />
12:37 < wurp2> Great!<br />
12:38 <@mwester> We *will not* use the OM git repo, as that is owned and<br />
controlled by Openmoko the company...<br />
</pre><br />
<br />
== Reference Material ==<br />
* [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br />
* [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Community]]</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-09T00:23:08Z<p>Ferric: /* Overview */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
Follow the project here: [http://shr.projects.openmoko.org/ SHR Project Homepage]<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* [[User:Ferric|ferric]]<br />
* [[User:Paulproteus|paulproteus]]<br />
* [[User:Ainulindale|Ainulindale]]<br />
* [[User:jluis|Jose Luis]]<br />
* [[User:Kevin_Dean|Kevin Dean]]<br />
* [[User:Cb22|cb22]]<br />
* [[User:Jeremy-list|Jeremy List]]<br />
* mwester<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|Have server CPU time and disk space; just need to talk about git branches<br />
|[[User:Paulproteus|paulproteus]]<br />
|<br />
|2008-07-03<br />
|-<br />
|phonekit to ophoned adapter<br />
|Not started<br />
|[[User:Ainulindale|Ainulindale]]<br />
|[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br />
|2008-07-08<br />
|-<br />
|Test & label good SHR releases<br />
|Awaiting builds<br />
|[[User:Kevin_Dean|Kevin Dean]]<br />
|Nobody<br />
|2008-07-05<br />
|-<br />
|Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br />
|Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br />
|[[User:Ferric|ferric]]<br />
|N/A<br />
|2008-07-08<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|-<br />
|Identify differences between FSO & 2007.2 that need investigation<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|-<br />
|Switch FSO to use the matchbox window manager (as does 2007.2)<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|}<br />
<br />
Completed tasks:<br />
{|<br />
|+<br />
|Task<br />
|Resolution<br />
|When resolved<br />
|-<br />
|Set up launcher (home) page and document how to add new apps to it<br />
|The launcher will be the apps tab of openmoko-today2<br />
|2008-07-08<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...<br />
<br />
== Project links ==<br />
[http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br />
<br />
== IRC conversation about how we're using revision control ==<br />
From 2007-07-07<br />
<pre><br />
12:36 < wurp2> Everything *new* goes on OM projects site<br />
12:36 < Ainulindale> I totally agree<br />
12:36 < wurp2> Updates to 2007.2 apps go back into the home svn<br />
12:36 < Ainulindale> paulproteus: no, you're an external cabal all by yourself<br />
:-)<br />
12:36 < cb22> anyone planning on drawing up a roadmap?<br />
12:36 < paulproteus> cb22, We can do that in Trac in fact.<br />
12:36 < wurp2> And changes to the underlying release go as patches into our OE<br />
branch, yes?<br />
12:36 < paulproteus> (or on the wiki page)<br />
12:36 < paulproteus> wurp2, Right<br />
12:36 < paulproteus> mwester, Sanity-check my terminology where I mess things<br />
up!<br />
12:37 < Ainulindale> hmmm fuzzy for me but what should go in OM and what should<br />
go in OE ?<br />
12:37 <@mwester> Sure<br />
12:37 <@mwester> What do you mean by OM?<br />
12:37 < paulproteus> Ainulindale, New software we write goes in the<br />
projects.openmoko.org.<br />
12:37 <@mwester> right.<br />
12:37 < Ainulindale> Ok so the wrapper for example<br />
12:37 < wurp2> Anything stand-alone goes in OM (projects.openmoko.org)<br />
12:37 < wurp2> yeah<br />
12:37 <@mwester> So we will use projects.openmoko.org for as much as we can,<br />
and OE to build the distro.<br />
12:37 < Ainulindale> Sounds right to me<br />
12:37 < wurp2> Great!<br />
12:38 <@mwester> We *will not* use the OM git repo, as that is owned and<br />
controlled by Openmoko the company...<br />
</pre><br />
<br />
== Reference Material ==<br />
* [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br />
* [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Community]]</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-09T00:22:10Z<p>Ferric: /* Tasks & status */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* [[User:Ferric|ferric]]<br />
* [[User:Paulproteus|paulproteus]]<br />
* [[User:Ainulindale|Ainulindale]]<br />
* [[User:jluis|Jose Luis]]<br />
* [[User:Kevin_Dean|Kevin Dean]]<br />
* [[User:Cb22|cb22]]<br />
* [[User:Jeremy-list|Jeremy List]]<br />
* mwester<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|Have server CPU time and disk space; just need to talk about git branches<br />
|[[User:Paulproteus|paulproteus]]<br />
|<br />
|2008-07-03<br />
|-<br />
|phonekit to ophoned adapter<br />
|Not started<br />
|[[User:Ainulindale|Ainulindale]]<br />
|[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br />
|2008-07-08<br />
|-<br />
|Test & label good SHR releases<br />
|Awaiting builds<br />
|[[User:Kevin_Dean|Kevin Dean]]<br />
|Nobody<br />
|2008-07-05<br />
|-<br />
|Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br />
|Done! [http://shr.projects.openmoko.org/ SHR Project HomePage]<br />
|[[User:Ferric|ferric]]<br />
|N/A<br />
|2008-07-08<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|-<br />
|Identify differences between FSO & 2007.2 that need investigation<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|-<br />
|Switch FSO to use the matchbox window manager (as does 2007.2)<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|}<br />
<br />
Completed tasks:<br />
{|<br />
|+<br />
|Task<br />
|Resolution<br />
|When resolved<br />
|-<br />
|Set up launcher (home) page and document how to add new apps to it<br />
|The launcher will be the apps tab of openmoko-today2<br />
|2008-07-08<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...<br />
<br />
== Project links ==<br />
[http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br />
<br />
== IRC conversation about how we're using revision control ==<br />
From 2007-07-07<br />
<pre><br />
12:36 < wurp2> Everything *new* goes on OM projects site<br />
12:36 < Ainulindale> I totally agree<br />
12:36 < wurp2> Updates to 2007.2 apps go back into the home svn<br />
12:36 < Ainulindale> paulproteus: no, you're an external cabal all by yourself<br />
:-)<br />
12:36 < cb22> anyone planning on drawing up a roadmap?<br />
12:36 < paulproteus> cb22, We can do that in Trac in fact.<br />
12:36 < wurp2> And changes to the underlying release go as patches into our OE<br />
branch, yes?<br />
12:36 < paulproteus> (or on the wiki page)<br />
12:36 < paulproteus> wurp2, Right<br />
12:36 < paulproteus> mwester, Sanity-check my terminology where I mess things<br />
up!<br />
12:37 < Ainulindale> hmmm fuzzy for me but what should go in OM and what should<br />
go in OE ?<br />
12:37 <@mwester> Sure<br />
12:37 <@mwester> What do you mean by OM?<br />
12:37 < paulproteus> Ainulindale, New software we write goes in the<br />
projects.openmoko.org.<br />
12:37 <@mwester> right.<br />
12:37 < Ainulindale> Ok so the wrapper for example<br />
12:37 < wurp2> Anything stand-alone goes in OM (projects.openmoko.org)<br />
12:37 < wurp2> yeah<br />
12:37 <@mwester> So we will use projects.openmoko.org for as much as we can,<br />
and OE to build the distro.<br />
12:37 < Ainulindale> Sounds right to me<br />
12:37 < wurp2> Great!<br />
12:38 <@mwester> We *will not* use the OM git repo, as that is owned and<br />
controlled by Openmoko the company...<br />
</pre><br />
<br />
== Reference Material ==<br />
* [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br />
* [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Community]]</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-09T00:21:30Z<p>Ferric: /* Tasks & status */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the [[OpenmokoFramework|FSO]], some of the 2007.2 GTK software, and the [[ASU_Feature_Plan|ASU]] that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* [[User:Ferric|ferric]]<br />
* [[User:Paulproteus|paulproteus]]<br />
* [[User:Ainulindale|Ainulindale]]<br />
* [[User:jluis|Jose Luis]]<br />
* [[User:Kevin_Dean|Kevin Dean]]<br />
* [[User:Cb22|cb22]]<br />
* [[User:Jeremy-list|Jeremy List]]<br />
* mwester<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|Have server CPU time and disk space; just need to talk about git branches<br />
|[[User:Paulproteus|paulproteus]]<br />
|<br />
|2008-07-03<br />
|-<br />
|phonekit to ophoned adapter<br />
|Not started<br />
|[[User:Ainulindale|Ainulindale]]<br />
|[[User:Ferric|ferric]], [[User:Wurp|Wurp]]<br />
|2008-07-08<br />
|-<br />
|Test & label good SHR releases<br />
|Awaiting builds<br />
|[[User:Kevin_Dean|Kevin Dean]]<br />
|Nobody<br />
|2008-07-05<br />
|-<br />
|Set up projects.openmoko.org project for the patch to apply to FSO to make it SHR<br />
|Done! [http://shr.projects.openmoko.org/ SHR_Project_Homepage SHR Project HomePage]<br />
|[[User:Ferric|ferric]]<br />
|--<br />
|2008-07-08<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|-<br />
|Identify differences between FSO & 2007.2 that need investigation<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|-<br />
|Switch FSO to use the matchbox window manager (as does 2007.2)<br />
|Started<br />
|[[User:Wurp|Wurp]]<br />
|Nobody yet<br />
|2008-07-08<br />
|}<br />
<br />
Completed tasks:<br />
{|<br />
|+<br />
|Task<br />
|Resolution<br />
|When resolved<br />
|-<br />
|Set up launcher (home) page and document how to add new apps to it<br />
|The launcher will be the apps tab of openmoko-today2<br />
|2008-07-08<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...<br />
<br />
== Project links ==<br />
[http://docs.openmoko.org/trac/milestone/SHR SHR Trac Milestone]<br />
<br />
== IRC conversation about how we're using revision control ==<br />
From 2007-07-07<br />
<pre><br />
12:36 < wurp2> Everything *new* goes on OM projects site<br />
12:36 < Ainulindale> I totally agree<br />
12:36 < wurp2> Updates to 2007.2 apps go back into the home svn<br />
12:36 < Ainulindale> paulproteus: no, you're an external cabal all by yourself<br />
:-)<br />
12:36 < cb22> anyone planning on drawing up a roadmap?<br />
12:36 < paulproteus> cb22, We can do that in Trac in fact.<br />
12:36 < wurp2> And changes to the underlying release go as patches into our OE<br />
branch, yes?<br />
12:36 < paulproteus> (or on the wiki page)<br />
12:36 < paulproteus> wurp2, Right<br />
12:36 < paulproteus> mwester, Sanity-check my terminology where I mess things<br />
up!<br />
12:37 < Ainulindale> hmmm fuzzy for me but what should go in OM and what should<br />
go in OE ?<br />
12:37 <@mwester> Sure<br />
12:37 <@mwester> What do you mean by OM?<br />
12:37 < paulproteus> Ainulindale, New software we write goes in the<br />
projects.openmoko.org.<br />
12:37 <@mwester> right.<br />
12:37 < Ainulindale> Ok so the wrapper for example<br />
12:37 < wurp2> Anything stand-alone goes in OM (projects.openmoko.org)<br />
12:37 < wurp2> yeah<br />
12:37 <@mwester> So we will use projects.openmoko.org for as much as we can,<br />
and OE to build the distro.<br />
12:37 < Ainulindale> Sounds right to me<br />
12:37 < wurp2> Great!<br />
12:38 <@mwester> We *will not* use the OM git repo, as that is owned and<br />
controlled by Openmoko the company...<br />
</pre><br />
<br />
== Reference Material ==<br />
* [http://www.pokylinux.org/doc/poky-handbook.html How to build a linux distribution using bitbake, etc]<br />
* [http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html Using DBus in python]<br />
<br />
[[Category:Openmoko]]<br />
[[Category:Community]]</div>Ferrichttp://wiki.openmoko.org/wiki/MokoMakefileMokoMakefile2008-07-04T07:27:47Z<p>Ferric: Updated to include git branch to use for FSO</p>
<hr />
<div>{{Languages|MokoMakefile}}<br />
<br />
<br />
MokoMakefile is a Makefile which saves lots of work when setting up an Openmoko build environment.<br />
By automating the setup process of a new Openmoko build environment, it provides an environment which is configured the same for all the existing developers and should therefore be preferred over manual procedures or individual setup procedures.<br />
It brings the same repeatability to build environment creation and maintenance as that which the BitBake scripts bring to [[OpenEmbedded]] ease and standardize the process of building OpenEmbedded.<br />
<br />
Unlike the manual process described at [[Building OpenMoko from scratch]], MokoMakefile does not install anything into your system (it can and should be started as normal user).<br />
MokoMakefile is a wrapper around all that is required to make it easy to set up and maintain a development environment that fully complies with the setup instructions published by Openmoko.<br />
<br />
MokoMakefile is developed by [[User:RodWhitby|Rod Whitby]] - it is not an official product of OpenMoko (although I would be happy for them to pick it up and use it internally). If there is any discrepancy between the [[OpenMoko2007.2#How_to_build|official OpenMoko build instructions]], and the operation of the MokoMakefile, then you should consider the official instructions to be correct.<br />
<br />
The MokoMakefile is able to build both OM-2007.2 and QTopia-X11 images.<br />
<br />
MokoMakefile also builds the QEMU-based Neo1973 emulator as part of the build process and has make targets to install the OpenMoko images into it and run it. These commands can also be used without downloading and building the whole OpenMoko OpenEmbedded distribution. This part is described in [[Using QEMU with MokoMakefile]].<br />
<br />
== Requirements for building Openmoko ==<br />
Independent on whether MokoMakefile or a manual process is used to setup an OpenMoko build environment, there are several requirements which must be fulfilled in order for the OpenMoko build to succeed:<br />
<br />
* RAM: The build host needs to have at least 512MB of RAM, and about the same amount of swap. Some packages built by OpenEmbedded like busybox are built by compiling all source files into one binary which causes gcc to grow beyond 300MB of size and no part of this memory may be on swap for the compile to finish in predictable time. For busybox, this can be turned off, but turning this off means that busybox will not as well optimized by gcc.<br />
<br />
* Disk space: You need about 12 GB of available disk space for the OpenMoko build to succeed (see below for a tip on how to reduce this).<br />
<br />
* Time: The initial build takes at least 5 hours (on 2GHz core2duo without multiprocessor optimization) and may take several days on slower machines.<br />
<br />
=== Required software ===<br />
<br />
Some distribution specific hints on preparing your build host for building OpenEmbedded are on http://www.openembedded.org/wiki/OEandYourDistro but they may be outdated, incomplete and do not cover everything which OpenMoko needs to build.<br />
<br />
A good guide is [[Building OpenMoko from scratch#Build host prerequisites|the section on build host prerequisites]] in [[Building OpenMoko from scratch]]<br />
<br />
If you forgot anything which OE needs itself, OE will tell you shortly after you start building, but it does not check build dependencies of OpenMoko, so you either have to install them before starting or install them after the build failed. OpenEmbedded will continue where it stopped when you restart the build afterwards.<br />
<br />
==== Package requirements by distribution ====<br />
Your distribution needs to provide these commands in order for OpenEmbedded to start building:<br />
subversion texi2html texinfo help2man<br />
<br />
OpenMoko needs the development packages (with header files, development libraries and tools) in order to finish building:<br />
ncurses zlib (or libz) OpenSSL GTK++<br />
<br />
Because there are bugs in the interaction of QEMU and GCC-4, you'll need a copy of gcc-3.x installed as well.<br />
<br />
===== Debian / Ubuntu =====<br />
apt-get install subversion build-essential help2man diffstat texi2html texinfo cvs gawk cogito<br />
<br />
apt-get install libncurses5-dev zlib1g-dev libssl-dev libgtk2.0-dev <br />
# To prevent errors in host validation<br />
apt-get install ca-certificates<br />
# For OpenMoko 2007.2 using BitBake-1.8.8:<br />
apt-get install python-pysqlite2 sqlite3 sqlite3-doc python-pysqlite2-dbg<br />
# For building faster<br />
apt-get install quilt python-psyco ccache<br />
# For qemu, install a second compiler for bug avoidance; MokoMakefile knows to look for it.<br />
apt-get install gcc-3.4 g++-3.4 libsdl1.2-dev lynx netpbm dosfstools<br />
<br />
===== SuSE =====<br />
For building Openmoko on 10.3, you need<br />
gcc-c++ ncurses-devel zlib-devel libopenssl-devel gtk2-devel subversion diffstat texinfo help2man<br />
For MokoMakefile to not fail on compiling qemu-user, you need to use gcc33:<br />
wget download.opensuse.org/repositories/devel:/tools:/gcc/openSUSE_Factory/i586/{cpp,gcc}33-3.3.3-41.8.i586.rpm<br />
rpm -Uhv {cpp,gcc}33-3.3.3-41.8.i586.rpm<br />
<br />
See also the [[Talk:MokoMakefile#Building_on_SuSE_Linux_10.3-AMD64|Talk page on Building on SuSE Linux 10.3-AMD64]]<br />
<br />
10.1 and 10.2: same packages as 10.3, but install <code>openssl-devel</code> instead of libopenssl-devel.<br />
<br />
==== For all distributions ====<br />
As the QEMU-based neo1973 emulator is also built as part of the build process started by MokoMakefile, so you need gcc-3.3 and other packages for building QEMU installed. See [[Using QEMU with MokoMakefile#Build requirements|the build requirements section]] in [[Using QEMU with MokoMakefile]] for information on the required software.<br />
<br />
If you are having problems compiling QEMU and do not need it, you can disable building of QEMU by adding following line to build/conf/local.conf file:<br />
ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
<br />
===== Proxy =====<br />
Users behind a proxy should ensure that their proxy is configured in their wgetrc file as the http_proxy environment variable is unset by MokoMakefile.<br />
<br />
== Building Openmoko with MokoMakefile ==<br />
<br />
1 - Create your $OMDIR directory (note that you can change ~/moko to any directory you like. If you have your ~moko dir mounted from a different file system, be sure to edit /etc/mtab to add the 'exec' permission to the file system, else bitbake will fail with error messages stating that /usr/bin/env is an invalid interpreter):<br />
mkdir ~/moko ; cd ~/moko<br />
2 - Grab MokoMakefile:<br />
wget http://www.rwhitby.net/files/openmoko/Makefile<br />
<br />
If that doesn't work, try <br />
<br />
wget http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/Makefile<br />
<br />
{{note|MokoMakefile uses BitBake 1.8.8 which requires python-sqlite2 and sqlite-3.3 or later. Users of SUSE Linux 10.1 can update to [http://download.opensuse.org/pub/opensuse/distribution/10.2/repo/oss/suse/i586/sqlite-3.3.8-14.i586.rpm the version of openSUSE 10.2]}}<br />
<br />
3 - Set up the environment:<br />
make setup<br />
<br />
If you want to make the ASU, at this point you need to edit your Makefile. Change<br />
OM_GIT_BRANCH := org.openmoko.dev<br />
to say<br />
OM_GIT_BRANCH := org.openmoko.asu.dev<br />
or<br />
OM_GIT_BRANCH := org.openmoko.asu.stable<br />
<br />
And, for FSO use:<br />
OM_GIT_BRANCH := org.openembedded.dev<br />
<br />
<br />
4 - Start building. Before starting a lengthy make process, check the Tips section below for how to make Make multicore aware. You may want to modify the build/conf/local.conf file for your target (emulation/chroot) environment:<br />
make openmoko-devel-image<br />
(or use "make openmoko-qtopia-x11-image" if you're building the ASU)<br />
(or use "make fso-image" if you're building the FSO)<br />
<br />
<br />
''Hint:'' The images build with this command can be found under {$OMDIR}/build/tmp/deploy/images/neo1973<br />
<br />
This will set up the recommended directory structure as described in [[Building OpenMoko from scratch]], will download all the required software (from the right places with the right versions), and will immediately start building an image.<br />
<br />
Once you have done this, you can choose to continue using the MokoMakefile to initiate your subsequent builds, or you can go into the build directory and run bitbake commands manually. The choice is yours.<br />
<br />
==Updating the environment==<br />
For easy maintenance of your build environment the following commands are available.<br />
<br />
1 - To update the MokoMakefile to the latest version:<br />
make update-makefile <br />
<br />
2 - To make sure that any recent changes to the build directory structure have been applied:<br />
make setup <br />
<br />
3 - To update the OpenMoko repository checkout and the MokoMakefile patches to the latest version:<br />
make update<br />
<br />
A quick way to rebuild a new image with the latest updates:<br />
make update-makefile && make setup update openmoko-devel-image<br />
<br />
==Build issues==<br />
First, make sure that the problem is reproducible after running<br />
<br />
make update-makefile && make setup && make update<br />
<br />
then run<br />
<br />
make clean-package-<foo><br />
<br />
(where you replace <foo> with the name of the package which is failing)<br />
<br />
and finally<br />
<br />
make openmoko-devel-image<br />
<br />
With luck - you should now have images in your $omdir/build/tmp/deploy/glibc/images/neo1973/ directory.<br />
You can then [[Flashing openmoko||flash these.]]<br />
<br />
<br />
If not, and you can get the error to occur three times in a row after running that sequence of commands (including the update and setup steps) three times, then feel free to report it to rwhitby in #openmoko on [http://wiki.openmoko.org/wiki/Development_resources#IRC IRC].<br />
<br />
===Known MokoMakefile errors ===<br />
<br />
===Fixes for distribution/environment-specific or isolated issues===<br />
<br />
Work-arounds for temporary or isolated problems can be found and should be added to the [[Talk:MokoMakefile|Discussion page]] which is associated with this page. As they are fixed, they will be removed from that page.<br />
<br />
==Tips==<br />
*You can reduce the amount of consumed disk space significantly by adding<br />
INHERIT += "rm_work"<br />
in your local.conf (e.g. ~/moko/build/conf/local.conf). This will remove the contents of each build/tmp/work/*/<package> directory after the corresponding package builds correctly. As of 10/16/07, this appears to be present in local.conf by default.<br />
<br />
*If a certain package does not build due to corrupted download or some such try to remove the sources and rebuild it.<br />
rm sources/<package>*<br />
cd build<br />
. ../setup-env<br />
bitbake -crebuild <package><br />
after that your build might just work again.<br />
<br />
*For people with multiple CPU's (or dual-core ones) this small patch might be useful to build things faster.<br />
Edit the local.conf and add the following lines:<br />
PARALLEL_MAKE = "-j 4"<br />
BB_NUMBER_THREADS = "4"<br />
<br />
Change the PARALLEL_MAKE and BB_NUMBER_THREADS values to something that suits better if it chokes your machine.<br />
<br />
* I have some problem with the parallel building, mkfs.jffs failed to build the image because the directory was modify while the building of the fs. [[User:Patrick.hetu|patrick.hetu]] 02:19, 27 May 2008 (UTC) <br />
<br />
*For amd64 host users you need the patch from http://bugs.openembedded.org/show_bug.cgi?id=1765 to build db3-native<br />
<br />
* If you encounter an error related with the qemu-native package and not compiling for the qemu, you can edit the build/conf/local.conf file and add ENABLE_BINARY_LOCALE_GENERATION = "0" line to avoid the error.<br />
<br />
* To prevent building tons of locales, add a line like this to local.conf:<br />
GLIBC_GENERATE_LOCALES = "en_US.UTF-8 nl_NL.UTF-8"<br />
<br />
* To not build any binary locales at all, add this to local.conf:<br />
ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
<br />
* If you want to rebuild the package indexes (for instance, after compiling a new version of a package) without building <code>openmoko-devel-image</code>, run <code>make build-package-package-index</code>.<br />
<br />
[[User:Wurp]] will update this to be a little more comprehensible, but maybe it can help someone as-is in the meantime:<br />
* If MokoMakefile always fails on some fetch in zlib, just find the binary somewhere, add it to the downloads or sources directory manually (create the .md5 matching file if necessary), and retry.<br />
<br />
=== Useful commands ===<br />
Here is the list (not complete) of useful MokoMakefile commands (actually make targets) and a short description of each one. These should be run inside $OMDIR directory.<br />
<br />
; make openmoko-devel-image : build the full development image<br />
<br />
; make openmoko-devel-tools : build statically-linked [[dfu-util]] and [[openocd]] binaries<br />
<br />
; make openmoko-toolchain : builds [[toolchain]]<br />
<br />
; make qemu : builds qemu, downloads flash images from official repository, flashes qemu emulated Neo1973 and runs emulator (see also [[OpenMoko under QEMU]]). <br />
<br />
; make qemu-local : same as ''make qemu'', but uses locally built images instead of official ones.<br />
<br />
; make run-qemu : runs qemu with usb keyboard ''(note: qemu must first be built!)''. This target starts the emulator with some predefined set of options. If you need to start it with other options (enable telnet, etc), see [[QEMU_command_line]].<br />
<br />
; make build-package-<package name> : buids ''<package name>'' package<br />
<br />
; make update-makefile : updates MokoMakefile<br />
<br />
; make clean-package-<foo>: cleans the "<foo>" package<br />
<br />
; make setup : to make sure that any recent changes to the build directory structure have been applied<br />
<br />
; make update : to update the OpenMoko repository checkout and the MokoMakefile patches to the latest version<br />
<br />
==Developing with MokoMakefile==<br />
<br />
{{note|If using MokoMakefile with OM2007.2 then references to $OMDIR/openmoko should be replaced with $OMDIR/openembedded. Also references to tmp/work/armv4t-linux should be replaced with tmp/work/fic-gta01-angstrom-linux-gnueabi}}<br />
<br />
For the following explanations $OMDIR is the directory where there Makefile puts all the stuff.<br />
<br />
To make in-tree changes and have them built and used by qemu:<br />
<br />
cd $OMDIR/openmoko<br />
quilt new descriptive-patch-name.patch<br />
quilt add trunk/src/name-of-file-to-change # do this for every file you are about to modify<br />
...make the changes...<br />
quilt refresh # this creates a file in $OMDIR/patches/openmoko-HEAD/ and updates the quilt series file there<br />
<br />
Note: Do '''NOT''' use absolute paths as this confuses quilt and will get you a diff of the file against /dev/null!<br />
<br />
To build the changes and have them used by qemu:<br />
<br />
make build-qemu<br />
make flash-qemu-local<br />
make run-qemu<br />
<br />
If you want to modify applications instead of the openmoko toolchain, this is what you have to do (example: openmoko-messages):<br />
<br />
cd $OMDIR/build<br />
. ../setup-env<br />
bitbake -c unpack openmoko-messages<br />
cd tmp/work/armv4t-linux/openmoko-messages-0.0.1+svnnow-r2_2276/openmoko-messages/<br />
''...make the changes...''<br />
cd -<br />
bitbake openmoko-messages<br />
<br />
Then continue with MokoMakefile usage.<br />
<br />
If you want to add an application to your openmoko distribution, do this:<br />
All file edits should be done using quilt as described above. That way a patch can easily be submitted to the openmoko project.<br />
First, create a directory that will correspond to your package and edit a '''.bb''' file in there:<br />
cd $OMDIR/openmoko/<br />
quilt new mycoolpackage.patch<br />
mkdir trunk/oe/packages/mycoolpackage<br />
quilt add trunk/oe/packages/mycoolpackage/mycoolpackage_1.bb<br />
quilt edit trunk/oe/packages/mycoolpackage/mycoolpackage_1.bb<br />
<br />
The file should have the following content:<br />
DESCRIPTION = "This is a cool package"<br />
SECTION = "username/mycoolpackage"<br />
PV = "1"<br />
<br />
inherit autotools<br />
<br />
SRC_URI = "http://www.example.com/download/mycoolpackage-1.tar.gz"<br />
<br />
Explanation:<br />
* DESCRIPTION - Just a short text explaining the package<br />
* SECTION - I have no clue, but I'll use username/mycoolpackage for now<br />
* PV - Package Version<br />
* inherit autotools - The package can be compiled by './configure && make && make install' so we tell MokoMakefile to do it this way.<br />
* SRC_URI = ... - This is the download location of the package source. It's imperative that the tar.gz contains a directory called '''packagename-packageversion''' (in this case: mycoolpackage-1) so that MokoMakefile can find it automatically or the build will fail.<br />
<br />
This is not all. We also need to tell MokoMakfile that it needs to build and include the package in the image. To do this, do<br />
$OMDIR/openmoko# quilt edit trunk/oe/packages/tasks/task-openmoko.bb<br />
Here, increase the value '''PR''' by one and add '''mycoolpackage \''' (with the backslash!) just before the line reading '''# update-alternatives \'''.<br />
<br />
Now run<br />
quilt refresh<br />
cd ..<br />
make update openmoko-devel-image<br />
<br />
And if everything's alright you should now have an OpenMoko image to flash to your phone or run in qemu as described above.<br />
<br />
=== Hello World application ===<br />
<br />
There is a [http://wiki.openmoko.org/wiki/Building_a_hello_world_application Hello World!] tutorial available too.<br />
<br />
==Testimonials==<br />
MokoMakefile is recommended by 4 out of 4 new developers on #openmoko, with testimonials such as "For some reason last night I couldn't get my manual install of everything to work (bb complained about my bbpath I think) ... but with your makefile, it works great!", "MokoMakefile rocks!", "Wow this build system is nice - it just seems more polished than my gumstix toolchain buildroot system", and "make openmoko-devel-image :) - no magic there".<br />
<br />
Project page:<br />
http://mokomakefile.projects.openmoko.org/<br />
<br />
<br />
[[Category:Software]]<br />
[[Category:Applications]]<br />
[[Category:Application Developer]]</div>Ferrichttp://wiki.openmoko.org/wiki/Openmoko_Local_Groups:_NYC_MetroOpenmoko Local Groups: NYC Metro2008-07-03T20:03:28Z<p>Ferric: </p>
<hr />
<div>{|<br />
!No !! Name !! openmoko username !! interest <br />
|-<br />
|0||Carlos T. Linares || dux || gps use for mapping, location-based triggers, ui customization<br />
|-<br />
|1||Dean Collins || Dean.Collins || Funding ASP delivered sotware applications for OpenMoko handsets. [http://www.Cognation.net www.Cognation.net]<br />
|-<br />
|2||Michael Cole||michaelC||Integrating a portable (x-platform) tablet-capable personal knowledge environment (based on Squeak)<br />
|-<br />
|3||Bert Hartmann||BertHartm||Awesome Linux phone<br />
|-<br />
|4||Aditya Chadha||[[User:Ferric|ferric]]||Tinkerer<br />
|}<br />
<br />
[[Category:Community]]<br />
[[Category:Openmoko Local Groups]]</div>Ferrichttp://wiki.openmoko.org/wiki/User:FerricUser:Ferric2008-07-03T20:01:19Z<p>Ferric: </p>
<hr />
<div>Proud GTA01 owner in NY<br />
<br />
coordinates: http://aditya.sublucid.com/</div>Ferrichttp://wiki.openmoko.org/wiki/User:FerricUser:Ferric2008-07-03T20:01:00Z<p>Ferric: New page: Proud GTA01 owner in NY</p>
<hr />
<div>Proud GTA01 owner in NY</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-03T20:00:29Z<p>Ferric: /* Tasks & status */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the FSO, some of the 2007.2 GTK software, and the ASU that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* [[User:Ferric|ferric]]<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|'''Needs owner!'''<br />
|'''Put your name here!'''<br />
|Nobody yet<br />
|2008-07-03<br />
|-<br />
|GSMD to ophoned adapter<br />
|Not started<br />
|[[User:Wurp|Wurp]]<br />
|[[User:Ferric|ferric]]<br />
|2008-07-03<br />
|-<br />
|Test & label good SHR releases<br />
|Not started<br />
|'''Needs owner!'''<br />
|'''Put your name here!'''<br />
|2008-07-03<br />
|-<br />
|Set up baseline git repo for SHR<br />
|Not started<br />
|[[User:Ferric|ferric]]<br />
|Nobody yet<br />
|2008-07-03<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-03T19:59:54Z<p>Ferric: /* Interest */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the FSO, some of the 2007.2 GTK software, and the ASU that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* [[User:Ferric|ferric]]<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|'''Needs owner!'''<br />
|'''Put your name here!'''<br />
|Nobody yet<br />
|2008-07-03<br />
|-<br />
|GSMD to ophoned adapter<br />
|Not started<br />
|[[User:Wurp|Wurp]]<br />
|[[User:Ferric|Ferric]]<br />
|2008-07-03<br />
|-<br />
|Test & label good SHR releases<br />
|Not started<br />
|'''Needs owner!'''<br />
|'''Put your name here!'''<br />
|2008-07-03<br />
|-<br />
|Set up baseline git repo for SHR<br />
|[[User:Ferric|Ferric]]<br />
|Nobody yet<br />
|2008-07-03<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-03T19:59:45Z<p>Ferric: /* Interest */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the FSO, some of the 2007.2 GTK software, and the ASU that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* [[User:Ferric|Ferric]]<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|'''Needs owner!'''<br />
|'''Put your name here!'''<br />
|Nobody yet<br />
|2008-07-03<br />
|-<br />
|GSMD to ophoned adapter<br />
|Not started<br />
|[[User:Wurp|Wurp]]<br />
|[[User:Ferric|Ferric]]<br />
|2008-07-03<br />
|-<br />
|Test & label good SHR releases<br />
|Not started<br />
|'''Needs owner!'''<br />
|'''Put your name here!'''<br />
|2008-07-03<br />
|-<br />
|Set up baseline git repo for SHR<br />
|[[User:Ferric|Ferric]]<br />
|Nobody yet<br />
|2008-07-03<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...</div>Ferrichttp://wiki.openmoko.org/wiki/Stable_Hybrid_ReleaseStable Hybrid Release2008-07-03T19:59:09Z<p>Ferric: /* Tasks & status */</p>
<hr />
<div>''This page is a placeholder to get us organized until we can get a build started.''<br />
<br />
== Overview ==<br />
The [[Stable Hybrid Release]] (SHR) is intended to be a combination of the FSO, some of the 2007.2 GTK software, and the ASU that provides all of the functionality of the 2007.2 software, but with the stability of the FSO and the new GUI toolkits provided by the ASU. It will probably be based on an ASU build, with the FSO software and GTK end-user apps added.<br />
<br />
(We're not married to the idea of using the GTK apps, but they already exist and are more-or-less debugged at least on the UI side. If someone knows of a more stable and/or usable app that's appropriate for the OM, let us know by dropping a comment on the Talk tab of this page.)<br />
<br />
== First steps ==<br />
The first pass at making the GTK software use the FSO will involve just creating a gsmd workalike that sends commands to the ophoned dbus api from FSO. mickeyterm is an example of another program that lets you send GSM commands through ophoned.<br />
<br />
We want to have a build that is stable, so we'll need some standard way of identifying the latest stable pieces of all the different software in the SHR, as well as a way to identify previous released versions of the SHR.<br />
<br />
== Interest ==<br />
Here's a list of people who've expressed an interest in working on the SHR. Please add your name (with a link to your user page) if you'd like to help. Also, please put a way to contact you on your user page.<br />
<br />
* [[User:Wurp|wurp2]]<br />
* _ferric<br />
<br />
== Tasks & status ==<br />
Here's a list of the tasks for the SHR:<br />
{|cellpadding="5" cellspacing="0" border="1" width="600"<br />
|+<br />
|Task<br />
|Status<br />
|Owner<br />
|Helping out<br />
|Last update<br />
|-<br />
|Run the build host<br />
|'''Needs owner!'''<br />
|'''Put your name here!'''<br />
|Nobody yet<br />
|2008-07-03<br />
|-<br />
|GSMD to ophoned adapter<br />
|Not started<br />
|[[User:Wurp|Wurp]]<br />
|[[User:Ferric|Ferric]]<br />
|2008-07-03<br />
|-<br />
|Test & label good SHR releases<br />
|Not started<br />
|'''Needs owner!'''<br />
|'''Put your name here!'''<br />
|2008-07-03<br />
|-<br />
|Set up baseline git repo for SHR<br />
|[[User:Ferric|Ferric]]<br />
|Nobody yet<br />
|2008-07-03<br />
|-<br />
|[[#List_of_packages_included|Identify packages to go into SHR]]<br />
|Started<br />
|Anyone & everyone<br />
|see above<br />
|2008-07-03<br />
|}<br />
<br />
Statuses:<br />
* '''Needs owner!''' - someone needs to take responsibility for this task<br />
* Not started - someone has taken responsibility, but hasn't done anything yet...<br />
* Started - someone has started work, but there is nothing usable yet<br />
* Alpha - it might work, maybe<br />
* Beta - it probably works most of the time<br />
* Maintained - a stable release is out there, working on oddball bugs & new features<br />
* Done - a stable release is out there, no activity on this task now<br />
<br />
== List of packages included ==<br />
<br />
From FSO:<br />
* ophoned<br />
* preferencesd<br />
* pimd<br />
* odeviced<br />
* lots more...<br />
<br />
From 2007.2:<br />
* TODO<br />
* lots more...<br />
<br />
From ASU:<br />
* TODO<br />
* lots more...</div>Ferric