MeeGo wiki - User contributions [en]

ARM/N950

2011-10-19T13:19:05Z

Tjyrinki: minutes -> tens of minutes, eventually it booted just fine

= MeeGo 1.3 Community Edition installation for N950 =

(Basic information as copied from https://meego.com/community/device-program/devices/nokia-n9-devkit)

The Nokia N950 is a platform available now for developers targeting the Nokia N9 and MeeGo handset apps in general. Technical details are available at http://developer.nokia.com/swipe. Questions & comments: http://forum.meego.com/showthread.php?t=3597.

IMPORTANT: commercial developers are encouraged to apply directly at http://developer.nokia.com - thank you for your understanding.

== How to use Community Edition on N950 ==

Assumption: you have Nokia N950 device with the Beta2 release (firmware version 34-2 1.2011.34-2_PR_RM680). You should also have the skills required, similar to what is required for using N900 CE: http://wiki.meego.com/ARM/N900/GettingStarted. These instructions also assume that you are using Linux as OS on your computer.

'''The procedures described here will void any warranty (if there was any), and will destroy your Harmattan setup, losing any data you have there.''' However, you can always go back to a fresh Harmattan installation with the OneClickFlasher package available at: http://www.developer.nokia.com/info/sw.nokia.com/id/db230178-aa63-4c73-ba7f-20930da13cad/Nokia_N950_OneClickFlashers.html (note - please login to https://www.developer.nokia.com first or you'll get redirection errors)

=== Downloading the MeeGo Community Edition release ===

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Image
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Release date
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.2.90.5.0.20110927.81.CE.2011-09-27.1/images/mg-handset-armv7nhl-n950-ce-testing/ Fall Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| v1.3 Handset image for Fall 2011
|style="border-style: solid; border-width: 0 0 1px 0"| 28.9.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/ Weekly image]
|style="border-style: solid; border-width: 0 1px 1px 0"| From here, you can find the weekly and daily builds.
|style="border-style: solid; border-width: 0 0 1px 0"|
|}

=== Flasher for N950 ===
Download Harmattan flasher from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php here].

Before you proceed make sure that "Device lock" is not enabled in Harmattan (In Settings \ Security \ Device Lock \ Autolock: off). If you have an Mail-for-Exchange account configured, you may need to delete it before you can disable device lock.

If flasher bombs out with "Devicelock ON: cannot flash unsigned image", then you didn't, go back and disable it.

If the beta2 flasher errors with "bb5_rdc_cert_read" or [http://www.martindengler.com/proj/n950-flasher-beta1#failure a few other errors], try the [http://www.martindengler.com/proj/n950-flasher-beta1 beta1 flasher].

=== MeeGo Bootloader (Moslo) ===

In order to boot MeeGo on N950, the default OS, Harmattan, must be replaced with MOSLO, the Meego OS LOader.
Moslo can be flashed as a fiasco image, available at: http://tablets-dev.nokia.com/moslo.php. Moslo source repository is located at: https://gitorious.org/meego-developer-edition-for-n900/moslo). Current moslo fiasco image for N950 is moslo-rootfs-1.2011.34-2_RM680-OEM1-916_0.0.13-12.1.bin

Nokia N9 similarly will need its own Moslo.

* IMPORTANT: before installing Moslo, boot into Harmattan at least once and wait for a few minutes.
* Power off the device, disconnect usb or changer.
* Run flasher:
sudo flasher -F moslo-rootfs-1.2011.34-2_RM680-OEM1-916_0.0.13-12.1.bin -f
Flasher now waits for a device to connect.
* Connect your N950 and wait for flashing to finish.
* Do not disconnect. Read on.

=== Write CE to device ===

After flashing MOSLO, boot the device by disconnecting and re-connecting the USB cable to the PC. You will see a warning and a disclaimer screen for 10 seconds followed by green text based MOSLO welcome screen. Wait for the text "Rootfs now exported via USB".

If you don't get the MOSLO screen after successfully flashing MOSLO, then let the device finish booting into harmattan and reboot it. It can take several full reboots of the device to fully enable MOSLO.

If you have automount enabled in your Linux system, the device may appear as a normal USB drive to your desktop. Automount may not show the drive at first because it is in vfat format. Automount will typically use volume ID as mountpoint name.

IMPORTANT: On some systems (Ubuntu) automounting may have too restrictive options. Manual mounting is recommended.

IMPORTANT: Although the '''drive exported by device via MOSLO to the host PC it appears as /dev/sdX, inside the device it is a partition''', instead of a full drive.

At first MOSLO connection, the partition has to be reformatted. Make sure it is unmounted:
sudo umount /dev/sdX
sudo mkfs.ext4 /dev/sdX
You will see warning: "/dev/sdX is entire device, not just one partition! Proceed anyway? (y,n)". This is expected. Just make sure you got the right device node and say "y".

For mounting the MeeGo rootfs manually:
sudo mkdir -p /media/<choose mountpoint name for your N950>
sudo mount /dev/sdX /media/<mountpoint of your N950>

If you already had an MeeGo image on the partition, it can be erased by running:
sudo rm -rf /media/<mountpoint of your N950>/*

Extract the Community Edition .tar.bz2 to the mounted rootfs partition with:
sudo tar --numeric-owner -xf <path>/<CE_package>.tar.bz2 -C /media/<mountpoint of your N950>

After the extraction is ready, unmount/remove safely/eject the partition before disconnecting from usb:
sudo umount /media/<mountpoint of your N950>

=== Boot to CE ===

* The device should start booting to MeeGo right after disconnecting the USB.
* Otherwise start normally by hosding power hoy for 2-4 seconds.
* First you should see the disclaimer screen.
* Next you see a green-on-black Moslo bootscreen.
* The last line should say: "Running Meego Kernel" (it is shown very briefly)
* Then wait patiently for desktop to come up.

Shutting down is done simply by holding the power key until either a shut down graphic or a red screen is shown.
Check that screen back light goes out. If device does not react, hold the power key for over 8 seconds.
This will force HW shut down. Note: using forceful shut down might corrupt the filesystem, leading to a non-bootable setup.

====Trouble starting?====

If device does not react, hold the power key for over 8 seconds.

In case battery is very low, the screen may stay black even if booting continues, or the device may shutdown (and likewise stay black).
* Connect usb or charger and let Moslo charge the battery at least for a few <del>minutes</del> tens of minutes.
* Then disconnect usb/charger and device should continue booting to MeeGo.
* You can reconnect usb/charger after a few seconds. Latest at the Meego splash screen.

Don't panic - try again, check the steps and finally ask for advice at #meego-arm IRC channel.

=== How to remove MeeGo/Moslo and restore Harmattan ===
In order to boot Harmattan again, MeeGo and Moslo must be removed.
This can be done by using OneClickFlasher available here:
http://www.developer.nokia.com/info/sw.nokia.com/id/db230178-aa63-4c73-ba7f-20930da13cad/Nokia_N950_OneClickFlashers.html

Running the OneClickFlasher will overwrite MeeGo/Moslo with Harmattan. All personal settings will be lost.
It will take about 15-30 minutes.

== Open issues ==

* How about dual boot with Harmattan?
** Not possible with current Moslo release. Community is encouraged to find a way, with modified Moslo or some other means eg. u-boot.
* Will this work in N9?
** Not at the moment. We are working to make a N9 release as well, stay tuned for more information.

=== Reporting bugs against Community Edition ===

* File a bug report on [http://bugs.meego.com/ bugs.meego.com]
* Use '''[CE]''' in the summary
* Add the '''N950''' and '''N900CE''' keywords to the bug report
* Select from Platform '''N900''', if bug can be reproduced with N900 also.

*Notice:
** If bug is producible with MeeGo image also, remove the [CE] prefix from the summary. It's used only for the Community Edition specific bugs.
** Feel free to suggest MeeGo_N900CE_Release_Blocker.
** '''If bug is for application''', check if there's a '''upstream link''' for direct reporting in [[/AppsInCE | CE application list]]. If there's a link, please report to upstream, if not, then to the MeeGo Bugzilla.
** If you found a bug when using MeeGo 1.2 '''Harmattan''', please file the bug to the [http://www.developer.nokia.com/bugs/ http://www.developer.nokia.com/bugs/]

= More info =

More information can be found in [[N950 landing page]].

[[Category:N950]]

ARM/N9

2011-10-19T07:54:45Z

Tjyrinki: make into actual redirect

#REDIRECT [[ARM/N950]]

N9

2011-10-19T07:54:17Z

Tjyrinki: another redirect page

#REDIRECT [[ARM/N950]]

ARM/N950

2011-10-14T08:30:25Z

Tjyrinki: /* MeeGo Bootloader (Moslo) */ mention N9 needing its own as well

= MeeGo 1.3 Community Edition installation for N950 =

(Basic information as copied from https://meego.com/community/device-program/devices/nokia-n9-devkit)

The Nokia N950 is a platform available now for developers targeting the Nokia N9 and MeeGo handset apps in general. Technical details are available at http://developer.nokia.com/swipe. Questions & comments: http://forum.meego.com/showthread.php?t=3597.

IMPORTANT: commercial developers are encouraged to apply directly at http://developer.nokia.com - thank you for your understanding.

== How to use Community Edition on N950 ==

Assumption: you have N950 device with working Harmattan setup. You should also have the skills required, similar to what is required for using N900 CE: http://wiki.meego.com/ARM/N900/GettingStarted.

'''The procedures described here will void any warranty (if there was any), and will destroy your Harmattan setup, losing any data you have there.''' However, you can always go back to a fresh Harmattan installation with the OneClickFlasher package available at: http://www.developer.nokia.com/info/sw.nokia.com/id/db230178-aa63-4c73-ba7f-20930da13cad/Nokia_N950_OneClickFlashers.html

=== Downloading the MeeGo Community Edition release ===

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Image
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Release date
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.2.90.5.0.20110927.81.CE.2011-09-27.1/images/mg-handset-armv7nhl-n950-ce-testing/ Fall Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| v1.3 Handset image for Fall 2011
|style="border-style: solid; border-width: 0 0 1px 0"| 28.9.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/ Weekly image]
|style="border-style: solid; border-width: 0 1px 1px 0"| From here, you can find the weekly and daily builds.
|style="border-style: solid; border-width: 0 0 1px 0"|
|}

=== Flasher for N950 ===
Download Harmattan flasher from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php here].

Before you proceed make sure that "Device lock" is not enabled in Harmattan (In Settings \ Security \ Device Lock \ Autolock: off). If you have an Mail-for-Exchange account configured, you may need to delete it before you can disable device lock.

If flasher bombs out with "Devicelock ON: cannot flash unsigned image", then you didn't, go back and disable it.

