MeeGo wiki - User contributions [en]

MeeGo Apps/Packaging

2012-01-05T16:23:44Z

Xfade: /* Harmattan categories */

== Packaging ==

[http://apps.formeego.org Apps for MeeGo] will import all information from your package in [[OBS]]. OBS is master for the data at all times. New to OBS? Please read [[Getting_started_with_OBS]].

For proper looking application entries in Apps, make sure you add the following items:

=== Screenshots ===

You can add multiple screenshots to your OBS package. Click on 'Source files' and then 'Add File' to upload
files through the webui. If you are using the osc tool to submit to OBS, then you can just 'osc add' the files and commit them in one go.

Make sure the filename ends with screenshot.png.

Example:
<pre>testapp1_screenshot.png
intro_screenshot.png
whatever_screenshot.png</pre>

There is a good screenshot tool available in 'Store' named 'ScreenCapture'.

=== Icon ===

Add a PNG file to your OBS project with filename icon.png. Make sure the resolution of the file is at least 80x80.

=== Description ===

Make sure your project description has some meaningful info, as this description will be seen by end users. This is the way to market your application, so spend some time describing your app as detailed as possible.

You can do this on the package page in OBS. Listed under the heading 'Actions', click on 'Edit Package Information'.

=== Harmattan categories ===
In your debian/control file set Section: user/<category>, where <category> must be picked from:

<pre>internet
office
graphics
games
multimedia
education
science
system
development
accessibility
network
location
utilities
</pre>

Example:
<pre>Section: user/games</pre>

Note that user/other is a very weak category choice, please make sure you pick one of the above. It seems that Qt Creator defaults to user/other, so make sure to change this!

MeeGo Apps/Submit

2012-01-04T15:46:24Z

Xfade: /* What happens next */

==Promotion to Apps==

''At the moment we're testing promotion for Harmattan target only. Other targets will follow soon.''

[http://apps.formeego.com Apps for MeeGo] imports all it's information from [https://build.pub.meego.com OBS]. You will need to make sure your app is packaged and building inside OBS. If you have never worked with OBS before, please read our [[Getting_started_with_OBS]] introduction.

Please make sure you have added proper description, screenshots and icons to your package. If you you didn't add this information to your project yet, please look at the [[MeeGo_Apps/Packaging]] guidelines. Your package '''will be rejected''' if you don't add this information. You will receive an email describing the problem.

At this time it is only possible to submit a package which has no external dependencies, other than what is provided in the SDK. If you need other libraries for instance, then you should link them in statically. We're looking into adding shared dependencies, but that still needs discussion. '''Do not try to submit libraries etc, apps in Apps will not be able to use them.'''

To promote your app to Apps, you need to go through the [[MeeGo_Apps/Community_QA]] process. This means your package will go in to a testing queue, where community members can fill in a form to rate your app on certain QA requirements.

===Submit Request===
To initiate this process, your need to do a SR (Submit Request) from the package page in your home project in the [https://build.pub.meego.com MeeGo Community OBS].

Example:<pre>https://build.pub.meego.com/package/show?package=attitude&project=home%3Ajaffa</pre>

Click on 'Submit Package', you can find that under 'Actions'.

You will now see a popup form. Enter the following in the 'To target project' field:
<pre>MeeGo:1.2:Harmattan:Apps:Testing</pre>

You can leave the description field empty.
''Notice'': 'Remove local package if request is accepted' should '''*NOT*''' be selected! (Otherwise your package will be removed from your home once it is accepted into Testing)

Now click the Submit button. You will receive an email at certain stages of the process to keep you informed about the progress of your package.

===What happens next===

The package will now be tested using some automated scripts.

Checks in place are:
<ul>
<li>Are you maintainer for this package (This will be done if the package is already in Apps, rejection will happen if you are not marked as 'downloader' for the package in OBS.)</li>
<li>Does your package have at least one screenshot and an icon.</li>
<li>Trial build. The package will be built in a clean repository against the SDK only. If building fails, the package will be rejected.</li>
</ul>
Once these tests succeed, the package will be moved into MeeGo:1.2:Harmattan:Apps:Testing. The data for this package will be imported into the apps.formeego.com website database after the build succeeds. In the category listing, you will see a link to '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications waiting to be tested]'.

''Notice'': Make sure you are logged in.

Here you will see a list of applications that are in Testing. When you go to the application details page, you will see a button on the left side called 'Community QA'.

More information about testing can be found on the [[MeeGo_Apps/Community_QA#Testing]] page.

MeeGo Apps/Community QA

2012-01-04T12:34:10Z

Xfade: /* Harmattan */

== Community QA ==

If you would like to help test new applications to make sure they are ready for a larger audience, then welcome!

'''Notice''': Applications in Testing are not guaranteed to work and might make your device unstable. Only use this repository if you know what you are doing.

=== Preparations ===
You need to install the following:

==== Harmattan ====
On the application grid in your device, click on the 'Settings' icon. Click on 'Applications', 'Installations' and make sure the slider is set to on for 'Allow installations from non-Store sources.

Now use the browser to download:
* [http://apps.formeego.org/n9client Apps client for Harmattan]

In the 'Transfers' window, click on org.formeego.apps*.deb, this will install the client. This will also enable the MeeGo:1.2:Harmattan:Apps repository on your device.

You can download the '''Apps Testing enabler''' from within the Apps client, alternatively you can download:

* [http://apps.formeego.org/n9testing Testing repository enabler]

In the 'Transfers' window, click on apps-testing-enabler-harmattan*.deb. This will enable the MeeGo:1.2:Apps:Testing repository on your device.

When you start 'Apps', it will check if the Testing repository is enabled. If it is, then apps in the Testing repositories are shown.

If you want to disable the Testing repository, just uninstall the apps-testing-enabler-harmattan package.

=== Testing ===

On the [http://apps.formeego.org Apps for MeeGo] website there is a special '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications Waiting for Review]'section.

'''Notice''': Make sure you are logged in to the site. You can use your meego.com username and password.

'Applications waiting for review' lists all the applications per category. You can find these applications in the Apps client on your device too.

When you go to the application details page, you will see a button on the left side called 'Community QA'. The Community QA form will let you answer [[MeeGo_Apps/QA_Rules]] about the application. Make sure you install the app in question and answer these questions truthfully. Your QA form results are visible for everybody.

Once the application receives 6 positive reviews and the quarantine period has expired, the application will automatically be moved to Apps. After some time the app will show up on the Apps website and the Apps client.

MeeGo Apps/Submit

2011-12-02T13:39:17Z

Xfade: /* Promotion to Apps */

==Promotion to Apps==

''At the moment we're testing promotion for Harmattan target only. Other targets will follow soon.''

[http://apps.formeego.com Apps for MeeGo] imports all it's information from [https://build.pub.meego.com OBS]. You will need to make sure your app is packaged and building inside OBS. If you have never worked with OBS before, please read our [[Getting_started_with_OBS]] introduction.

Please make sure you have added proper description, screenshots and icons to your package. If you you didn't add this information to your project yet, please look at the [[MeeGo_Apps/Packaging]] guidelines. Your package '''will be rejected''' if you don't add this information. You will receive an email describing the problem.

At this time it is only possible to submit a package which has no external dependencies, other than what is provided in the SDK. If you need other libraries for instance, then you should link them in statically. We're looking into adding shared dependencies, but that still needs discussion. '''Do not try to submit libraries etc, apps in Apps will not be able to use them.'''

To promote your app to Apps, you need to go through the [[MeeGo_Apps/Community_QA]] process. This means your package will go in to a testing queue, where community members can fill in a form to rate your app on certain QA requirements.

===Submit Request===
To initiate this process, your need to do a SR (Submit Request) from the package page in your home project in the [https://build.pub.meego.com MeeGo Community OBS].

Example:<pre>https://build.pub.meego.com/package/show?package=attitude&project=home%3Ajaffa</pre>

Click on 'Submit Package', you can find that under 'Actions'.

You will now see a popup form. Enter the following in the 'To target project' field:
<pre>MeeGo:1.2:Harmattan:Apps:Testing</pre>

You can leave the description field empty.
''Notice'': 'Remove local package if request is accepted' should '''*NOT*''' be selected! (Otherwise your package will be removed from your home once it is accepted into Testing)

Now click the Submit button. You will receive an email at certain stages of the process to keep you informed about the progress of your package.

===What happens next===

The package will now be tested using some automated scripts.

Checks in place are:
<ul>
<li>Are you maintainer for this package (This will be done if the package is already in Apps, rejection will happen if you are not marked as 'downloader' for the package in OBS.)</li>
<li>Does your package have at least one screenshot and an icon.</li>
<li>Trial build. The package will be built in a clean repository against the SDK only. If building fails, the package will be rejected.</li>
</ul>
Once these tests succeed, the package will be moved into MeeGo:1.2:Harmattan:Testing. The data for this package will be imported into the apps.formeego.com website database after the build succeeds. In the category listing, you will see a link to '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications waiting to be tested]'.

''Notice'': Make sure you are logged in.

Here you will see a list of applications that are in Testing. When you go to the application details page, you will see a button on the left side called 'Community QA'.

More information about testing can be found on the [[MeeGo_Apps/Community_QA#Testing]] page.

MeeGo Apps/Submit

2011-11-15T11:59:24Z

Xfade: /* Promotion to Apps */

==Promotion to Apps==

''At the moment we're testing promotion for Harmattan target only. Other targets will follow soon.''

[http://apps.formeego.com Apps for MeeGo] imports all it's information from [https://build.pub.meego.com OBS]. You will need to make sure your app is packaged and building inside OBS. If you have never worked with OBS before, please read our [[Getting_started_with_OBS]] introduction.

Please make sure you have added proper description, screenshots and icons to your package. If you you didn't add this information to your project yet, please look at the [[MeeGo_Apps/Packaging]] guidelines. Your package '''will be rejected''' if you don't add this information. You will receive an email describing the problem.

At this time it is only possible to submit a package which has no external dependencies, other than what is provided in the SDK. If you need other libraries for instance, then you should link them in statically. We're looking into adding shared dependencies, but that still needs discussion.

To promote your app to Apps, you need to go through the [[MeeGo_Apps/Community_QA]] process. This means your package will go in to a testing queue, where community members can fill in a form to rate your app on certain QA requirements.

===Submit Request===
To initiate this process, your need to do a SR (Submit Request) from the package page in your home project in the [https://build.pub.meego.com MeeGo Community OBS].

Example:<pre>https://build.pub.meego.com/package/show?package=attitude&project=home%3Ajaffa</pre>

Click on 'Submit Package', you can find that under 'Actions'.

You will now see a popup form. Enter the following in the 'To target project' field:
<pre>MeeGo:1.2:Harmattan:Apps:Testing</pre>

You can leave the description field empty.
''Notice'': 'Remove local package if request is accepted' should '''*NOT*''' be selected! (Otherwise your package will be removed from your home once it is accepted into Testing)

Now click the Submit button. You will receive an email at certain stages of the process to keep you informed about the progress of your package.

===What happens next===

The package will now be tested using some automated scripts.

Checks in place are:
<ul>
<li>Are you maintainer for this package (This will be done if the package is already in Apps, rejection will happen if you are not marked as 'downloader' for the package in OBS.)</li>
<li>Does your package have at least one screenshot and an icon.</li>
<li>Trial build. The package will be built in a clean repository against the SDK only. If building fails, the package will be rejected.</li>
</ul>
Once these tests succeed, the package will be moved into MeeGo:1.2:Harmattan:Testing. The data for this package will be imported into the apps.formeego.com website database after the build succeeds. In the category listing, you will see a link to '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications waiting to be tested]'.

''Notice'': Make sure you are logged in.

Here you will see a list of applications that are in Testing. When you go to the application details page, you will see a button on the left side called 'Community QA'.

More information about testing can be found on the [[MeeGo_Apps/Community_QA#Testing]] page.

MeeGo Apps/Packaging

2011-11-15T11:30:19Z

Xfade: /* Packaging */

MeeGo Apps/Packaging

2011-11-15T11:29:31Z

Xfade: /* Packaging */

== Packaging ==

[http://apps.formeego.org Apps for MeeGo] will import all information from your package in [[OBS]]. OBS is master for the data at all times. New to OBS, please read [[Getting_started_with_OBS]].

For proper looking application entries in Apps, make sure you add the following items.

=== Screenshots ===

You can add multiple screenshots to your OBS package. Click on 'Source files' and then 'Add File' to upload
files through the webui. If you are using the osc tool to submit to OBS, then you can just 'osc add' the files and commit them in one go.

Make sure the filename ends with screenshot.png.

Example:
<pre>testapp1_screenshot.png
intro_screenshot.png
whatever_screenshot.png</pre>

There is a good screenshot tool available in 'Store' named 'ScreenCapture'.

=== Icon ===

Add a PNG file to your OBS project with filename icon.png. Make sure the resolution of the file is at least 80x80.

=== Description ===

Make sure your project description has some meaningful info, as this description will be seen by end users. This is the way to market your application, so spend some time describing your app as detailed as possible.

You can do this on the package page in OBS. Listed under the heading 'Actions', click on 'Edit Package Information'.

=== Harmattan categories ===
In your debian/control file set Section: user/<category>, where <category> must be picked from:

<pre>internet
office
graphics
games
multimedia
education
science
system
development
accessibility
network
location
utilities
</pre>

Example:
<pre>Section: user/games</pre>

MeeGo Apps/Packaging

2011-11-15T11:24:15Z

Xfade: /* Description */

== Packaging ==

Apps ForMeeGo will import all information from your package in [[OBS]]. OBS is master for the data at all times. For proper looking application entries in Apps, make sure you add the following items.

=== Screenshots ===

You can add multiple screenshots to your OBS package. Click on 'Source files' and then 'Add File' to upload
files through the webui. If you are using the osc tool to submit to OBS, then you can just 'osc add' the files and commit them in one go.

Make sure the filename ends with screenshot.png.

Example:
<pre>testapp1_screenshot.png
intro_screenshot.png
whatever_screenshot.png</pre>

There is a good screenshot tool available in 'Store' named 'ScreenCapture'.

=== Icon ===

Add a PNG file to your OBS project with filename icon.png. Make sure the resolution of the file is at least 80x80.

=== Description ===

Make sure your project description has some meaningful info, as this description will be seen by end users. This is the way to market your application, so spend some time describing your app as detailed as possible.

You can do this on the package page in OBS. Listed under the heading 'Actions', click on 'Edit Package Information'.

=== Harmattan categories ===
In your debian/control file set Section: user/<category>, where <category> must be picked from:

<pre>internet
office
graphics
games
multimedia
education
science
system
development
accessibility
network
location
utilities
</pre>

Example:
<pre>Section: user/games</pre>

MeeGo Apps/Community QA

2011-11-15T11:15:59Z

Xfade: /* Harmattan */

== Community QA ==

If you would like to help test new applications to make sure they are ready for a larger audience, then welcome!

'''Notice''': Applications in Testing are not guaranteed to work and might make your device unstable. Only use this repository if you know what you are doing.

=== Preparations ===
You need to install the following:

==== Harmattan ====
On the application grid in your device, click on the 'Settings' icon. Click on 'Applications', 'Installations' and make sure the slider is set to on for 'Allow installations from non-Store sources.

Now use the browser to download:
* [http://apps.formeego.org/n9client Apps client for Harmattan]

In the 'Transfers' window, click on org.formeego.apps*.deb, this will install the client. This will also enable the MeeGo:1.2:Harmattan:Apps repository on your device.

* [http://apps.formeego.org/n9testing Testing repository enabler]

In the 'Transfers' window, click on apps-testing-enabler-harmattan*.deb. This will enable the MeeGo:1.2:Apps:Testing repository on your device.

When you start 'Apps', it will check if the Testing repository is enabled. If it is, then apps in the Testing repositories are shown.

If you want to disable the Testing repository, just uninstall the apps-testing-enabler-harmattan package.

=== Testing ===

On the [http://apps.formeego.org Apps for MeeGo] website there is a special '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications Waiting for Review]'section.

'''Notice''': Make sure you are logged in to the site. You can use your meego.com username and password.

'Applications waiting for review' lists all the applications per category. You can find these applications in the Apps client on your device too.

When you go to the application details page, you will see a button on the left side called 'Community QA'. The Community QA form will let you answer [[MeeGo_Apps/QA_Rules]] about the application. Make sure you install the app in question and answer these questions truthfully. Your QA form results are visible for everybody.

Once the application receives 6 positive reviews and the quarantine period has expired, the application will automatically be moved to Apps. After some time the app will show up on the Apps website and the Apps client.

MeeGo Apps/Community QA

2011-11-15T10:10:27Z

Xfade: /* Testing */

== Community QA ==

If you would like to help test new applications to make sure they are ready for a larger audience, then welcome!

'''Notice''': Applications in Testing are not guaranteed to work and might make your device unstable. Only use this repository if you know what you are doing.

=== Preparations ===
You need to install the following:

==== Harmattan ====
In your device, click on the 'Settings' icon. Click on 'Applications', 'Installations' and make sure the slider is set to on for 'Allow installations from non-Store sources.

Now use the browser to download:
* [http://apps.formeego.org/n9client Apps client for Harmattan]

In the 'Transfers' window, click on org.formeego.apps*.deb, this will install the client. This will also enable the MeeGo:1.2:Harmattan:Apps repository on your device.

* [http://apps.formeego.org/n9testing Testing repository enabler]

In the 'Transfers' window, click on apps-testing-enabler-harmattan*.deb. This will enable the MeeGo:1.2:Apps:Testing repository on your device.

When you start 'Apps', it will check if the Testing repository is enabled. If it is, then apps in the Testing repositories are shown.

If you want to disable the Testing repository, just uninstall the apps-testing-enabler-harmattan package.

=== Testing ===

On the [http://apps.formeego.org Apps for MeeGo] website there is a special '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications Waiting for Review]'section.

'''Notice''': Make sure you are logged in to the site. You can use your meego.com username and password.

'Applications waiting for review' lists all the applications per category. You can find these applications in the Apps client on your device too.

When you go to the application details page, you will see a button on the left side called 'Community QA'. The Community QA form will let you answer [[MeeGo_Apps/QA_Rules]] about the application. Make sure you install the app in question and answer these questions truthfully. Your QA form results are visible for everybody.

Once the application receives 6 positive reviews and the quarantine period has expired, the application will automatically be moved to Apps. After some time the app will show up on the Apps website and the Apps client.

MeeGo Apps/Community QA

2011-11-15T10:07:02Z

Xfade: /* Harmattan */

== Community QA ==

If you would like to help test new applications to make sure they are ready for a larger audience, then welcome!

'''Notice''': Applications in Testing are not guaranteed to work and might make your device unstable. Only use this repository if you know what you are doing.

=== Preparations ===
You need to install the following:

==== Harmattan ====
In your device, click on the 'Settings' icon. Click on 'Applications', 'Installations' and make sure the slider is set to on for 'Allow installations from non-Store sources.

Now use the browser to download:
* [http://apps.formeego.org/n9client Apps client for Harmattan]

In the 'Transfers' window, click on org.formeego.apps*.deb, this will install the client. This will also enable the MeeGo:1.2:Harmattan:Apps repository on your device.

* [http://apps.formeego.org/n9testing Testing repository enabler]

In the 'Transfers' window, click on apps-testing-enabler-harmattan*.deb. This will enable the MeeGo:1.2:Apps:Testing repository on your device.

When you start 'Apps', it will check if the Testing repository is enabled. If it is, then apps in the Testing repositories are shown.

If you want to disable the Testing repository, just uninstall the apps-testing-enabler-harmattan package.

=== Testing ===

On the [http://apps.formeego.org Apps for MeeGo] website there is a special '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications Waiting for Review]'section.

'''Notice''': Make sure you are logged in to the site.

Applications waiting for review lists all the applications per category. You can find these applications in the Apps client on your device too.

When you go to the application details page, you will see a button on the left side called 'Community QA'. The Community QA form will let you answer [[MeeGo_Apps/QA_Rules]] about the application. Make sure you install the app in question and answer these questions truthfully. Your QA form results are visible for everybody.

Once the application receives 6 positive reviews and the quarantine period has expired, the application will automatically be moved to Apps. After some time the app will show up on the Apps website and the Apps client.

MeeGo Apps/Submit

2011-11-14T13:46:59Z

Xfade: /* Submit Request */

==Promotion to Apps==

''At the moment we're testing promotion for Harmattan target only. Other targets will follow soon.''

Please make sure you have added proper description, screenshots and icons to your package. If you you didn't add this information to your project yet, please look at the [[MeeGo_Apps/Packaging]] guidelines. Your package '''will be rejected''' if you don't add add this information.

At this time it is only possible to submit a package which has no external dependencies, other than what is provided in the SDK. If you need other libraries for instance, then you should link them in statically. We're looking into adding shared dependencies, but that still needs discussion.

To promote your app to Apps, you need to go through the [[MeeGo_Apps/Community_QA]] process. This means your package will go in to a testing queue, where community members can fill in a form to rate your app on certain QA requirements.

===Submit Request===
To initiate this process, your need to do a SR (Submit Request) from the package page in your home project in the [https://build.pub.meego.com MeeGo Community OBS].

Example:<pre>https://build.pub.meego.com/package/show?package=attitude&project=home%3Ajaffa</pre>

Click on 'Submit Package', you can find that under 'Actions'.

You will now see a popup. Enter the following in the 'To target project' field:
<pre>MeeGo:1.2:Harmattan:Apps:Testing</pre>

You can leave the description field empty.
''Notice'': 'Remove local package if request is accepted' should '''*NOT*''' be selected! (Otherwise your package will be removed from your home once it is accepted into Testing)

Now click the Submit button. You will receive an email at certain stages of the process to keep you informed about the progress of your package.

===What happens next===

The package will now be tested using some automated scripts.

Checks in place are:
<ul>
<li>Are you maintainer for this package (This will be done if the package is already in Apps, rejection will happen if you are not marked as 'downloader' for the package in OBS.)</li>
<li>Trial build. The package will be built in a clean repository against the SDK only. If building fails, the package will be rejected.</li>
</ul>
Once these tests succeed, the package will be moved into MeeGo:1.2:Harmattan:Testing. The data for this package will be imported into the apps.formeego.com website database after the build succeeds. In the category listing, you will see a link to '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications waiting to be tested]'.

''Notice'': Make sure you are logged in.

Here you will see a list of applications that are in Testing. When you go to the application details page, you will see a button on the left side called 'Community QA'.

MeeGo Apps/Submit

2011-11-07T19:31:13Z

Xfade: /* Submit Request */

==Promotion to Apps==

''At the moment we're testing promotion for Harmattan target only. Other targets will follow soon.''

Please make sure you have added proper description, screenshots and icons to your package. If you you didn't add this information to your project yet, please look at the [[MeeGo_Apps/Packaging]] guidelines. Your package '''will be rejected''' if you don't add add this information.

At this time it is only possible to submit a package which has no external dependencies, other than what is provided in the SDK. If you need other libraries for instance, then you should link them in statically. We're looking into adding shared dependencies, but that still needs discussion.

To promote your app to Apps, you need to go through the [[MeeGo_Apps/Community_QA]] process. This means your package will go in to a testing queue, where community members can fill in a form to rate your app on certain QA requirements.

===Submit Request===
To initiate this process, your need to do a SR (Submit Request) from the package page in your home project in the [https://build.pub.meego.com MeeGo Community OBS].

Example:<pre>https://build.pub.meego.com/package/show?package=attitude&project=home%3Ajaffa</pre>

Click on 'Submit Package', you can find that under 'Actions'.

You will now see a popup. Enter the following in the 'To target project' field:
<pre>MeeGo:1.2:Harmattan:Testing</pre>

You can leave the description field empty.
''Notice'': 'Remove local package if request is accepted' should '''*NOT*''' be selected! (Otherwise your package will be removed from your home once it is accepted into Testing)

Now click the Submit button. You will receive an email at certain stages of the process to keep you informed about the progress of your package.

===What happens next===

The package will now be tested using some automated scripts.

Checks in place are:
<ul>
<li>Are you maintainer for this package (This will be done if the package is already in Apps, rejection will happen if you are not marked as 'downloader' for the package in OBS.)</li>
<li>Trial build. The package will be built in a clean repository against the SDK only. If building fails, the package will be rejected.</li>
</ul>
Once these tests succeed, the package will be moved into MeeGo:1.2:Harmattan:Testing. The data for this package will be imported into the apps.formeego.com website database after the build succeeds. In the category listing, you will see a link to '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications waiting to be tested]'.

''Notice'': Make sure you are logged in.

Here you will see a list of applications that are in Testing. When you go to the application details page, you will see a button on the left side called 'Community QA'.

MeeGo Apps/Submit

2011-11-07T19:25:54Z

Xfade: /* What happens next */

==Promotion to Apps==

''At the moment we're testing promotion for Harmattan target only. Other targets will follow soon.''

Please make sure you have added proper description, screenshots and icons to your package. If you you didn't add this information to your project yet, please look at the [[MeeGo_Apps/Packaging]] guidelines. Your package '''will be rejected''' if you don't add add this information.

At this time it is only possible to submit a package which has no external dependencies, other than what is provided in the SDK. If you need other libraries for instance, then you should link them in statically. We're looking into adding shared dependencies, but that still needs discussion.

To promote your app to Apps, you need to go through the [[MeeGo_Apps/Community_QA]] process. This means your package will go in to a testing queue, where community members can fill in a form to rate your app on certain QA requirements.

===Submit Request===
To initiate this process, your need to do a SR (Submit Request) from the package page in your home project.

Example:<pre>https://build.pub.meego.com/package/show?package=attitude&project=home%3Ajaffa</pre>

Click on 'Submit Package', you can find that under 'Actions'.

You will now see a popup. Enter the following in the 'To target project' field:
<pre>MeeGo:1.2:Harmattan:Testing</pre>

You can leave the description field empty.
''Notice'': 'Remove local package if request is accepted' should '''*NOT*''' be selected! (Otherwise your package will be removed from your home once it is accepted into Testing)

Now click the Submit button. You will receive an email at certain stages of the process to keep you informed about the progress of your package.

===What happens next===

The package will now be tested using some automated scripts.

Checks in place are:
<ul>
<li>Are you maintainer for this package (This will be done if the package is already in Apps, rejection will happen if you are not marked as 'downloader' for the package in OBS.)</li>
<li>Trial build. The package will be built in a clean repository against the SDK only. If building fails, the package will be rejected.</li>
</ul>
Once these tests succeed, the package will be moved into MeeGo:1.2:Harmattan:Testing. The data for this package will be imported into the apps.formeego.com website database after the build succeeds. In the category listing, you will see a link to '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications waiting to be tested]'.

''Notice'': Make sure you are logged in.

Here you will see a list of applications that are in Testing. When you go to the application details page, you will see a button on the left side called 'Community QA'.

MeeGo Apps/Submit

2011-11-07T19:24:56Z

Xfade:

==Promotion to Apps==

''At the moment we're testing promotion for Harmattan target only. Other targets will follow soon.''

Please make sure you have added proper description, screenshots and icons to your package. If you you didn't add this information to your project yet, please look at the [[MeeGo_Apps/Packaging]] guidelines. Your package '''will be rejected''' if you don't add add this information.

At this time it is only possible to submit a package which has no external dependencies, other than what is provided in the SDK. If you need other libraries for instance, then you should link them in statically. We're looking into adding shared dependencies, but that still needs discussion.

To promote your app to Apps, you need to go through the [[MeeGo_Apps/Community_QA]] process. This means your package will go in to a testing queue, where community members can fill in a form to rate your app on certain QA requirements.

===Submit Request===
To initiate this process, your need to do a SR (Submit Request) from the package page in your home project.

Example:<pre>https://build.pub.meego.com/package/show?package=attitude&project=home%3Ajaffa</pre>

Click on 'Submit Package', you can find that under 'Actions'.

You will now see a popup. Enter the following in the 'To target project' field:
<pre>MeeGo:1.2:Harmattan:Testing</pre>

You can leave the description field empty.
''Notice'': 'Remove local package if request is accepted' should '''*NOT*''' be selected! (Otherwise your package will be removed from your home once it is accepted into Testing)

Now click the Submit button. You will receive an email at certain stages of the process to keep you informed about the progress of your package.

===What happens next===

The package will now be tested using some automated scripts.

Checks in place are:
<ul>
<li>Are you maintainer for this package (This will be done if the package is already in Apps, rejection will happen if you are not marked as 'downloader' for the package in OBS.)</li>
<li>Trial build. The package will be built in a clean repository against the SDK only. If building fails, the package will be rejected.</li>
</ul>
Once these tests succeed, the package will be moved into MeeGo:1.2:Harmattan:Testing. The data for this package will be imported into the apps.formeego.com website database after the build succeeds. In the category listing, you will see a link to 'Applications waiting to be tested' (http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/).

''Notice'': Make sure you are logged in.

Here you will see a list of applications that are in Testing. When you go to the application details page, you will see a button on the left side called 'Community QA'.

MeeGo Apps/Submit

2011-11-07T19:23:44Z

Xfade: Information on how to submit your package to Apps

==Promotion to Apps==

''At the moment we're testing promotion for Harmattan target only. Other targets will follow soon.''

Please make sure you have added proper description, screenshots and icons to your package. If you you didn't add this information to your project yet, please look at the packaging guidelines(http://wiki.meego.com/MeeGo_Apps/Packaging). Your package '''will be rejected''' if you don't add add this information.

At this time it is only possible to submit a package which has no external dependencies, other than what is provided in the SDK. If you need other libraries for instance, then you should link them in statically. We're looking into adding shared dependencies, but that still needs discussion.

To promote your app to Apps, you need to go through the [[MeeGo_Apps/Community_QA]] process. This means your package will go in to a testing queue, where community members can fill in a form to rate your app on certain QA requirements.

===Submit Request===
To initiate this process, your need to do a SR (Submit Request) from the package page in your home project.

Example:<pre>https://build.pub.meego.com/package/show?package=attitude&project=home%3Ajaffa</pre>

Click on 'Submit Package', you can find that under 'Actions'.

You will now see a popup. Enter the following in the 'To target project' field:
<pre>MeeGo:1.2:Harmattan:Testing</pre>

You can leave the description field empty.
''Notice'': 'Remove local package if request is accepted' should '''*NOT*''' be selected! (Otherwise your package will be removed from your home once it is accepted into Testing)

Now click the Submit button. You will receive an email at certain stages of the process to keep you informed about the progress of your package.

===What happens next===

The package will now be tested using some automated scripts.

Checks in place are:
<ul>
<li>Are you maintainer for this package (This will be done if the package is already in Apps, rejection will happen if you are not marked as 'downloader' for the package in OBS.)</li>
<li>Trial build. The package will be built in a clean repository against the SDK only. If building fails, the package will be rejected.</li>
</ul>
Once these tests succeed, the package will be moved into MeeGo:1.2:Harmattan:Testing. The data for this package will be imported into the apps.formeego.com website database after the build succeeds. In the category listing, you will see a link to 'Applications waiting to be tested' (http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/).

''Notice'': Make sure you are logged in.

Here you will see a list of applications that are in Testing. When you go to the application details page, you will see a button on the left side called 'Community QA'.

MeeGo Apps/Community QA

2011-11-07T19:10:18Z

Xfade: Created page with "== Community QA == If you would like to help test new applications to make sure they are ready for a larger audience, then welcome! '''Notice''': Applications in Testing are no..."

== Community QA ==

If you would like to help test new applications to make sure they are ready for a larger audience, then welcome!

'''Notice''': Applications in Testing are not guaranteed to work and might make your device unstable. Only use this repository if you know what you are doing.

=== Preparations ===
You need to install the following:

==== Harmattan ====
In your device, click on the Settings icon. Click on 'Applications', 'Installations' and make sure the slider is set to on for 'Allow installations from non-Store sources.

Now use the browser to download:
* [http://apps.formeego.org/n9client Apps client for Harmattan]

In the 'Transfers' window, click on org.formeego.apps*.deb, this will install the client. This will also enable the MeeGo:1.2:Harmattan:Apps repository on your device.

* [http://apps.formeego.org/n9testing Testing repository enabler]

In the 'Transfers' window, click on apps-testing-enabler-harmattan*.deb. This will enable the MeeGo:1.2:Apps:Testing repository on your device.

When you start 'Apps', it will check if the Testing repository is enabled. If it is, then apps in the Testing repositories are also shown.

If you want to disable the Testing repository, just uninstall the apps-testing-enabler-harmattan package.

=== Testing ===

On the [http://apps.formeego.org Apps for MeeGo] website there is a special '[http://apps.formeego.org/staging/basecategories/n9/pr1.0/harmattan/ Applications Waiting for Review]'section.

'''Notice''': Make sure you are logged in to the site.

Applications waiting for review lists all the applications per category. You can find these applications in the Apps client on your device too.

When you go to the application details page, you will see a button on the left side called 'Community QA'. The Community QA form will let you answer [[MeeGo_Apps/QA_Rules]] about the application. Make sure you install the app in question and answer these questions truthfully. Your QA form results are visible for everybody.

Once the application receives 6 positive reviews and the quarantine period has expired, the application will automatically be moved to Apps. After some time the app will show up on the Apps website and the Apps client.

MeeGo Apps/QA

2011-11-07T18:58:50Z

Xfade: moved MeeGo Apps/QA to MeeGo Apps/QA Rules: Clarify this is about QA rules

#REDIRECT [[MeeGo Apps/QA Rules]]

MeeGo Apps/QA Rules

2011-11-07T18:58:50Z

Xfade: moved MeeGo Apps/QA to MeeGo Apps/QA Rules: Clarify this is about QA rules

= Automated tests =

* Does package name already exist in repository
** If yes: Check if owner
* Are all dependencies available in the repository or it's parents.
* Does it build against Apps-testing
* Does the package have a description

= Crowdsourced quality assurance =

Proposed initial set of quality metrics for promotion into ''Apps''. Unlike in [http://wiki.maemo.org/Extras-testing/QA_checklist maemo.org Extras], a guided form will be provided.

{| class="wikitable"
! Question
! colspan="3" | Possible answers
! colspan="2" | Requirement
|-
| Days in quarantine?
| colspan="3" | System
| colspan="2" | >= 10
|-
| Screenshot in OBS. if user-facing?
| colspan="3" | System
| colspan="2" | y
|-
| Should be in Apps?
| Yes
| colspan="2" | No
| ''y'' - ''n'' > 10
| Mandatory
|-
| Appropriate icon, if user-installable?
| Yes
| No
| Don't know
| rowspan="3" | ''y'' - ''n'' > 3
| rowspan="6" | Optional
|-
| Appropriate description?
| Yes
| No
| Don't know
|-
| In approriate package group?
| Yes
| No
| Don't know
|-
| Impacts power/performance in unexpected way?
| Yes
| No
| Don't know
| rowspan="3" | ''y'' - ''n'' > 2
|-
| Obvious license/copyright issues?
| Yes
| No
| Don't know
|-
| Uninstall cleanly?
| Yes
| No
| Don't know
|}

* "Packagers/authors/maintainers" is a term which refers to the "maintainers" of the package within OBS and apps.meego.com. It does not encompass all contributors to the project.
* Packagers/authors/maintainers will '''not''' be permitted to vote on their own packages.
* Packagers/authors/maintainers will be able to remove their package from -testing at any time.
* ''Optional'' questions are not required for a user to vote on a package.
* ''Mandatory'' questions must be answered for a user to vote on a package.
* All criteria must be met for a package to be unlocked.

== Shortcut upgrades ==
Some packages will be urgent bug fixes in response to an external API change or critcial bug. In addition to a package owner (or repository master) being able to pull a package on-demand; the promotion capability to -testing should have a ''Critical bug-fix'' box (if, and only if, the package already exists in Apps). This will:

* Add a large box to the evaluation page saying: "The package maintainer has indicated that this release fixes a critical bug. No new functionality should be introduced, as the QA criteria have been relaxed.''
* All the requirements below will be halved (e.g. 5 day quarantine, 5 net positive votes for inclusion, 1 net positive vote for uninstallation)
* An additional question will be mandatory:

{| class="wikitable"
! Question
! colspan="3" | Possible answers
! colspan="2" | Requirement
|-
| Introduces new functionality?
| Yes
| colspan="2" | No
| ''n'' - ''y'' > 5
| Mandatory
|}

Regular reporting will be done over the use of the ''critical fix'' flag. If testers or packagers are found to be abusing it, they will be banned from further testing and/or use of the flag for a period (to be determined).

= Changing the QA rules =

The procedure for making changes to [[MeeGo Apps]] QA rules is the following:

* Send a proposal to the MeeGo Community mailing list
* After the proposal has been discussed on the list, file a bug about it
* MeeGo Community Office will make the final decision on the rule change and implement it

MeeGo Apps

2011-10-26T13:12:21Z

Xfade: /* Accessing Apps */

MeeGo Community Apps is the repository where open source software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met. This project falls under the responsibility of the [[Community Office]]. The LF have refused to allow 'apps' in the meego.com namespace; the [[/Problem Statement|problem statement]] tries to explain more.

= Accessing Apps =

* [http://apps.formeego.org Apps for MeeGo web interface]
* [http://apps.formeego.org/ocs/providers.xml Open Collaboration Services (OCS) API provider file for Apps]
* [http://gitorious.org/meego-community-extras-client Client code in Gitorious]
* [http://github.com/nemein Server code on GitHub]
* [[MeeGo_Apps/Packaging]] Packaging guidelines.

= Process =

A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|request access]] to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems.

Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package. The Apps-testing repository is intended for [[MeeGo Apps/QA|stability testing and community QA]]. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.

== Supporting Process References ==
* [[Build_Infrastructure/Community_Builder#Getting_Access|Getting access to the Community OBS]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[MeeGo Apps/QA|QA Process]]
* [[MeeGo_Apps/repositories|Repository layout description]]

= Community Apps Team =

* Client Application: Martin Grimme
* Web Site: Niels Breet, Henri Bergius, Ferenc Szekely
* OCS Interface: Niels Breet, Henri Bergius, Ferenc Szekely
* Build Service: Niels Breet, David Greaves
* Graphics, design: Istvan Jozsa

== Community Apps Volunteer Team ==

* Graphics: Tim Samoff

== Team Communication Channels ==
* Use the [http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List] for questions and discussion.
* File bugs in the [https://bugs.meego.com/enter_bug.cgi?product=Community%20Apps Community Apps Component]
* Ask questions in the #meego IRC Channel

= Plans and Schedule =

Working on:

W26:
* Automatic import/delete packages in MeeGo Apps by BOSS participant signaling (niels)
* OCS interface additions: commenting and voting (ferenc/henri)
* List apps in testing queue (ferenc)
* QA result signaling to BOSS (niels/david)
* Configure Apps build targets in OBS, cleanup old build targets (niels)
* Document Apps submit process (niels)

Open issues (help appreciated):

Documentation:
* Document QA process

Design:
* Front page design (Mike?/Tim)
* Icons for App categories

MeeGo Apps/Packaging

2011-10-26T13:06:18Z

Xfade: Created page with "== Packaging == Apps ForMeeGo will import all information from your package in OBS. OBS is master for the data at all times. For proper looking application entries in Apps, make..."

== Packaging ==

Apps ForMeeGo will import all information from your package in OBS. OBS is master for the data at all times. For proper looking application entries in Apps, make sure you add the following items.

=== Screenshots ===

You can add multiple screenshots to your OBS package. Click on 'Source files' and then 'Add File' to upload
files through the webui. If you are using the osc tool to submit to OBS, then you can just 'osc add' the files and commit them in one go.

Make sure the filename ends with screenshot.png.

Example:
<pre>testapp1_screenshot.png
intro_screenshot.png
whatever_screenshot.png</pre>

There is a good screenshot tool available in 'Store' named 'ScreenCapture'.

=== Icon ===

Add a PNG file to your OBS project with filename icon.png. Make sure the resolution of the file is at least 80x80.

=== Description ===

Make sure your project description has some meaningful info, as this description will be seen by end users. This is the way to market your application, so spend some time describing your app as detailed as possible.

You can do this on the package page in OBS. Click on 'Actions' and then 'Edit Package Information'.

=== Harmattan categories ===
In your debian/control file set Section: user/<category>, where <category> must be picked from:

<pre>internet
office
graphics
games
multimedia
education
science
system
development
accessibility
network
location
utilities
</pre>

Example:
<pre>Section: user/games</pre>

Community Office/Community device program/Nokia

2011-07-01T14:26:49Z

Xfade: /* Accepted */

= Nokia Participation Details =
* Program Contact: [[User:qgil|Quim Gil]]
Update: Nokia N950 handsets are ready! https://meego.com/community/device-program/devices/nokia-n9-devkit

== N950 Devkit Program Details ==
* Device: Nokia N950 loaded with MeeGo 1.2 Harmattan
* Quantity: 250
* Additional Criteria / Terms:
** One submission per developer please
** Device to be loaned to participant for [period needed].
** May not be able to ship to certain countries / locations.
** Nokia employees are not eligible.
* Timeframe: distribution active.

'''QUESTIONS / ANSWERS & UPDATES:''' http://forum.meego.com/showthread.php?t=3597

== General thoughts on device program ==

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

Candidates must be community developers ready to start working on new or existing open source applications, to be published in apps.meego.com and the Nokia Store. Links to your current projects are relevant! Deadline for applications: end of Tuesday, June 28th.

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.

== Results ==

'''WORK IN PROGRESS'''

=== Accepted ===

For the sake of transparency and collaboration:
* Please link your name to a page describing your Nokia N950 related work e.g. a wiki page.
* Add here one line of text summarizing the project(s) and feature(s) you are concentrating.
* We haven't done the 'Nokia employee' check yet. If you happen to be one, contact Quim Gil.

[[User:aaporantalainen|Aapo Rantalainen]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
First goal: [http://www.umsic.org/jammo/ JamMo] (will need some underlying libraries, e.g. [http://www.clutter-project.org/ clutter])

[http://wiki.meego.com/User:Broothy Ádám Balázs]
* '''Sent my Account ID to Quim, i'm already Nokia launchpad member. Awaiting any reply.'''
* [http://store.ovi.com/content/113753 Switchboard]
** [http://www.youtube.com/watch?v=GdskgAfjjxc MobileMind]

Adam Pigg 
Porting my Qt/QML apps/games from maemo, and further work on Kexi and some more QML games
[http://www.piggz.co.uk My Site]

[[User:Captianigloo|Aguirre Nicolas]] (captainigloo) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting [http://enna.geexbox.org Enna], [http://svn.enlightenment.org/svn/e/trunk/E-MODULES-EXTRA/elfe elfe] and all [http://www.enlightenment.org EFL/Enlightenment] libraries to Meego.

Alan M Bruce

[[User:mardy|Alberto Mardegan]] (Mardy) 
Developing QML port of [http://www.mardy.it/mappero Mappero], possibly [http://www.mardy.it/oculo Oculo] and [http://neverball.org Neverball] (for the latter I'm now working on a N900 port).

Aleix Pol (apol) 
Porting "horaris" and "kanban" maemo applications, finally get to have a usable KAlgebra Mobile version working on MeeGo, hopefully drag other KDE applications with this effort.

[https://meego.com/users/avis Alexander Terekhov] (Avis) '''ID sent, already a Launchpad member''' 
Porting and improving [http://qt-apps.org/content/show.php/Smart+Shopper?content=139742 Smart Shopper] project.

[[User:amandalam|Amanda Hoi Ching Lam]] (amandalam) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Traditional Chinese language and utility apps for the MeeGo & Harmattan platforms, including but not limited to a Chinese character lookup app, and applications localized for the Traditional Chinese communities in Hong Kong, Macau and Taiwan. [https://sites.google.com/site/amandahoic/Home/ Amanda's Software Projects]

[https://meego.com/users/andreagrandi Andrea Grandi] (Andy80) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
QML native client for Soma.fm radio. Based on the old mSoma: https://gitorious.org/msoma

Andrei Mirestean

[[User:Jaffa|Andrew Flegg]] (Jaffa) '''Device received''' 
Porting apps from Maemo (Attitude & Hermes), developer tools, and apps.meego.com workflow. [[User:Jaffa|"Want to know more?"]]

[[User:fiferboy|Andrew Olmsted]] (fiferboy) '''ID sent''', '''Already a Launchpad member (but my Launchpad account hasn't activated)''' 
[http://andrew.olmsted.ca/meego Fiferboy's Projects] (Birdlist, Personal Lexicon, other ideas), porting and packaging some pure Qt apps

[[User:anidel|Aniello Del Sorbo]] (anidel) 
Porting [http://maemo.org/downloads/product/Maemo5/xournal/ Xournal] from Maemo to Harmattan/MeeGo

Antti Pohjola (Summel1) ''' ID sent, Applied for the Nokia Developer Launchpad program ''' 
Porting [http://www.summeli.fi/?p=2453 AntSnes] and [http://www.summeli.fi/?p=2520 gpSP] from Symbian^3 to Harmattan/MeeGo.

[[User:awhiemstra|Arjen-Wander Hiemstra]] 
Porting [http://gluon.gamingfreedom.org Gluon] to MeeGo/Harmattan.

[https://meego.com/users/djarty Artem Sereda] (DJArty) 
Porting qutIM, openpref, arora, links, groove, microdc, Ukrainian localization.

Assaf Paz '''ID sent''', '''applied for Nokia Launchpad''' 
Adapting [http://code.google.com/p/qwazer/ Qwazer] to also work on Meego, hopefully create an Exchange Webmail client in pure QML (N900 was the initial target), Hebrew support

[[User:Bart-cerneels|Bart Cerneels]](Stecchino) 
Mobile UX' for Amarok using QML. [http://amarok.kde.org Amarok website]

[[User:khertan|Benoît HERVIER]] (Khertan) '''ID sent''', '''waiting answer from Nokia Developer Launchpad program''' 
Porting [http://khertan.net/khteditor KhtEditor] a source code editor, [http://khertan.net/khweeteur Khweeteur] a twitter/identi.ca client, [http://khertan.net/python_sdist_maemo Sdist_maemo] and developping KhtSync a automated file synchronization application, and KhtDrive an app to measure car and driver performances for eco driving.

[[User:Termana|Bradley Smith]] (Termana) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Developing a karaoke game with built-in pitch correction.

[[User:arfoll|Brendan Le Foll]], '''ID sent''', '''applied for Nokia Launchpad''' 
Porting XBMC + MeeGo TV stuff + doing audio continuums using pulseaudio.

Carsten Munk

Christian Pühringer (cip) '''ID sent, already a Launchpad member''' 
[https://github.com/cip/WikiOnBoard/wiki WikiOnBoard] Offline reader for Wikipedia using [http://openzim.org zim] format.

[[User:Clint|Clint Adams]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Libre.fm-related software development and porting, advocacy

[[User:Cpscotti|Clovis Scotti]] (cpscotti) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Developing the "connected snowboarding" [http://www.pushsnowboarding.com Push Snowboarding] application/project. Also, I'll be very happy to port other apps I did (mainly for Maemo) + new projects.

Cornelius Hald

[https://meego.com/users/zehjotkah Cosimo Kroll] (zehjotkah) '''ID sent''', '''already a Launchpad member''' 
[http://wiki.maemo.org/MeeGo_Coding_Competition_2011 MeeGo Coding Competition 2011]

Cristian Grozea '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
magnus-plus photo: an application that combines a camera-based magnifier with more advanced image processing techniques, that would enable one to: 
- use it as a magnifier (with optional light from the camera LED). 
- use it as a photo negatives lightbox that automatically inverts the negatives and adjusts the colors for proper display:
the user just have to hover it over the (back-lit) negatives and on the screen the corresponding positive (or magnified part of it) is displayed in real-time. 
- use it as an EVF add-on to SLRs to help with manual focus, leveraging the possibility of amplifying contrast and magnifying. 

Damian Waradzyn 
Porting and further development of [http://talk.maemo.org/showthread.php?t=58402 CloudGPS]

Daniel Martin Yerga

David Derby '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting [http://www.6809.org.uk/dragon/xroar.shtml XRoar - Dragon & CoCo emulator] and [http://icculus.org/avp/ Aliens versus Predator (Gold Edition) game engine].

David Galindo

[[User:Lbt|David Greaves]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Mainly CE, Harmattan and Apps to start with. Hopefully Surrounds later.

Diego Marcos

Dimitar Pashov

Dru Moore

Eero af Heurlin

[[User:Emocow | Ferdinand Mayet]] ('''Nokia Developer ID sent''') 
Development of a golf GPS application

Frank Sievertsen '''ID Sent, Applied for Nokia Developer Launchpad program, waiting for approval''' 
Open-Source Spideroak Mobile Client and other apps

Gary Birkett
N9 Qt port of liqcalendar

[http://meego.com/users/garyd Gary Driggs] ('''dev ID sent, already reg'd as Launchpad member''')
Porting [http://www.gnu.org/s/gnash Gnash] to MeeGo ARM devices.

George Ruinelli '''ID sent, Applied for the Nokia Developer Launchpad program''' 
Porting my [http://maemo.org/packages/view/sleepanalyser/ SleepAnalyser] from MAEMO as well as other smaller apps I wrote/ported. See [http://wiki.maemo.org/User:Caco3] for details.

Gerard Braad

Harald Sitter

[[User:helihyv|Heli Hyvättinen]] '''Nokia Developer ID sent, applied for the Nokia Developer Launchpad program''' 
Porting Ghosts Overboard (a game) and Chess Clock from Maemo and adding new features to the former.

[[User:bergie|Henri Bergius]] 
Porting Buscatcher, Midgard and Node.js -related tools to MeeGo. However, I've withdrawn my device program application because I already got a N950 via Helsinki MeeGo Network.

Hiemanshu Sharma '''ID Sent, Applied for Nokia Developer Launchpad program''' 
Currently working on porting [[http://forum.meego.com/showthread.php?t=3660|Komedia]]. More apps in the pipeline including Quassel (IRC Client), a Google Reader (name suggestions are welcome) and a 'Line of the day' kind of app (a glorified version of cowsay). Also working on getting an opencv port to give way for Face Detection/Facial recognition APIs.

[[User:Divan|Ivan Daniluk]] ''' ID sent, Applied for the Nokia Developer Launchpad program''' 
Porting [[User:Divan|my Maemo5 applications]], adding full Vkontakte support, Russian and Ukrainian localization and developing new apps in progress..

Janne Mäkinen '''ID sent''', '''applied for Nokia Launchpad''' 
Porting/Rewriting Maemo 5 stuff

[[User:Javispedro|Javier de San Pedro Martín]] 
Porting my [http://wiki.maemo.org/User:Javispedro Maemo 5 applications and SDL games], and [http://gitorious.org/hsdl/pages/Home SDL] itself.

Jeremias Bosch

[[User:vandenoever|Jos van den Oever]] 
Porting [http://webodf.org WebODF] to MeeGo using QML and JavaScript.
Experiment with a semantic logging tool
Experiment with a [http://blogs.kde.org/node/4161 metronome application] in QML.

[[User:Metropt|Jose Xavier]], '''ID sent''', '''waiting answer from Nokia Developer Launchpad program''' 
My goal is to port the OpenPilot Ground Control Station to the MeeGo platform and adapt the UI for a better mobile experience. You can see more information about OpenPilot GCS here: http://wiki.openpilot.org/display/Doc/Ground+Control+Station+User+Manual

[[User:Bundyo|Kamen Bundev]] (Bundyo), '''ID sent''', '''applied for Nokia Launchpad''' 
Rewriting Search Tool, porting Maemo 5 work, NodeJS, possible Tear rewrite.

Karl Johan Grøttum

[[User:kemargrant | kemar grant]], '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
My goal is to bring Screen Mirroring to Meego along with playing local files
easily to a desktop. The app is called groundwork and it is opensource. Code will be shifted to Launchpad once I can begin testing on a meego device.
http://code.google.com/p/groundwork/

Ken Young 
Initially I will port the Maemo [http://wiki.maemo.org/Orrery Orrery] program, and add support for the magnetometer. I will
also port some other apps from Maemo 5.

[[User:Kimitake|Kimitake]] '''ID sent, already a Launchpad member''' 
developing Qt-based micro blogging client for twitter, identi.ca, wassr, jp

Kirill Kulakov

[[User:lostinmirkwood|Kristopher C. Kantor]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
* Continuing Development of [http://ansela.garage.maemo.org/ Ansel-A]: Digital Darkroom for Qt Devices

[[User:shadymilkman|Kyle Thomas]] 
Creating Reedit: [http://www.shadymilkman.com/p/n9-project.html Reedit] A full featured Reddit list browser 
Submitted credentials to the N.D.Launchpad for application review, waiting for instructions.

[[User:Creamygoodness|Lance Colton]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Working on Proximus during July, I will see what we can do with Conky after that.

Lasse Kärkkäinen 
Porting [http://performous.org/ Performous] singing/band game from PC to N900 and MeeGo

Lasse Stenberg

Laszlo Papp (Already got one earlier, thus I do not need a new one ;) )

liang wei (foolegg) 
[[Cuteinputmethod]] is a Chinese Input Method, designed for handset device. 
(received notify mail, and sent reply with Nokia Developer Account Id)

Luis Felipe Strano Moraes '''ID sent''', '''applied for Launchpad membership''' 

Luiz Augusto von Dentz

Marat Fayzullin (fms) '''ID sent''', '''already a Launchpad member''' 
Porting the following:
[http://fms.komkon.org/SlideRule/ SlideRule],
[http://fms.komkon.org/ColEm/ ColEm],
[http://fms.komkon.org/fMSX/ fMSX],
[http://fms.komkon.org/Speccy/ Speccy],
[http://fms.komkon.org/ATI85/ AlmostTI],
[http://fms.komkon.org/MG/ MasterGear],
[http://fms.komkon.org/iNES/ iNES],
[http://fms.komkon.org/VGB/ VGB],
[http://fms.komkon.org/VGBA/ VGBA].
Also expecting to port the FBReader and an IRC client (although most likely not XChat).

[[User:deimos|Marco Bavagnoli]] (deimos) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
I'm porting [http://mediadownloader.cz.cc/?page_id=2 mediadownloader] application just ported to [http://mediadownloader.cz.cc/?p=153 maemo] and here a [http://www.youtube.com/watch?v=_Dsj2piBQCw video].

[[User:Mece|Marcus Wikström]] (mece) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
[http://talk.maemo.org/showthread.php?t=73490 Tweed Suit] for N9/50. Probably Qlister and also planning an location based tracking service/app.

Marijn Kruisselbrink

[[User:mgedmin|Marius Gedminas]] (mgedmin) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Planning to port [http://mg.pov.lt/gtimelog GTimeLog].

Marko Mattila

[http://wiki.meego.com/User:Vgrade Martin Brook] (vgrade) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 

I would plan to contnue my contributions to the N900 Community Edition of MeeGo which I assume will push right through into the N9. I am very interested in contributing to the exciting new architecture built on Wayland to give this device the best user experience.

Local Network Meetups, Cambridge, Birmingham, Koln, Dusseldorf

Martin Grimme (pycage) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Doing the Community Apps installer client. Also targetting Harmattan with my OSS MeeGo apps (which are currently mostly running on the WeTab).

[http://wiki.meego.com/User:Martink Martin Kolman] (MartinK) '''ID sent''', '''applied for the Nokia Launchpad''' 
Porting the modRana GPS navigation system and Mieru manga and comic book reader.

[[User:twoboxen|Matt Hawkins]] (twoboxen) '''ID sent''', '''Already a Launchpad member''' 
Open sourcing and working on my cross-platform OpenGL engine (HawkEngine) and several [https://sites.google.com/site/hawkorn/games games]. This engine builds projects and binaries for Qt, iOS, Android (though the NDK is touchy), WebOS, Glut, etc.

[[User:zas|Matti Henrik Karjalainen]] (zas) '''ID sent, applied for Nokia Launchpad''' 
[http://tols17.oulu.fi/~matkarja/meego/ Projects] (Currently working on Tap 'em (game))

[http://forum.meego.com/member.php?u=9286 Michael Muth] (helex) '''ID sent, already a Launchpad member''' 
[http://talk.maemo.org/showthread.php?p=1001316 ClipMan], [http://talk.maemo.org/showthread.php?t=52589 DreamRemote], TcpKeyboard, something like [http://talk.maemo.org/showthread.php?t=72408 ConkyLayoutSwitcher] (have to see how the UI works in detail - need to create it from scratch)

[http://blog.mikeasoft.com/tag/maemo/ Michael Sheldon] (Elleo) '''ID sent, applied for Nokia Launchpad''' 
Creating a [http://libre.fm Libre.fm] radio client and porting [http://www.jokosher.org Jokosher] to small screen devices.

[http://blog.cihar.com/ Michal Čihař] (Nijel) '''ID sent, applied for Nokia Launchpad''' 
Creating a [http://wammu.eu/ Gammu] application for phone for data synchronization and backup.

Michele Tameni ( netvandal ) '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''

- Luca's Mirror: It’s a simple app that transform your phone into a hand-held mirror with some other cool addictions.

- Semantic experiment : Experiment with Notification Area mixed with the semantic information stored in tracker, reacting to user action with usefull notification
More info [http://michele.tameni.it/project/meego/ Here]

Mike Choy : Porting Maesynth and Maelophone from N900 Python to QML and C++. Stress testing the new [https://projects.developer.nokia.com/qtgameenabler Qt Game Enabler] to see if we finally have low latency audio support in Qt. Will also look to see if we can get midi sample support via Wild Midi or equivalent.

Mikko Vartiainen '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''
http://forum.meego.com/showthread.php?t=3607

[https://projects.developer.nokia.com/home/user/mmlado Mladen Milankovic] '''IDs sent''' 
Develop games in QML

Mures Andone

[[User:Nielsmayer|Niels Mayer]] '''[https://projects.developer.nokia.com/home/user/NielsMayer Nokia Developer ID] sent''', '''Applied for the Nokia Developer Launchpad program''' 
[http://wiki.meego.com/Tubelet-and-cutetube-port Port cutetube-qml to MeeGo tablet UX/harmattan UX.] 
[http://code.google.com/p/ytd-meego/wiki/CitizenJournalismWithYoutubeDirectForMeego YouTube Direct For MeeGo]

[[User:olka|Oleksandr Kachur]] '''ID sent'''. '''Waiting answer from Nokia Developer Launchpad program''' 
Developing cloud music player integrated with Google music, Amazon music and last.fm services.

Olle Tränk (zeamoceq) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting [http://qticksize.zeamoceq.net qTickSize] (interface to Swedish online stock broker)

Oscar Martinez '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Port 2d puzzle board game [http://kde-apps.org/content/show.php/kMagnet?content=109111 kMagnet] or a new 2d board puzzle game

[[User:Lorenzph|Philip Lorenz]] (Nokia Developer ID sent) 
Development of a hiking application supporting the user when planning and executing the trip.

[[User:Ph5|Philipp Zabel]] (pH5) ''' ID sent, applied for the Nokia Developer Launchpad program ''' 
Integration of [https://www.torproject.org/ Tor] support, porting of [http://maemo.org/downloads/product/Maemo5/frogatto/ Frogatto], [https://garage.maemo.org/projects/beifahrer/ Beifahrer] and [https://garage.maemo.org/projects/cinaest/ Cinaest]

Randall Arnold
Application testing, local and regional meetup/event demos, product evangelism, peripheral design

Ravi Vagadia '''ID Sent''', '''Applied for the Nokia Developer Launchpad Program''' 
VLC Remote & Trip Management App.

Ray Donnelly

[[User:Rlinfati|Rodrigo Linfati]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program'''
* Upgrade GoogleLatitude to the current API
* Find your Frient: a apps that inform you position directly to you friend without any external server.

Roman Morawek

[http://wiki.meego.com/User:Wonko Ruediger Gad (wonko)] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Amongst other things I'll port my existing applications for Maemo5/Fremantle to MeeGo/Harmattan: VU Meter, StultitiaSimplex, Zeecontrol, Advanced Clock Plugin (for details please see my page).

[[User:generalantilles|Ryan Abel]] (GeneralAntilles) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Working with fiferboy on a photographer's application suite ([http://thousandsparrows.com/meego/ SnapGo], currently) to include feature like a light meter and GPS track recording.

Sam Bristow

[[User:Eipi|Sanjeev Visvanatha]] (EIPI) , '''d.n.c ID sent''', '''could not apply for Nokia Launchpad''' 
Porting MaeFlight from Maemo 5, and adding functionality for Harmattan

Seif Lotfy

Sergey Ivanov 
Developing software for the mobile operating system MeeGo, associated with the processing of audio and video streams.

Sergey Ivanov

[[User:Spenap|Simón Pena]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting and enhancing Maevies from Maemo 5 to Meego/Harmattan

Simon Pickering (lardman) '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Porting mBarcode, working on Augmented Reality app (mAR), time and location event app (Proximus), additional location methods (offline cellid, magnetic field line direction)
Page here: http://wiki.meego.com/User_talk:Lardman

[[User:Somnathbanik|Somnath Banik]]: '''Nokia Developer ID Sent''', '''Applied for Nokia Developer Launchpad Program'''
* Porting my existing Symbian^3 multimedia applications to MeeGo/N9 with a new and exciting UI components of Harmattan/MeeGo.
* Creating simple and easy open source application to inspire beginner developers to work on MeeGo/N9 technology.

Stani Michiels

Stefanos Harhalakis

Stephen Gadsby (sjgadsby) '''ID sent''', '''applied for Nokia Launchpad''' 
writing a [[User:Sjgadsby#Preferred Shopper Card Wallet|not-yet-named wallet for store loyalty cards]]

[[User:vitaminj|Stephen Spencer]] (VitaminJ) '''ID sent, applied for the Nokia Developer Launchpad program''' 
[http://jenkins.vitaminj.co.uk/job/meex/ Meex], a portable DJing application

Susanna Huhtanen

Tadej Novak '''ID sent, applied for the Nokia Developer Launchpad program''' 
Porting my desktop IP TV player and schedule to Meego

[http://wiki.meego.com/User:Kenya888 Takahiro Hashimoto] 
porting qimsys/mozc to Harmattan/MeeGo, developing streaming multimedia player with QML

Tasuku Suzuki

Teemu Hukkanen

[http://teom.wordpress.com Teo Mrnjavac] '''ID sent, applied for the Nokia Developer Launchpad program''' 
[http://ur1.ca/4kkwh Porting] [http://amarok.kde.org Amarok] to tablets and handsets running MeeGo/Harmattan.

Thomas Cherryhomes - Lead Developer for LinuxMCE
* LinuxMCE is a next generation smart home platform encompassing media, home automation, telecom, and security features. http://www.linuxmce.org/
* A 25 min demo of the software can be seen here: http://video.google.com/videoplay?docid=2176025602905109829
* Nokia N950 will be used as a test platform for the new QML/Qt Quick based qOrbiter we are writing to replace our existing Orbiter software, qOrbiter videos here:
** http://www.youtube.com/watch?v=NDGagn3EciA
** http://www.youtube.com/watch?v=oUHrCdBgoyQ

[[user:thp|Thomas Perl]] '''ID sent'''
* [http://gpodder.org/ gPodder] - Integrating gPodder with Harmattan (including specific APIs)
* Open source work on Python-related APIs (PySide, etc..) + Python tutorials
* Get [[Games|Mong]] in shape for Harmattan
* Port over some of my existing [http://maemo.org/profile/view/thp/ Maemo 5 apps]

[[user:harbaum|Till Harbaum]] '''ID sent, applied for the Nokia Developer Launchpad program'''
* First action: Try to get [http://www.harbaum.org/till/cacheme CacheMe] to work nicely
* Might have to work on qt theming (and convince people that this is a good thing :-)
* [https://build.pub.meego.com/project/show?project=home%3Aharbaum Community OBS home project]
* And of course i'd like to port some of my previous Maemo projects ...

[[User:timsamoff|Tim Samoff]]
* [http://thp.io/2011/mong/ "Mong"]
* MeeGo Community Apps website design
* A few other things that are brewing (games, sound generators, etc.)

[[User:timoph|Timo Härkönen]] (timoph) '''ID sent, applied for Launchpad membership'''
* [http://gitorious.org/random-timoph impuzzle, etc.]
* [http://timoph.fi timoph.fi]
* [https://build.pub.meego.com/project/show?project=home%3Atimoph Community OBS home project]

[http://wiki.meego.com/User:Venemo Timur Kristóf]

* '''Sent my Account ID to Quim, applied at Nokia launchpad. Awaiting any reply.'''
* [http://wiki.meego.com/User:Venemo/HarmattanPlans My Harmattan Plans]
** [http://gitorious.org/colorful-apps/puzzle-master Puzzle Master]
** [http://forum.meego.com/showthread.php?t=3711 Public transportation app] (Click on the [http://forum.meego.com/showthread.php?t=3711 link] and post to the thread if you are interested to contribute.)
** [https://gitorious.org/colorful-apps/memory-game Memory game]
** Labirynth game (No code available yet)

Tom Swindell
* [[User:Tswindell/CommunityApplicationDevelopment]]: Columbus Navigation Toolkit, Media IM Status Updater.

[[User:tlaukkanen|Tommi Laukkanen]]
* Facebook client [http://kasvopus.com Kasvopus], Twitter client [http://twimgo.com TwimGo], Google Reader client [http://newsflow.mobi NewsFlow], FourSquare client [http://nelisquare.com Nelisquare]

Toni Nikkanen

[https://meego.com/users/sandst1 Topi Santakivi] '''ID sent''', '''applied for Nokia Launchpad'''
* Porting FunkeySynth, a MeeGo Tablet synthesizer to Harmattan
* Demo clip and further info in [http://sandst1.wordpress.com/ my blog]

Tuomas Kulve

[https://meego.com/users/vasvlad Uladzislau Vasilyeu] (Vasvlad) '''ID sent, applied for the Nokia Developer Launchpad program''' 
* Porting OMWeather to Harmattan

[[User:drowne|Valerio Di Donato]] '''ID sent, applied for Nokia Launchpad ''' 
Location-Based games and application development, mobile game design. Junomi Developer ( serious game presented at Games for Health Conference in Boston, May 2011 )

Ville Jyrkkä

Ville Ranki

Willem Liu

[[User:ph0b|Xavier Hallade]] '''ID sent, applied for Nokia Launchpad ''' 
Writing tutorials to help other developers to step in MeeGo / Building MeeGo Paris network / Developing an audio player to access to more than 47 000 webradios referenced on AOL shoutcast (by name, genre, current track)

Yann Bieber '''ID sent, applied for Nokia Launchpad ''' 
Porting [http://code.google.com/p/wagic/ Wagic] on Harmattan based on either Qt or SDL

Zaheer Merali '''ID sent''' '''Applied for the Nokia Developer Launchpad (for individuals) program'''
* Porting [http://gstreamer.freedesktop.org GStreamer] plugins not shipped by Nokia to Harmattan
* Porting [http://www.flumotion.net Flumotion] an open source streaming solution to Harmattan taking advantage of the hardware encoding and the camera

Zap Andersson

Zeeshan Ali

-----
Second batch - to be integrated witrh the list above.

Max Waterman '''ID sent''', '''applied for Nokia Launchpad'''
* Porting ZouBa to MeeGo/H and QML, plust other app ideas.

Sławomir Musiał '''ID sent''', '''applied for Nokia Launchpad'''
* [http://www.swinkels.tvtom.pl/eCards eCards] Application for creating and sending e-cards

[https://meego.com/users/scifiguy Sudheer K.] '''ID sent''', '''applied for Nokia Launchpad'''
* Porting [https://garage.maemo.org/projects/marketstoday Markets Today], a Stock Quotes app to Harmattan
* Evaluate porting of VICaR (Call router application) and new application ideas on Harmattan

Mohannad Hammadeh '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Porting mPrayerTime to Meego-Harmattan, updating the UI and adding more features.

[[User:antman8969|Anthony Naddeo]] (antman8969 here on meego.com, but antman8069 on developer.nokia.com) '''id sent, applied for launch program''' 
Creator and maintainer of [http://linkedup.googlecode.com Linkedup] - LinkedIn client for Maemo, Meego, Harmattan..... anything Qt

Leaf Johnson

Ed Page

William Su (sony123) '''ID sent, Applied for the Nokia Developer Launchpad program''' 
[http://talk.maemo.org/showthread.php?p=1019939#post1019939 Stockona] - a google finance client.
Currently working on:
* Local portfolio creation.
* Webview integration: Make in-app news feed reading possible.

Anthony Day

[[User:mattaustin|Matt Austin]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Transperth trains live departure boards app, Player numbers AFL footy app, Amazon S3 bucket & file browser

[https://meego.com/users/smoku Tomasz Sterna] '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Port my touch screen [http://tomasz.sterna.tv/maemo/ ports of games for Maemo] (Widelands, Bos Wars, Robbo) and UAE4All, PSX4All emulators
* Port support for SIXAXIS(TM) Controller
* Possibly build and integrate [http://codex.xiaoka.com/wiki/cordia:start Cordia HD] on Harmattan

Olli Laasonen '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
* Porting apps from Maemo (Who is calling?, Advanced phone lock, Sanakirja.org dictionary client).
* Developing small handy applications.

Ville Syrjälä

Shane Bryan

Jure Repinc

[http://maemo.org/profile/view/rm_you/ Adam Harwell] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
* Porting [http://maemo.org/downloads/product/OS2008/advanced-backlight/ Advanced Backlight] from Maemo, adding new features
* Helping with photo utility suite project
* Will help beta test apps for people on IRC

Boris Pohler

Eike Hein

Jeffrey Malone (ieatlint) - '''ID sent, already a Nokia Launchpad member'''.
Will be creating a transit application around the public NextBus real-time vehicle tracking API for dozens of transit agencies in North America.
Hopefully collaborating with others working on transit applications... :)

Thomas Boutroue (aka TheBootroo)
Making a small and smart mobile widgets toolkit on top of plain QWidget + CSS for styling, named MWTk.
And using this toolkit to make several apps for MeeGo (and runs onto Maemo5 and Symbian too, even on desktop OS) and a new environment, that aims to be a good alternative to default MeeGo Handset UX, bringing it on pair with Harmattan UX, by giving it a successor to the deprecated MeeGoTouchFramework.
Already some testable sources can be found on the project gitorious repos.
https://gitorious.org/meego-community-mobile-ux-ng
And there is a page with some screenshots of the look that MTWk can do (this page will be moved on gitorious wiki soon) :
http://modern-os.projects.servhome.org/mobileApps/

Stephan Bulgin '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
blog/website in near future. to showcase my projects.

[[User:mdengler|Martin Dengler]] '''ID sent''', '''Waiting for Launchpad account to be activated''' 
I am working on porting a tron-like game (armegatron preferably or glTron) to the N9, and developing Ringr, a location-based ringtone management application.

[[User:Rafael2k|Rafael Diniz]] '''ID sent''', '''Waiting for Launchpad account to be activated''' 
I plan to develop FM RDS applications with focus in the new standards from RadioDNS like the RadioVIS (partly based in the already existent the N900-fmvis http://code.google.com/p/n900-fmvis/).
I'm a member of a university radio station (Radio Muda FM, 88.5MHz) and my plan is to develop "real life" radio station applications. 
I'll also rewrite an application I did for audio streaming, darknow (a gui for darkice, http://darksnow.radiolivre.org) which is an icecast2 client, and also write an audio/video icecast2 client (based in a software I did called theorur, http://theorur.sarava.org), all using QT.

Anderson Briglia

[[User:Milhouse|Neil MacLeod]] '''ID sent, Applied for the Nokia Developer Launchpad program''' 
Develop an audio recording application with geo-location support, plus other applications to improve personal productivity utilising the Harmattan notification/event view.

Nilanjan Chakravorty - '''ID sent, Had applied for the Nokia Developer Launchpad program'''
* Leverage my financial background with IT to develop
''- Portfolio management application
- Bloomberg Pricing data application''

David Perlow '''ID sent, Applied for the Nokia Developer Launchpad program'''

Pawel Kurdybacha

Philippe Coval (RzR) ''' ID sent , member of LP, http://rzr.online.fr/q/meego , http://wiki.meego.com/User:Rzr , https://www.developer.nokia.com/Profile/?u=www.rzr.online.fr ( qt4, qml, opengl, debian)

Philipp Engelhard '''[https://www.developer.nokia.com/Profile/?u=-philipp Nokia Developer ID] sent''', '''Applied for the Nokia Developer Launchpad program''' 
* Develop a maze game for children and adults
* Develop a "Nokia Bots" like program for alarm and battery

[[User:Rnazarov|Ruslan Nazarov]] '''ID sent''', '''waiting answer from Nokia Developer Launchpad program''' 
Porting [https://gitorious.org/titanim TitanIM] (Vkontakte instant messenger)

Moritz Mühlenhoff

Matt Williams

[[User:Asys3|Uwe Koch]] '''ID sent, Applied for the Nokia Developer Launchpad program''' 
* Port hopefully all of my games Lineo,Q,TwinDistress,Sokoban and Jooleem

Frank Banul '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Port TabletBridge and RadioTimeToGo

Felipe Erias Morandeira

[[User:kojacker|Ryan Faulkner]] '''ID sent, Already a Lunchpad member''' 
* Various applications, bits and bobs (links coming)

[[User:hopbeat|Arkadiusz Stopczynski]] '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Various academic projects, including novel user interfaces, social web, BCI and portable cognitive sensors. All the crazy stuff mentioned here: http://www.milab.imm.dtu.dk
* Some utility applications that make your everyday tasks easier, such as shortcutd or lockdaemon for Maemo

Ferenc Szekely

[[User:w00t|Robin Burchell]] (w00t) '''ID sent''', '''Already a Launchpad member (but my Launchpad account hasn't activated)''' 
meego.com hackery, meego-ux in particular. Qt Components. Anything else I find interesting - see [[User:w00t/N950Development]] for plans, as I think of anything interesting to write.

Mohammad Abu-Garbeyyeh '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Planning a wiki page with a todo list, main project here: http://bt-messenger.com

[[User:sebas|Sebastian Kügler]] (sebas) '''ID sent, Applied for the Nokia Developer Launchpad program'''
* Bringing Plasma Active ( http://community.kde.org/Plasma/Active )to MeeGo

Juha Ristolainen '''ID sent, already a Launchpad member''' 
Heiaheia fitness-service application for MeeGo. Untappd.com client for MeeGo.

Ilya Skriblovsky '''[https://www.developer.nokia.com/Profile/?u=IlyaSkriblovsky Nokia Developer ID] sent, applied for Nokia Developer Launchpad''' 
* Port NWTBible (Bible reader), Planaris (Hierarchical Todo list) to MeeGo

Rich Jones

[[User:Bemasc/N950_Project|Benjamin Schwartz]] '''ID sent, applied for Nokia Launchpad ''' 
I will attempt to convert [http://sugarlabs.org Sugar] [http://activities.sugarlabs.org Activities] into MeeGo apps, and hopefully in the process acquire some insight into the potential for MeeGo to form the basis of future Sugar revisions

Nicolai Hess

Hussain Shafiu '''ID sent''', '''Already a Launchpad member waiting for Launchpad account to be activated)''' 

Shan Yafeng '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
An education program for exchange information between students and teacher in class. And port some programs to the nokia N900/N950 device. The progress can be found here : http://cuckoohello.wordpress.com

[[User:vitna|Vaselli Vittorio]] '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' My actual project is http://forum.meego.com/showthread.php?t=3652, but i have in program to develop much more game for the Harmanattan platform

------
Third batch

Niels Breet '''ID sent''', '''Applied for the Nokia Developer Launchpad program''' 
Set up & Testing Harmanttan building on MeeGo Community OBS

Andre Klapper

Reggie Suplido

Koos Vriezen

Micke Prag

Aigars Mahinovs

Miika Johannes Ahdesmaki

Andreas Schildbach

Ilya Paramonov

Thomas B. Ruecker

Damion Yates

Antti Raina

Andrew Zhilin

Glen Gray

Johan Paul

Simon La Rose

Daniele Maio

Joerg Reisenweber

Nathan Willis

Peter Hunt

Philford Barrett

Uwe Kaminski

Kyösti Ranto

Alex Tyler

Stuart Howarth

Wes Hardaker

Christoph Keller

Luke Bratch

David Sansome

Jason Byrne

Hillel Lubman

Kirill Krinkin

Si Howard

Klaus Rotter

Piotr Pokora

Ivan Shvedunov

Andres Gomez

William Stephenson

Jason Flatt

Jens Persson

Anderson Lizardo Gomes

pancake

Rodrigo Vivi

Nicola De Filippo

Getting started with OBS

2011-06-30T08:16:13Z

Xfade: Open ;)

The MeeGo Open Build System (OBS) seems rather complicated, this page will attempt to make it nice and easy to get started. See also the Mer project's documentation on [http://wiki.maemo.org/Mer/Build/Application_Building application building] with OBS.

It's a work in progress, feel free to add and modify!

=Pre-requisites=

* You need a meego.com login to be able to access the OBS
* You need to be running one of the [http://download.opensuse.org/repositories/openSUSE:/Tools/ supported OSes]
* Install osc (for example, <code>apt-get install osc</code> may work out-of-the-box on recent versions of Ubuntu & Debian, other repositories are available on [http://download.opensuse.org/repositories/openSUSE:/Tools/ openSUSE tools])

=Setting up your home project=

Your home project is like a home directory in which you can create sub-projects, repositories, etc.

* Visit the OBS page (https://build.pub.meego.com)
* Log in and click on 'create home project' (down at the bottom of the page iirc)

=Overview=
OBS is based around ''projects'', ''packages'' and ''repositories''. '''Packages''' have a set of files (source code, packaging meta-data, etc.) which are compiled by build servers against particular distributions. Each distribution results in your code being available in a '''repository'''.

==Setting up a sub-project==
A sub-project allows you to group related activities together.

* In the "Overview" tab for your home project, select "Actions > Create subproject".

==Creating a project==
A project is required before anything can be built.

* Go to the "Projects" tab for the project in which you wish to create it
* Select "Add a new package"
* Enter a UNIX-style (all lower case) "Name"
* Enter a title-case, with appropriate spacing, "Title"
* Enter a brief "Description"
* Click "Save Changes"

==Adding repositories==

* Go to the "Repositories" tab for the project in question
* Click "Add Repository"

==Adding files to a package and building them==

===From the terminal===
* Checkout (like SVN) your home project, which will contain all your sub-projects and packages
osc -A https://api.pub.meego.com co home:[username]

* Add files to your local copy
** For MeeGo this will be a .spec file and a tarball containing your source code, etc.
** For Harmattan this will be a <code>.dsc</code> file, source tarball and <code>debian.tar.gz</code> (this allows one to keep the debian directory out of the source)
osc add [filename]

* Commit the files
osc commit

At this point the OBS will try to build your project remotely. You can also build locally by doing <code>osc build</code>

===Using the webinterface===
* Add the correct files as listed above and they will be automatically built for you

MeeGo Apps

2011-06-28T13:56:35Z

Xfade: Clarify

MeeGo Community Apps is the repository where open source software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met. This project falls under the responsibility of the [[Community Office]].

= Accessing Apps =

* [http://apps-beta.meego.com Apps Beta Web Interface]
* [http://apps-beta.meego.com/ocs/providers.xml Open Collaboration Services (OCS) API provider file for Apps]
* [http://gitorious.org/meego-community-extras-client Client code in Gitorious]
* [http://github.com/nemein Server code on GitHub]

= Process =

A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|request access]] to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems.

Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package. The Apps-testing repository is intended for [[MeeGo Apps/QA|stability testing and community QA]]. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.

== Supporting Process References ==
* [[Build_Infrastructure/Community_Builder#Getting_Access|Getting access to the Community OBS]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[MeeGo Apps/QA|QA Process]]
* [[MeeGo_Apps/repositories|Repository layout description]]

= Community Apps Team =

* Lead Developer: Niels Breet
* Client Application: Martin Grimme
* Web Site: Ferenc Szekely
* OCS Interface: Henri Bergius
* Build Service: David Greaves

== Community Apps Volunteer Team ==

* Graphics: Tim Samoff

== Team Communication Channels ==
* Use the [http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List] for questions and discussion.
* File bugs in the [https://bugs.meego.com/enter_bug.cgi?product=Community%20Apps Community Apps Component]
* Ask questions in the #meego IRC Channel

= Plans and Schedule =

Working on:

W26:
* Automatic import/delete packages in MeeGo Apps by BOSS participant signaling (niels)
* OCS interface additions: commenting and voting (ferenc/henri)
* List apps in testing queue (ferenc)
* QA result signaling to BOSS (niels/david)
* Configure Apps build targets in OBS, cleanup old build targets (niels)
* Document Apps submit process (niels)

Open issues (help appreciated):

Documentation:
* Document QA process

Design:
* Front page design (Mike?/Tim)
* Icons for App categories

MeeGo Apps

2011-06-28T13:52:33Z

Xfade: Update schedule

MeeGo Community Apps is the repository where open source software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met. This project falls under the responsibility of the [[Community Office]].

= Accessing Apps =

* [http://apps-beta.meego.com Apps Beta Web Interface]
* [http://apps-beta.meego.com/ocs/providers.xml Open Collaboration Services (OCS) API provider file for Apps]
* [http://gitorious.org/meego-community-extras-client Client code in Gitorious]
* [http://github.com/nemein Server code on GitHub]

= Process =

A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|request access]] to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems.

Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package. The Apps-testing repository is intended for [[MeeGo Apps/QA|stability testing and community QA]]. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.

== Supporting Process References ==
* [[Build_Infrastructure/Community_Builder#Getting_Access|Getting access to the Community OBS]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[MeeGo Apps/QA|QA Process]]
* [[MeeGo_Apps/repositories|Repository layout description]]

= Community Apps Team =

* Lead Developer: Niels Breet
* Client Application: Martin Grimme
* Web Site: Ferenc Szekely
* OCS Interface: Henri Bergius
* Build Service: David Greaves

== Community Apps Volunteer Team ==

* Graphics: Tim Samoff

== Team Communication Channels ==
* Use the [http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List] for questions and discussion.
* File bugs in the [https://bugs.meego.com/enter_bug.cgi?product=Community%20Apps Community Apps Component]
* Ask questions in the #meego IRC Channel

= Plans and Schedule =

Working on:

W26:
* Automatic import/delete packages in MeeGo Apps by BOSS participant signaling (niels)
* OCS interface fixes (ferenc/henri)
* List apps in testing queue (?)
* QA result signaling to BOSS (niels/david)
* Configure Apps build targets in OBS, cleanup old build targets (niels)
* Document Apps submit process (niels)

Open issues (help appreciated):

Documentation:
* Document QA process

Design:
* Front page design (Mike?/Tim)
* Icons for App categories

MeeGo-Meeting IRC Schedule

2011-06-22T16:32:17Z

Xfade: Add MeeGo IT meeting

To avoid meeting conflicts in [http://meego.com/community/irc-channel #meego-meeting], please add your meeting here with date and UTC time until we have a more robust solution. You might also want to review our [[IRC guidelines]] for the MeeGo project.

We have two meeting rooms:

[http://meego.com/community/irc-channel #meego-meeting], also called Meeting Room 1

[http://meego.com/community/irc-channel #meego-meeting2], also called Meeting Room 2

== Regular Meetings ==

'''Monday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0px 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 7:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|MeeGo Core Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0px 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 0px 0"| 15:00
|style="border-style: solid; border-width: 0 1px 0px 0"| [[Local_MeeGo_Networks/MeeGo_Network_Finland#Online_Community_Meetings | MeeGo Network Finland Community Meetings]]
|style="border-style: solid; border-width: 0 1px 0px 0"| Monthly meeting every 1st Monday
|style="border-style: solid; border-width: 0 0px 0px 0"| #meego-meeting
|}

'''Tuesday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Meetings| QA Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 08:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/QA-tools/Meetings| QA-Tools Meeting]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting2
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 08:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[SDK/Meetings/Release| SDK Meeting (Release)]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 11:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/DeveloperEdition/Meetings| N900 Community Edition Team Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 13:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Netbook Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 14:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Community_Office/Meetings| Community Office Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Bi-Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 15:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Project/Dialer/Meetings| Dialer Project Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 0 0"| 17:00
|style="border-style: solid; border-width: 0 1px 0 0"| [[Events/Meetings|Events Meeting]]
|style="border-style: solid; border-width: 0 1px 0 0"| Bi-Weekly *
|style="border-style: solid; border-width: 0"| #meego-meeting
|}

<nowiki>*</nowiki> Every other week.

'''Wednesday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 05:30
|style="border-style: solid; border-width: 0 1px 1px 0"| [[SDK/Meetings| SDK Meeting]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Handset Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo SDK Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting2
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 08:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MCTS Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 15:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[LocalizationMeetings| Localization / L10n Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Monthly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|}

'''Thursday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 06:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Technical_Steering_Group_meetings| Technical Steering Group Meeting]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Bi-Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Tablet 1.2 Critical bug tracking]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting2
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo N900 DE 1.2 Critical bug tracking]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 0 0"| 08:00
|style="border-style: solid; border-width: 0 1px 0 0"| [[ARM/N900/Meetings| MeeGo N900 DE Common Software + Hardware Adaptation Meetings]]
|style="border-style: solid; border-width: 0 1px 0 0"| Weekly
|style="border-style: solid; border-width: 0"| #meego-meeting
|}

'''Friday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 0 0"| 07:00
|style="border-style: solid; border-width: 0 1px 0 0"| [[ARM/N900/Browser/Meetings | Meego N900 DE Browser & Wlan team meeting ]]
|style="border-style: solid; border-width: 0 1px 0 0"| Weekly
|style="border-style: solid; border-width: 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 0 0"| 14:00
|style="border-style: solid; border-width: 0 1px 0 0"| [[MeeGo_Apps | MeeGo Apps meeting ]]
|style="border-style: solid; border-width: 0 1px 0 0"| Weekly
|style="border-style: solid; border-width: 0"| #meego-meeting
|}

'''Sunday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-}

== Ad Hoc Meetings ==

Scheduling a one-time meeting? Add it to this section.

* [[MeeGo Apps|MeeGo Apps]] meeting: Friday, 17th of June 2011 at 14:00 UTC

=== Guidelines ===

Please refer to the [[IRC guidelines]] for more details about how to run a MeeGo IRC meeting and using #meego-meeting.

You might also be interested in these [[IRC Presentation Tips]].

Getting started with OBS

2011-06-22T14:16:21Z

Xfade: /* Pre-requisites */

The Meego Online Build System (OBS) seems rather complicated, this page will attempt to make it nice and easy to get started.

It's a work in progress, feel free to add and modify!

=Pre-requisites=

* You need a meego.com login to be able to access the OBS
* You need to be running one of the supported OSes (see list here: http://download.opensuse.org/repositories/openSUSE:/Tools/)

* Install osc (for example, <code>apt-get install osc</code> may work out-of-the-box on recent versions of Ubuntu & Debian, otherwise add a repository for your distro from [http://download.opensuse.org/repositories/openSUSE:/Tools/ openSUSE tools]

=Setting up your home project=

Your home project is like a home directory in which you can create sub-projects, repositories, etc.

* Visit the OBS page (https://build.pub.meego.com)
* Log in and click on 'create home project' (down at the bottom of the page iirc)

=Setting up a sub-project=

* In the overview tab, click on Actions and select "Create subproject".

==Adding files to a sub-project and building them==

From the terminal:
* Checkout your empty project (like SVN)
<code>osc -A https://api.pub.meego.com co home:[username]</code>
* Add files to your local copy
** For Meego this will be a .spec file and a tarball containing your source code, etc.
** For Harmattan this will be a .dsc file, source tarball plus debian.tar.gz (this allows one to keep the debian directory out of the source)
<code>osc -A https://api.pub.meego.com add [filename]</code>
* Commit the files
<code>osc -A https://api.pub.meego.com commit</code>
** At this point the OBS will try to build your project remotely
** To build locally you can do the following: osc build

Using the webinterface:
* Add the correct files as listed above and they will be automatically built for you

Getting started with OBS

2011-06-22T14:13:49Z

Xfade: Add commands

The Meego Online Build System (OBS) seems rather complicated, this page will attempt to make it nice and easy to get started.

It's a work in progress, feel free to add and modify!

=Pre-requisites=

* You need a meego.com login to be able to access the OBS
* You need to be running one of the supported OSes (see list here: http://download.opensuse.org/repositories/openSUSE:/Tools/)

* Install osc (for example, <code>apt-get install osc</code> may work out-of-the-box on recent versions of Ubuntu & Debian)

=Setting up your home project=

Your home project is like a home directory in which you can create sub-projects, repositories, etc.

* Visit the OBS page (https://build.pub.meego.com)
* Log in and click on 'create home project' (down at the bottom of the page iirc)

=Setting up a sub-project=

* In the overview tab, click on Actions and select "Create subproject".

==Adding files to a sub-project and building them==

From the terminal:
* Checkout your empty project (like SVN)
<code>osc -A https://api.pub.meego.com co home:[username]</code>
* Add files to your local copy
** For Meego this will be a .spec file and a tarball containing your source code, etc.
** For Harmattan this will be a .dsc file, source tarball plus debian.tar.gz (this allows one to keep the debian directory out of the source)
<code>osc -A https://api.pub.meego.com add [filename]</code>
* Commit the files
<code>osc -A https://api.pub.meego.com commit</code>
** At this point the OBS will try to build your project remotely
** To build locally you can do the following: osc build

Using the webinterface:
* Add the correct files as listed above and they will be automatically built for you

Build Infrastructure/Community Builder/Installation

2011-06-15T09:58:20Z

Xfade: /* Installing the Workers */

== Preparing Host ==
Starting with a minimal Suse 11.2 install

Most of the commands below can be copied into a shell; so we'll define some base data in shell variables to allow you to customise your setup.
(Yes this could all be one monolithic script or a pre-made VM ... but if you're going to run one of these you should at least get your hands dirty setting it up ;) )
<pre>
ROOTFS=/data/11.2min/image-root
ROUTER_IP=10.0.0.1
VG=VM
</pre>

Based on http://en.opensuse.org/Build_Service/KIWI/Cookbook
<pre>
zypper ar http://download.opensuse.org/repositories/Virtualization:/Appliances/openSUSE_11.2/ Virtualization:Appliances
zypper refresh
</pre>

<pre>
zypper in kiwi kiwi-templates kiwi-desc-xenboot squashfs emacs
</pre>

Prepare the storage for LV usage
<pre>
parted /dev/sdb
mklabel
gpt
yes
mkpart p1 0 10%
mkpart p2 10% 20%
mkpart p3 20% 30%
mkpart p4 30% 40%
mkpart p5 40% 50%
mkpart p6 50% 60%
mkpart p7 60% 70%
mkpart p8 70% 80%
mkpart p9 80% 90%
mkpart p10 90% 100%
quit
</pre>
Then make the VG
<pre>
pvcreate /dev/sdb?*
vgcreate $VG /dev/sdb1
</pre>

Prepare an openSUSE minimal image:
<pre>
mkdir -p /data/11.2min
rm -rf /data/11.2min/image-root
kiwi --prepare suse-11.2-JeOS --root $ROOTFS --add-profile xenFlavour --add-package less --add-package iputils --add-package kernel-xen --add-package wget --add-package less --add-package iputils --add-package terminfo --add-package emacs --add-package sudo
</pre>

Update the config & modules:

<pre>
echo default $ROUTER_IP > $ROOTFS/etc/sysconfig/network/routes
echo NETCONFIG_DNS_POLICY=\"\" >> $ROOTFS/etc/sysconfig/network/config
echo nameserver 8.8.8.8 > $ROOTFS/etc/resolv.conf
echo default $ROUTER_IP > $ROOTFS/etc/sysconfig/network/routes
cat << EOF >$ROOTFS/etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='static'
BROADCAST=''
STARTMODE='onboot'
EOF
echo /dev/xvda1 swap swap defaults 0 0 >> $ROOTFS/etc/fstab
</pre>

Prepare some overlay data from the main host to allow ssh into guests
etc
<pre>
# Allow user ssh to all VMs and retain sudo rights
# Should probably be done periodically somehow
mkdir -p /data/vm_overlay
mkdir -p /data/vm_overlay/etc/sysconfig/
ln /etc/passwd /data/vm_overlay/etc/
ln /etc/shadow /data/vm_overlay/etc/
ln /etc/group /data/vm_overlay/etc/
ln /etc/sudoers /data/vm_overlay/etc/
# Fix for screen/bash ctrl-arrow
ln /etc/inputrc /data/vm_overlay/etc/
# Network proxy information
ln /etc/sysconfig/proxy /data/vm_overlay/etc/sysconfig/
</pre>

(note JeOS 11.2 won't allow su - <user> or ssh when user is disabled using !
in /etc/shadow. Instead use an impossible hash.)

=== Xen Networking ===
Yast is cleverer than you so apparently you should use that... I'm sure if you ask it nicely it will work. Alternatively:

in /etc/xen/xend-config.sxp
{{{
(network-script 'network-bridge netdev=eth0')
}}}
Then
{{{
ln -s /dev/.sysconfig/network/ /dev/shm/sysconfig
}}}
and then
{{{
rcxend restart
}}}

== Useful ==

<pre>
chroot_vm() {
GUEST=$1
xm list | grep "^$GUEST " && echo "$GUEST is running" && return
mkdir /mnt/${GUEST}_chroot/
mount /dev/$VG/${GUEST}_root /mnt/${GUEST}_chroot/ &&
chroot /mnt/${GUEST}_chroot/
umount /mnt/${GUEST}_chroot/
rmdir /mnt/${GUEST}_chroot/
}
</pre>

== VM creation fn/scripts ==

The following function/scripts assume
* a VG exists defined by the env variable $VG
* there is a rootfs at /data/11.2min/image-root/

The scripts look in /etc/hosts for the IP so put appropriate lines in there.

Create Xen volumes
<pre>
mk_lv() {
GUEST=$1
lvremove /dev/$VG/${GUEST}_*
lvcreate -L 10G $VG -n ${GUEST}_root
lvcreate -L 2G $VG -n ${GUEST}_swap
mkswap -f /dev/$VG/${GUEST}_swap
}
</pre>

Copy the minimal image and overlay to the VM root disk and set an IP
<pre>
mk_fs() {
GUEST=$1
IP=$(grep " $GUEST " /etc/hosts | cut -f1 -d" ")
if ! [[ $IP =~ ^[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}$ ]] ; then
echo "No IP for $GUEST in /etc/hosts" && return
fi
echo IP is $IP
mkdir -p /mnt/lvm
echo mkfs &&
mkfs -text4 /dev/$VG/${GUEST}_root &&
echo mounting &&
mount /dev/$VG/${GUEST}_root /mnt/lvm &&
echo copy rootfs &&
rsync -HAXa /data/11.2min/image-root/ /mnt/lvm/ &&
echo copy overlay &&
echo ${GUEST}.meego.com > /mnt/lvm/etc/HOSTNAME &&
echo "IPADDR='$IP/24'" >> /mnt/lvm/etc/sysconfig/network/ifcfg-eth0 &&
rsync -HAXa /data/vm_overlay/ /mnt/lvm/ &&
echo copy home &&
rsync -HAXa /home /mnt/lvm/ &&
echo setup root equivalence to allow root rsync/ssh &&
mkdir /mnt/lvm/root/.ssh &&
chmod 700 /mnt/lvm/root/.ssh &&
cp /root/.ssh/id_rsa.pub /mnt/lvm/root/.ssh/authorized_keys &&
sed -i -e's/^root:.*/root:*:::::::/' /mnt/lvm/etc/shadow &&
echo sync &&
sync &&
echo umount &&
umount /mnt/lvm
}
</pre>

Make per-machine files in /etc/xen/ with unique MACs
Additional LV space can be allocated here too
<pre>
mk_g() {
GUEST=$1
MAC=$2
cat <<EOF > /etc/xen/$GUEST.cfg
name='${GUEST}'
disk=['phy:/dev/$VG/${GUEST}_root,xvda2,w', 'phy:/dev/$VG/${GUEST}_swap,xvda1,w']
vif=['mac=$MAC, bridge=eth0']
memory='2048'

root='/dev/xvda2 rw'
kernel='/boot/vmlinuz-2.6.31.12-0.2-xen'
ramdisk='/boot/initrd-2.6.31.12-0.2-xen'
extra='clocksource=jiffies console=hvc0 xencons=tty'

on_poweroff='destroy'
on_reboot='restart'
on_crash='restart'
EOF
}
</pre>

== Create The VMs ==

On the appropriate xen host, make sure you add the machines to
/etc/hosts and setup the base data environment:
<pre>
VG=VM
</pre>

<pre>
mk_lv cfe
mk_lv cbe
mk_lv cstore
mk_lv csign
</pre>

<pre>
mk_fs cfe
mk_fs cbe
mk_fs cstore
mk_fs csign
</pre>

<pre>
mk_g cfe 00:16:3E:40:B5:FE
mk_g cbe 00:16:3E:40:B5:BE
mk_g cstore 00:16:3E:40:B5:5E
mk_g csign 00:16:3E:40:51:64
</pre>

Then start the VMs:
<pre>
xm create /etc/xen/cfe.cfg
xm create /etc/xen/cbe.cfg
</pre>

== Installing the Backend ==

On this guest we need also to setup openSUSE Tools repository:

<pre>
cd /etc/zypp/repos.d/;
zypper ar http://download.opensuse.org/repositories/Maemo:/MeeGo-Infra:/OBS/Tools_Unstable_openSUSE_11.2/Maemo:MeeGo-Infra:OBS.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUSE_11.2/openSUSE:Tools:Unstable.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key
<pre>
Install:
<pre>
zypper in obs-server obs-signer obs-utils createrepo dpkg lighttpd
</pre>

<pre>
nano /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 armv5el armv7el"
</pre>

Now /usr/lib/obs/server/BSConfig.pm needs to point to correct server names corresponding to source server, where workers are going to download the source, and the repository server, where RPM repos are going to be shared to users.

What's needed here?????????
<pre>
nano /usr/lib/obs/server/BSConfig.pm
#add
our $srcserver = "http://csrc:5352";
our $reposerver = "http://cbe:5252";
our $serviceserver = "http://csrc:5152";
our $servicedir = "/usr/lib/obs/service/";
our $repodownload = "http://crepo.meego.com";
our @reposervers = ("http://cbe:5252");
our $stageserver = 'rsync://obsrun@cdownload/repo';
#
</pre>

Configure services as daemons

<pre>
chkconfig --add obsrepserver obsscheduler obsdispatcher obspublisher obswarden obssigner
</pre>

Start Services
<pre>
rcobsrepserver start
rcobsscheduler start
rcobsdispatcher start
rcobspublisher start
rcobswarden start
rcobssigner start
</pre>
Not started
<pre>
rcobsservice
</pre>

=== Lighttpd ===

lighttpd also needs to be available on backend server. This is required to provide directory listing on the repositories available on this server when an http/s request to maemo-repo is made through web ui.

Create a new file under /etc/lighttpd/vhosts.d/. It can be obs.conf as well, and add:

<pre>
nano /etc/lighttpd/vhosts.d/obs.conf

$HTTP["host"] =~ "crepo.meego.com" {
server.name = "crepo.meego.com"

server.document-root = "/srv/obs/repos/"
dir-listing.activate = "enable"
}
</pre>

To enable vhosts, remember to uncomment the following in the 'custom includes':

<pre>
nano /etc/lighttpd/lighttpd.conf
##
## custom includes like vhosts.
##
#include "conf.d/config.conf"
# following line uncommented as per
# /usr/share/doc/packages/obs-api/README.SETUP
include_shell "cat vhosts.d/*.conf"
</pre>
And disable ipv6 unless it's secured correctly
<pre>
server.use-ipv6 = "disable"
</pre>
Start lighttpd

<pre>
#first add it as deamon
chkconfig --add lighttpd
rclighttpd start
</pre>

=== Prepare repository imports ===
<pre>
mkdir -p /srv/obs/build/MeeGo:current:Handset/standard/armv5el
mkdir -p /srv/obs/build/MeeGo:current:Handset/standard/armv7el
mkdir -p /srv/obs/build/MeeGo:current:Handset/standard/i586
mkdir -p /srv/obs/build/MeeGo:current:IVI/standard/i586
mkdir -p /srv/obs/build/MeeGo:current:IVI/standard/armv5el
mkdir -p /srv/obs/build/MeeGo:current:IVI/standard/armv7el
mkdir -p /srv/obs/build/MeeGo:current:Netbook/standard/armv7el
mkdir -p /srv/obs/build/MeeGo:current:Netbook/standard/armv5el
mkdir -p /srv/obs/build/MeeGo:current:Netbook/standard/i586

chown -R obsrun:obsrun /srv/obs/build/MeeGo:current:Handset
chown -R obsrun:obsrun /srv/obs/build/MeeGo:current:IVI
chown -R obsrun:obsrun /srv/obs/build/MeeGo:current:Netbook

ln -s /data/mirror/meego-current/current\:Handset/armv5l_full/ /srv/obs/build/MeeGo\:current\:Handset/standard/armv5el/\:full
ln -s /data/mirror/meego-current/current\:Handset/armv7l_full/ /srv/obs/build/MeeGo\:current\:Handset/standard/armv7el/\:full
ln -s /data/mirror/meego-current/current\:Handset/i586_full/ /srv/obs/build/MeeGo\:current\:Handset/standard/i586/\:full

ln -s /data/mirror/meego-current/current\:IVI/armv5l_full/ /srv/obs/build/MeeGo\:current\:IVI/standard/armv5el/\:full
ln -s /data/mirror/meego-current/current\:IVI/armv7l_full/ /srv/obs/build/MeeGo\:current\:IVI/standard/armv7el/\:full
ln -s /data/mirror/meego-current/current\:IVI/i586_full/ /srv/obs/build/MeeGo\:current\:IVI/standard/i586/\:full

ln -s /data/mirror/meego-current/current\:Netbook/armv5l_full/ /srv/obs/build/MeeGo\:current\:Netbook/standard/armv5el/\:full
ln -s /data/mirror/meego-current/current\:Netbook/armv7l_full/ /srv/obs/build/MeeGo\:current\:Netbook/standard/armv7el/\:full
ln -s /data/mirror/meego-current/current\:Netbook/i586_full/ /srv/obs/build/MeeGo\:current\:Netbook/standard/i586/\:full
</pre>

== Installing the Storage node ==

On this guest we need also to setup openSUSE Tools repository:

<pre>
cd /etc/zypp/repos.d/;
zypper ar http://download.opensuse.org/repositories/Maemo:/MeeGo-Infra:/OBS/Tools_Unstable_openSUSE_11.2/Maemo:MeeGo-Infra:OBS.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUSE_11.2/openSUSE:Tools:Unstable.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key
<pre>
Install:
<pre>
zypper in obs-server obs-source_service
</pre>

<pre>
nano /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 armv5el armv7el"
</pre>

Now /usr/lib/obs/server/BSConfig.pm needs to point to correct server names corresponding to source server, where workers are going to download the source, and the repository server, where RPM repos are going to be shared to users.

What's needed here?????????
<pre>
nano /usr/lib/obs/server/BSConfig.pm
#add

our $srcserver = "http://csrc:5352";
our $reposerver = "http://cbe:5252";
our $serviceserver = "http://csrc:5152";
our $servicedir = "/usr/lib/obs/service/";
our $repodownload = "http://crepo.meego.com";
our @reposervers = ("http://cbe:5252");

#
</pre>

Configure services as daemons

<pre>
chkconfig --add obssrcserver obsservice
</pre>

Start Services
<pre>
rcobssrcserver start
rcobsservice start
</pre>

== Installing the Frontend ==

On this guest we need also to setup openSUSE Tools repository:

<pre>
cd /etc/zypp/repos.d/;
zypper ar http://download.opensuse.org/repositories/Maemo:/MeeGo-Infra:/OBS/Tools_Unstable_openSUSE_11.2/Maemo:MeeGo-Infra:OBS.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUSE_11.2/openSUSE:Tools:Unstable.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key
<pre>

Install obs-api (It's going to install lighttpd webserver by dependency for you).
<pre>
zypper in obs-api memcached
</pre>

=== Setup MySQL ===

MySQL server needs to be installed and configured to start as daemon

<pre>
chkconfig --add mysql
rcmysql start
</pre>

Setup a secure installation, if it's the first time starting MySQL

<pre>
/usr/bin/mysql_secure_installation
</pre>

<pre>
touch /root/.my.cnf
chmod 0600 /root/.my.cnf
nano /root/.my.cnf

[client]
user = root
password = <PASSWORD>
[mysqladmin]
user= root
password = <PASSWORD>
</pre>

The frontend instance holds 2 applications, the API and the webui. Each one need a database created

<pre>
mysql -u root -p
create database api_production;
create database webui_production;
</pre>

Add obs user to handle these databases
<pre>
GRANT all privileges
ON api_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
GRANT all privileges
ON webui_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
FLUSH PRIVILEGES;
</pre>

Now secure the passwd storing config files
<pre>
touch /srv/www/obs/api/config/database.yml
touch /srv/www/obs/webui/config/database.yml
chmod 600 /srv/www/obs/api/config/database.yml
chmod 600 /srv/www/obs/webui/config/database.yml
chown lighttpd /srv/www/obs/api/config/database.yml
chown lighttpd /srv/www/obs/webui/config/database.yml
</pre>

Configure your MySQL user and password in the "production:" section of the API config:
<pre>
nano /srv/www/obs/api/config/database.yml
#change the production section
production:
adapter: mysql
database: api_production
username: obs
password: ************
</pre>

Do the same for the webui. It's configured, by default to use SQLite, but since we're configuring the cluster for production environment, let's bind it to mysql:
<pre>
nano /srv/www/obs/webui/config/database.yml
#change the production section
production:
adapter: mysql
database: webui_production
username: obs
password: ************
</pre>

Populate the database
<pre>
mkdir -p /srv/www/obs/api/db/data/production
cd /srv/www/obs/api/
RAILS_ENV="production" rake db:migrate
chown lighttpd.lighttpd log/*

cd /srv/www/obs/webui/
RAILS_ENV="production" rake db:migrate
chown lighttpd.lighttpd log/*
</pre>

You can check the migration was successful verifying the “migrated” message at the end of each statement.

Setup and configure lighttpd for the API and webui

You need to setup the correct hostnames to where webui, API and repo server are going to point to

Edit /etc/lighttpd/vhosts.d/obs.conf
<pre>
$SERVER["socket"] == "192.168.60.100:443" {
ssl.engine = "enable"
ssl.pemfile = "certificate.pem"
$HTTP["host"] =~ "^cbuild" {
server.name = "cbuild.meego.com"

rails_app = "webui"
rails_root = "/srv/www/obs/webui"
rails_procs = 10
# production/development are typical values here
rails_mode = "production"

log_root = "/srv/www/obs/webui/log"

include "vhosts.d/rails.inc"
}
$HTTP["host"] =~ "^capi" {
server.name = "capi.meego.com"
rails_app = "api"
rails_root = "/srv/www/obs/api"
rails_procs = 10
# production/development are typical values here
rails_mode = "production"

log_root = "/srv/www/obs/api/log"

include "vhosts.d/rails.inc"
}

}

$HTTP["host"] =~ "download" {
# This should point to an rsync populated download repo
# server.name = "download.obs.maemo.org"
# server.document-root = "/srv/obs/repos/"

proxy.server = ( "" => ( (
"host" => "10.1.1.11",
"port" => 80
))
)
}
</pre>

To enable these vhosts, make sure to '''uncomment''' the following in the 'custom includes' section at the bottom of /etc/lighttpd/lighttpd.conf:
<pre>
nano /etc/lighttpd/lighttpd.conf
##
## custom includes like vhosts.
##
#include "conf.d/config.conf"
include_shell "cat /etc/lighttpd/vhosts.d/*.conf"
</pre>

Also need to disable IPv6 unkess it's secured
<pre>
server.use-ipv6 = "disable"
</pre>

Also, the modules "mod_magnet", "mod_rewrite" and FastCGI need to be enabled by uncommenting the corresponding lines in /etc/lighttpd/modules.conf:

<pre>
server.modules = (
"mod_access",
# "mod_alias",
# "mod_auth",
# "mod_evasive",
# "mod_redirect",
"mod_rewrite",
# "mod_setenv",
# "mod_usertrack",
)

##
## mod_magnet
##
include "conf.d/magnet.conf"

##
## FastCGI (mod_fastcgi)
##
include "conf.d/fastcgi.conf"
</pre>

You need also to configure /srv/www/obs/webui/config/environments/production.rb to point to correct server names:

<pre>
nano /srv/www/obs/webui/config/environments/production.rb
FRONTEND_HOST = "capi.meego.com"
FRONTEND_PORT = 80
EXTERNAL_FRONTEND_HOST = "capi.meego.com"
BUGZILLA_HOST = "http://bugs.moego.com/"
DOWNLOAD_URL = "http://cdownload.meego.com/"
</pre>

Do the same for /srv/www/obs/api/config/environments/production.rb. As soon your backend is not on the same machine as the api (frontend), change the following:

<pre>
nano /srv/www/obs/api/config/environments/production.rb
SOURCE_HOST = "csrc.meego.com"
SOURCE_PORT = 5352
DOWNLOAD_URL='http://cdownload.meego.com/'
</pre>

ligthttpd user and group need to be the owner of api and webui dirs (as well as log and tmp):

<pre>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</pre>

Make sure TCP port 5352 is open on the firewall. Ensure lighttpd and obs ui helpers start:

<pre>
chkconfig --add memcached
chkconfig --add lighttpd
chkconfig --add obsapidelayed
chkconfig --add obswebuidelayed

rcmemcached start
rclighttpd start
rcobsapidelayed start
rcobswebuidelayed start
</pre>

rcobsapidelayed

= Preparing Worker Host =

<pre>
vgadd OBS /dev/sda4
vgcreate OBS /dev/sda4
</pre>

== Installing the Workers ==

The other hosts on the cluster are reserved to be used as workers,
where package builds are going to place.

The same openSUSE Tools repository addition must be done for each worker.
<pre>
cd /etc/zypp/repos.d/;
zypper ar http://download.opensuse.org/repositories/Maemo:/MeeGo-Infra:/OBS/Tools_Unstable_openSUSE_11.2/Maemo:MeeGo-Infra:OBS.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUSE_11.2/openSUSE:Tools:Unstable.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key.
</pre>

<pre>
zypper in obs-worker qemu-devel mount-static bash-static
</pre>

(mount-static and bash-static are needed on the worker for rpm cross-compile to work)

For Xen workers we need a suitable initrd:
<pre>
export rootfstype="ext4"
mkinitrd -d /dev/null -m "ext4 binfmt_misc" -k vmlinuz-$(uname -r) -i initrd-$(uname -r)-obs_worker
</pre>
This will create an initrd for your kernel
<pre>
Kernel image: /boot/vmlinuz-2.6.31.12-0.2-xen
Initrd image: /boot/initrd-2.6.31.12-0.2-xen-obs_worker
</pre>
Make sure you link initrd-xen-worker -> initrd-2.6.31.12-0.2-xen-obs_worker
<pre>
ln -s /boot/initrd-$(uname -r)-obs_worker /boot/initrd-xen-worker
ln -s vmlinuz-$(uname -r) vmlinuz-xen-worker
</pre>

This assumes you have a VG dedicated to workers called "OBS"

Edit the file /etc/sysconfig/obs-worker in order to point to correct repository server.

<pre>
nano /etc/sysconfig/obs-worker
OBS_SRC_SERVER="csrc:5352"
OBS_REPO_SERVERS="cbe:5252"
OBS_VM_TYPE="xen"
OBS_VM_KERNEL="/boot/vmlinuz-xen-worker"
OBS_VM_INITRD="/boot/initrd-xen-worker"
OBS_VM_DISK_AUTOSETUP_ROOT_FILESIZE="8192"
OBS_VM_DISK_AUTOSETUP_SWAP_FILESIZE="2048"
OBS_INSTANCE_MEMORY="1024"
OBS_STORAGE_AUTOSETUP="yes"
OBS_SETUP_WORKER_PARTITIONS="use_obs_vg"
OBS_WORKER_ROOT_SIZE="8192"
OBS_WORKER_SWAP_SIZE="2048"
</pre>

Note that the OBS_VM_KERNEL/INITRD params are for kvm only. The Xen VM pulls in /usr/lib/build/xen.conf from the repo master (backend server, cbe). It does this

The obsstoragesetup will wipe the OBS VG and create root/swap LVs for each worker
<pre>
rcobsstoragesetup start
</pre>

Output:
<pre>
mdadm: No arrays found in config file or automatically
Waiting for udev to settle...
Scanning for LVM volume groups...
Reading all physical volumes. This may take a while...
Found volume group "OBS" using metadata type lvm2
Activating LVM volume groups...
0 logical volume(s) in volume group "OBS" now active
done
Logical volume "worker_root_1" created
Logical volume "worker_swap_1" created
Logical volume "worker_root_2" created
Logical volume "worker_swap_2" created
Logical volume "worker_root_3" created
Logical volume "worker_swap_3" created
Logical volume "worker_root_4" created
Logical volume "worker_swap_4" created
Logical volume "worker_root_5" created
Logical volume "worker_swap_5" created
Logical volume "worker_root_6" created
Logical volume "worker_swap_6" created
Logical volume "worker_root_7" created
Logical volume "worker_swap_7" created
Logical volume "worker_root_8" created
Logical volume "worker_swap_8" created
Logical volume "worker_root_9" created
Logical volume "worker_swap_9" created
Logical volume "worker_root_10" created
Logical volume "worker_swap_10" created
Logical volume "worker_root_11" created
Logical volume "worker_swap_11" created
Logical volume "worker_root_12" created
Logical volume "worker_swap_12" created
Logical volume "worker_root_13" created
Logical volume "worker_swap_13" created
Logical volume "worker_root_14" created
Logical volume "worker_swap_14" created
Logical volume "worker_root_15" created
Logical volume "worker_swap_15" created
Logical volume "worker_root_16" created
Logical volume "worker_swap_16" created
Logical volume "cache" created
mke2fs 1.41.9 (22-Aug-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
3555328 inodes, 14201856 blocks
710092 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
434 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Looking for OBS Server LVM Volume
Setup local storage
Looking for OBS Worker Cache LVM Volume
Setting up OBS Workers according to LVM Volumes
Found XEN virtualization
done
</pre>

Test?
<pre>
xm create -c /var/run/obs/worker/8/build/xen.conf name=build:root8 memory=40 disk=phy:/dev/mapper/OBS-worker_root8,hda1,w disk=phy:/dev/mapper/OBS-worker_swap8,hda2,w extra="init=/.build/initscript_qemu_vm panic=1 console=ttyS0
</pre>

Start the worker service:

<pre>
chkconfig --add obsworker
rcobsworker start
</pre>

[[Category:Build Infrastructure]]

Build Infrastructure/Community Builder/Installation

2011-06-15T09:40:39Z

Xfade: Update worker install

== Preparing Host ==
Starting with a minimal Suse 11.2 install

Most of the commands below can be copied into a shell; so we'll define some base data in shell variables to allow you to customise your setup.
(Yes this could all be one monolithic script or a pre-made VM ... but if you're going to run one of these you should at least get your hands dirty setting it up ;) )
<pre>
ROOTFS=/data/11.2min/image-root
ROUTER_IP=10.0.0.1
VG=VM
</pre>

Based on http://en.opensuse.org/Build_Service/KIWI/Cookbook
<pre>
zypper ar http://download.opensuse.org/repositories/Virtualization:/Appliances/openSUSE_11.2/ Virtualization:Appliances
zypper refresh
</pre>

<pre>
zypper in kiwi kiwi-templates kiwi-desc-xenboot squashfs emacs
</pre>

Prepare the storage for LV usage
<pre>
parted /dev/sdb
mklabel
gpt
yes
mkpart p1 0 10%
mkpart p2 10% 20%
mkpart p3 20% 30%
mkpart p4 30% 40%
mkpart p5 40% 50%
mkpart p6 50% 60%
mkpart p7 60% 70%
mkpart p8 70% 80%
mkpart p9 80% 90%
mkpart p10 90% 100%
quit
</pre>
Then make the VG
<pre>
pvcreate /dev/sdb?*
vgcreate $VG /dev/sdb1
</pre>

Prepare an openSUSE minimal image:
<pre>
mkdir -p /data/11.2min
rm -rf /data/11.2min/image-root
kiwi --prepare suse-11.2-JeOS --root $ROOTFS --add-profile xenFlavour --add-package less --add-package iputils --add-package kernel-xen --add-package wget --add-package less --add-package iputils --add-package terminfo --add-package emacs --add-package sudo
</pre>

Update the config & modules:

<pre>
echo default $ROUTER_IP > $ROOTFS/etc/sysconfig/network/routes
echo NETCONFIG_DNS_POLICY=\"\" >> $ROOTFS/etc/sysconfig/network/config
echo nameserver 8.8.8.8 > $ROOTFS/etc/resolv.conf
echo default $ROUTER_IP > $ROOTFS/etc/sysconfig/network/routes
cat << EOF >$ROOTFS/etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='static'
BROADCAST=''
STARTMODE='onboot'
EOF
echo /dev/xvda1 swap swap defaults 0 0 >> $ROOTFS/etc/fstab
</pre>

Prepare some overlay data from the main host to allow ssh into guests
etc
<pre>
# Allow user ssh to all VMs and retain sudo rights
# Should probably be done periodically somehow
mkdir -p /data/vm_overlay
mkdir -p /data/vm_overlay/etc/sysconfig/
ln /etc/passwd /data/vm_overlay/etc/
ln /etc/shadow /data/vm_overlay/etc/
ln /etc/group /data/vm_overlay/etc/
ln /etc/sudoers /data/vm_overlay/etc/
# Fix for screen/bash ctrl-arrow
ln /etc/inputrc /data/vm_overlay/etc/
# Network proxy information
ln /etc/sysconfig/proxy /data/vm_overlay/etc/sysconfig/
</pre>

(note JeOS 11.2 won't allow su - <user> or ssh when user is disabled using !
in /etc/shadow. Instead use an impossible hash.)

=== Xen Networking ===
Yast is cleverer than you so apparently you should use that... I'm sure if you ask it nicely it will work. Alternatively:

in /etc/xen/xend-config.sxp
{{{
(network-script 'network-bridge netdev=eth0')
}}}
Then
{{{
ln -s /dev/.sysconfig/network/ /dev/shm/sysconfig
}}}
and then
{{{
rcxend restart
}}}

== Useful ==

<pre>
chroot_vm() {
GUEST=$1
xm list | grep "^$GUEST " && echo "$GUEST is running" && return
mkdir /mnt/${GUEST}_chroot/
mount /dev/$VG/${GUEST}_root /mnt/${GUEST}_chroot/ &&
chroot /mnt/${GUEST}_chroot/
umount /mnt/${GUEST}_chroot/
rmdir /mnt/${GUEST}_chroot/
}
</pre>

== VM creation fn/scripts ==

The following function/scripts assume
* a VG exists defined by the env variable $VG
* there is a rootfs at /data/11.2min/image-root/

The scripts look in /etc/hosts for the IP so put appropriate lines in there.

Create Xen volumes
<pre>
mk_lv() {
GUEST=$1
lvremove /dev/$VG/${GUEST}_*
lvcreate -L 10G $VG -n ${GUEST}_root
lvcreate -L 2G $VG -n ${GUEST}_swap
mkswap -f /dev/$VG/${GUEST}_swap
}
</pre>

Copy the minimal image and overlay to the VM root disk and set an IP
<pre>
mk_fs() {
GUEST=$1
IP=$(grep " $GUEST " /etc/hosts | cut -f1 -d" ")
if ! [[ $IP =~ ^[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}$ ]] ; then
echo "No IP for $GUEST in /etc/hosts" && return
fi
echo IP is $IP
mkdir -p /mnt/lvm
echo mkfs &&
mkfs -text4 /dev/$VG/${GUEST}_root &&
echo mounting &&
mount /dev/$VG/${GUEST}_root /mnt/lvm &&
echo copy rootfs &&
rsync -HAXa /data/11.2min/image-root/ /mnt/lvm/ &&
echo copy overlay &&
echo ${GUEST}.meego.com > /mnt/lvm/etc/HOSTNAME &&
echo "IPADDR='$IP/24'" >> /mnt/lvm/etc/sysconfig/network/ifcfg-eth0 &&
rsync -HAXa /data/vm_overlay/ /mnt/lvm/ &&
echo copy home &&
rsync -HAXa /home /mnt/lvm/ &&
echo setup root equivalence to allow root rsync/ssh &&
mkdir /mnt/lvm/root/.ssh &&
chmod 700 /mnt/lvm/root/.ssh &&
cp /root/.ssh/id_rsa.pub /mnt/lvm/root/.ssh/authorized_keys &&
sed -i -e's/^root:.*/root:*:::::::/' /mnt/lvm/etc/shadow &&
echo sync &&
sync &&
echo umount &&
umount /mnt/lvm
}
</pre>

Make per-machine files in /etc/xen/ with unique MACs
Additional LV space can be allocated here too
<pre>
mk_g() {
GUEST=$1
MAC=$2
cat <<EOF > /etc/xen/$GUEST.cfg
name='${GUEST}'
disk=['phy:/dev/$VG/${GUEST}_root,xvda2,w', 'phy:/dev/$VG/${GUEST}_swap,xvda1,w']
vif=['mac=$MAC, bridge=eth0']
memory='2048'

root='/dev/xvda2 rw'
kernel='/boot/vmlinuz-2.6.31.12-0.2-xen'
ramdisk='/boot/initrd-2.6.31.12-0.2-xen'
extra='clocksource=jiffies console=hvc0 xencons=tty'

on_poweroff='destroy'
on_reboot='restart'
on_crash='restart'
EOF
}
</pre>

== Create The VMs ==

On the appropriate xen host, make sure you add the machines to
/etc/hosts and setup the base data environment:
<pre>
VG=VM
</pre>

<pre>
mk_lv cfe
mk_lv cbe
mk_lv cstore
mk_lv csign
</pre>

<pre>
mk_fs cfe
mk_fs cbe
mk_fs cstore
mk_fs csign
</pre>

<pre>
mk_g cfe 00:16:3E:40:B5:FE
mk_g cbe 00:16:3E:40:B5:BE
mk_g cstore 00:16:3E:40:B5:5E
mk_g csign 00:16:3E:40:51:64
</pre>

Then start the VMs:
<pre>
xm create /etc/xen/cfe.cfg
xm create /etc/xen/cbe.cfg
</pre>

== Installing the Backend ==

On this guest we need also to setup openSUSE Tools repository:

<pre>
cd /etc/zypp/repos.d/;
zypper ar http://download.opensuse.org/repositories/Maemo:/MeeGo-Infra:/OBS/Tools_Unstable_openSUSE_11.2/Maemo:MeeGo-Infra:OBS.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUSE_11.2/openSUSE:Tools:Unstable.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key
<pre>
Install:
<pre>
zypper in obs-server obs-signer obs-utils createrepo dpkg lighttpd
</pre>

<pre>
nano /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 armv5el armv7el"
</pre>

Now /usr/lib/obs/server/BSConfig.pm needs to point to correct server names corresponding to source server, where workers are going to download the source, and the repository server, where RPM repos are going to be shared to users.

What's needed here?????????
<pre>
nano /usr/lib/obs/server/BSConfig.pm
#add
our $srcserver = "http://csrc:5352";
our $reposerver = "http://cbe:5252";
our $serviceserver = "http://csrc:5152";
our $servicedir = "/usr/lib/obs/service/";
our $repodownload = "http://crepo.meego.com";
our @reposervers = ("http://cbe:5252");
our $stageserver = 'rsync://obsrun@cdownload/repo';
#
</pre>

Configure services as daemons

<pre>
chkconfig --add obsrepserver obsscheduler obsdispatcher obspublisher obswarden obssigner
</pre>

Start Services
<pre>
rcobsrepserver start
rcobsscheduler start
rcobsdispatcher start
rcobspublisher start
rcobswarden start
rcobssigner start
</pre>
Not started
<pre>
rcobsservice
</pre>

=== Lighttpd ===

lighttpd also needs to be available on backend server. This is required to provide directory listing on the repositories available on this server when an http/s request to maemo-repo is made through web ui.

Create a new file under /etc/lighttpd/vhosts.d/. It can be obs.conf as well, and add:

<pre>
nano /etc/lighttpd/vhosts.d/obs.conf

$HTTP["host"] =~ "crepo.meego.com" {
server.name = "crepo.meego.com"

server.document-root = "/srv/obs/repos/"
dir-listing.activate = "enable"
}
</pre>

To enable vhosts, remember to uncomment the following in the 'custom includes':

<pre>
nano /etc/lighttpd/lighttpd.conf
##
## custom includes like vhosts.
##
#include "conf.d/config.conf"
# following line uncommented as per
# /usr/share/doc/packages/obs-api/README.SETUP
include_shell "cat vhosts.d/*.conf"
</pre>
And disable ipv6 unless it's secured correctly
<pre>
server.use-ipv6 = "disable"
</pre>
Start lighttpd

<pre>
#first add it as deamon
chkconfig --add lighttpd
rclighttpd start
</pre>

=== Prepare repository imports ===
<pre>
mkdir -p /srv/obs/build/MeeGo:current:Handset/standard/armv5el
mkdir -p /srv/obs/build/MeeGo:current:Handset/standard/armv7el
mkdir -p /srv/obs/build/MeeGo:current:Handset/standard/i586
mkdir -p /srv/obs/build/MeeGo:current:IVI/standard/i586
mkdir -p /srv/obs/build/MeeGo:current:IVI/standard/armv5el
mkdir -p /srv/obs/build/MeeGo:current:IVI/standard/armv7el
mkdir -p /srv/obs/build/MeeGo:current:Netbook/standard/armv7el
mkdir -p /srv/obs/build/MeeGo:current:Netbook/standard/armv5el
mkdir -p /srv/obs/build/MeeGo:current:Netbook/standard/i586

chown -R obsrun:obsrun /srv/obs/build/MeeGo:current:Handset
chown -R obsrun:obsrun /srv/obs/build/MeeGo:current:IVI
chown -R obsrun:obsrun /srv/obs/build/MeeGo:current:Netbook

ln -s /data/mirror/meego-current/current\:Handset/armv5l_full/ /srv/obs/build/MeeGo\:current\:Handset/standard/armv5el/\:full
ln -s /data/mirror/meego-current/current\:Handset/armv7l_full/ /srv/obs/build/MeeGo\:current\:Handset/standard/armv7el/\:full
ln -s /data/mirror/meego-current/current\:Handset/i586_full/ /srv/obs/build/MeeGo\:current\:Handset/standard/i586/\:full

ln -s /data/mirror/meego-current/current\:IVI/armv5l_full/ /srv/obs/build/MeeGo\:current\:IVI/standard/armv5el/\:full
ln -s /data/mirror/meego-current/current\:IVI/armv7l_full/ /srv/obs/build/MeeGo\:current\:IVI/standard/armv7el/\:full
ln -s /data/mirror/meego-current/current\:IVI/i586_full/ /srv/obs/build/MeeGo\:current\:IVI/standard/i586/\:full

ln -s /data/mirror/meego-current/current\:Netbook/armv5l_full/ /srv/obs/build/MeeGo\:current\:Netbook/standard/armv5el/\:full
ln -s /data/mirror/meego-current/current\:Netbook/armv7l_full/ /srv/obs/build/MeeGo\:current\:Netbook/standard/armv7el/\:full
ln -s /data/mirror/meego-current/current\:Netbook/i586_full/ /srv/obs/build/MeeGo\:current\:Netbook/standard/i586/\:full
</pre>

== Installing the Storage node ==

On this guest we need also to setup openSUSE Tools repository:

<pre>
cd /etc/zypp/repos.d/;
zypper ar http://download.opensuse.org/repositories/Maemo:/MeeGo-Infra:/OBS/Tools_Unstable_openSUSE_11.2/Maemo:MeeGo-Infra:OBS.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUSE_11.2/openSUSE:Tools:Unstable.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key
<pre>
Install:
<pre>
zypper in obs-server obs-source_service
</pre>

<pre>
nano /etc/sysconfig/obs-server
OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 armv5el armv7el"
</pre>

Now /usr/lib/obs/server/BSConfig.pm needs to point to correct server names corresponding to source server, where workers are going to download the source, and the repository server, where RPM repos are going to be shared to users.

What's needed here?????????
<pre>
nano /usr/lib/obs/server/BSConfig.pm
#add

our $srcserver = "http://csrc:5352";
our $reposerver = "http://cbe:5252";
our $serviceserver = "http://csrc:5152";
our $servicedir = "/usr/lib/obs/service/";
our $repodownload = "http://crepo.meego.com";
our @reposervers = ("http://cbe:5252");

#
</pre>

Configure services as daemons

<pre>
chkconfig --add obssrcserver obsservice
</pre>

Start Services
<pre>
rcobssrcserver start
rcobsservice start
</pre>

== Installing the Frontend ==

On this guest we need also to setup openSUSE Tools repository:

<pre>
cd /etc/zypp/repos.d/;
zypper ar http://download.opensuse.org/repositories/Maemo:/MeeGo-Infra:/OBS/Tools_Unstable_openSUSE_11.2/Maemo:MeeGo-Infra:OBS.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUSE_11.2/openSUSE:Tools:Unstable.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key
<pre>

Install obs-api (It's going to install lighttpd webserver by dependency for you).
<pre>
zypper in obs-api memcached
</pre>

=== Setup MySQL ===

MySQL server needs to be installed and configured to start as daemon

<pre>
chkconfig --add mysql
rcmysql start
</pre>

Setup a secure installation, if it's the first time starting MySQL

<pre>
/usr/bin/mysql_secure_installation
</pre>

<pre>
touch /root/.my.cnf
chmod 0600 /root/.my.cnf
nano /root/.my.cnf

[client]
user = root
password = <PASSWORD>
[mysqladmin]
user= root
password = <PASSWORD>
</pre>

The frontend instance holds 2 applications, the API and the webui. Each one need a database created

<pre>
mysql -u root -p
create database api_production;
create database webui_production;
</pre>

Add obs user to handle these databases
<pre>
GRANT all privileges
ON api_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
GRANT all privileges
ON webui_production.*
TO 'obs'@'%', 'obs'@'localhost' IDENTIFIED BY '************';
FLUSH PRIVILEGES;
</pre>

Now secure the passwd storing config files
<pre>
touch /srv/www/obs/api/config/database.yml
touch /srv/www/obs/webui/config/database.yml
chmod 600 /srv/www/obs/api/config/database.yml
chmod 600 /srv/www/obs/webui/config/database.yml
chown lighttpd /srv/www/obs/api/config/database.yml
chown lighttpd /srv/www/obs/webui/config/database.yml
</pre>

Configure your MySQL user and password in the "production:" section of the API config:
<pre>
nano /srv/www/obs/api/config/database.yml
#change the production section
production:
adapter: mysql
database: api_production
username: obs
password: ************
</pre>

Do the same for the webui. It's configured, by default to use SQLite, but since we're configuring the cluster for production environment, let's bind it to mysql:
<pre>
nano /srv/www/obs/webui/config/database.yml
#change the production section
production:
adapter: mysql
database: webui_production
username: obs
password: ************
</pre>

Populate the database
<pre>
mkdir -p /srv/www/obs/api/db/data/production
cd /srv/www/obs/api/
RAILS_ENV="production" rake db:migrate
chown lighttpd.lighttpd log/*

cd /srv/www/obs/webui/
RAILS_ENV="production" rake db:migrate
chown lighttpd.lighttpd log/*
</pre>

You can check the migration was successful verifying the “migrated” message at the end of each statement.

Setup and configure lighttpd for the API and webui

You need to setup the correct hostnames to where webui, API and repo server are going to point to

Edit /etc/lighttpd/vhosts.d/obs.conf
<pre>
$SERVER["socket"] == "192.168.60.100:443" {
ssl.engine = "enable"
ssl.pemfile = "certificate.pem"
$HTTP["host"] =~ "^cbuild" {
server.name = "cbuild.meego.com"

rails_app = "webui"
rails_root = "/srv/www/obs/webui"
rails_procs = 10
# production/development are typical values here
rails_mode = "production"

log_root = "/srv/www/obs/webui/log"

include "vhosts.d/rails.inc"
}
$HTTP["host"] =~ "^capi" {
server.name = "capi.meego.com"
rails_app = "api"
rails_root = "/srv/www/obs/api"
rails_procs = 10
# production/development are typical values here
rails_mode = "production"

log_root = "/srv/www/obs/api/log"

include "vhosts.d/rails.inc"
}

}

$HTTP["host"] =~ "download" {
# This should point to an rsync populated download repo
# server.name = "download.obs.maemo.org"
# server.document-root = "/srv/obs/repos/"

proxy.server = ( "" => ( (
"host" => "10.1.1.11",
"port" => 80
))
)
}
</pre>

To enable these vhosts, make sure to '''uncomment''' the following in the 'custom includes' section at the bottom of /etc/lighttpd/lighttpd.conf:
<pre>
nano /etc/lighttpd/lighttpd.conf
##
## custom includes like vhosts.
##
#include "conf.d/config.conf"
include_shell "cat /etc/lighttpd/vhosts.d/*.conf"
</pre>

Also need to disable IPv6 unkess it's secured
<pre>
server.use-ipv6 = "disable"
</pre>

Also, the modules "mod_magnet", "mod_rewrite" and FastCGI need to be enabled by uncommenting the corresponding lines in /etc/lighttpd/modules.conf:

<pre>
server.modules = (
"mod_access",
# "mod_alias",
# "mod_auth",
# "mod_evasive",
# "mod_redirect",
"mod_rewrite",
# "mod_setenv",
# "mod_usertrack",
)

##
## mod_magnet
##
include "conf.d/magnet.conf"

##
## FastCGI (mod_fastcgi)
##
include "conf.d/fastcgi.conf"
</pre>

You need also to configure /srv/www/obs/webui/config/environments/production.rb to point to correct server names:

<pre>
nano /srv/www/obs/webui/config/environments/production.rb
FRONTEND_HOST = "capi.meego.com"
FRONTEND_PORT = 80
EXTERNAL_FRONTEND_HOST = "capi.meego.com"
BUGZILLA_HOST = "http://bugs.moego.com/"
DOWNLOAD_URL = "http://cdownload.meego.com/"
</pre>

Do the same for /srv/www/obs/api/config/environments/production.rb. As soon your backend is not on the same machine as the api (frontend), change the following:

<pre>
nano /srv/www/obs/api/config/environments/production.rb
SOURCE_HOST = "csrc.meego.com"
SOURCE_PORT = 5352
DOWNLOAD_URL='http://cdownload.meego.com/'
</pre>

ligthttpd user and group need to be the owner of api and webui dirs (as well as log and tmp):

<pre>
chown -R lighttpd.lighttpd /srv/www/obs/{api,webui}
</pre>

Make sure TCP port 5352 is open on the firewall. Ensure lighttpd and obs ui helpers start:

<pre>
chkconfig --add memcached
chkconfig --add lighttpd
chkconfig --add obsapidelayed
chkconfig --add obswebuidelayed

rcmemcached start
rclighttpd start
rcobsapidelayed start
rcobswebuidelayed start
</pre>

rcobsapidelayed

= Preparing Worker Host =

<pre>
vgadd OBS /dev/sda4
vgcreate OBS /dev/sda4
</pre>

== Installing the Workers ==

The other hosts on the cluster are reserved to be used as workers,
where package builds are going to place.

The same openSUSE Tools repository addition must be done for each worker.
<pre>
cd /etc/zypp/repos.d/;
zypper ar http://download.opensuse.org/repositories/Maemo:/MeeGo-Infra:/OBS/Tools_Unstable_openSUSE_11.2/Maemo:MeeGo-Infra:OBS.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools:/Unstable/openSUSE_11.2/openSUSE:Tools:Unstable.repo
zypper ar http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.2/openSUSE:Tools.repo
zypper ref
# Accept the trust key.
</pre>

<pre>
zypper in obs-worker qemu-devel mount-static bash-static
</pre>

(mount-static and bash-static are needed on the worker for rpm cross-compile to work)

For Xen workers we need a suitable initrd:
<pre>
export rootfstype="ext4"
mkinitrd -d /dev/null -m "ext4 binfmt_misc" -k vmlinuz-$(uname -r) -i initrd-$(uname -r)-obs_worker
</pre>
This will create an initrd for your kernel
<pre>
Kernel image: /boot/vmlinuz-2.6.31.12-0.2-xen
Initrd image: /boot/initrd-2.6.31.12-0.2-xen-obs_worker
</pre>
Make sure you link initrd-xen-worker -> initrd-2.6.31.12-0.2-xen-obs_worker
<pre>
ln -s /boot/initrd-$(uname -r)-obs_worker /boot/initrd-xen-worker
ln -s vmlinuz-$(uname -r)-xen vmlinuz-xen-worker
</pre>

This assumes you have a VG dedicated to workers called "OBS"

Edit the file /etc/sysconfig/obs-worker in order to point to correct repository server.

<pre>
nano /etc/sysconfig/obs-worker
OBS_SRC_SERVER="csrc:5352"
OBS_REPO_SERVERS="cbe:5252"
OBS_VM_TYPE="xen"
OBS_VM_KERNEL="/boot/vmlinuz-xen-worker"
OBS_VM_INITRD="/boot/initrd-xen-worker"
OBS_VM_DISK_AUTOSETUP_ROOT_FILESIZE="8192"
OBS_VM_DISK_AUTOSETUP_SWAP_FILESIZE="2048"
OBS_INSTANCE_MEMORY="1024"
OBS_STORAGE_AUTOSETUP="yes"
OBS_SETUP_WORKER_PARTITIONS="use_obs_vg"
OBS_WORKER_ROOT_SIZE="8192"
OBS_WORKER_SWAP_SIZE="2048"
</pre>

Note that the OBS_VM_KERNEL/INITRD params are for kvm only. The Xen VM pulls in /usr/lib/build/xen.conf from the repo master (backend server, cbe). It does this

The obsstoragesetup will wipe the OBS VG and create root/swap LVs for each worker
<pre>
rcobsstoragesetup start
</pre>

Output:
<pre>
mdadm: No arrays found in config file or automatically
Waiting for udev to settle...
Scanning for LVM volume groups...
Reading all physical volumes. This may take a while...
Found volume group "OBS" using metadata type lvm2
Activating LVM volume groups...
0 logical volume(s) in volume group "OBS" now active
done
Logical volume "worker_root_1" created
Logical volume "worker_swap_1" created
Logical volume "worker_root_2" created
Logical volume "worker_swap_2" created
Logical volume "worker_root_3" created
Logical volume "worker_swap_3" created
Logical volume "worker_root_4" created
Logical volume "worker_swap_4" created
Logical volume "worker_root_5" created
Logical volume "worker_swap_5" created
Logical volume "worker_root_6" created
Logical volume "worker_swap_6" created
Logical volume "worker_root_7" created
Logical volume "worker_swap_7" created
Logical volume "worker_root_8" created
Logical volume "worker_swap_8" created
Logical volume "worker_root_9" created
Logical volume "worker_swap_9" created
Logical volume "worker_root_10" created
Logical volume "worker_swap_10" created
Logical volume "worker_root_11" created
Logical volume "worker_swap_11" created
Logical volume "worker_root_12" created
Logical volume "worker_swap_12" created
Logical volume "worker_root_13" created
Logical volume "worker_swap_13" created
Logical volume "worker_root_14" created
Logical volume "worker_swap_14" created
Logical volume "worker_root_15" created
Logical volume "worker_swap_15" created
Logical volume "worker_root_16" created
Logical volume "worker_swap_16" created
Logical volume "cache" created
mke2fs 1.41.9 (22-Aug-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
3555328 inodes, 14201856 blocks
710092 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
434 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Looking for OBS Server LVM Volume
Setup local storage
Looking for OBS Worker Cache LVM Volume
Setting up OBS Workers according to LVM Volumes
Found XEN virtualization
done
</pre>

Test?
<pre>
xm create -c /var/run/obs/worker/8/build/xen.conf name=build:root8 memory=40 disk=phy:/dev/mapper/OBS-worker_root8,hda1,w disk=phy:/dev/mapper/OBS-worker_swap8,hda2,w extra="init=/.build/initscript_qemu_vm panic=1 console=ttyS0
</pre>

Start the worker service:

<pre>
chkconfig --add obsworker
rcobsworker start
</pre>

[[Category:Build Infrastructure]]

MeeGo-Meeting IRC Schedule

2011-06-14T14:34:07Z

Xfade: Add MeeGo Apps meeting

To avoid meeting conflicts in [http://meego.com/community/irc-channel #meego-meeting], please add your meeting here with date and UTC time until we have a more robust solution. You might also want to review our [[IRC guidelines]] for the MeeGo project.

We have two meeting rooms:

[http://meego.com/community/irc-channel #meego-meeting], also called Meeting Room 1

[http://meego.com/community/irc-channel #meego-meeting2], also called Meeting Room 2

== Regular Meetings ==

'''Monday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0px 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 7:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|MeeGo Core Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0px 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 0px 0"| 15:00
|style="border-style: solid; border-width: 0 1px 0px 0"| [[Local_MeeGo_Networks/MeeGo_Network_Finland#Online_Community_Meetings | MeeGo Network Finland Community Meetings]]
|style="border-style: solid; border-width: 0 1px 0px 0"| Monthly meeting every 1st Monday
|style="border-style: solid; border-width: 0 0px 0px 0"| #meego-meeting
|}

'''Tuesday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Meetings| QA Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 08:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/QA-tools/Meetings| QA-Tools Meeting]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting2
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 08:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[SDK/Meetings/Release| SDK Meeting (Release)]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 11:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[ARM/N900/DeveloperEdition/Meetings| N900 Community Edition Team Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 13:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Netbook Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 14:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Community_Office/Meetings| Community Office Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Bi-Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 15:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Project/Dialer/Meetings| Dialer Project Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 0 0"| 17:00
|style="border-style: solid; border-width: 0 1px 0 0"| [[Events/Meetings|Events Meeting]]
|style="border-style: solid; border-width: 0 1px 0 0"| Bi-Weekly *
|style="border-style: solid; border-width: 0"| #meego-meeting
|}

<nowiki>*</nowiki> Every other week.

'''Wednesday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 05:30
|style="border-style: solid; border-width: 0 1px 1px 0"| [[SDK/Meetings| SDK Meeting]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Handset Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo SDK Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting2
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 08:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MCTS Bug Triage Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 15:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[LocalizationMeetings| Localization / L10n Meetings]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Monthly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|}

'''Thursday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 06:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Technical_Steering_Group_meetings| Technical Steering Group Meeting]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Bi-Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Tablet 1.2 Critical bug tracking]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting2
|-
|style="border-style: solid; border-width: 0 1px 1px 0"| 07:00
|style="border-style: solid; border-width: 0 1px 1px 0"| [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo N900 DE 1.2 Critical bug tracking]]
|style="border-style: solid; border-width: 0 1px 1px 0"| Weekly
|style="border-style: solid; border-width: 0 0 1px 0"| #meego-meeting
|-
|style="border-style: solid; border-width: 0 1px 0 0"| 08:00
|style="border-style: solid; border-width: 0 1px 0 0"| [[ARM/N900/Meetings| MeeGo N900 DE Common Software + Hardware Adaptation Meetings]]
|style="border-style: solid; border-width: 0 1px 0 0"| Weekly
|style="border-style: solid; border-width: 0"| #meego-meeting
|}

'''Friday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-
|style="border-style: solid; border-width: 0 1px 0 0"| 07:00
|style="border-style: solid; border-width: 0 1px 0 0"| [[ARM/N900/Browser/Meetings | Meego N900 DE Browser & Wlan team meeting ]]
|style="border-style: solid; border-width: 0 1px 0 0"| Weekly
|style="border-style: solid; border-width: 0"| #meego-meeting
|}

'''Sunday'''
{|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"| Time (UTC)
!style="border-style: solid; border-width: 0 1px 1px 0"| Meeting
!style="border-style: solid; border-width: 0 1px 1px 0"| Interval
!style="border-style: solid; border-width: 0 0 1px 0"| Channel
|-}

== Ad Hoc Meetings ==

Scheduling a one-time meeting? Add it to this section.

* [[MeeGo Apps|MeeGo Apps]] meeting: Friday, 17th of June 2011 at 14:00 UTC

=== Guidelines ===

Please refer to the [[IRC guidelines]] for more details about how to run a MeeGo IRC meeting and using #meego-meeting.

You might also be interested in these [[IRC Presentation Tips]].

MeeGo Apps

2011-06-14T12:43:10Z

Xfade: /* Plans and Schedule */

MeeGo Community Apps is the repository where open source software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met. This project falls under the responsibility of the [[Community Office]].

= Accessing Apps =

* [http://apps-beta.meego.com Apps Beta Web Interface]
* [http://gitorious.org/meego-community-extras-client Client code in Gitorious]
* [http://github.com/nemein Server code on GitHub]

= Process =

A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|request access]] to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems.

Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package. The Apps-testing repository is intended for [[MeeGo Apps/QA|stability testing and community QA]]. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.

== Supporting Process References ==
* [[Build_Infrastructure/Community_Builder#Getting_Access|Getting access to the Community OBS]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[MeeGo Apps/QA|QA Process]]
* [[MeeGo_Apps/repositories|Repository layout description]]

= Community Apps Team =

* Lead Developer: Niels Breet
* Client Application: Martin Grimme
* Web Site: Ferenc Szekely
* OCS Interface: Henri Bergius
* Build Service: David Greaves

== Team Communication Channels ==
* Use the [http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List] for questions and discussion.
* File bugs in the [https://bugs.meego.com/enter_bug.cgi?product=Community%20Apps Community Apps Component]
* Ask questions in the #meego IRC Channel

= Plans and Schedule =

Working on:

W24:
* Automatic import/delete packages in MeeGo Apps by BOSS participant signaling (niels)
* OCS interface fixes (ferenc/henri)
* List apps in testing queue (?)
* QA result signaling to BOSS (niels/david)
* Configure Apps build targets in OBS, cleanup old build targets (niels)

Open issues (help appreciated):

Documentation:
* Document Apps submit process
* Document QA process

Design:
* Front page design
* Icons for App categories

MeeGo Apps

2011-06-14T10:15:48Z

Xfade: /* Supporting Process References */

MeeGo Community Apps is the repository where open source software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met. This project falls under the responsibility of the [[Community Office]].

= Accessing Apps =

* [http://apps-beta.meego.com Apps Beta Web Interface]
* [http://gitorious.org/meego-community-extras-client Client code in Gitorious]
* [http://github.com/nemein Server code on GitHub]

= Process =

A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|request access]] to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems.

Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package. The Apps-testing repository is intended for [[MeeGo Apps/QA|stability testing and community QA]]. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.

== Supporting Process References ==
* [[Build_Infrastructure/Community_Builder#Getting_Access|Getting access to the Community OBS]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[MeeGo Apps/QA|QA Process]]
* [[MeeGo_Apps/repositories|Repository layout description]]

= Community Apps Team =

* Lead Developer: Niels Breet
* Client Application: Martin Grimme
* Web Site: Ferenc Szekely
* OCS Interface: Henri Bergius
* Build Service: David Greaves

== Team Communication Channels ==
* Use the [http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List] for questions and discussion.
* File bugs in the [https://bugs.meego.com/enter_bug.cgi?product=Community%20Apps Community Apps Component]
* Ask questions in the #meego IRC Channel

= Plans and Schedule =

'''Henri & Neils to add'''

MeeGo Apps/repositories

2011-06-14T10:13:38Z

Xfade: Add repositories design as sub page

== Repositories==

There will be multiple repositories for a certain MeeGo release. Let's use MeeGo 1.1 as an example:

*'''MeeGo:1.1:Apps''' This targets MeeGo 1.1 Core. This means that applications in this repository can only have dependencies on MeeGo 1.1 Core.
*'''MeeGo:1.1:Apps:Handset''' This targets MeeGo 1.1 Core for apps intended for only the MeeGo 1.1 Handset UX.
*'''MeeGo:1.1:Apps:IVI''' This targets MeeGo 1.1 Core for apps intended for only the MeeGo 1.1 IVI UX.
*'''MeeGo:1.1:Apps:Netbook''' This targets MeeGo 1.1 Core for apps intended for only the MeeGo 1.1 Netbook UX.

Additionally there is '''Apps+'''

*'''MeeGo:1.1:Apps+''' This targets MeeGo 1.1 Core '''plus''' Surrounds. This means that applications in this repository can have additional dependencies and may not be compliant.
*'''MeeGo:1.1:Apps+:Handset''' This targets MeeGo 1.1 Core+Surrounds for apps intended for only the MeeGo 1.1 Handset UX.
*'''MeeGo:1.1:Apps+:IVI''' This targets MeeGo 1.1 Core+Surrounds for apps intended for only the MeeGo 1.1 IVI UX.
*'''MeeGo:1.1:Apps+:Netbook''' This targets MeeGo 1.1 Core+Surrounds for apps intended for only the MeeGo 1.1 Netbook UX.

As a separate project there will be:

*'''MeeGo:1.1:Surrounds''' This repository hosts libraries which are not included in MeeGo, but are a dependency for common Linux applications.

MeeGo Apps

2011-06-14T10:11:20Z

Xfade: Remove old content

MeeGo Community Apps is the repository where open source software created by the MeeGo community can be found. Developers can build their applications on the MeeGo Community OBS, a sophisticated build system. These applications can be published into the end-user facing Apps repository after certain conditions have been met. This project falls under the responsibility of the [[Community Office]].

= Accessing Apps =

* [http://apps-beta.meego.com Apps Beta Web Interface]
* [http://gitorious.org/meego-community-extras-client Client code in Gitorious]
* [http://github.com/nemein Server code on GitHub]

= Process =

A developer will need to [[Build_Infrastructure/Community_Builder#Getting_Access|request access]] to the Community OBS. Once the account has been activated, the developer can create a 'home' project. Inside this project one can build packages against any project(repository) in the OBS. This allows the developer to build an application against the Apps repository and make sure there are no dependency issues or other problems.

Once a developer determines that the application is ready for end-users, the package can be promoted to Apps-testing. The promotion request triggers some automated tests on the package. The Apps-testing repository is intended for [[MeeGo Apps/QA|stability testing and community QA]]. If the package meets all promotion criteria, it will be moved to the Apps repository. This makes it available for every end user with a MeeGo device, provided they have enabled the repository in their garage client.

== Supporting Process References ==
* [[Build_Infrastructure/Community_Builder#Getting_Access|Getting access to the Community OBS]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[MeeGo Apps/QA|QA Process]]

= Community Apps Team =

* Lead Developer: Niels Breet
* Client Application: Martin Grimme
* Web Site: Ferenc Szekely
* OCS Interface: Henri Bergius
* Build Service: David Greaves

== Team Communication Channels ==
* Use the [http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List] for questions and discussion.
* File bugs in the [https://bugs.meego.com/enter_bug.cgi?product=Community%20Apps Community Apps Component]
* Ask questions in the #meego IRC Channel

= Plans and Schedule =

'''Henri & Neils to add'''

File:MeeGo Introduction-test.pdf

2011-05-12T10:39:15Z

Xfade: Testing

Testing

Build Infrastructure/Packagers Developers

2011-05-04T08:48:53Z

Xfade: Add note about different OBS services

These pages are in preparation - contributions welcome.

Note: See [[OBS|the OBS wiki page]] for explanation of the different OBS services MeeGo offers.

This track will give you a brief introduction to the features and capabilities of the OBS instance hosted at build.meego.com.
Note: You need an account to access build.meego.com.
If you have no account, you can still learn how the OBS works at the upstream project's own instance [http://build.opensuse.org http://build.opensuse.org] .

In this track, you'll learn how to use the web interface, the commandline client and create your first package.
The packaging guidelines and more advanced topics are also covered.

== How to get started ==

You need an account on build.meego.com. To request an account:
# Go to [http://bugs.meego.com MeeGo bugzilla].
# Click New in the upper navigational bar to begin filing a bug.
# On the next page, click MeeGo Community Infrastructure.
# On the following page, click Build Service and file your bug.

== How to use the web interface ==
A series of pages will make you familiar with webinterface basics. It's divided into several subpages:
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_1|Part 1 - Login and first steps]]
* [[Build_Infrastructure/Packagers_Developers/WebUI_part_2|Part 2 - Creating a link and adding a repository]]
* [[Developing_in_a_MeeGo_Environment#Building_your_package:_Step_by_step|Part 3 - Your first own package]]

== How to use the commandline client ==
* Part 1 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_1|initial setup]]
* Part 2 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_2|checkout of projects, commit]]
* Part 3 - [http://en.opensuse.org/openSUSE:OSC branch, edit, localbuild, commit, submitreq]
* part 4 - [[Build_Infrastructure/Packagers_Developers/CLI_Part_4|more commands: localcheckbuild]]

== MeeGo Packaging guidelines and Howto ==
* [[Packaging|Packaging]]
* [[Packaging/Guidelines|Packaging Guidelines]]
* [[SDK/Docs/1.0/Packaging/Tutorial|Packaging Tutorial]]

== [[Build_Infrastructure/QA|QA Processes around the OBS]] ==
See the [[Quality]] page.

== Verifying Your Package Changes Locally and Online ==
* [[Build_Infrastructure/Packagers_Developers/Using_OBS_chroot_for_development|Using OBS chroot for development]]

== IRC / mailinglists / contact ==

If you need help, you can join #meego or #meego-dev on irc.freenode.net . See also [[Community communication|this page]] about all MeeGo IRC channels.

You can join [http://lists.meego.com/listinfo/meego-dev MeeGo-dev] and [http://lists.meego.com/listinfo/meego-packaging MeeGo-packaging] mailing lists [http://lists.meego.com/mailman/listinfo over here].

[[Category:Build Infrastructure]]

OBS

2011-05-04T08:41:03Z

Xfade: Add link to gettings started for build.

'''Open Build Service (OBS)'''

The OBS (Open Build Service) is a build management system written for the community by openSuse/Novell.

MeeGo has two main OBS setups:
* The [[Core OBS]] : https://build.meego.com/ - used by core developers to build the main MeeGo distribution; accounts provided to anyone who earns commit rights to a MeeGo package. More information on how to get an account can be found [[Build_Infrastructure/Packagers_Developers#How_to_get_started|here]]
* The [[OBS/Community OBS|Community OBS]] : https://build.pub.meego.com/ - used by MeeGo community members to build opensource applications and libraries

Additionally vendors may have private OBS installations

OBS installations may be linked to each other so that software build on a vendor OBS or the community OBS may refer to and track software packages being developed on the core OBS.

Whilst the OBS does the bulk of the compiling and building there is additional QA, automation and test infrastructure used by the MeeGo Project : The [[Build Infrastructure]] article has more details.

'''Get a Community OBS account'''

https://build.pub.meego.com/user/register_user

'''Setup a local test instance'''

There is a wiki article on how to [[OBS setup|setup a Build Service of your own]] - note that you don't need to do this to build locally; it's only usually needed by vendors.

MeeGo Apps/sprint

2011-05-02T13:07:07Z

Xfade: Automatic import works

= Apps Sprint =

Success criteria:

Deliver a working process to:

# (x) Upload source
# (x) Build binary rpm
# ( ) Allow promotion to Apps:Testing
# ( ) Automatically validate and accept to Apps:Testing
# ( ) Build in Apps:Testing
# ( ) Start Community test process
# ( ) Accept/reject application (notify user)
# ( ) Publish to Apps
# (X) Notify http://apps-beta.meego.com/
# (X) Available in http://apps-beta.meego.com/
# ( ) Install on ...? DE?

== Implementation/Acceptance details ==
When something is ticked in the main list, details should be provided here

=== Upload source ===
This is standard OBS functionality.

The user is expected to have a home: area and know how to issue a
submit request.

=== Build binary rpm ===

[https://build.pub.meego.com/project/show?project=MeeGo%3A1.2%3AApps MeeGo:1.2:Apps] and [https://build.pub.meego.com/project/show?project=MeeGo%3A1.2%3AApps%3ATesting MeeGo:1.2:Apps:Testing] projects have been created.

These build against MeeGo:1.2 (which for now is MeeGo:Trunk, which is a snapshot of 1.1.99.3.20110419.9)

A developer needs to build against MeeGo:1.2 in home:<username>

=== Allow promotion to Apps:Testing ===

A nice test package is omweather in home:vasvlad. This already builds against MeeGo:1.2.

=== Automatically validate and accept to Apps:Testing ===

This activity is carried out by a BOSS process.

The "REQUEST_CREATE" event targetting Apps:Testing is captured and a
process started.

The process is:
Ruote.process_definition :name => 'Apps_submit do
sequence do
end
end

* need better 'process/event' mapping and tracking

=== Build in Apps:Testing ===
=== Start Community test process ===
=== Accept/reject application (notify user) ===
=== Publish to Apps ===
=== Notify http://apps-beta.meego.com/ ===

BOSS participant written and tested. apps-beta now imports packages when signaled by the participant

=== Available in http://apps-beta.meego.com/ ===

Tested.

=== Install on ...? DE? ===

== Tasks Arising ==

This is for the "hmmm, we really need to have a ...." ideas that come
out in the sprint

* Tutorial docs for OBS and App process

MeeGo Apps/sprint

2011-04-22T12:50:25Z

Xfade: Building works, info about test package

= Apps Sprint =

Success criteria:

Deliver a working process to:

# (x) Upload source
# (x) Build binary rpm
# ( ) Allow promotion to Apps:Testing
# ( ) Automatically validate and accept to Apps:Testing
# ( ) Build in Apps:Testing
# ( ) Start Community test process
# ( ) Accept/reject application (notify user)
# ( ) Publish to Apps
# ( ) Notify http://apps-beta.meego.com/
# ( ) Available in http://apps-beta.meego.com/
# ( ) Install on ...? DE?

== Implementation/Acceptance details ==
When something is ticked in the main list, details should be provided here

=== Upload source ===
This is standard OBS functionality.

The user is expected to have a home: area and know how to issue a
submit request.

=== Build binary rpm ===

[https://build.pub.meego.com/project/show?project=MeeGo%3A1.2%3AApps MeeGo:1.2:Apps] and [https://build.pub.meego.com/project/show?project=MeeGo%3A1.2%3AApps%3ATesting MeeGo:1.2:Apps:Testing] projects have been created.

These build against MeeGo:1.2 (which for now is MeeGo:Trunk, which is a snapshot of 1.1.99.3.20110419.9)

A developer needs to build against MeeGo:1.2 in home:<username>

=== Allow promotion to Apps:Testing ===

A nice test package is omweather in home:vasvlad. This already builds against MeeGo:1.2.

=== Automatically validate and accept to Apps:Testing ===

This activity is carried out by a BOSS process.

The "REQUEST_CREATE" event targetting Apps:Testing is captured and a
process started.

The process is:
Ruote.process_definition :name => 'Apps_submit do
sequence do
end
end

* need better 'process/event' mapping and tracking

=== Build in Apps:Testing ===
=== Start Community test process ===
=== Accept/reject application (notify user) ===
=== Publish to Apps ===
=== Notify http://apps-beta.meego.com/ ===
=== Available in http://apps-beta.meego.com/ ===
=== Install on ...? DE? ===

== Tasks Arising ==

This is for the "hmmm, we really need to have a ...." ideas that come
out in the sprint

* Tutorial docs for OBS and App process

MeeGo Apps/sprint

2011-04-22T11:46:00Z

Xfade: /* Build binary rpm */

= Apps Sprint =

Success criteria:

Deliver a working process to:

# (x) Upload source
# ( ) Build binary rpm
# ( ) Allow promotion to Apps:Testing
# ( ) Automatically validate and accept to Apps:Testing
# ( ) Build in Apps:Testing
# ( ) Start Community test process
# ( ) Accept/reject application (notify user)
# ( ) Publish to Apps
# ( ) Notify http://apps-beta.meego.com/
# ( ) Available in http://apps-beta.meego.com/
# ( ) Install on ...? DE?

== Implementation/Acceptance details ==
When something is ticked in the main list, details should be provided here

=== Upload source ===
This is standard OBS functionality.

The user is expected to have a home: area and know how to issue a
submit request.

=== Build binary rpm ===

[https://build.pub.meego.com/project/show?project=MeeGo%3A1.2%3AApps MeeGo:1.2:Apps] and [https://build.pub.meego.com/project/show?project=MeeGo%3A1.2%3AApps%3ATesting MeeGo:1.2:Apps:Testing] projects have been created.

These build against MeeGo:1.2 (which for now is MeeGo:Trunk, which is a snapshot of 1.1.99.3.20110419.9)

A developer needs to build against MeeGo:1.2 in home:<username>

=== Allow promotion to Apps:Testing ===
=== Automatically validate and accept to Apps:Testing ===

This activity is carried out by a BOSS process.

The "REQUEST_CREATE" event targetting Apps:Testing is captured and a
process started.

The process is:
Ruote.process_definition :name => 'Apps_submit do
sequence do
end
end

* need better 'process/event' mapping and tracking

=== Build in Apps:Testing ===
=== Start Community test process ===
=== Accept/reject application (notify user) ===
=== Publish to Apps ===
=== Notify http://apps-beta.meego.com/ ===
=== Available in http://apps-beta.meego.com/ ===
=== Install on ...? DE? ===

== Tasks Arising ==

This is for the "hmmm, we really need to have a ...." ideas that come
out in the sprint

* Tutorial docs for OBS and App process

MeeGo Apps/sprint

2011-04-22T10:48:07Z

Xfade: Create Apps projects

= Apps Sprint =

Success criteria:

Deliver a working process to:

# (x) Upload source
# ( ) Build binary rpm
# ( ) Allow promotion to Apps:Testing
# ( ) Automatically validate and accept to Apps:Testing
# ( ) Build in Apps:Testing
# ( ) Start Community test process
# ( ) Accept/reject application (notify user)
# ( ) Publish to Apps
# ( ) Notify http://apps-beta.meego.com/
# ( ) Available in http://apps-beta.meego.com/
# ( ) Install on ...? DE?

== Implementation/Acceptance details ==
When something is ticked in the main list, details should be provided here

=== Upload source ===
This is standard OBS functionality.

The user is expected to have a home: area and know how to issue a
submit request.

=== Build binary rpm ===

[https://build.pub.meego.com/project/show?project=MeeGo%3A1.2%3AApps MeeGo:1.2:Apps] and [https://build.pub.meego.com/project/show?project=MeeGo%3A1.2%3AApps%3ATesting MeeGo:1.2:Apps:Testing] projects have been created.

These these builds against MeeGo:Trunk, which is a snapshot of 1.1.99.3.20110419.9

=== Allow promotion to Apps:Testing ===
=== Automatically validate and accept to Apps:Testing ===

This activity is carried out by a BOSS process.

The "REQUEST_CREATE" event targetting Apps:Testing is captured and a
process started.

The process is:
Ruote.process_definition :name => 'Apps_submit do
sequence do
end
end

* need better 'process/event' mapping and tracking

=== Build in Apps:Testing ===
=== Start Community test process ===
=== Accept/reject application (notify user) ===
=== Publish to Apps ===
=== Notify http://apps-beta.meego.com/ ===
=== Available in http://apps-beta.meego.com/ ===
=== Install on ...? DE? ===

== Tasks Arising ==

This is for the "hmmm, we really need to have a ...." ideas that come
out in the sprint

* Tutorial docs for OBS and App process

User:Xfade

2011-04-19T08:38:42Z

Xfade:

test
.
.
.
.
.

User:Xfade

2011-04-15T07:05:30Z

Xfade:

test
.
.
.
.

User:Xfade

2011-04-14T13:01:59Z

Xfade:

test
.
.
.

User:Xfade

2011-04-14T10:37:40Z

Xfade:

test
.
.
.
.

User:Xfade

2011-04-14T10:34:01Z

Xfade:

test
.
.
.
.
.

User:Xfade

2011-04-14T10:09:09Z

Xfade:

test
.
.
.
.

User:Xfade

2011-04-13T16:45:04Z

Xfade:

test
.
.
.

User:Xfade

2011-04-13T16:43:47Z

Xfade:

test
.
.

User:Xfade

2011-04-13T16:40:53Z

Xfade:

test
.