If the beta2 flasher errors with "bb5_rdc_cert_read" or [http://www.martindengler.com/proj/n950-flasher-beta1#failure a few other errors], try the [http://www.martindengler.com/proj/n950-flasher-beta1 beta1 flasher].

=== MeeGo Bootloader (Moslo) ===

In order to boot MeeGo on N950, the default OS, Harmattan, must be replaced with MOSLO, the Meego OS LOader.
Moslo can be flashed as a fiasco image, available at: http://TBD. For license information and sources see: https://gitorious.org/meego-developer-edition-for-n900/moslo).

Nokia N9 similarly will need its own Moslo.

ETA for Moslo availability: soon

* IMPORTANT: before installing Moslo, boot into Harmattan at least once and wait for a few minutes.
* Power off the device, disconnect usb or changer.
* Run flasher:
sudo flasher -F <moslo-image.bin> -f
Flasher now waits for a device to connect.
* Connect your N950 and wait for flashing to finish.
* Do not disconnect. Read on.

=== Write CE to device ===

After flashing MOSLO, boot the device by disconnecting and re-connecting the USB cable to the PC. You will see a warning and a disclaimer screen for 10 seconds followed by green text based MOSLO welcome screen. Wait for the text "Rootfs now exported via USB".

If you don't get the MOSLO screen after successfully flashing MOSLO, then let the device finish booting into harmattan and reboot it. It can take several full reboots of the device to fully enable MOSLO.

If you have automount enabled in your Linux system, the device may appear as a normal USB drive to your desktop. Automount may not show the drive at first because it is in vfat format. Automount will typically use volume ID as mountpoint name.

IMPORTANT: On some systems (Ubuntu) automounting may have too restrictive options. Manual mounting is recommended.

IMPORTANT: Although the '''drive exported by device via MOSLO to the host PC it appears as /dev/sdX, inside the device it is a partition''', instead of a full drive.

At first MOSLO connection, the partition has to be reformatted. Make sure it is unmounted:
sudo umount /dev/sdX
sudo mkfs.ext4 /dev/sdX
You will see warning: "/dev/sdX is entire device, not just one partition! Proceed anyway? (y,n)". This is expected. Just make sure you got the right device node and say "y".

For mounting the MeeGo rootfs manually:
sudo mkdir -p /media/<choose mountpoint name for your N950>
sudo mount /dev/sdX /media/<mountpoint of your N950>

If you already had an MeeGo image on the partition, it can be erased by running:
sudo rm -rf /media/<mountpoint of your N950>/*

Extract the Community Edition .tar.bz2 to the mounted rootfs partition with:
sudo tar --numeric-owner -xf <path>/<CE_package>.tar.bz2 -C /media/<mountpoint of your N950>

After the extraction is ready, unmount/remove safely/eject the partition before disconnecting from usb:
sudo umount /media/<mountpoint of your N950>

=== Boot to CE ===

* The device should start booting to MeeGo right after disconnecting the USB.
* Otherwise start normally by hosding power hoy for 2-4 seconds.
* First you should see the disclaimer screen.
* Next you see a green-on-black Moslo bootscreen.
* The last line should say: "Running Meego Kernel" (it is shown very briefly)
* Then wait patiently for desktop to come up.

Shutting down is done simply by holding the power key until either a shut down graphic or a red screen is shown.
Check that screen back light goes out. If device does not react, hold the power key for over 8 seconds.
This will force HW shut down. Note: using forceful shut down might corrupt the filesystem, leading to a non-bootable setup.

====Trouble starting?====

If device does not react, hold the power key for over 8 seconds.

In case battery is very low, the screen may stay black even if booting continues.
* Connect usb or charger and let Moslo charge the battery at least for a few minutes.
* Then disconnect usb/charger and device should continue booting to MeeGo.
* You can reconnect usb/charger after a few seconds. Latest at the Meego splash screen.

Don't panic - try again, check the steps and finally ask for advice at #meego-arm IRC channel.

=== How to remove MeeGo/Moslo and restore Harmattan ===
In order to boot Harmattan again, MeeGo and Moslo must be removed.
This can be done by using OneClickFlasher available here:
http://www.developer.nokia.com/info/sw.nokia.com/id/db230178-aa63-4c73-ba7f-20930da13cad/Nokia_N950_OneClickFlashers.html

Running the OneClickFlasher will overwrite MeeGo/Moslo with Harmattan. All personal settings will be lost.
It will take about 15-30 minutes.

== Open issues ==

* How about dual boot with Harmattan?
** Not possible with current Moslo release. Community is encouraged to find a way, with modified Moslo or some other means eg. u-boot.
* Will this work in N9?
** Not at the moment. We are working to make a N9 release as well, stay tuned for more information.

=== Reporting bugs against Community Edition ===

* File a bug report on [http://bugs.meego.com/ bugs.meego.com]
* Use '''[CE]''' in the summary
* Add the '''N950''' and '''N900CE''' keywords to the bug report
* Select from Platform '''N900''', if bug can be reproduced with N900 also.

*Notice:
** If bug is producible with MeeGo image also, remove the [CE] prefix from the summary. It's used only for the Community Edition specific bugs.
** Feel free to suggest MeeGo_N900CE_Release_Blocker.
** '''If bug is for application''', check if there's a '''upstream link''' for direct reporting in [[/AppsInCE | CE application list]]. If there's a link, please report to upstream, if not, then to the MeeGo Bugzilla.
** If you found a bug when using MeeGo 1.2 '''Harmattan''', please file the bug to the [http://www.developer.nokia.com/bugs/ http://www.developer.nokia.com/bugs/]

= More info =

More information can be found in [[N950 landing page]].

[[Category:N950]]

User:Tjyrinki

2011-09-26T16:47:31Z

Tjyrinki: instructions for enabling my MeeGo repository

== Timo Jyrinki ==

Email:: timo.jyrinki at iki dot fi 
Homepage:: http://iki.fi/tjyrinki/

Interests::
* http://www.debian.fi/
* http://www.ubuntu-fi.org/
* http://www.vapaasuomi.fi/

=== My MeeGo Repository ===

Project: https://build.pub.meego.com/project/show?project=home%3Atjyrinki

I aim to have both MeeGo and Harmattan packages available.

Currently, enabling my harmattan packages on [[ARM/N950|Nokia N950 or N9]] running the default software instead of MeeGo (CE):
<pre>
devel-su
repo="home-tjyrinki"
url="http://repo.pub.meego.com/home:/tjyrinki/harmattan/"
echo "deb ${url} ./" | tee "/etc/apt/sources.list.d/${repo}.list"
apt-get update
</pre>

Category:N950

2011-09-20T10:04:53Z

Tjyrinki: Created page with "Pages related to Nokia N950 (the developer version of Nokia N9)."

Pages related to Nokia N950 (the developer version of Nokia N9).

N900

2011-09-13T06:40:19Z

Tjyrinki: link to N950 page, expand participate sentence a bit

[[File:Screenshot.png|400px|thumb|right]]

= MeeGo Community Edition for Nokia N900 =
'' "I have N900, and want to try MeeGo on it." '' 
'' "I want to develop MeeGo/Qt applications on my N900 device" '' 
'' "I want to develop MeeGo OS, on existing N900 or other ARM-based device" '' 
'' "I want to be in the frontline of developing MeeGo 1.2/1.3 on the latest '''Nokia N9/N950''' devices" ''

== Introduction ==
When using MeeGo on the Nokia N900, or other ARM-based handset, it's recommended to use MeeGo [[ARM/N900|Community Edition]]. [[ARM/N900|Community Edition]] is an edition of the core MeeGo 1.2. The [[ARM/N900|Community Edition]] is developed with the ARM and handset compatibility in mind, this way developers already owning a N900 device may start developing with it immediately.

For more information about the Community Edition, please visit [[ARM/N900|page.]]

== Status ==
The working status of MeeGo for N900 implementation can be seen on [[ARM/N900/Status|Status page.]] This MeeGo Community Edition is also be the place where similar effort on ARM using Nokia N9 (and N950) is take place - see [[ARM/N950|N950/N9 page]].

== Install ==
To install MeeGo 1.2 Community Edition for N900, refer to our [[ARM/N900/GettingStarted|Getting Started page.]]

=== Image releases ===
When downloading images, you can choose from several images from our repository, or even [[ARM/Creating ARM image using MeeGo Image Creator|build one yourself.]]

[[ARM/N900/GettingStarted]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Image
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Release date
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.2.0.90.6.20110630.4.DE.2011-07-01.1/images/mg-handset-armv7nhl-n900-ce-stable/ Summer Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| Image for Summer 2011.
|style="border-style: solid; border-width: 0 0 1px 0"| 1.7.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.2.0.90.5.20110621.5.DE.2011-06-23.1/images/mg-handset-armv7nhl-n900-ce-stable/ Midsummer Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| Image for Midsummer 2011.
|style="border-style: solid; border-width: 0 0 1px 0"| 23.6.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ SF/MeeGoConf Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| San Francisco release, image released at MeeGo conference.(recommended)
|style="border-style: solid; border-width: 0 0 1px 0"| 23.5.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| 15.04.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/ Weekly image]
|style="border-style: solid; border-width: 0 1px 1px 0"| From here, you can find the weekly and daily builds.
|style="border-style: solid; border-width: 0 0 1px 0"|
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [https://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo Core 1.1]
|style="border-style: solid; border-width: 0 1px 1px 0"| Original MeeGo core 1.1 release for N900.
|style="border-style: solid; border-width: 0 0 1px 0"| 28.10.2010
|}

=== Applications ===
If you want to try out some applications on MeeGo [[ARM/N900|Community Edition]], get them from [[ARM/N900/CoolStuff|here.]] Eventually applications will be in [[http://apps-beta.meego.com/applications/MeeGo Community apps site]].

== Participate ==
If you are interested in helping develop MeeGo or applications for your favorite hardware, please visit on MeeGo [[ARM/N900|Community Edition page]] for the mailing lists and other communication methods.

== FAQ ==
Q. Where can I download the N900 Community Edition release? 
A. See [[#Download_image]]

Q. Where do I see the maturity of the current image? 
A. See the Community Edition [[ARM/N900/Status|Status page.]]

Q. My battery is drained. How do I recharge it? 
A. Look from [[ARM/N900/Recover_From_Drained_Battery|battery recharge guide.]]

Q. I want to install back to Maemo5 as my only operating system. How do I do that? 
A. See the [http://wiki.maemo.org/Updating_the_firmware#N900_2 restore Maemo guide] from Maemo wiki.

Q. I want a usb connection to my N900. How do I do it? 
A. Use ssh. See [[ARM/N900/Tips_and_Tricks/N900_USB_Networking|guide.]]

Release Infrastructure/BOSS/Installation

2011-08-29T10:52:38Z

Tjyrinki: /* SUSE */ fix opensuse 11.4 zypper url

= Overview =

Whilst BOSS is deployed in production, this packaged version is still
in beta-testing and is subject to change. In particular the
repositories are not yet finalised (eg installing from :RC).

However BOSS and SkyNET both install and run at a basic level on a
clean Debian 6.0 or OpenSuse 11.4 installation.

= Installation =

== Preparation ==

* Proxy : On OpenSUSE you need to set the proxy in /etc/sysconfig/proxy

== BOSS ==
=== Overview ===
BOSS provides the ruote worker and the main AMQP server.

This component is the main process dispatcher; no work happens
here but all process steps are initiated from here.

Currently BOSS uses the Ruote filesystem storage system and the
worker and viewer need to run on the same system. This will change
when BOSS moves to Redis.

The stable and testing projects are at the community OBS, the state
of the packages can be monitored at :

Testing : https://build.pub.meego.com/project/monitor?project=Project:MINT:Testing

Release Candidate : https://build.pub.meego.com/project/monitor?project=Project:MINT:RC

Stable : (No release yet) https://build.pub.meego.com/project/monitor?project=Project:MINT

=== SUSE ===

(old version of BOSS on openSUSE 11.2)
zypper ar http://download.opensuse.org/repositories/Maemo:/MeeGo-Infra/openSUSE_11.2-plus/Maemo:MeeGo-Infra.repo
zypper ref
zypper in boss

(new version of BOSS on opensuse 11.4)
zypper ar http://repo.pub.meego.com/Project:/MINT:/RC/openSUSE_11.4/Project:MINT:RC.repo MINT
zypper ref
zypper in boss

This will install Rabbit MQ and the boss worker daemon.

To run boss:

rcboss start / stop

=== Debian Squeeze/6.0 ===

cat <<EOF > /etc/apt/sources.list.d/MINT.list
deb http://repo.pub.meego.com/Project:/MINT:/RC/Debian_6.0/ /
EOF

apt-get update
apt-get install --no-install-recommends boss

This will install Rabbit MQ and the boss worker daemon.

Then, as usual
/etc/init.d/boss {start|stop|restart|force-reload|log}

Default settings are found in /etc/default/boss

=== Configuration ===

BOSS is preconfigured with username boss and password boss on the boss vhost
(AMQP will lose vhosts soon)

BOSS stores workitem and process data in /var/spool/boss/

=== SkyNET installation for OpenSuse 11.4 ===

In order to be able to work with BOSS, please install SkyNET now:

zypper in boss-skynet

from the repository

https://build.pub.meego.com/project/monitor?project=Project:MINT:RC

== BOSS-Viewer ==

This must be installed on the boss server when using the FS storage.

The default port is 9292, point your browser at http://127.0.0.1:9292/_ruote/ (if you are running on the same machine)

#FIXME: Make sure you go to /_ruote/ otherwise you will get a big scary error.

=== SUSE ===

zypper ar https://build.pub.meego.com/project/monitor?project=Project:MINT:RC
zypper ref
zypper in boss-viewer

This will install boss-viewer.

To run boss-viewer:

rcboss-viewer start / stop

=== Debian Squeeze/6.0 ===

cat <<EOF > /etc/apt/sources.list.d/MINT.list
deb http://repo.pub.meego.com/Project:/MINT:/RC/Debian_6.0/ /
EOF

apt-get update
apt-get install --no-install-recommends boss-viewer

This will install the boss viewer.

Then, as usual
/etc/init.d/boss {start|stop|restart|force-reload|log}

== BOSS OBS Plugin ==
The OBS plugin is designed to launch processes when a build/publish event occurs on the OBS

=== Installation ===
The plugin is installed on the OBS backend which runs the schedulers

openSUSE 11.2
zypper ar http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_11.2/devel:languages:perl.repo
zypper ar http://repo.pub.meego.com/Project:/MINT:/RC/openSUSE_11.2/Project:MINT:RC.repo
zypper ref
zypper in boss-obs-plugin

opensuse 11.4
zypper ar http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_11.4/devel:languages:perl.repo
zypper ar http://repo.pub.meego.com/Project:/MINT:/Testing/openSUSE_11.4/Project:MINT:Testing.repo
zypper ref
zypper in boss-obs-plugin

=== Configuration ===

'''You *MUST* have a participant registered as "obs_event" (provided by the robogrator launcher package https://meego.gitorious.org/meego-infrastructure-tools/boss-launcher-robogrator ) running before enabling this plugin or ruote will silently fill up with hundreds/thousands/millions of stalled processes.'''

Edit the file:
/usr/lib/obs/server/BSConfig.pm
and define/add:
our $notification_plugin = "notify_boss";
our $BOSS_host="boss"; # hostname for server running BOSS AMQP
our $BOSS_user="boss"; # AMQP username
our $BOSS_passwd="boss"; # AMQP password (cleartext)

You may also uncomment and set to 1:
our $multiaction_notify_support = 1;
(This allows osc requests containing multiple actions to be handled properly).

The plugin itself is installed in :
/usr/lib/obs/server/plugins/notify_boss.pm

The schedulers will need to be restarted to take effect. Note there is currently an issue that
the plugin will block if the AMQP server is not available - this will halt the OBS.

= Getting started and Testing the Deployment =

Once you have installed BOSS and SkyNET you are ready to create and run some processes.

== Watch BOSS ==
On the BOSS machine:

/etc/init.d/boss log &

You'll see messages about the engine being alive and participant
registration. Further debug output is possible here.

== Setup a participant ==

On the skynet machine we need to setup some code as a participant:

skynet make_participant -n check -p /usr/share/doc/python-boss-skynet/example-check-participant
skynet make_participant -n notify -p /usr/share/doc/python-boss-skynet/example-notify-participant

This creates a daemontools/participant directory structure with a
symbolic link to the code for these participants.

Now we need to ensure they start to run under daemontools (and restart if
there's a problem):

skynet enable check
skynet enable notify

To watch the log output:

skynet log check &
skynet log notify &

Now we need to tell boss that there is something listening on these
queues and available for use in processes:

skynet register -n check
skynet register -n notify

The skynet command also supports:
* stop : shutdown the participant and don't respawn.
* reload : stop and start once
* register : can also specify the amqp queue to use if it's not the name

== Launch a process ==

With a participant ready to do some work, we're ready to launch a process:

/usr/share/boss-skynet/skynet_launch

The log output should show

2011-03-29 00:49:21.186558500 checking for /tmp/success
2011-03-29 00:49:21.186849500 Failed to read /tmp/success
2011-03-29 00:49:21.708706500 Nothing to say

Now do:

echo Hi there > /tmp/success

And relaunch:

/usr/share/boss-skynet/skynet_launch

gives
2011-03-29 00:49:31.659986500 checking for /tmp/success
2011-03-29 00:49:31.660440500 Read /tmp/success
2011-03-29 00:49:31.878978500 Send email saying : Hi there
2011-03-29 00:49:31.878980500

Of course a process can be launched from anywhere on the network using
any 'trigger' and participants also run on any machine.

== Debugging ==

= Next steps =

Do something useful with your installation using the [[../Standard workflow|standard workflow]] and the [[../Participants|participants and launchers]]

ARM/N900

2011-08-12T21:20:13Z

Tjyrinki: /* MeeGo 1.2 Community Edition for Nokia N900 */ link to N950(/N9) specific page

= MeeGo 1.2 Community Edition for Nokia N900=

'''What's hot:'''
Test the Summer Release of the MeeGo 1.2 Community Edition for N900: [http://repository.maemo.org/meego/n900-de/archive/1.2.0.90.6.20110630.4.DE.2011-07-01.1/images/mg-handset-armv7nhl-n900-ce-stable/ download] - [[ARM/N900/GettingStarted|install]] - [[ARM/N900/CoolStuff|cool stuff]] - [http://forum.meego.com/forumdisplay.php?f=7 discuss]
'''Nokia N9, N950, Qt and Community Edition''', [http://flors.wordpress.com/2011/06/20/nokia-n9-state-of-the-art-of-mobile-linux-and-qt/ read Quim's blog], and [[ARM/N950|N950 page]].

== Introduction ==
The target of this activity is to make a Community Edition of MeeGo for the Nokia N900 device. '''Note: The initiative was originally called Developer Edition, so you will see that mentioned in many places'''. Don't get confused, this is the same thing :)

The Community Edition is an 'overlay' constructed above the current core MeeGo 1.2. The Community Edition project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft, it will not take into account all features commonly present in a handset OS. To see what features will be implemented look at [[#Key_features]]. Flashed with this edition, N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Community Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of the Community Edition that are not yet implemented from the [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Community Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Community Edition image, can be seen on the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found on the [[ARM/N900/GettingStarted|Getting Started page]]. Please refer to them for more instructions.

* [[ARM/N900/GettingStarted|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] on the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Community Edition.

== Release schedule ==

=== Summer information ===

During July-August, there will be limitation on activity for the CE. As always it's still very likely you can get help at almost any time at #meego-arm.
* No weekly meetings, next one is 2nd August
* Image creation support, .ks maintenance?
* OBS acceptance
* Weekly releases

This shows the '''release schedule''' and content. It should be understood that Community Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.2.0.90.6.20110630.4.DE.2011-07-01.1/images/mg-handset-armv7nhl-n900-ce-stable/ Summer Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 1.7.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| 1H/2011 achievement
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Summer_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.2.0.90.5.20110621.5.DE.2011-06-23.1/images/mg-handset-armv7nhl-n900-ce-stable/ Midsummer Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.6.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Pre-Summer release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Summer_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| MeeGo Conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the MeeGo Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to MeeGo, but wondering where to start? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* To contribute fixes, see [[ARM/N900/ReleaseProcess]].
* Follow Discussion
** Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
** Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
** Join [[ARM/N900/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Learn
** Play a little with Tablet UX pre-alpha, as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details at [[ARM/N900/TabletUX]].
** Look into learning QML, if you haven't already.
*Contribute
** Would like to contribute the test cases? You will find useful information [[Quality|here]].
** Would like to contribute artwork? See [[ARM/N900/Artwork]].
** To the [[ARM/N900/Performance|performance optimization]].
** Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Community Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute, be it bugs, code, artwork, or something else. Core team itself has been divided into the following categories:

* Scrum master: [http://meego.com/users/msugano Makoto Sugano]
** [[ARM/N900/Performance|UX & Performance]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
** [[ARM/N900/Common|Adaptation]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
** [[ARM/N900/CoolStuff|Applications]] facilitator: [http://meego.com/users/jukkaeklund Jukka Eklund]
** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/sage Marko Saukko].
* [[ARM/N900/QA|QA]]: [http://meego.com/users/jkunnari Jake Kunnari], [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
* Community manager: [http://meego.com/users/jukkaeklund Jukka Eklund]

<nowiki>*</nowiki>The Dialer project has been merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the Community Edition, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in Community Edition & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class impacts performance.

Q. Where can I download the N900 Community Edition release? 
A. See [[ARM/N900/GettingStarted|installation instructions]]

Q. What UI will the Community Edition use? 
A. Based on what's available on MeeGo trunk. At the moment, we're working with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might even be multiple options for the user to select.

Q. If I get "The package integrity check failed." (NOKEY) when trying to zypper install MeeGo 1.2 packages, where can I find the missing keys?[1.6.2011] 
A. (no answer yet)

Q. I installed to eMMC and it's dog-slow? [1.6.2011] 
A. The eMMC currently has a severe performance problem, [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295]

Q. What is this Community Edition really about? 
A. [[ARM/N900/CE_Factsheet|Check out the MeeGo CE description.]]

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

== Reporting bugs against N900 Community Edition ==

* File a bug report on [http://bugs.meego.com/ bugs.meego.com]
* Use '''[CE]''' in the summary
* Add the '''N900CE''' keyword to the bug report
* Select from Platform '''N900''', if N900 was in use.

*Notice:
** If bug is producible with MeeGo image also, remove the [CE] prefix from the summary. It's used only for the N900 CE specific bugs.
** Feel free to suggest MeeGo_N900CE_Release_Blocker.
** '''If bug is for application''', check if there's a '''upstream link''' for direct reporting in [[/AppsInCE | CE application list]]. If there's a link, please report to upstream, if not, then to the MeeGo Bugzilla.

[[File:Splash-developers.png]]

[[Category:N900]]

N900

2011-06-22T09:40:45Z

Tjyrinki: rephrasing my N9 tagline to emphasize MeeGo 1.2/1.3 especially

[[File:20000101-034513.png|400px|thumb|right]]

= MeeGo 1.2 Community Edition for Nokia N900 =
'' "I have N900, and want to try MeeGo on it." '' 
'' "I want to develop MeeGo/Qt applications on my N900 device" '' 
'' "I want to develop MeeGo OS, on existing N900 or other ARM-based device" '' 
'' "I want to be in the frontline of developing MeeGo 1.2/1.3 on the latest Nokia N9/N950 devices" ''

== Introduction ==
When using MeeGo on the Nokia N900, or other ARM-based handset, it's recommended to use MeeGo [[ARM/N900|Community Edition]]. [[ARM/N900|Community Edition]] is an edition of the core MeeGo 1.2. The [[ARM/N900|Community Edition]] is developed with the ARM and handset compatibility in mind, this way developers already owning a N900 device may start developing with it immediately.

For more information about the Community Edition, please visit [[ARM/N900|page.]]

== Status ==
The working status of MeeGo for N900 implementation can be seen on [[ARM/N900/Status|Status page.]] This MeeGo Community Edition will also be the place where similar effort on ARM using Nokia N9 (and N950) will take place at.

== Install ==
To install MeeGo 1.2 Community Edition for N900, refer to our [[ARM/N900/GettingStarted|Getting Started page.]]

=== Image releases ===
When downloading images can choose from several images from our repository, or even [[ARM/Creating ARM image using MeeGo Image Creator|build one yourself.]]

[[ARM/N900/GettingStarted]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Image
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Release date
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer Release
|style="border-style: solid; border-width: 0 1px 1px 0"| Image for summer 2011.
|style="border-style: solid; border-width: 0 0 1px 0"| (coming soon)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ SF/MeeGoConf Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| San Francisco release, image released at MeeGo conference.(recommended)
|style="border-style: solid; border-width: 0 0 1px 0"| 23.5.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| 15.04.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/ Weekly image]
|style="border-style: solid; border-width: 0 1px 1px 0"| From here you can find the weekly and daily builds.
|style="border-style: solid; border-width: 0 0 1px 0"|
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [https://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo Core 1.1]
|style="border-style: solid; border-width: 0 1px 1px 0"| Original MeeGo core 1.1 release for N900.
|style="border-style: solid; border-width: 0 0 1px 0"| 28.10.2010
|}

=== Applications ===
If you want to try out some applications on MeeGo [[ARM/N900|Community Edition]] get them from [[ARM/N900/CoolStuff|here.]] Eventually applications will be in [[http://apps-beta.meego.com/applications/MeeGo Community apps site]].

== Participate ==
If you are interested to help developing MeeGo or applications for your favorite hardware. Please visit on MeeGo [[ARM/N900|Community Edition page.]]

== FAQ ==
Q. Where can I download the N900 Community Edition release? 
A. See [[#Download_image]]

Q. Where do I see the maturity of the current image? 
A. See the Community Edition [[ARM/N900/Status|Status page.]]

Q. My battery is drained, how shall I recharge it? 
A. Look from [[ARM/N900/Recover_From_Drained_Battery|battery recharge guide.]]

Q. I want to install back to Maemo5 as my only operating system, how will I do that? 
A. See the [http://wiki.maemo.org/Updating_the_firmware#N900_2 restore Maemo guide] from Maemo wiki.

Q. I want a usb connection to my N900, how will I do it? 
A. Use ssh. See [[ARM/N900/Tips_and_Tricks/N900_USB_Networking|guide.]]

N900

2011-06-21T16:33:43Z

Tjyrinki: mention N9 and N950

[[File:20000101-034513.png|400px|thumb|right]]

= MeeGo 1.2 Community Edition for Nokia N900 =
'' "I have N900, and want to try MeeGo on it." '' 
'' "I want to develop MeeGo/Qt applications on my N900 device" '' 
'' "I want to develop MeeGo OS, on existing N900 or other ARM-based device" '' 
'' "I want to be in the frontline of freeing up the new Nokia N9 (and Nokia N950)" ''

== Introduction ==
When using MeeGo on the Nokia N900, or other ARM-based handset, it's recommended to use MeeGo [[ARM/N900|Community Edition]]. [[ARM/N900|Community Edition]] is an edition of the core MeeGo 1.2. The [[ARM/N900|Community Edition]] is developed with the ARM and handset compatibility in mind, this way developers already owning a N900 device may start developing with it immediately.

For more information about the Community Edition, please visit [[ARM/N900|page.]]

== Status ==
The working status of MeeGo for N900 implementation can be seen on [[ARM/N900/Status|Status page.]] This MeeGo Community Edition will also be the place where similar effort on OMAP3 using Nokia N9 phone (and Nokia N950) will take place at.

== Install ==
To install MeeGo 1.2 Community Edition for N900, refer to our [[ARM/N900/GettingStarted|Getting Started page.]]

=== Image releases ===
When downloading images can choose from several images from our repository, or even [[ARM/Creating ARM image using MeeGo Image Creator|build one yourself.]]

[[ARM/N900/GettingStarted]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Image
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Release date
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer Release
|style="border-style: solid; border-width: 0 1px 1px 0"| Image for summer 2011.
|style="border-style: solid; border-width: 0 0 1px 0"| (coming soon)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ SF/MeeGoConf Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| San Francisco release, image released at MeeGo conference.(recommended)
|style="border-style: solid; border-width: 0 0 1px 0"| 23.5.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego Developer Edition image.
|style="border-style: solid; border-width: 0 0 1px 0"| 15.04.2011
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/ Weekly image]
|style="border-style: solid; border-width: 0 1px 1px 0"| From here you can find the weekly and daily builds.
|style="border-style: solid; border-width: 0 0 1px 0"|
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [https://meego.com/downloads/releases/1.1/meego-v1.1-handset MeeGo Core 1.1]
|style="border-style: solid; border-width: 0 1px 1px 0"| Original MeeGo core 1.1 release for N900.
|style="border-style: solid; border-width: 0 0 1px 0"| 28.10.2010
|}

=== Applications ===
If you want to try out some applications on MeeGo [[ARM/N900|Community Edition]] get them from [[ARM/N900/CoolStuff|here.]] Eventually applications will be in [[http://apps-beta.meego.com/applications/MeeGo Community apps site]].

== Participate ==
If you are interested to help developing MeeGo or applications for your favorite hardware. Please visit on MeeGo [[ARM/N900|Community Edition page.]]

== FAQ ==
Q. Where can I download the N900 Community Edition release? 
A. See [[#Download_image]]

Q. Where do I see the maturity of the current image? 
A. See the Community Edition [[ARM/N900/Status|Status page.]]

Q. My battery is drained, how shall I recharge it? 
A. Look from [[ARM/N900/Recover_From_Drained_Battery|battery recharge guide.]]

Q. I want to install back to Maemo5 as my only operating system, how will I do that? 
A. See the [http://wiki.maemo.org/Updating_the_firmware#N900_2 restore Maemo guide] from Maemo wiki.

Q. I want a usb connection to my N900, how will I do it? 
A. Use ssh. See [[ARM/N900/Tips_and_Tricks/N900_USB_Networking|guide.]]

ARM/N900/Install/MMC

2011-06-16T15:14:10Z

Tjyrinki: /* Load or flash kernel on N900 */ link to dual-boot page

= Installing MeeGo to N900 on external MMC card =

'''NOTE: Read the whole guide before doing any steps from this guide to make sure you understand everything.'''

If you do not want to erase the NAND partition or the internal 32G eMMC from the N900 device, this installation is for you. What you need for this installation is a raw image that can be put to the MMC card and kernel (same kernel that is installed to the MMC).

=== Images ===

Raw images and corresponding kernel images can be found at http://repo.meego.com/MeeGo/builds/ (development builds) and http://repo.meego.com/MeeGo/releases/ (stable releases)

Find official release images here ([[ARM/N900#Releases]])

You may want to check for the most recent N900 test reports at [[Quality#MeeGo_Handset_Testing]] to see how much functionality is known to work on the N900.

== Installing Rootfs on external MMC card ==

First what you need, is a microSD memory card which does not contain any information that you need, as it will be erased during this operation.

The steps in this guide require an MMC card of at least 4gb.

=== Linux ===

When inserting the microSD memory card in the card reader, you need to find out what the proper device for the card is. You can also plug the N900 into your computer's USB slot using the package provided cable. Make sure the external microSD card is unmounted, as with most modern linux distributions today it will get auto-mounted if the has a valid filesystem (FAT32 or ExtX). To unmount, you can try this example:
sudo umount /dev/sdX

And use the mount command to determine if/ where it is mounted:
sudo mount (for an example how the microSD would look go [[MountOutput here]].

Finding out the device node can also be done with for example fdisk:
sudo fdisk -l

An example output ('''NOTE: The /dev/sdX is used as an example on your PC this might be also called /dev/mmcblk0, /dev/sdd or something else''')
$ sudo fdisk -l
...
Disk /dev/sdX: 3965 MB, 3965714432 bytes
194 heads, 30 sectors/track, 1330 cylinders
Units = cylinders of 5820 * 512 = 2979840 bytes
Disk identifier: 0x0001ab40

Device Boot Start End Blocks Id System
/dev/sdX1 1 588 1708984 83 Linux

'''NOTE: The .raw image contains the partition table as well. So the image needs to be written to /dev/sdX not /dev/sdX1.'''

After you are 100% sure that the /dev/sdX is the microSD memory card you just inserted in the card reader, you can use for example dd to put the image to the card:
$ sudo dd bs=4096 if='''<raw_image>''' of=/dev/sdX

If you are low on disk space, you can use

$ bzcat <raw_image>.bz2 | sudo dd bs=4096 of=/dev/sdX

to decompress the compressed raw image on the fly without having to unpack it on you computer first. And if you have pv(1) installed, you can add it in between to display the progress (the image is ~ 2GB in size as of 2010-10-04):

$ bzcat <raw_image>.bz2 | pv | sudo dd bs=4096 of=/dev/sdX

The dd does not show any progress until the file is written to the device, so be patient.

Although sending a USR1 signal to a running dd process makes it print I/O statistics to standard error and then resume copying:
$ dd if=/dev/zero of=/dev/null& pid=$!
from another term:
$ kill -USR1 $pid

dd will output:

328356+0 records in
328356+0 records out
1344946176 bytes (1.3 GB) copied, 105.625 s, 12.7 MB/s

After this, you can insert the card in the N900.

=== Windows ===

# Download and install bzip2 to Windows http://gnuwin32.sourceforge.net/packages/bzip2.htm
# Uncompress raw image in command prompt "bunzip2.exe <compressed raw image>"
# Download the Win32DiskImager.exe program: https://launchpad.net/win32-image-writer/+download (zip file)
# Unzip the file and extract the contents to a known directory
# Run W32DiskImager.exe
# Select the MeeGo image file (note you must write *.* file name to see all files)
# Select the drive letter which corresponds to the microSD memory card.
# Click the "Write" button to byte-copy the image to the microSD memory card.

''''''NOTE!!''' If you get error 'Not enough space on disk'. Try again with external memorycard reader.'''

=== Mac OS X ===

When inserting the microSD memory card in the card reader, you need to find out what the proper device for the card is. This can be done with disktool:
diskutil list

An example output ('''NOTE: The /dev/diskX is used as an example on your Mac this might be also called /dev/disk2, /dev/disk3 or something else''')
$ diskutil list
...
/dev/diskX
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *4.1 GB disk3
1: DOS_FAT_32 DISKETTE 4.1 GB disk3s1

'''NOTE: The .raw image contains the partition table as well. So the image needs to be written to /dev/diskX not /dev/diskX1.'''

'''NOTE: If you want to improve the speed writing your mmc card, you can use the raw device, avoiding the use of the os buffer, add 'r' add the name of your mmc interface, example: /dev/rdiskX'''

After you are 100% sure that the /dev/diskX is the microSD memory card you just inserted in the card reader, you can use for example dd to put the image to the card:
$ sudo dd bs=4096 if='''<raw_image>''' of=/dev/diskX

If you are low on disk space, you can use

$ bzcat <raw_image>.bz2 | sudo dd bs=4096 of=/dev/diskX

to decompress the compressed raw image on the fly without having to unpack it on you computer first.

The dd does not show any progress until the file is written to the device, so be patient.

Although sending a SIGINFO signal to a running dd process makes it print I/O statistics to standard error and then resume copying:
$ dd if=/dev/zero of=/dev/null& pid=$!
from another term:
$ kill -SIGINFO $pid

After dd is done dd will output something similar like this:

475136+1 records in
475136+1 records out
1946157057 bytes transferred in 2606.033611 secs (746789 bytes/sec)

After this, you can eject the microSD and insert the card in the N900.

=== On the N900 itself ===

This should be a last resort solution.

# Download and unpack the raw image to a desktop computer (see above).
# un-mount the microSD memory card
sudo gainroot
umount /dev/mmcblkXpY
dd if=/home/user/MyDocs/'''<raw_image>''' of=/dev/mmcblk1

==== Notes ====
* X, Y in umount command should be the device number and partition number, usually 1, 1. '''Do not take information from /proc/partitions!'''
N900 swaps devices during boot and /proc/partitions is what the kernel initially sees when it is loaded. N900's SD-Card is /dev/mmcblk1 for Maemo5-Standard-Install and not like shown in /proc/partitions, /dev/mmcblk0! NITdroid's SD-install has SD-Card as /dev/mmcblk0 instead. If you want to see what is mounted at the moment type "mount|grep mmc" or "df|grep mmc".
* There might be more than one partition on the microSD memory card, though it is unlikely and depends on your own setup. You need to unmount all partitions before you proceed to `dd`.

* It is possible to download the compressed image to your N900 but it is not recommended as it takes very long to unpack.
* `dd` does not give any output while it is copying, so be patient.
* If you aren't sure about any of these steps you should not proceed without consulting a professional.

== Load or flash kernel on N900 ==

Before the MeeGo is able to boot you need also load the kernel (vmlinuz) provided with the raw image to the device. This can be done with the [[ARM/N900/tools/flasher|flasher]].

=== Dual-boot with maemo using u-boot ===

See [[ARM/N900/Install/Dual_Boot]] instead.

=== Load or flash manually ===
====Prerequisites====

* the flasher application needs to be installed on your computer. You can get it from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php here].
On 64-bit Ubuntu/Debian this command would do the trick, after downloading the .deb file:

$ sudo dpkg --force-architecture -i maemo_flasher-*i386.deb

====Running Meego====

'''NOTE: First open the back cover of N900 and insert the MMC card to the slot, reinstall the back cover again.

'''NOTE: Back cover must be closed to boot from MMC.'''

'''NOTE: If you have a flashing jig, you will need to put a magnet at the red location marked [http://www.daimi.au.dk/~cvm/magnet.png here]'''

You need to execute the following command on your host system.

'''NOTE: the device must be turned off and disconnected from the computer. Connect it to the computer using the USB cable only after executing the command'''

$ sudo flasher-3.5 -l -k '''<kernel>''' -b

A message like:
flasher v2.5.2 (Oct 21 2009)
Suitable USB device not found, waiting.
is shown on the terminal of the computer.

Then connect N900 to the computer via the USB cable and Meego OS will be booted.
You may need to keep 'U' key pressed (on the phone's keyboard) when connecting the cable.

'''NOTE: The command above will only load the kernel to the device, so next time you boot the device the original kernel should be used and your Maemo 5 OS should boot normally.'''

If you want to flash the kernel to your device so that it is not forgotten when it is powered off use option -f instead of option -l on command above.

'''NOTE: It's highly recommended NOT to flash the kernel on your device unless you really know what you're doing (so please use -l instead of -f). Don't blame us if you brick your device, you have been warned!'''

{| class="wikitable" border="1" cellpadding="5"
|+ Examples of files that can be used with this guide
! MeeGo Version
! <kernel>
! <raw_image>
|-
| 1.0.99.2.20101019.1
| [http://repo.meego.com/MeeGo/builds/1.0.99/1.0.99.2.20101019.1/handset/images/meego-handset-armv7l-n900/meego-handset-armv7l-n900-1.0.99.2.20101019.1-vmlinuz-2.6.35.3-10.3-n900 meego-handset-armv7l-n900-1.0.99.2.20101019.1-vmlinuz-2.6.35.3-10.3-n900]
| [http://repo.meego.com/MeeGo/builds/1.0.99/1.0.99.2.20101019.1/handset/images/meego-handset-armv7l-n900/meego-handset-armv7l-n900-1.0.99.2.20101019.1-mmcblk0p.raw.bz2 meego-handset-armv7l-n900-1.0.99.2.20101019.1-mmcblk0p.raw.bz2]
|-
| 1.1.80.0.20101001.1
| [http://repo.meego.com/MeeGo/builds/trunk/1.1.80.0.20101001.1/handset/images/meego-handset-armv7l-n900/meego-handset-armv7l-n900-1.1.80.0.20101001.1-vmlinuz-2.6.35.3-8.5-n900 meego-handset-armv7l-n900-1.1.80.0.20101001.1-vmlinuz-2.6.35.3-8.5-n900]
| [http://repo.meego.com/MeeGo/builds/trunk/1.1.80.0.20101001.1/handset/images/meego-handset-armv7l-n900/meego-handset-armv7l-n900-1.1.80.0.20101001.1-mmcblk0p.raw.bz2 meego-handset-armv7l-n900-1.1.80.0.20101001.1-mmcblk0p.raw.bz2]
|}

[[Category:N900]]

ARM/N900/Install

2011-06-16T15:09:54Z

Tjyrinki: Redirected page to ARM/N900#Installing and running

#REDIRECT [[ARM/N900#Installing_and_running]]

ARM/N900/Install

2011-06-16T15:08:29Z

Tjyrinki: Redirected page to N900#Installing and running

#REDIRECT [[N900#Installing_and_running]]

ARM/N900/Install

2011-06-16T15:07:48Z

Tjyrinki: redirect to N900#Installing_and_running

#REDIRECT N900#Installing_and_running

ARM/N900/Install/Dual Boot

2011-06-04T08:50:43Z

Tjyrinki: SF release requires 4GB card (source: lwn)

== Dual booting Maemo 5 (Fremantle) PR1.3 and MeeGo Developer Edition ==

WARNING: This guide is experimental and everything you do with this guide is at your own responsibility and risk

WARNING: DO NOT RELY ON WALL CHARGER, ONLY USB CHARGING FOR 1.1 IMAGES, see [http://bugs.meego.com/show_bug.cgi?id=2260 meego bug #2260] (no longer applies to images from april 2011 - wall charger is better)

WARNING: If you are unable to boot anything, do NOT let the device stay in u-boot. IMMEDIATELY reflash back to Maemo. Your battery may drain otherwise. You can solve a drain situation by reflashing back to Maemo using another, charged, battery. Or charge your battery in another Nokia device using the same battery type, such as the 5800, using a wall charger. There is a [[ARM/N900/Recover From Drained Battery|guide to battery drainage solving]].

This is a simplified guide for dual-booting with u-boot on Nokia N900.

'''You must be using the PR1.3 kernel and nothing else'''. You will likely end up in a reboot loop if you don't have this otherwise. To check this, in Settings -> About product, make sure you see:

<pre>Version: 20.2010.36-2</pre>

You will need a 4 GB microSD card or bigger. You may also see "MMC", which is basically the same thing as the microSD card.

# Enable the maemo.org extras-devel repository, see http://wiki.maemo.org/Extras-devel (The software hosted in extras-devel is not ready for normal users! PLEASE PLEASE PLEASE don't play with it unless you really know what you are doing. It is recommended to disable the extras-devel repository after you have installed the package below, and do not install any updated packages that you might be notified of while extras-devel is enabled. Be ready to file proper bug reports instead of posting complaints.)
# Install the 'uboot-pr13' package from 'System' section
# Verify it's installed by restarting your N900. A penguin should show up at startup and U-boot will be mentioned, let it time out and boot into Maemo.
# Download the image from [http://repository.maemo.org/meego/n900-de/ http://repository.maemo.org/meego/n900-de/] (you need the raw.bz2 file for the daily acceptance image)
# Follow the [[ARM/N900/Install/MMC#Installing Rootfs on external MMC card|instructions for installing a rootfs on an external MMC card]] to write the raw image to your microSD
# Insert the microSD, put back phone back cover (otherwise, microSD card won't be properly detected at startup by MeeGo) and turn on the N900, let U-boot menu time out and MeeGo will boot.
# Enjoy!

To boot back in to Maemo turn off your phone, then either remove the microSD and then turn on your phone, or turn it on and interrupt the boot during the countdown by pressing a button and then type "run noloboot".

If you want to remove U-boot you can as root in Maemo run: apt-get install --reinstall kernel kernel-flasher

If you are unable to get back into Maemo, please follow http://wiki.maemo.org/Updating_the_tablet_firmware in order to reflash your device. This will destroy your current Maemo setup, but return your device to a working state

For the technically minded, you can flasher '-F <firmware image> -u' and 'flasher -f zImage -R' to get your original kernel back and hopefully get back to your current Maemo setup. If you have used other kernels than PR1.3 kernel as is required, this will not work.

=== Trick way install u-boot using flasher ===

This is more risk so please use previous way instead.

Note all warnings of previous section.

'''You must be using the PR1.3 kernel and nothing else'''. You will likely end up in a reboot loop if you don't have this otherwise. You need dpkg tool to use this.

# Download 'uboot-pr13_*_armel.deb' from http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/u/uboot-pr13/
# unpack deb: "dpkg -X uboot-pr13_1.0.2_armel.deb uboot-pr13"
# flash to device: "sudo flasher-3.5 -f -F temp/boot/uboot-and-zImage-2.6.28-20103103+0m5.fiasco"

[[Category:N900]]

ARM/N900/ReleaseProcess

2011-06-03T05:34:47Z

Tjyrinki: /* DE-affiliated meego.com users */

This page describes the [[ARM/N900/DeveloperEdition|N900 Developer edition]] release process.

== Principles ==

* Everything we cannot get into MeeGo 1.2/will have significant difficulties getting into MeeGo 1.2 due to feature freeze will go into the N900 DE OBS project.
* Everything should ideally be contributed back to MeeGo 1.3 release track.
* We should stay ABI compatible with MeeGo 1.2.
* We should be aiming for providing a MeeGo compliant "product".

== Repository setup ==

We have two OBS projects on the [http://build.pub.meego.com Community OBS]:

* [https://build.pub.meego.com/project/show?project=Project%3ADE%3ATrunk Project:DE:Trunk] (stable repository)
* [https://build.pub.meego.com/project/show?project=Project%3ADE%3ATrunk:Testing Project:DE:Trunk:Testing] (staging repository)

''Currently'', each of them builds against MeeGo 1.2 release, via the Project:DE:MeeGo:1.2/standard .

When again developing against a moving target instead of a published release, each of them will have two build targets for the packages:

* 'standard', which points to the current state of the MeeGo 1.x trunk which becomes next weekly.
* 'weekly', which points to MeeGo 1.x weekly release.

This setup will allow us to look-ahead on upcoming issues caused by changes done in the MeeGo 1.x trunk.

== Image building and testing matrix ==

MeeGo.com weekly release comes out on wednesdays. DE weekly release comes out on fridays.

Both sanity & acceptance tests are very brief run-throughs of the functionality of the entire MeeGo distribution, to assure that the basic health of the distribution and report major regressions at the earliest time. All the checkpoints in sanity & acceptance test reflect the most important and basic functionality of the distribution.

We do the sanity test against the Trunk and the acceptance test against Trunk:Testing.

{| class="wikitable" border=1
|-
! Day
! MeeGo.com 1.2 Trunk & Project:DE:Trunk
! MeeGo.com 1.2 Trunk & Project:DE:Trunk:Testing
! MeeGo.com 1.2 Weekly & Project:DE:Trunk
! MeeGo.com 1.2 Weekly & Project:DE:Trunk:Testing
|-
| Monday
| sanity
| acceptance
|
|
|-
| Tuesday
| sanity
| acceptance
|
|
|-
| Wednesday (Freeze, only fixes to make sure a proper weekly release happens are let in to Trunk)
|
|
| weekly release track sanity
| weekly release track acceptance
|-
| Thursday
| sanity
| acceptance
| weekly release track sanity
| weekly release track acceptance
|-
| Friday (after weekly release, repository unfreezes)
| sanity
| acceptance
| weekly release track sanity, if OK, DE weekly release
|
|}

Rationale:

Weekly release == MeeGo 1.2 Trunk on wednesdays, so no need to have seperate images.

Weekly release acceptance testing needs to happen to make the fixes flow to weekly release fix.

"Normal" Sanity/acceptance serves to help prepare for next weeks changes.

== Procedures ==

=== Developer: Branch a package and submit changes to DE ===

Choose your origin (in the following, ORIGIN) of the package:

* MeeGo.com:MeeGo:1.2:oss (currently 1.2)
* Project:DE:Trunk:Testing (fix a package already contained in DE)

osc -A <nowiki>https://api.pub.meego.com</nowiki> branch -cm "To work on MeeGo DE" ORIGIN packagename

This creates home:yourusername:branches:ORIGIN.

Go to https://build.pub.meego.com/home/list_my and find your project.

If there is no repositories listed in Repositories tab,
go and click "add repository" and "advanced interface" and choose Project:DE:Trunk:Testing as project,
"standard" as repository, new name "standard" and architecturesi armv8el and i586.

.. do your work

'''NOTE:''' Remember to add entry to .changes file and describe what your submit fixes. "- Fixes for BMC#1234" isn't enough, but "- photo-index.patch: Fixed segmentation fault when indexing photos (BMC#1234)" would do.

After your work is done, i.e., doing the changes to the package and after you have committed the changes to your branch, it is time to check that everything is like it should be. So, lets verify the diff between your branch and the target. NOTE: If you are submitting new package to Project:DE:Trunk:Testing the diff is most probably empty.

osc -A <nowiki>https://api.pub.meego.com</nowiki> submitreq -dm "." home:yourusername:branches:ORIGIN packagename Project:DE:Trunk:Testing

After you have confirmed that the diff is ok. It is time to submit the changes:

osc -A <nowiki>https://api.pub.meego.com</nowiki> submitreq -m "What you changed" home:yourusername:branches:ORIGIN packagename Project:DE:Trunk:Testing

As a result of this command you will get request id that corresponds the request. You can check your request from the OBS webui https://build.pub.meego.com/request/show/REQUEST_ID

=== Release engineering ===

If you'd like to help out with release engineering, poke Stskeeps / Carsten Munk on IRC.

General procedure for reviewing [https://build.pub.meego.com/project/list_requests?project=Project:DE:Trunk:Testing requests towards Project:DE:Trunk:Testing]:

* Verify the package actually builds in the origin project
* Review the package on basis of [[Packaging/Guidelines|packaging guidelines]]
* When accepting the change to Project:DE:Trunk:Testing make sure that there is existing package link already if the change is a patch is to package in MeeGo.com:Trunk
osc -A https://api.pub.meego.com linkpac -c MeeGo.com:Trunk <package> Project:DE:Trunk
osc -A https://api.pub.meego.com linkpac Project:DE:Trunk <package> Project:DE:Trunk:Testing
* After the link is created and review for the changes have been made you can accept the package. ''NOTE:'' It is recommended to ''Forward to Project:DE:Trunk'' (but not accept the package in Project:DE:Trunk) instead of just ''Accept'' the package to make sure it ends up to the Project:DE:Trunk project eventually.

Conditions and procedure for accepting a package change into Project:DE:Trunk from Project:DE:Trunk:Testing:
* The package change must not break any compilation in Trunk:Testing
* The package change must have been included in one acceptance testing image and no regressions seen because of it by QA.
* When OK, submit package to Project:DE:Trunk and remove package from Project:DE:Trunk:Testing (use UI).
* Only accept changes to Project:DE:Trunk that fix issues towards maintaining quality of the weekly image release from Wednesday to Friday weekly release time (soft freeze)
* Accept in the [https://build.pub.meego.com/project/list_requests?project=Project:DE:Trunk requests list towards Project:DE:Trunk]
* Decline any changes made directly to Project:DE:Trunk not done from Project:DE:Trunk:Testing.

==== When link needs to be updated ====

osc -A https://api.pub.meego.com linkpac -c -f MeeGo.com:MeeGo:1.2:oss <PACKAGE> Project:DE:Trunk
cd <package_checkout>
osc -A https://api.pub.meego.com up
patch -p0 < project.diff
# Fix conflicts
osc rm project.diff
osc ci -m "Rebased link."

==== Image creation ====

Multiple options, we are currently looking at having the images physically built in internal Nokia IMG service and transferred to a public download site.

==== Image configurations ====

N900 DE image configurations (kickstart files) are located at https://gitorious.org/meego-developer-edition-for-n900/image-configurations gitorious tree under the kickstarts directory.

==== Daily image creator ====

From the git tree above the images are created by daily-image-builder, which is available at https://gitorious.org/image-building-tools/daily-image-builder

daily-image-builder script is executed every morning on computer X from where the images are uploaded to http://repository.maemo.org/meego/n900-de/daily/ around UTC 03:00.

==== Release Format ====

The directories in n900-de repository look following 1.1.99.2.20110412.6.DE.2011-04-19.2 where the start is the MeeGo version and the end after DE is the DE build version in following format YYYY-MM-DD.<build_count>

The MeeGo version is taken from http://download.meego.com/trunk-daily/builds/trunk/

==== Images ====

Currently we have couple of different images types:

mg-handset-armv7nhl-n900-de-sanity
mg-handset-armv7nhl-n900-de-acceptance
mg-tablet-armv7nhl-n900-de-acceptance

All the images use MeeGo Trunk (later on MeeGo 1.2) daily repository as a base. So no Trunk:Testing packages are used. This pretty much means that DE images are closest to the MeeGo sanity test report results. In DE case the sanity and acceptance in image name means which DE repository we are using in addition to the MeeGo Trunk, i.e., in sanity images we use Project:DE:Trunk repository and in acceptance Project:DE:Trunk:Testing repository.

Tablet image uses also Project:DE:Devel:Tablet repository for some n900 tablet specific modifications.

=== DE-affiliated meego.com users ===

'''Please send mail to carsten@maemo.org to get activated on community OBS'''

* stskeeps
* [http://www.meego.com/users/sage sage]
* alaukkanen
* jkunnari
* marquiz
* sachawla
* ksilinja
* liljeber
* sikemppa
* kjokinie
* msugano
* msafr
* zhurakiv
* japaloja
* logoel
* lamikr
* vesku
* tjyrinki

[[Category:N900]]

ARM/N900

2011-06-01T15:03:40Z

Tjyrinki: /* FAQ */ starting my n00b questions / documenting them, maybe removed or moved elsewhere later

= MeeGo 1.2 Developer Edition for Nokia N900=

'''What's hot:'''
Test the '''MeeGoConf/SF release''' of the MeeGo 1.2 Developer Edition for N900: [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ download] - [[#Installing_and_running|install]] - [[ARM/N900/CoolStuff|cool stuff]]

== Introduction ==
The target of this activity is to make a Developer Edition of MeeGo for the Nokia N900 device. This Developer Edition is an 'overlay' constructed above the current core MeeGo 1.2. The DE project is working as a draft of a MeeGo handset image, to make possible the MeeGo development on your N900 hardware. Being a draft it will not take into account all features commonly present in a handset OS. To see what features will be implemented look [[#Key_features]]. Flashed with this edition N900 will be usable as a primary phone device for a developer/hacker person. '''This is not meant for regular (Maemo 5) users. Using this release will probably void any warranty and there is no (other than community-based) support available.'''

=== Target ===
The focus is on meeting the non-functional targets (such as performance) rather than number of features. This will hopefully encourage more people to use MeeGo on N900, and continue enhancing the functionality or build new stuff. Developer Edition is based on MeeGo 1.2 handset trunk content, and selected community contributions ([[ARM/N900/CoolStuff|see the candidates]]). Core MeeGo 1.2 Handset features can be found in [https://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&version=1.0&version=1.1&version=1.2&version=1.0&version=1.1&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_status=ACCEPTED&bug_status=RESOLVED&bug_status=RELEASED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bug_id_type=anyexact&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= featurezilla], and features of DE not yet implemented from [[ARM/N900/Configuration|Configuration list.]]

== Key features ==
These use cases shall be the prominent ones in the Developer Edition. (If you want to promote a feature to this list, please add it to the feedback section first.)

'''Cellular voice calls''' (Dialer, People)

* Make voice calls (input number directly, initiate from Contacts, initiate from Call history)
* Receive calls
* Default ringtone plays
* Volume control works via System UI
* SIM PIN entry support

'''SMS''' (SMS, People)
* Send new SMS (input number, send from Contacts)
* Receive SMS, and reply to sender

'''Browser use over WLAN''' (Browser, Settings)
* Able to connect to WLAN AP (with security etc.)
* Open a complex modern website (eg. gmail.com)

'''Camera''' (meegocamera)
* Still image capture
* Support for N900 keys (zoom, capture)

'''Common SW''' (Settings, xterm, lock)

Common components such as System UI, Home screen etc. shall be made functional so that basic device usage is smooth and fast. N900 device specific features such as keys, display and battery will be optimized. [[SDK|MeeGo SDK]] fully supports this edition, as it is MeeGo 1.2 compliant.

== Status ==
The maturity of Developer Edition image, can be seen from the [[ARM/N900/Status|Status page.]]

== Installing and running ==
Image download and installing instructions can be found from [[N900#Install|N900 page,]] please refer to them for more instructions.

* [[N900#Install|Download and install]] instructions page.
* [[ARM/N900/Status|Status and reports]] of the latest image.
* [[ARM/N900/CoolStuff|Applications and accessories]] for the Developer Edition.

== Release schedule ==

This shows the '''release schedule''' and content. It should be understood that Developer Edition is still based on "best-effort" model, so this might change any time. If you want to make sure targets are kept, please join the project and help us. For more detailed list of features that are implemented on the releases, look in the [[ARM/N900/Configuration|Configuration page.]]

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0"
|-
!style="border-style: solid; border-width: 0 1px 1px 0"| Release
!style="border-style: solid; border-width: 0 1px 1px 0"| Date
!style="border-style: solid; border-width: 0 1px 1px 0"| Description
!style="border-style: solid; border-width: 0 0 1px 0"| Main Features
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| "Summer release"
|style="border-style: solid; border-width: 0 1px 1px 0"| end of June
|style="border-style: solid; border-width: 0 1px 1px 0"| Summer release of Meego DE
|style="border-style: solid; border-width: 0 0 1px 0"| (coming soon)
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.7.20110516.2.DE.2011-05-23.1/images/mg-handset-armv7nhl-n900-de-sanity/ MeeGo Conference Release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 23.5.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Meego conference release
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Meego_Conference_Release|link]]
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| [http://repository.maemo.org/meego/n900-de/archive/1.1.99.2.20110412.6.DE.2011-04-15.1/images/mg-handset-armv7nhl-n900-de-acceptance/ Alpha release]
|style="border-style: solid; border-width: 0 1px 1px 0"| 15.04.2011
|style="border-style: solid; border-width: 0 1px 1px 0"| Alpha release of the Meego DE image.
|style="border-style: solid; border-width: 0 0 1px 0"| [[ARM/N900/Configuration#Alpha_Release|Calls, SMS, Browser and Camera.]]
|-
|}

== I want to help! ==
Willing to contribute the code to DE/MeeGo, but wondering where to start from? Learn the ropes from the MeeGo experts! This [[Media:Meegokickoff.pdf|material (meego developer's journey)]] gives the overview on the daily development workflow.

Some more concrete steps:

* To contribute fixes see [[ARM/N900/ReleaseProcess]].
* Follow Discussion
** Join [http://lists.meego.com/listinfo/meego-porting meego-porting@meego.com] and [http://lists.meego.com/listinfo/meego-handset meego-handset@meego.com] mailing lists
** Hang out in [http://webchat.freenode.net/?channels=#meego-arm #meego-arm IRC channel on irc.freenode.net]
** Join [[ARM/N900/DeveloperEdition/Meetings|weekly team meetings]] are held in the public IRC. This meeting is registered on the [[MeeGo-Meeting_IRC_Schedule|MeeGo IRC Meeting Page]]. The agenda and the archives are also available.
* Learn
** Play a little with Tablet UX pre-alpha as it's possible the same applications will be replacing some of the Handset UX ones. Experiments are being tried with the Tablet UX on N900. Find more details on [[ARM/N900/TabletUX]].
** Look into learning QML if you haven't already.
*Contribute
** Would like to contribute the test cases? You will find the useful information [[Quality|here]].
** Would like to contribute artwork? See [[ARM/N900/Artwork]].
** To the [[ARM/N900/Performance|performance optimization]].
** Follow [http://qa-reports.meego.com/1.2/Handset/Acceptance/N900 acceptance testing reports] and see if there's anything of your interest you'd like to work on.
* Look through [[ARM/N900/Developers|Developers page,]] for tips and tricks.

== Organization ==
Core team, of Developer Edition, is formed in and around Nokia. In addition to core team, we hope to see growing community working on this. There is something for everybody to contribute be it bugs, code, artwork or something else. Core team itself has been divided into following categories:

* Program lead: [http://meego.com/users/bittinen Mika Leppinen]
** R&D lead: [http://meego.com/users/msugano Makoto Sugano]
*** [[ARM/N900/VoiceSMS|Voice/SMS]] team lead: [http://meego.com/users/sabotage Shane Bryan]. *
*** [[ARM/N900/Browser|Browser/WLAN]] team lead: [http://meego.com/users/vesku Vesa-Matti Hartikainen]
*** [[ARM/N900/Common|Common SW]] team lead: [http://meego.com/users/harrihakulinen Harri Hakulinen]. **
*** [[ARM/N900/ReleaseProcess|Release & integration]]: [http://meego.com/users/ericlr Eric Le Roux], [http://meego.com/users/stskeeps Carsten Munk], [http://meego.com/users/sage Marko Saukko].
** [[ARM/N900/QA|QA]]: [http://meego.com/users/jaritah Jari Tahvanainen], [http://meego.com/users/markraja Marko Rajala]
** [[ARM/N900/PM|Product management]]: [http://meego.com/users/jukkaeklund Jukka Eklund], [http://meego.com/users/samipienimaki Sami Pienimäki]

<nowiki>*</nowiki>This project is merged with the MeeGo mainstream [[Project/Dialer|Dialer project.]] 
<nowiki>**</nowiki>Includes the [[ARM/N900/HW_Adaptation_team|Hardware Adaptation]] (maintained by [http://meego.com/users/stskeeps Carsten Munk]).

== FAQ ==

Q. Let's assume my bug fix was accepted only in the DE, but rejected in the official 1.2. What do we do with the bug? 
A. Submit the fix to 1.3. Change the status to "RESOLVED". Comment that the fix is available in DE & 1.3.

Q. Which SD card should I be using? 
A. Class 6 and higher. The class has the impact on the performance.

Q. Where can I download the N900 DE release? 
A. See [[N900#Install|installation instructions]]

Q. What is the UI of DE going to be? 
A. Based on what's available on MeeGo trunk. At the moment we work with the MeeGo 1.1-originated Handset UX and apps. We are evaluating the new tablet-originated UX and apps (see [[ARM/N900/TabletUX]]). This is still to be decided, and there might be even multiple options for the user to select.

Q. If I get "The package integrity check failed." (NOKEY) when trying to zypper install MeeGo 1.2 packages, where can I find the missing keys?[1.6.2011] 
A. (no answer yet)

Q. I installed to eMMC and it's dog-slow? [1.6.2011] 
A. The eMMC currently has a severe performance problem, [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295]

== Ideas, feedback etc. ==

Please add stuff to the [[ARM/N900/Ideas|Ideas]] page.

== Reporting bugs against N900 DE ==

Currently there is no special Bugzilla product/component for the N900 Developer Edition ([http://twitter.com/jukkaeklund/status/74396393195839488 it's "the same MeeGo"]). According to [http://twitter.com/jukkaeklund/status/74396845920632832 this post] by Jukka, you should:

* File a bug report on [http://bugs.meego.com/ bugs.meego.com]
* Use '''[DE]''' in the summary
* Add the '''N900''' keyword to the bug report

[[File:Splash-developers.png]]

[[Category:N900]]

ARM/N900/Performance

2011-06-01T09:45:10Z

Tjyrinki: /* Improvement ideas */ link to emmc slowness bug

== DE Performance page ==
=== Problems ===

* Startup time of applications
* Startup time of the device
* Right after the homescreen has loaded, after the first boot, device is unusable for a while
* Memory use
* Slow I/O performance 2-20x slower than Maemo5 on N900
* UI scrolling freezes for 1-2s from time to time

== Benchmark results ==
* Results from Q/A http://wiki.meego.com/ARM/N900/QA/Performance
* SunSpider (JavaScript performance
** 6.1s with GPE MiniBrowser (image DE.2011-05-30 acceptance)
** 6.8s with Fennec (image DE.2011-05-30 acceptance)
** These are actually pretty good results. Indicates that raw CPU perfomance is ok.
* widgetsgallery -timedemo (TBD)

== Improvement ideas ==
* optimizing MTF packages, there might be some configuration options, etc.?
* ramzswap trial
* CGROUPS optimization, most likely still not done
* eMMC performance investigation, maemo is 2-20x faster? see [https://bugs.meego.com/show_bug.cgi?id=18295 bug #18295]
* last resort type of thing: taking NAND to use as swap (and destroying maemo installation)
* adjust stack sizes
* lower GLES ParamBuffer size
* Remove unused applifed processes.
* Merge meego-volume-control to systemui
* cache some often used data in NAND and symlink there
* tracker configuration
* test overclock with known testing (from qa-tools guys perhaps)
* real microsdhc tests based on class speed rating
** actually answer specific questions about how write/read speed effect perf
*** app startup times
*** general usage
*** media write times
*** cataloguing media

== TODO list ==
* Profile startup of simple MTF, QML, and Qt apps
* Profile memory use of simple MTF, QML, and Qt apps
* Investigate configuration options for MTF
* Investigate configuration options for Qt
* Investigate configuration options for QML
* Update MTF (libmeegotouch, mcompositor, home, system ui, etc. ) to get latest optimizations from upstream
* Update Qt

== Issues being worked on ==
* https://bugs.meego.com/show_bug.cgi?id=18268

== Tools ==
* Smaps (Memory use) http://wiki.meego.com/ARM/N900/Developers/Sp_smaps_snapshot
* Bonnie (I/O performance) http://wiki.meego.com/Bonnie
* Gprof
* Oprofile (Not available)
* More: http://wiki.meego.com/SDK/Developer_tools

ARM/N900/ReleaseProcess

2011-06-01T05:54:06Z

Tjyrinki: /* Repository setup */ Update to current situation.

Who's who

2011-02-08T11:41:04Z

Tjyrinki: edited my line

Let's use this page while it's useful. See also the [http://meego.com/community/members full list of meego.com members].

== MeeGo structure ==

=== Technical Steering Group ===
''Members of the [http://meego.com/about/governance TSG]''

* [http://meego.com/users/valhalla Valtteri Halla] (Nokia) - Benevolent dictator
* [http://meego.com/users/imad Imad Sousou/imad] (Intel) - Benevolent dictator

=== Architects ===
* [http://meego.com/users/poussa Sakari Poussa] (Nokia)
* [http://meego.com/users/sunilsaxena Sunil Saxena] (Intel)
* [http://meego.com/users/arjan Arjan Van De Ven] (Intel)
* [http://meego.com/users/mythi Mikko Ylinen] (Nokia)

=== Community Office ===

* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] (Intel) - Coordinator
* [http://meego.com/users/qgil Quim Gil/qgil] (Nokia) - Coordinator

=== Maintainers ===
* [[Maintainers structure ]]

See also [[Community Office]] - [http://wiki.meego.com/index.php?title=Special%3AListUsers&username=&group=bureaucrat&limit=50 wiki administrators]

== MeeGo developers ==
People paid to contribute to MeeGo and/or have commit rights.

* [http://meego.com/users/hbons Hylke Bons/hbons] - User Experience Designer
* [http://meego.com/users/harrihakulinen Harri Hakulinen/harha] - N900 Project Lead
* [http://meego.com/users/auke Auke Kok/auke] - Release developer, fast boot
* [http://meego.com/users/jku Jussi Kukkonen/jku] - Developer
* [http://meego.com/users/nmcgovern Neil McGovern/nmcgovern] - Developer
* [http://meego.com/users/nashif Anas Nashif/anaZ] - Distribution Architect
* [http://meego.com/users/pohly Patrick Ohly/pohly] - Developer
* [http://meego.com/users/quang Quang Pham/quang] - Developer
* [http://meego.com/users/zhuyanhai Zhu Yanhai/yanhai] - Developer
* [http://meego.com/users/rogerwang Roger WANG/roger] - Developer
* [http://meego.com/users/jbarnes Jesse Barnes/jbarnes] - Graphics stack developer
* [http://meego.com/users/jausmus James Ausmus/jausmus] - Developer
* [http://meego.com/users/fabo Fathi Boudra/fabo] - Developer
* [http://meego.com/users/sabotage Shane Bryan/sabotage] - Handset Developer
* [http://meego.com/users/mikeleib Michael Leibowitz/mikeleib] - Handset Developer
* [http://meego.com/users/mardy Alberto Mardegan/mardy] - Developer
* [http://meego.com/users/ayanes Adrian Yanes/ayanes] - Application Framework Developer & MeeGo Touch Theme maintainer.
* [http://meego.com/users/msafr miroslav Safr/msafr] - Developer
* [http://meego.com/users/curlybeast Martyn Russell/martyn] - '''Tracker''' developer & meego maintainer
* [http://meego.com/users/ifrade Ivan Frade/frade] - '''Tracker''' developer & meego maintainer
* [http://meego.com/users/senko Senko Rasic/ptlo] - Developer

== Linux Foundation contributors ==
'' Staff Members of the Linux Foundation [http://www.linuxfoundation.org]''

* [http://meego.com/users/dl9pf Jan-Simon Möller/dl9pf ] - Buildplatform Developer, [http://en.opensuse.org/Build_Service OBS] developer, Linux Foundation Staff Member
* [http://meego.com/users/ibrahim Ibrahim Haddad/ibrahim ] - Linux Foundation Director of Engineering/Technical Alliances, responsible for MeeGo activities at the Linux Foundation (details found [http://meego.com/community/blogs/ibrahim/2010/introducing-myself-meego-community here]).

== Other community members ==
The real deal is in the [http://meego.com/community/members full list of meego.com member profiles] (more than 5.000 already!). See also the list of [[Special:ListUsers|Wiki users]].

If you are in the list below but you are working with a de-facto role in the MeeGo project please help making your role official.

('''Please keep this list alphabetically-ordered, as it will make finding people easier''')

* [http://meego.com/users/qole Alan Bruce/qole] - Maemo Community Council member
* [http://meego.com/users/camahueto Alberto O. / camahueto] - Lawyer working in an unidentified Intellectual Property office. Free Software aficionado.
* [http://meego.com/users/agrin Alejandro Grin / agrin] - Independent developer.
* [http://meego.com/users/locusf Aleksi Suomalainen / LoCusF] - developer
* [http://meego.com/users/alessandro Alessandro Cogliati] - Browser/Flash developer, Nokia Meego.
* [http://meego.com/users/alexbez Alexander 'Sasha' Bezprozvanny / alexbez] Gadget freak and Maemo community member / Former Maemo team member (RTCom/Applications), now Technology Manager @ Ixonos Plc.
* [http://meego.com/users/ab Alexander Bokovoy / ab] - Senior Architect, Media applications, Nokia, Samba Team member
* [http://meego.com/users/aesantos Alexandra Engström Santos / aesantos] - Localisation SW Testing Project Manager, European Portuguese translator
* [http://meego.com/users/indeyets Alexey Zakhlestin/JimiDini] - maemo.org web/Midgard developer
* [http://meego.com/users/andre André Klapper/andre__] - maemo.org bugmaster
* [http://meego.com/users/aboaboit Andrea Borgia / aboaboit] - Maemo community member
* [http://meego.com/users/th0br0 Andreas Osowski / th0br0] - developer, Fedora Packager, interested in the RWG
* [http://meego.com/users/andrewfblack Andrew F Black / AndrewFBlack] - Maemo community member / Theme Designer / talk.maemo.org Moderator and Theme Designer.
* [http://meego.com/users/jaffa Andrew Flegg / Jaffa] - Long term gadget freak & Maemo community member
* [http://meego.com/users/antonr AntonR / AntonR] - Browser/Gecko embedding, Geo services.
* [http://meego.com/users/bdale Bdale Garbee / bdale] - HP, Debian
* [http://meego.com/users/khertan Benoît Hervier / khertan] - Maemo community member, software developer.
* [http://meego.com/users/earthling Bernd Stramm / earthling] - Independent developer.
* [http://meego.com/users/termana Bradley Smith / Termana] - MSMQSD MeeGo port Team Member
* [http://meego.com/users/bman Brian McKenzie / b-man] - Long term Maemo community member, software porter/developer, beta tester
* [http://meego.com/users/bundyo Bundyo / Bundyo] - Maemo community member, contributor
* [http://meego.com/users/stskeeps Carsten Munk/Stskeeps] - N900 hardware adaptation team member
* [http://meego.com/users/clay Clay Carey / Clay] - Moblin community member, software developer
* [http://meego.com/users/clintcan Clint Christopher Cañada / clintcan] - Moblin oriented netbook user, open source enthusiast and packages rpms for moblin/centos/rhel for personal use in spare time.
* [http://meego.com/users/leinir Dan Leinir Turthra Jensen / leinir] N810 owner, MeeGo community member (via Mer)
* [http://meego.com/users/daperl Da Perl / daperl] - Maemo community member, software developer
* [http://meego.com/users/b0unc3 Daniele Maio / b0unc3] - Maemo community member/contributor, software developer
* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/lbt David Greaves / lbt] - Mer OBS build guy
* [http://meego.com/users/dspeed Derek Speed / dspeed] - Linux and open source evangelist at Intel
* [http://meego.com/users/OdyX Didier Raboud / OdyX] - Debian pkg-meego packager
* [http://meego.com/users/glezos Dimitris Glezos / glezos] - Localization Engineer ([http://www.transifex.net/ Transifex])
* [http://meego.com/users/dirkhh Dirk Hohndel/dirkhh] - Chief Linux and open source technologist at Intel
* [http://meego.com/users/spaghetty Domenico Chierico / spaghetty] - Maemo community member
* [http://meego.com/users/epage Ed Page / epage] - Maemo community member, software developer
* [http://borasky-research.net M. Edward (Ed) Borasky] - Linux capacity planning / audio / openSUSE / Twitter geek
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - Moblin.org & meego.com website techy
* [http://meego.com/users/debernardis Ernesto de Bernardis / debernardis] - Maemo community member, mobile device tinkerer
* [http://meego.com/users/fgs Floriano Scioscia / fgs] - Maemo community member, IT engineer and junior researcher
* [http://meego.com/users/frederico Frederico Schardong / frederico] - Maemo community member, open source developer
* [http://meego.com/users/fpp Fred Pacquier / fpp] - maemo.org old-timer, platform-neutrality advocate, Python evangelist, and big mouth.
* [http://meego.com/users/amby Gabor Ambrozy / Amby] - Maemo community member, Save the End-Users advocate
* [http://meego.com/users/gaveen Gaveen Prabhasara / gaveen] - a DevOps guy. Planning to become a Fedora packager soon. FOSS / Linux / Ruby advocate
* [http://meego.com/users/gbraad Gerard Braad / gbraad] - Maemo community member, Fedora Project member, (open source) Hardware/Software engineer
* [http://meego.com/users/slaine Glen Gray / slaine] - Moblin community member, software engineer
* [http://meego.com/users/gcobb Graham Cobb / gcobb] - Maemo community member and application developer, former Commnunity Council member
* [http://meego.com/users/halton Halton Huo/Halton] - Browser Developer, Mozilla Contributor at Intel
* [http://meego.com/users/bergie Henri Bergius/bergie] - maemo.org web/Midgard developer
* [http://meego.com/users/ianbrasil Ian Lawrence / ianbrasil] - Author - Professional Ubuntu Mobile Development, Moblin and Maemo community member
* [http://meego.com/users/jmk Janne Karhunen / jmk] - Maemo system architect, System Software engineering + Security, Nokia MeeGo
* [http://meego.com/users/jannis Jannis Pohlmann / jannis] - Software developer (Xfce, tumbler etc.)
* [http://meego.com/users/kyber Jarkko Moilanen / kyb3R] - Community Manager - MeeGo Network Finland
* [http://meego.com/users/zerojay Jason Carter / zerojay] - Long term Maemo community member
* [http://meego.com/users/jkridner Jason Kridner / jkridner] - BeagleBoard.org Community Manager, Gentoo user, TI employee
* [http://meego.com/users/javispedro Javier S. Pedro / javispedro] - Maemo Community Council member
* [http://meego.com/users/jebba Jeff Moe / jebba] - [http://wiki.maemo.org/User:Jebba Maemo Contributor]
* [http://meego.com/users/jeremiah Jeremiah Foster/jeremiah] - maemo.org debmaster
* [http://meego.com/users/tuju Juha Tuomala / Tuju] - Fedora packager.
* [http://meego.com/users/jak Julian Andres Klode / jak] - Debian developer, Ubuntu member
* [http://meego.com/users/Krohon Krohon / Krohon] - Newbie, software developer
* [http://meego.com/users/leoz Leonid Zolotarev / LeoZ] - Browser buddy, Nokia MeeGo
* [http://meego.com/users/lpotter Lorn Potter / lpotter / ljp] - QDF, Mobility, Nokia
* [http://meego.com/users/hrw Marcin Juszkiewicz / hrw ] - OpenEmbedded developer, [http://marcin.juszkiewicz.com.pl/ self-employed] as OpenEmbedded/Poky Linux consultant/developer.
* [http://meego.com/users/margie Margie Foster/mlfoster] - Localization project manager for Moblin & meego.com website developer
* [http://meego.com/users/penguinbait Matthew Lewis/penguinbait] - Maemo Community Council member
* [http://meego.com/users/detective Max Maher / detective] - Maemo community member, software porter/developer, QA Engineer
* [http://meego.com/users/vgrade Martin Brook Vgrade/vgrade] -MSMQSD MeeGo port Team Member
* [http://meego.com/users/martinmohring Martin Mohring/ScriptRipper] - Buildplatform Developer, [http://en.opensuse.org/Build_Service OBS] Maintainer ([http://lizards.opensuse.org/2008/11/18/arm-support-for-opensuse-buildservice-and-opensuse ARM] and [http://lizards.opensuse.org/2010/08/22/obs-2-1-status-of-powerpc-and-mips-support-with-qemu MIPS] Support, [http://lizards.opensuse.org/2010/08/15/obs-2-1-features-and-status ACL], [http://en.opensuse.org//openSUSE:Build_Service_Testing testing] and many other parts), CTO Datasoft
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/mikael Mikael Söderberg / mksoderberg] - Chair of the GENIVI Alliance Reference System Work Group
* [http://meego.com/users/krypton Mithlesh Thukral / krypton] - Software developer, Linux kernel contributor, India
* [http://meego.com/users/mitsutaka Mitsutaka Amano / mitsutaka] - Moblin community member from Moblin 1.x, [http://git.moblin.org/cgit.cgi/moblin-image-creator Moblin Image Creator] maintainer, MeeGo/Moblin contributor, l10n(Japanese), Japanese evangelist, MIRACLE LINUX CORPORATION.
* [http://meego.com/users/niqt Nicola De FIlippo / niqt] - Qt4 Maemo Contributor, Maemo community member, software engineer
* [http://meego.com/users/xfade Niels Breet/X-Fade] - maemo.org webmaster
* [http://meego.com/users/noel Noel Arnold] - Technical Writer, reviews MeeGo web content and creates help files for MeeGo devices
* [http://meego.com/users/omaciel Og Maciel / OgMaciel] - GNOME Foundation member ([http://www.gnome.org/ GNOME])
* [http://meego.com/users/romaxa Oleg Romashin / romaxa] - Browser Developer, Mozilla Contributor, Nokia MeeGo
* [http://meego.com/users/mandrake Pasi Heinonen / ode2] - Qt4/GTK+ developer, .NET guy, daddy (read RTL)
* [http://meego.com/users/texrat Randall Arnold/Texrat] - two-term Maemo Community Council member, former Nokia employee (N800 launch team)
* [http://meego.com/users/rhertzog Raphaël Hertzog / buxy ] - Debian developer, [http://www.freexian.com self-employed] as free software consultant/developer.
* [http://meego.com/users/reggie Reggie Suplido] - maemo.org talkmaster
* [http://meego.com/users/ehamloptiran Robbie Newman / Ehamloptiran] - Maemo community member, software developer
* [http://meego.com/users/w00t Robin Burchell / w00t] - Developer of random things, gadget enthusiast, Maemo community member
* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate
* [http://meego.com/users/generalantilles Ryan Abel / GeneralAntilles] - Long term Maemo community member
* [http://meego.com/users/slauwers Sebastian Lauwers / crashanddie] - Maemo community member, talk.maemo.org moderator / ActivIdentity Professional Services Technical Consultant
* [http://meego.com/users/clax Sergey Vetrogonov / clax] - Qt developer, graphic designer, Russian and Ukrainian localization team coordinator ([http://www.transifex.net/ Transifex])
* [http://meego.com/users/sivan Sivan Greenberg / sivang] - Veteran linux developr and python literate, QA specialist and integration engineer.
* [http://meego.com/users/sjgadsby Stephen Gadsby / sjgadsby] - Maemo community member
* [http://meego.com/users/nagineni Sudarsana Nagineni / Babu] - Browser Developer, Nokia MeeGo
* [http://meego.com/users/tatlahte Tatu Lahtela / adeus] - Maemo community member, software developer
* [http://meego.com/users/tekojo Tero Kojo/tekojo] - Nokia's Maemo Technical Project Manager
* [http://meego.com/users/timeless timeless / timeless] - Mozilla contributor, Nokia employee
* [http://meego.com/users/timsamoff Tim Samoff / timsamoff] - Designer (graphic, UI, interaction, web), long-time Maemo Community member (two-term Maemo Community Council Member), and forever open source advocate
* [http://meego.com/users/framstag Tim Teulings / framstag] - Maemo community member, software developer
* [http://meego.com/users/timoph Timo Härkönen / timoph] - Maemo community member, software developer
* [http://meego.com/users/tjyrinki Timo Jyrinki / Mirv] ([http://nomovok.com/ Nomovok Ltd]) - [http://qa.debian.org/developer.php?login=timo@debian.org Debian developer], Ubuntu member, Openmoko contributor; all-around community and translations person + job related to MeeGo
* [http://meego.com/users/vdvsx Valério Valério/VDVsx] - Maemo Community member, software developer, Nokia employee
* [http://meego.com/users/vatula Veli-Pekka Vatula/vatula] - Nokia's Head of Maemo SW Testing
* [http://meego.com/users/vilvo Ville Ilvonen/vilvo] - Nokia's Maemo Test Tools and Test Automation
* [http://meego.com/users/wjbaird Warren Baird / wjbaird / photogeekmtl] - Developer, Product Manager, N900 user, Photographer, Digital Artist
* [http://meego.com/users/copyleft Youchen Lee / copyleft] - Debian/Ubuntu community member, software developer, deb packager.
* [http://meego.com/users/corsac Yves-Alexis Perez / Corsac] - Debian developer, Maemo community member, security engineer
* [http://meego.com/users/zaheerm Zaheer Abbas Merali / zaheerm] - GStreamer developer, Maemo community member and app developer

[[Category:Community]]

Release Infrastructure/Packaging

2010-07-23T13:38:30Z

Tjyrinki: mention dch -r

The infrastructure team has to package various scripts and applications for our target distributions: openSuse and Debian.

== Dependencies ==
When 'standard' modules and libraries are used they should be packaged for deployment

=== Ruby ===

==== openSuse ====
Should be done in an openSuse VM.

Tools:
zypper in rubygem-gem2rpm rake ruby-bundler meld dbus-1-x11

Create an OBS project targeting devel:languages:ruby:extensions eg:
<project name="home:lbt:ruby">
<title>ruby</title>
<description>Packages intended for d:l:r:e
</description>
<person role="maintainer" userid="lbt"/>
<person role="bugowner" userid="lbt"/>
<repository name="devel_languages_ruby_extensions_devel_languages_ruby_openSUSE_11.2">
<path project="devel:languages:ruby:extensions" repository="devel_languages_ruby_openSUSE_11.2"/>
<arch>x86_64</arch>
<arch>i586</arch>
</repository>
<repository name="devel_languages_ruby_extensions_devel_languages_ruby_openSUSE_11.3">
<path project="devel:languages:ruby:extensions" repository="devel_languages_ruby_openSUSE_11.3"/>
<arch>x86_64</arch>
<arch>i586</arch>
</repository>
</project>

Use [http://gitorious.org/~lbt/opensuse/lbts-opensuse-misc-scripts/blobs/master/gem-update this script] to fetch and prepare a gem package

Note that some validation is done and changes to the gems may be needed.

The gem can be manipulated by using:
gem unpack TheGem.gem
# edit data and change version
gem build TheGem.gemspec

=== Python ===

==== Generic ====

Well written setup.py for setup-tools (python-setuptools in debian) :

#!/usr/bin/python2
from distutils.core import setup
import os, sys
setup(name = 'package_name',
version = VERSION,
description = 'short description',
author = 'your name',
author_email = 'your email',
url = 'upstream url',
scripts = ['script1', 'script2'],
packages = ['package1', 'package2', 'package1.package3'],
package_dir={'mypkg': 'src/mypkg'},
package_data={'mypkg': ['data/*.dat']},
data_files=[('bitmaps', ['bm/b1.gif', 'bm/b2.gif']),
('config', ['cfg/data.cfg']),
('/etc/init.d', ['init-script'])]
)

==== RPM based distro ====

generate spec file from the setup.py file and modify to your needs :

python setup.py bdist_rpm --spec-only

==== DEB based distro ====

Easiest to use dh_auto_tools to build the deb.

debian/rules template :

#!/usr/bin/make -f
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
%:
dh $@ --buildsystem=python_distutils
#override steps if needed
#override_dh_install:
# dh_install

debian/control template:

Source: package_name
Section: devel
Priority: extra
Maintainer: Your name <your email>
Build-Depends: debhelper (>= 4.0.0), cdbs, python-dev, python-support
Standards-Version: 3.7.2
Homepage: upstream url

Package: package_name
Architecture: all
Depends: ${shlibs:Depends},
${misc:Depends},
${python:Depends}
Description: short description
long description

Debian changelog can be generated using dch --create and incremented using dch -i. To simply refresh for actual release, use dch -r.

Release Infrastructure/REVS

2010-07-22T13:30:00Z

Tjyrinki: A brief description of REVS.

= REVS =

So you want to get a ''grasp'' on what's going on when you release? Enter REVS – Release Engineering Visibility System (a software previously know as grasp).

REVS...
* is a data-warehouse, it's not a master data source. Updates may be lost.
* provides high speed access to all aspects of a release
* allows management reports on bugs, features, changes, packages

It integrates with, but isn't part of the [[BOSS]] workflow system.

Implementation consists of three areas:
* Data model
** Master python model
** Reporting model (django)
* Data uptake
** Sqlalchemy based; uses the revs object
** Per data-source feeds
* Reporting via Django

== Download Source Code ==

REVS is currently available in gitorious:

http://meego.gitorious.org/meego-infrastructure-tools/revs

git clone git@gitorious.org:meego-infrastructure-tools/revs.git

Readily installable packages (deb/rpm) may be published later on.

== Installing And Setting Up ==

Installing and setting up REVS is guided in the [http://meego.gitorious.org/meego-infrastructure-tools/revs/blobs/master/README.reporter README.reporter] file in the source code. It includes the following sections

* Setting REVS Up
** Prerequisites
** Running REVS
* Admin Interface and Trackers
** Admin interface
* Test Data
** Adding Data

== Testing ==

REVS allows usage of Django test framework to run unit tests on its components. Example is provided by running

<pre>
run_tests.sh
</pre>

in the source root directory. It reports if all tests passed.

== REVS License ==

REVS is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 2 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.

Localization team

2010-05-14T12:25:07Z

Tjyrinki: /* Contributors */ added myself

=== Announcement ===

Following the meeting on March 24, 2010 the creation of the Localization working group has not been approved by the Technical Steering Group :

* L10N will be included in the project setup drafts.

See the [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-03-24-19.58.html meeting minutes] for more details.

Current and older L10N meetings can be found [http://wiki.meego.com/L10n_meeting_schedule here].

=== How to contribute ===

To discuss and plan the localization of MeeGo, subscribe to the MeeGo l10n mailing list: http://lists.meego.com/listinfo/meego-il10n. You can also subscribe from your account page on meego.com.

=== Mission ===

The Localization working group defines the strategy for utilizing crowd-sourcing for translating MeeGo into multiple languages, and observes its implementation. Using [http://www.transifex.net/ Transifex] as the tool, our goal is to build a community of dedicated translators, editors, reviewers, and testers in multiple languages.

Related pages:
* [[L10n_plan]]
* [[L10N/RoadmapProposal]]
* [[LocalizationProcess]]
* [[How to run a translation team]]

=== Areas ===

The main areas within the scope of the working group are (in no particular order):

* Maemo/Moblin transition: bringing the best of localization policies, procedures, and best-known methods from maemo.org and moblin.org to meego.com
* Transifex administration: deciding where to host the tool, determining a team of admins and other users with special permissions, server administration
* Crowd-sourcing infrastructure: selection and administration of online tools for l10n community collaboration
* Localization teams: [[Language specific working groups]].
* How to run translation teams [[http://wiki.meego.com/How_to_run_a_translation_team]]

=== Contributors ===

MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:

* [http://meego.com/users/margie Margie Foster] - I am currently the l10n project manager for Moblin, and will be transitioning my focus to MeeGo. Submitter of this proposal and happy to take an active role. Full disclosure: I am an [http://intel.com Intel] employee.
* [http://meego.com/users/glezos Dimitris Glezos] - I am the creator and lead developer for [http://www.transifex.net/ Transifex], the L10n tool powering the translations of [http://translate.moblin.org/ Moblin] and [http://www.transifex.net/collections/c/maemo-extras/ Maemo Extras], and also the L10n lead of the Fedora Project. I'd be happy to take an active role in the L10n engineering of MeeGo. Full disclosure: I am an [http://indifex.com/ Indifex] employee, the company sponsoring the development of Transifex.
* [http://meego.com/users/omaciel Og Maciel] - I am deeply involved with the translation efforts of several open source groups including GNOME, Xfce, LXDE, Openbox, Moblin, and some minor contributions to KDE and Fedora. I'd be very interested to also take a more active role in the engineering and steering process of making MeeGo internationalized. Full disclosure: I am a big Transifex supporter (for many reasons) and am huge on quality control!
* [http://meego.com/users/milo Milo Casagrande] - I'm involved with different translation groups (Ubuntu, GNOME, and the Translation Project), and I'm leading the Italian Ubuntu translators group. I've made contributions also to Debian and Fedora, although I'm not really involved with them. I'd be happy to help this new L10n group.
* [http://meego.com/users/timeless timeless] - I maintain alternate translations of Maemo 4 and 5 for en_US and en_GB, which are also the basis for Mer. I've been on the periphery of l10n concerns as a member of the [http://mozilla.org Mozilla community]. Full disclosure: I am a [http://nokia.com Nokia] employee.
* [http://meego.com/users/solt Marcin Sołtysiak] - [http://www.midgard-project.org/ Midgard]/MidCOM contributor and translator, [http://qaiku.com Qaiku] translator, [http://maemo.org/downloads/product/OS2008/os2008pl/ OS2008] (Chinook/Diablo) translator. Just a fan.
* [http://meego.com/users/amfidiusz Adrian Marcinkowski] - [http://invisionpower.com/ IP.Board] active developer & translator, [http://instantbird.com/ Instanbird] translator & beta tester. I'm familiar with working on Mercurial and SVN repositories as well as on po/pot files - and more than eager to help with l10n of MeeGo!
* [http://meego.com/users/Saviq Michał Sawicz] - In terms of translation, I've been involved in several L10n projects, Moblin being one of them. I have also revised approach to L10n and L10n-related coding guidelines for the Elisa / Moovida project. I can help in both the core Localization Group and the Polish Localization Team.
* [http://meego.com/users/tjyrinki Timo Jyrinki] - L10n and I18N related work all-around. Ubuntu Finnish translators leader, GNOME translator, GNU translation project translator, Debian Developer et cetera. Managed to also get involved with Moblin translations and related discussions before it became MeeGo.

[[Category:Localization]]

Packaging

2010-04-28T11:35:26Z

Tjyrinki: mention conversion tutorial

= Creating Packages for MeeGo =

The build infrastructure is not announced yet, so information here is speculative.

What is known:

* The package format used by MeeGo is [http://en.wikipedia.org/wiki/RPM_Package_Manager RPM]. If you are a packager and used to DEB packages, see [[Packaging/Deb conversion example| conversion example]].

* MeeGo build tools and Infrastructure will probably derive from Moblin's (see [http://moblin.org/documentation/moblin-distro-developers-guide/moblin-infrastructure] and [http://moblin.org/documentation/moblin-distro-developers-guide/build-system]) with hopefully better support for ARM targets.

* MeeGo uses [[Build_System| OpenSUSE Build Services (OBS)]].

= Upstream =

As [[Maemo]] has had an old version of Debian as an [[upstream]] distribution, there have been lots of questions on what will be MeeGo's upstream, and why Maemo's relationship with Debian will be dropped. The answer is that MeeGo is an independent distribution : the only upstream is the projects included into MeeGo such as: kernel.org, X.org, Qt, etc. MeeGo policy is to push all bug fixes to upstream projects.

Why not be [[Debian]]-based? Having an upstream distribution has advantages and disadvantages.

* Advantages: you benefit from all the packaging, QA and maintenance done in the upstream distribution, thus there is a large selection of available ported software.
* Disadvantages: you have to align your build infrastructure with your upstream. You are dependent on the release cycle and architecture choices of upstream.

The choice is to have no upstream for MeeGo. It makes it easier to tailor MeeGo for its target devices, which are quite specific compared to Debian's. Maybe the Debian rhythm of updates would also be inadequate for MeeGo (smartphone OSs are currently evolving at a very rapid pace, but there is more up-to-date Ubuntu and Debian is working on more frequent updates). The Moblin build tools would also not have been compatible with Debian as upstream (this is mostly nonsense, see [[Mer]] and [[OBS]]).

Nonetheless MeeGo will be Linux Standard Base (LSB) compliant and its specific components will probably be available in Debian at some point.

= Packaging Guidelines =

Evolving [[Packaging/Guidelines|packaging guidelines]]...

= References =
*[http://lists.meego.com/pipermail/meego-dev MeeGo-dev mailing list]
*[http://www.allmeegodevices.com/2010/02/17/meego-a-whole-new-linux-ballgame/ A nice article about why no upsteam - Meego Devices]

[[Category:Packaging]]

Talk:Packaging/Deb conversion example

2010-04-28T09:25:56Z

Tjyrinki: a few notes

== Notes ==

* Originally written in trac wiki and converted manually, tables could be neater among else
* I've a lot of experience with .deb files, but started from 0 with .rpm files, so errors may easily exist in the tutorial since I'm so new to RPMs
--[[User:Tjyrinki|Tjyrinki]] 09:25, 28 April 2010 (UTC)

== Discussion ==

Improvements and additions welcome...

Packaging/Deb conversion example

2010-04-28T09:22:30Z

Tjyrinki: deb -> rpm conversion tutorial/example, contribution on behalf of Nokia. feel free to improve, discuss or contact about it.

= .deb to .rpm Conversion Example =

This page aims to act as a helpful source for people having .deb packages and wishing to offer them as .rpm packages instead in MeeGo. It will mean manual work for every package, but this page should help in getting a first working draft done quicker.

== Package Meta Files – .deb vs .rpm ==

In a DEB package, most of the package meta information is located under the directory ''debian'', mainly in files control and rules but also a few others. Meanwhile, the .spec file of an RPM contains all the RPM meta data in a single file. Notation of these files is completely different, similarities exist in separation of build phases into logical sections and vivid use of conditional variables. Source RPM (.srpm) package has the upstream .tar.gz together with patches while "source DEB" (a bundle which is fetched by the dget tool by pointing the tool to a .dsc file) is three files: .dsc, orig.tar.gz and .debian.tar.gz. The DEB files unpacked with dpkg-source -x, or during fetching with dget -x, becomes the combination where packaging is under debian/ and possible patches usually under debian/patches.

A table below describes the highest level differences:
{|
|-
! '''Data''' !! '''deb source format''' !! '''rpm source format'''
|-
| upstream source || as is || as is
|-
| full packaged source || 3 files, of which the .dsc file is a pointer that can be used to fetch and unpack 1) original source and 2) debian packaging and patches in .debian.tar.gz || .srpm that includes 1) original source, 2) spec file and optionally 3) patches
|-
| packaging metadata || after unpacking the debian/ directory as a whole || after unpacking the .spec file and patches separately
|}

== Getting The Source ==

In this example we select a random package to convert from deb format to rpm format. The lucky winner was Transmission BitTorrent Client. Note that it is already packaged for various other rpm distributions, so it's just for the sake of an example and in practice it would be probably beneficial to glance at existing .spec files. We are taking the debian/ directory and the upstream Transmission source to look at from Debian project by looking at and running (on our Debian/Ubuntu machine):

<pre>
# Download only
dget -d http://ftp.debian.org/debian/pool/main/t/transmission/transmission_1.92-1.dsc
# Unpack upstream source
tar jxvf transmission_1.92.orig.tar.bz2
# Unpack debian/ directory separately
tar zxvf transmission_1.92-1.debian.tar.gz
</pre>

== Writing Spec File ==

Start editing transmission.spec by copy-pasting the following template into your favorite text editor:

<pre>
Name:
Version:
Release:1%{?dist}
Summary:
Group:
License:
URL:
Source0:
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildRequires:
Requires:

%description

%prep
%setup -q

%build
%configure
make %{?_smp_mflags}

%install
rm -rf %{buildroot}
make install DESTDIR=%{buildroot}

%clean
rm -rf %{buildroot}

%files
%defattr(-,root,root,-)
%doc

%changelog
</pre>

It is more common than not in the rpm world to provide single binary package instead of multiple binary packages. Even so, it is possible to create multiple binaries from one source package even with rpm:s. For the sake of this example, we will do only one binary package similar to Transmission packaging in Fedora, even though Debian has multiple binaries generated.

In another window, go to the unpackaged debian/ directory and first take a look at the ''control'' file.
{|
! '''debian/control file entry''' !! '''.spec file entry''' !! '''notes'''
|-
| Source || Name ||
|-
| 1st line of Description of the main binary package || Summary || Should begin always with capital letter in the RPM world as per rpmlint policies
|-
| Description || %description ||
|-
| Section || Group || See ''less /usr/share/doc/rpm*/GROUPS'' and find a match''
|-
| Homepage || URL ||
|-
| Build-Depends || BuildRequires || This needs manual thinking and tinkering and will often require a bit of trial and error. Try to match the Debian packages to http://repo.meego.com/MeeGo/test/trunk-test/repo/ia32/os/i586/ package names.
|-
| Depends || Requires || Only if some specifics not covered by the non-devel version of BuildRequires package. In this example, the only non-macro dependency in control file's Depends: fields is lsb-base (>= 3.0), which corresponds to meego-lsb in MeeGo.
|}

More precisely the mapping of build depends from debian/control to .spec file goes like this:
{|
|-
! '''Debian dependency''' !! '''MeeGo dependency''' !! '''Notes'''
|-
| debhelper || not needed || deb packaging related
|-
| autotools-dev || not needed || contains only config.sub and config.guess system-wide files
|-
| libgtk2.0-dev || gtk2-devel ||
|-
| libevent-dev (>= 1.4) || libevent-devel >= 1.4 ||
|-
| libglib2.0-dev || glib2-devel ||
|-
| libnotify-dev || libnotify-devel ||
|-
| libssl-dev || openssl-devel ||
|-
| libcurl4-dev / libcurl-dev || libcurl-devel ||
|-
| chrpath || chrpath ||
|-
| intltool (>= 0.40) || intltool >= 0.40 ||
|-
| qt4-qmake || qt-devel || qt-devel includes both dev files and qmake
|-
| libqt4-dev || qt-devel || qt-devel includes both dev files and qmake
|-
| libcanberra-gtk-dev || libcanberra-devel || Note: commented out in control, but we can use them in our package
|-
| libgconf2-dev || GConf-dbus-devel || Note: commented out in control, but we can use them in our package
|}

Other stuff to fill in the .spec file from debian/ files:

{|
|-
! '''.spec file entry''' !! '''Where to find'''
|-
| License || debian/copyright
|-
| Source0 || upstream or debian/copyright
|-
| Version || obvious, or debian/changelog
|}

Now we have all the basics covered. Let's see what's remaining and potentially needing importing in some form or another:
{|
|-
! '''debian/ file''' !! '''What to do'''
|-
| *.install, *.dirs, *.links || Consider to be listed in .spec file's %files section
|-
| *.postinst || %post section
|-
| *.postrm || %postun section
|-
| changelog || %changelog, but should be new for the .rpm package
|}

In the case of post-installation scripts of Transmission, they deal with setting the permissions of the transmission-daemon binary so that it will be run as a special user. We can mimick that behavior in the %post section (and %postun section) of the spec file. A rough take on it is included in the example final spec file, but take into account that there may be or maybe will be policies defining a better way of doing eg. permission handling.

=== Files Section ===

This section is used to include all the wanted files to the resulting rpm binary package. When filling in the %files section of the .spec file, it is rather easy to miss files that are installed during the building. One tip is to check the build log for "error: Installed (but unpackaged) file(s) found" or "RPM build errors: Installed (but unpackaged) file(s) found" and utilize that information to select more files to the package.

%{_bindir}, %{_datadir}, %{_mandir} etc. variables should be used in the section to use standard directory names.

Localization files are handled specially. An rpm macro called %find_lang will find all the locale files that belong to the package, and put the list in a file, usually %{name}.lang. That file can be then used to include all of the locales. The "name" parameter given to %find_lang equals to package name, but if the translation domain differs from the package name, it should be specified instead. The generated list can be used with the -f parameter to %files when starting the %files section.

=== Final .spec File ===

This is the result of following the example through.

<pre>
Name: transmission
Version: 1.92
Release: 1%{?dist}
Summary: Lightweight BitTorrent client
Group: Applications/Internet
License: MIT
URL: http://www.transmissionbt.com/
Source0: http://download.m0k.org/transmission/files/transmission-1.92.tar.bz2
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

BuildRequires: gtk2-devel,libevent-devel >= 1.4,glib2-devel,libnotify-devel,openssl-devel,libcurl-devel,chrpath,intltool >= 0.40,qt-devel,libcanberra-devel,GConf-dbus-devel
Requires: meego-lsb >= 3.0

%description
Transmission is a simple BitTorrent client. It features a very simple,
intuitive interface (gui and command-line) on top on an efficient,
cross-platform back-end.

%prep
%setup -q

%build
%configure
make %{?_smp_mflags}

%install
rm -rf %{buildroot}
make install DESTDIR=%{buildroot}
%find_lang %{name}

%post
addgroup --system --quiet meego-transmission
adduser --system --group --no-create-home --quiet meego-transmission
chown meego-transmission:meego-transmission /var/lib/transmission-daemon/info
chown meego-transmission:meego-transmission /var/lib/transmission-daemon/downloads
chown meego-transmission:meego-transmission /etc/transmission-daemon/settings.json

%postun
if [ -d /var/lib/transmission-daemon/info ]; then
rm -rf /var/lib/transmission-daemon/info/*
fi

%clean
rm -rf %{buildroot}

%files -f %{name}.lang
%defattr(-,root,root,-)
%doc AUTHORS COPYING NEWS README
%{_bindir}/transmission*
%{_datadir}/applications/transmission.desktop
%{_datadir}/icons/hicolor/*/apps/transmission.png
%{_datadir}/icons/hicolor/scalable/apps/transmission.svg
%{_datadir}/pixmaps/*
%{_datadir}/transmission
%doc %{_mandir}/man1/transmission*

%changelog
* Mon Apr 26 2010 Timo Jyrinki <timo.jyrinki@nomovok.com> - 1.92
- http://trac.transmissionbt.com/wiki/Changes#version-1.92
</pre>

After build, rpmlint will give a couple of warnings, but no errors. The warnings currently relate to localizations for languages not yet supported in MeeGo, and two duplicate png image files that could be fixed by symlinking.

Language specific working groups

2010-03-08T12:14:48Z

Tjyrinki: add Finnish and myself as the team lead candidate

= Language Specific Working Groups =

If your language is not mentioned here, add a section for it, copy a table and list your name as shown.

----

== Arabic ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|GTalk/skype
|Bio/Website
|-
|Mehdi CHERFI
|cherfim/boulleh
|
|}

== Brazil::Brazilian Portuguese ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Og Maciel (Lead candidate volunteer)
|OgMaciel
|[[http://www.ogmaciel.com/?page_id=428]]
|-
|Frederico Schardong
|
|
|-
|Sergio Correia
|sergio
|
|-
|Duda Nogueira
|dudanogueira
|[[http://www.dudanogueira.com.br]]
|-
|}

== Catalan ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Josep Sanchez
|papapep
|[[https://wiki.ubuntu.com/JosepS%C3%A0nchez/English]]
|}

== Czech Republic::Czech ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|Jabber
|Bio
|-
|Petr Novak
|peta@jabber.org
|
|}

== Denmark::Danish ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Kris Thomsen
|Kristho
|
|}

== Finland::Finnish ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|Jabber
|Bio
|-
|Timo Jyrinki (Team Lead candidate)
|timo.jyrinki@jabber.org
|[http://www.linkedin.com/in/timoj], [https://launchpad.net/~ubuntu-l10n-fi], [http://www.gnome.fi/] etc.
|}

== France::French ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Farid Ziani
|
|
|}

== Galician ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|GTalk
|Bio
|-
|Felipe Gil-Castiñeira
|felipexil
|[[http://es.linkedin.com/pub/felipe-gil-castiñeira/1/b73/604]]
|-
|Miguel Anxo Bouzada
|mbouzada
|
|-
|Amador Loureiro Blanco
|dorfun
|[[http://www.adorfunteca.org]]
|}

== Germany::German ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Maximilian Gerhard (Team Lead candidate volunteer)
|TheOne
|-
|Claudius Henrichs
|Claudius
|http://www.linkedin.com/in/chenrichs
|}

== Hindi ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|GTalk
|Bio
|-
|Kiran Vaka
|kiran.vaka
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=kiran+vaka]]
|}

== Indonesian ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|GTalk/IRC Nick
|Bio
|-
|Andika Triwidada (volunteer to lead ID team)
|andika/andika
|[[http://id.linkedin.com/in/atriwidada]]
|}

== Israel::Hebrew ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Sivan Greenberg
|sivang
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=sivan+greenberg]]
|-
|Eliad Kimhy
|Eliad
|[[http://digdigdigi.blogspot.com/]]
|}

== Kannada ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|GTalk
|Bio
|-
|Prajwal Mohan
|prajwal.mohan
|
|}

== Marathi ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|GTalk
|Bio
|-
|Amit Bapat
|amitbapat
|[[http://www.linkedin.com/in/amitbapat]]
|}

== The Netherlands::Dutch ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Auke Kok
|auke
|(Intel MeeGo developer)
|-
|Bart
|DenBatte
|Just a user
|-
|Arnon Hoogerwerf
|gL|Homer
|Moblin User/game&web (Linux) serverhost.
|}

== Poland::Polish ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Michał Sawicz
|Saviq
|[[http://www.google.com/search?q=saviq+michał+sawicz]]
|-
|Marcin Sołtysiak (will humbly lead the effort)
|solt
|
|}

== European Portuguese ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC
|Bio
|-
|Alexandra Engström Santos (Team Lead candidate volunteer)
|aesantos
|[[http://fi.linkedin.com/in/alexandraengstromsantos]]
|}

== Punjabi ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|A S Alam
|aalam
|[[http://meego.com/users/aalam]]
|}

== Russian ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|Jabber
|Bio
|-
|Serg Vergun
|shad0w@jabber.spbu.ru
|Volunteer
|}

== Chinese (Taiwan) ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Cheng-Chia Tseng (Team Lead candidate volunteer)
|zerng07
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=cheng-chia+tseng]]
|}

== Simplified Chinese ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Ryan Lee
|
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=ryan+lee]]
|}

== Slovenian ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|Jure Repinc
|JLP
|[[http://www.google.com/search?ie=UTF-8&q=jure+repinc]]
|}

== Spanish ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|IRC Nick
|Bio
|-
|David Castañeda
|davidecr
|
|}

== Telugu ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|Skype
|Bio
|-
|Kiran Vaka
|kiran.waka
|[[http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=kiran+vaka]]
|}

== Walloon ==

{| style="color:green; background-color:#ffffcc;" cellpadding="20" cellspacing="0" border="1"
|Name
|Jabber
|Bio/Website
|-
|Djan Cayron (team coordinator candidate)
|jean "dot" cayron "at" gmail "dot" com
|[[http://wa.wikipedia.org/wiki/Jean_Cayron]] [[http://walotux.walon.org/]]
|}

User:Tjyrinki

2010-03-02T12:21:53Z

Tjyrinki: Created page with '== Timo Jyrinki == Email:: timo.jyrinki at iki dot fi Homepage:: http://iki.fi/tjyrinki/ Interests:: * http://www.debian.fi/ * http://www.ubuntu-fi.org/ * http://ww…'

== Timo Jyrinki ==

Email:: timo.jyrinki at iki dot fi
Homepage:: http://iki.fi/tjyrinki/

Interests::
* http://www.debian.fi/
* http://www.ubuntu-fi.org/
* http://www.vapaasuomi.fi/

Who's who

2010-03-02T08:28:45Z

Tjyrinki: /* MeeGo community */ added myself

== Technical Steering Group ==
''Members of the [http://meego.com/about/governance TSG]''

* [http://meego.com/users/valhalla Valtteri Halla] - Benevolent dictator
* [http://meego.com/users/imad Imad Sousou/imad] - Benevolent dictator

== Maemo community stakeholders ==
''Official representatives of the Maemo community''

==== Nokia ====

* [http://meego.com/users/qgil Quim Gil/qgil] - Nokia's Open Source Advocate
* [http://meego.com/users/tekojo Tero Kojo/tekojo] - Nokia's Maemo Technical Project Manager
* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

==== maemo.org ====

* [http://meego.com/users/bergie Henri Bergius/bergie] - maemo.org web/Midgard developer
* [http://meego.com/users/xfade Niels Breet/X-Fade] - maemo.org webmaster
* [http://meego.com/users/jeremiah Jeremiah Foster/jeremiah] - maemo.org debmaster
* [http://meego.com/users/andre André Klapper/andre__] - maemo.org bugmaster
* Karsten Bräckelmann/karstenb - maemo.org bugmaster
* [http://meego.com/users/stskeeps Carsten Munk/Stskeeps] - maemo.org distmaster & Mer project lead
* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/reggie Reggie Suplido] - maemo.org talkmaster
* [http://meego.com/users/indeyets Alexey Zakhlestin/JimiDini] - maemo.org web/Midgard developer

==== Maemo Community Council ====

* [http://meego.com/users/texrat Randall Arnold/Texrat] - Maemo Community Council member
* [http://meego.com/users/qole Alan Bruce/qole] - Maemo Community Council member
* [http://meego.com/users/gcobb Graham Cobb/gcobb] - Maemo Commnunity Council member
* [http://meego.com/users/penguinbait Matthew Lewis/penguinbait] - Maemo Community Council member
* [http://meego.com/users/vdvsx Valério Valério/VDVsx] - Maemo Community Council chair

== Moblin community stakeholders ==
''Representatives of the Moblin community''

* [http://meego.com/users/dirkhh Dirk Hohndel/dirkhh] - Chief Linux and open source technologist at Intel
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Intel's community manager for MeeGo
* [http://meego.com/users/margie Margie Foster/mlfoster] - Localization project manager for Moblin & meego.com website developer
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - Moblin.org & meego.com website techy

== Linux Foundation stakeholders ==
'' Staff Members of Linux Foundation''

* [http://meego.com/users/martinmohring Martin Mohring/ScriptRipper ] - Build Platform Developer, long-term Novell OBS contributor, Linux Foundation Staff Member
* [http://meego.com/users/dl9pf Jan-Simon Möller/dl9pf ] - Build Platform Developer, long-term Novell OBS contributor, Linux Foundation Staff Member

== MeeGo developers ==
'' People paid to contribute to MeeGo and/or have commit rights''

* [http://meego.com/users/hbons Hylke Bons/hbons] - User Experience Designer
* [http://meego.com/users/auke Auke Kok/auke] - Release developer, fast boot
* [http://meego.com/users/jku Jussi Kukkonen/jku] - Developer
* [http://meego.com/users/nmcgovern Neil McGovern/nmcgovern] - Developer
* [http://meego.com/users/nashif Anas Nashif/anaZ] - Distribution developer
* [http://meego.com/users/pohly Patrick Ohly/pohly] - Developer
* [http://meego.com/users/quang Quang Pham/quang] - Developer
* [http://meego.com/users/zhuyanhai Zhu Yanhai/yanhai] - Developer

== MeeGo community ==
''Anyone not in the above sections'' ('''Please keep this list alphabetically-ordered, as it will make finding people easier''')

* [http://meego.com/users/camahueto Alberto O. / camahueto] - Lawyer working in an unidentified Intellectual Property office. Free Software aficionado.
* [http://meego.com/users/ab Alexander Bokovoy / ab] - Senior Architect, Media applications, Nokia, Samba Team member
* [http://meego.com/users/aboaboit Andrea Borgia / aboaboit] - Maemo community member
* [http://meego.com/users/andrewfblack Andrew F Black / AndrewFBlack] - Maemo community member / Theme Designer / talk.maemo.org Moderator and Theme Designer.
* [http://meego.com/users/jaffa Andrew Flegg / Jaffa] - Long term gadget freak & Maemo community member
* [http://meego.com/users/earthling Bernd Stramm / earthling] - Independent developer.
* [http://meego.com/users/bman Brian McKenzie / b-man] - Long term Maemo community member, software porter/developer, beta tester
* [http://meego.com/users/bundyo Bundyo / Bundyo] - Maemo community member, contributor
* [http://meego.com/users/clintcan Clint Christopher Cañada / clintcan] - Moblin oriented netbook user, open source enthusiast and packages rpms for moblin/centos/rhel for personal use in spare time.
* [http://meego.com/users/leinir Dan Leinir Turthra Jensen / leinir] N810 owner, MeeGo community member (via Mer)
* [http://meego.com/users/daperl Da Perl / daperl] - Maemo community member, software developer
* [http://meego.com/users/lbt David Greaves / lbt] - Mer OBS build guy
* [http://meego.com/users/glezos Dimitris Glezos / glezos] - Localization Engineer ([http://www.transifex.net/ Transifex])
* [http://meego.com/users/spaghetty Domenico Chierico / spaghetty] - Maemo community member
* [http://meego.com/users/epage Ed Page / epage] - Maemo community member, software developer
* [http://borasky-research.net M. Edward (Ed) Borasky] - Linux capacity planning / audio / openSUSE / Twitter geek
* [http://meego.com/users/debernardis Ernesto de Bernardis / debernardis] - Maemo community member, mobile device tinkerer
* [http://meego.com/users/fabo Fathi Boudra / fabo] - Debian developer, Maemo community member, software engineer
* [http://meego.com/users/fgs Floriano Scioscia / fgs] - Maemo community member, IT engineer and junior researcher
* [http://meego.com/users/frederico Frederico Schardong / frederico] - Maemo community member, open source developer
* [http://meego.com/users/fpp Fred Pacquier / fpp] - maemo.org old-timer, platform-neutrality advocate, Python evangelist, and big mouth.
* [http://meego.com/users/amby Gabor Ambrozy / Amby] - Maemo community member, Save the End-Users advocate
* [http://meego.com/users/slaine Glen Gray / slaine] - Moblin community member, software engineer
* [http://meego.com/users/ianbrasil Ian Lawrence / ianbrasil] - Author - Professional Ubuntu Mobile Development, Moblin and Maemo community member
* [http://meego.com/users/zerojay Jason Carter / zerojay] - Long term Maemo community member
* [http://meego.com/users/javispedro Javier S. Pedro / javispedro] - Maemo community member
* [http://meego.com/users/jebba Jeff Moe / jebba] - [http://wiki.maemo.org/User:Jebba Maemo Contributor]
* [http://meego.com/users/jak Julian Andres Klode / jak] - Debian developer, Ubuntu member
* [http://meego.com/users/lpotter Lorn Potter / lpotter / ljp] - QDF, Mobility, Nokia
* [http://meego.com/users/hrw Marcin Juszkiewicz / hrw ] - OpenEmbedded developer, [http://marcin.juszkiewicz.com.pl/ self-employed] as OpenEmbedded/Poky Linux consultant/developer.
* [http://meego.com/users/detective Max Maher / detective] - Maemo community member, software porter/developer, QA Engineer
* [http://meego.com/users/mooninite Michael Cronenworth / mooninite] - Linux junkie/programmer (GTK+, PostgreSQL, MinGW, and more...)
* [http://meego.com/users/niqt Nicola De FIlippo / niqt] - Qt4 Maemo Contributor, Maemo community member, software engineer
* [http://meego.com/users/omaciel Og Maciel / OgMaciel] - GNOME Foundation member ([http://www.gnome.org/ GNOME])
* [http://meego.com/users/mandrake Pasi Heinonen / ode2] - Qt4/GTK+ developer, .NET guy, daddy (read RTL)
* [http://meego.com/users/rhertzog Raphaël Hertzog / buxy ] - Debian developer, [http://www.freexian.com self-employed] as free software consultant/developer.
* [http://meego.com/users/w00t Robin Burchell / w00t] - Developer of random things, gadget enthusiast, Maemo community member
* [http://meego.com/users/generalantilles Ryan Abel / GeneralAntilles] - Long term Maemo community member
* [http://meego.com/users/slauwers Sebastian Lauwers / crashanddie] - Maemo community member, talk.maemo.org moderator / ActivIdentity Professional Services Technical Consultant
* [http://meego.com/users/sivan Sivan Greenberg / sivang] - Veteran linux developr and python literate, QA specialist and integration engineer.
* [http://meego.com/users/sjgadsby Stephen Gadsby / sjgadsby] - Maemo community member
* [http://meego.com/users/timeless timeless / timeless] - Mozilla contributor, Nokia employee
* [http://meego.com/users/timsamoff Tim Samoff / timsamoff] - Designer (graphic, UI, interaction, web), long-time Maemo Community member (two-term Maemo Community Council Member), and forever open source advocate
* [http://meego.com/users/framstag Tim Teulings / framstag] - Maemo community member, software developer
* [http://meego.com/users/tjyrinki Timo Jyrinki / Mirv] - Debian developer, Ubuntu member, Openmoko contributor; all-around community and translations person + some MeeGo related work stuff
* [http://meego.com/users/corsac Yves-Alexis Perez / Corsac] - Debian developer, Maemo community member, security engineer
__NOTOC__ 

[[Category:Community]]

Build Infrastructure

2010-02-18T11:39:06Z

Tjyrinki: /* Better User Management and LDAP support */ link to the implementation as well

= MeeGo Build Infrastructure =

== Overview ==
MeeGo uses the [http://build.opensuse.org/ openSUSE Build System (OBS)] which provides a complete distribution development platform providing the infrastructure required for development of MeeGo releases. Moblin started using OBS in June 2008 and released Moblin 2.0 and Moblin 2.1 and many other derivative releases out of OBS which has proven to be a very reliable infrastructure that is fast evolving and rich with features supporting every single aspect of the process required for distribution building and maintenance.

MeeGo is using OBS 1.7 which is the latest version released early Feb. 2010.

The [http://en.opensuse.org/Build_Service/Roadmap roadmap for OBS] can be found here.

Some of the the interesting things on the roadmap:
* Project source linking
* User group handling as stable feature
* Complete patchinfo support may be a candidate
* Build Dependency Cycles are visible via the api
* Integrated QA support to run all kinds of additiional testsuites.

More details soon....

== Missing Features ==

With all the great features OBS provides, many features that we wish to have now are either on the long term roadmap or specific to our needs or not seen as high priority. Some of the things we wish to see implemented in OBS are:

* Proxy Support with inter-obs communication (http, https)
* ACL Support and support for hidden projects/packages and their resulting binaries and build information
* Better user/group/role management interface. Probably an overhaul of current user management system (active rbac)
* LDAP backend support for user/group management
* Linking of projects with smaller set of packages (for updates)
* Better build job allocation and improvement of the dispatcher

Some details about the wish list above:

=== Proxy Support ===
OBS offers a very nice feature allowing different instances to be linked. This works very nicely if you are not behind a firewall. When proxy is needed, various workarounds are necessary to create a usable link. While experimenting with adding proxy support we found out it is more complicated than just changing the code and make it point to a proxy. It seems that OBS requires certain headers and features that are not supported by proxies such as Squid.

=== ACL ===
A proposal exists to add ACL support at http://en.opensuse.org/Build_Service/Concepts/AccessControl.

=== Better User Management and LDAP support ===
Since Novell started using iChain the user management back-end is not maintained or improved. At the moment it is not even possible to change passwords and the interface for managing users is lacking. OBS has two authentication methids:
* iChain
* Built in user management (active rbac)

Session management and authentication/authorization code is spread all over the place in the API and needs to be cleaned up before it can be actually replaced with something decent that would also support LDAP and other authentication back-ends. Also we need to figure a way to realize the webui <-> api interface, since all authentication goes over the API and is implemented there (in the API).

Looking for a replacement for current user management system, [http://rdoc.info/projects/binarylogic/authlogic AuthLogic] seems to have all the ingredients we need to implement this and add LDAP support at the same time. iChain probably can be implemented as an AuthLogic add-on to make integration easier and to get this accepted upstream.

To summarize, we need an authentication system that can at least support the following 3 scenarios:
* LDAP - ''[http://gitorious.org/opensuse/build-service/commit/e523b55785b0714fa658868fee629056b64c1bf7 Implemented on 17 Feb 2010] and being backported to 1.7''
* Database (needed by all, but also with the passwords)
* iChain (that needs to be done with some coordination with the OBS team, since the internals are probably not publicly available).

In addition to that, the above needs to support "Role Based Access Control" (RBAC) which is currently available in obs and being used with active_rbac and would also integrate with the ACL proposal above.

=== Improving Job Allocation ===
Looking at the dispatcher code in OBS, the dispatcher uses a very basic shuffling algorithm to distribute jobs among workers in the build system. This might be a good approach for specific OBS configurations (maybe the opensuse.org setup), but observing dispatcher behavior over time shows that it can be improved, especially for small instances.
It is often annoying to see the kernel being dispatched from different project into the same host while all other workers are being idle. There are a few packages in MeeGo that needs lots of time to build (kernel, Qt, WebKit, Browsers..) and stacking them into one build host often takes very long time. The dispatcher does not take into account the current load status of the hosts or what is being built on those hosts. Typically every build host has 8 workers depending on the memory and cores available.

A few ideas on how this can be improved:
* Use a different job distribution algorithm based on load status and other information collected from previous builds
* Maintain an up to date repository about the status of hosts using agents that report about current load and other metrics and make this data available to the dispatcher. For example, it would help to know current utilization of the hosts and the busy status of the workers before dispatching a new job to the same host. We need to check if there are other hosts with less utilization.
*If a host has 8 worker instances and 4 are busy and there is another host with only 2/8 busy, then the dispatcher should prefer the latter.
*Avoid building the same package (from different projects) on the same host. Always try to find another hosts with less utilization first that is not building the same package.
*Since most of the build time for the majority of the packages is spent on creating the build environment, it would help if we can collect data about where the actual time is being spent
**Creation of Build Environment
**Compilation
**Testing
**Creating the package binaries..

An easier approach would be to use a round-robin mechanism assisted by information about load of hosts to skip busy hosts and try to find a less loaded host. All of the above requires a very robust metrics collection system with agents running on all hosts that deliver timely information about load, memory and other system data that might be useful to make a decision where to dispatch the next build job.