Maemo Wiki Mirror - User contributions [en]

MADDE/QtCreator integration for linux

2010-03-26T08:18:04Z

192.100.124.156: /* Add Qt for Maemo5 */

= QtCreator and MADDE on Linux =

This is a guide on how to enable MADDE in QtCreator. This is part of the technology preview. After following this guidance you are able to build your sources within QtCreator for your device, and deploy, run and debug your applications with few mouse clicks from your Linux installation (Ubuntu was used for this tutorial).

Requires:

* [[MADDE | MADDE]] installed on your Linux machine
* If you want to compile your code natively then you have to have "make" installed on your machine. If it is not install yet you can do that with:

sudo apt-get install make

== General advice ==
As this is a technology preview, remember that bugs can occur. If some of the components don't work as expected, please add your question to the [http://talk.maemo.org/showthread.php?t=46570 talk-thread] and follow up the discussion.

== Install latest QtCreator on your Linux computer ==

'''You cannot use the latest official QtCreator for this. The version has to be >= 1.3.80! For these instructions the version of the 2010-03-04 is used!''' Find the latest build of QtCreator for Linux here:

http://qt.nokia.com/developer/qt-snapshots

== Add Qt for Maemo5 ==

You can change the configuration of the Qt-version in your QtCreator installation by clicking:

Tools -> Options -> Qt4 -> Qt Versions

'''Tip:''' If you do not see any Qt version by default here, you most likely haven't installed the needed Qt libraries to compile your Qt application for your Linux environment.

In the next step you have to add the Qt version for Maemo5 to the configuration of QtCreator. It is needed to compile your sources for your Maemo device. Click on the "+" in the upper-right corner. The configuration form will ask you to enter a "Version name" and to locate "qmake". You can find it in your MADDE installation folder under:

<MADDE_folder>/targets/<target_name>/bin

For the '''standard installation''' it would be for example:

Version name: Maemo Qt4.5
qmake Location: /home/<username>/.madde/0.6.14/targets/fremantle-qt-0951/bin/qmake

'''Tip:''' You cannot find the folder if you click on "Choose...", as it is hidden. But after entering "/home/<username>/.madde/" in the text-field "qmake Location" you can select the rest via the "Choose..." button.

[[Image:01_linux_qtcreator_add_qmake.png|300px]] [[Image:02_linux_qtcreator_select_qmake.png|300px]]

Now you will see Qt for Maemo as a new Qt Version in Qt Creator. But first you will see the red cross next to the Qt Version in the column "Debugging Helper". The last step you have to do now is clicking on "Rebuild" and after a while (you can follow the status in the QtCreator main window) it should look like this:

[[Image:03_linux_qtcreator_qmake_rebuild.png|300px]] [[Image:04_linux_qtcreator_qmake_ready.png|300px]]

== Configure device run-time in Qt Creator ==

After setting up the connection between your Linux computer and your device, you will be able to compile, deploy, test and debug your application with a single mouse-click. The description shows the configuration for USB-networking and WLAN and is for each divided into two parts. It shows:

* what to install on device, and
* how to set-up your Linux machine

=== General device set-up ===

Please find the instructions on how to set up the device runtime from here:

* [[MADDE/QtCreator_integration_for_windows#Install_the_client | Install the client]]

=== Connect via USB-networking ===

==== Device configuration ====

The following guide shows you, what to do on your device to set up the USB connection. This has to be done '''before''' you connect your device with the Linux computer:

* [[MADDE/QtCreator_integration_for_windows#Configure_the_client_for_USB | Configure the client for USB networking]]

==== Linux configuration ====

Connect the device with your Linux machine. Then you click on "PC Suite mode" as connection mode. Now you should be able to see the device as a new wired network connection named "Auto usb0". Now you can configure the connection as follows.

1. Open the network connection settings:

[[Image:05_linux_network.png|400px]]

2. Change the method from "DHCP" to "Manual" and enter the details as shown in the screen-shot:

[[Image:06_linux_configure_usb.png|400px]]

After you have done this your connection should be established and the set-up ready to be used with QtCreator.

=== Connect via WLAN ===

If both devices are connected to the same wireless network the configuration is a bit easier, but be aware that the IP address might not be the same all the time. This effects the set up of your QtCreator configuration.

==== Device configuration ====

Please open the mad-developer application. If you are connected already to the wireless network, you can find the IP address in the initial window of the application:

[[Image:10_mac_mad-dev_wlan.png|300px]]

==== Linux configuration ====

Please just make sure, that your Linux computer and device are connected to the same network.

=== QtCreator Configuration ===

After the connection between your PC and the device is set up, you can configure QtCreator to deploy and run the built applications on device. You can add your device in the configuration. You will find it in:

QtCreator -> Preferences -> Qt4 -> Maemo Device Configurations

First get the password from the Mad Developer application. You get it by clicking on "Developer Password" in the main view. '''Be aware''' that each time you click on the button, a new password will be created and that the password is only valid for the time it is shown in the application.

[[Image:04_b_client_ready.png|300px]] [[Image:05_client_pw.png|300px]]

====Instructions for USB-network====

Add the password and all the data you see in the screenshot below. Check the box, that you want to use the password as the authentication method. After that click on "test" and see if the connection can be set up.

[[Image:07_linux_qtcreator_usb.png|300px]]

====Instructions for WLAN====

If your device is using the WLAN interface, please enter the IP address you can see in the mad-developer application on device.

[[Image:08_linux_qtcreator_wlan.png|300px]]

'''Tip''' You can use your ssh key for the connection. Click on "Deploy Key ..." and select your key. If the other settings are correct the key will be automatically deployed on your device, so that you don't have to worry about the passwords anymore.

=== Deploy SSH key ===

If you have already created a key for other purposes you don't have to create a new one and you can ignore the description on how to create the key and just continue with the deployment of the key.

==== Create a key ====

To create a key please open terminal and run:

ssh-keygen -t rsa -b 1024

Then please follow the instructions. If you don't choose a new location, the key will be stored in the standard location in the home folder (recommended). The terminal should look like this:

[[Image:09_linux_keygen.png|400px]]

==== Deploy the key from QtCreator ====

To be able to connect to your device by using the key, you have to:

* deploy your public key on your device, and
* specify in QtCreator, where to find the private key

You can configure these settings in the Maemo Device Configurations

Tools -> Options... -> Qt4 -> Maemo Device Configurations

'''Note: ''' For these steps your device has to be connected to the PC and the password has to be valid. By clicking "Test" button, you can check if that is the case.

Now you click on "Deploy..." and select the public key you have created before.

[[Image:10_linux_select_pubkey.png‎|300px]]

Once the key is deployed correctly you can set up your device-configuration to use the key to connect to the device. Change now the "Authentication type" from "Password" to "Key".

[[Image:11_linux_setkey.png‎|300px]]

Now click on "Apply" and your QtCreator installation is set up to connect to the device via SSH key.

== Use Maemo5 build settings ==

Now all the configuration is done and you can select Maemo as a build configuration. If you have a project, which you want to compile for Maemo, then click on the project button in the menu of the left side. Now you should seen a screen, like in the screen shot below. If you have the Qt libraries installed, then you will have the "Desktop" as the default option selected.

[[Image:12_linux_initial_config.png]]

'''Tip:'''

* It might be that you don't see the "Desktop" widget in your project configuration. In this case it might be that the configuration of the MADDE is not correct, or that a little bug prevents the widget from showing up. In this case click on "Dependencies" and then go back to "Build".

* If you start a new project you can add the Maemo build-configuration at the beginning:

:[[Image:13_linux_start_new_project.png|300px]]

Now press the plus in the widget, which shows, that "Desktop" is selected as default. This should open a new dialog, where you select "Maemo". After that you will find a new build-configuration. Now click in "Maemo" on "Run" and select your device, which you have configured before. In the example it was called Maemo 5.

[[Image:14_linux_select_device.png]]

Finally you can now set in the down left corner, which build configuration you want to use:

[[Image:15_linux_select_runtime.png]]

Now you can click on the run button, and your application will be automatically compiled for the Maemo device, delpoyed, and started.

[[Category:Development]]

Legacy Maemo 5 Documentation/Desktop Widget UI Guidelines

2009-11-24T08:27:28Z

192.100.124.156: /* Margins and positioning */

= Purpose of this document =
The Desktop Widget Guidelines‐document is intended as an aid for developers to build Desktop Widgets according to the design philosophy, interaction model, and visual look‐and‐feel of Maemo 5.

By following these guidelines, developers are assured to build Widgets that are consistent, and accessible for end‐users.

This document is supported by the [http://www.forum.nokia.com/info/sw.nokia.com/id/e778ba1f-2507-4672-be45-798359a3aea7/Fremantle_Master_Layout_Guide.html Fremantle Master Layout Guide] and [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide] for visual guidance and references, as well as by the [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification] for interaction and technical background information.
 

= Introduction =
Desktop Widgets can be defined as miniature applications – or applets – that reside on the Desktop for convenient, fast access to useful information or controls. Maemo 5 contains up to '''four''' Desktops, as illustrated in Figure 1, totaling in 3200x424 pixels of screen real‐estate for Desktop Widgets.

[[Image:desktop-views.png|Desktop views|600px]]
 '''Figure 1. Maemo 5 includes up to four Desktops for Widgets.'''

N.B. In Maemo terminology, in addition to Widgets, Maemo 5 also includes ''Application shortcuts'', ''Web bookmarks'', and ''Contacts''. Technically, however, these are considered Desktop Widgets as well, and the same guidelines apply. Thus, for the sake of readability, the term “Widget” used in this document encompasses '''all''' the aforementioned applets.

 

= Widget design =

== Design philosophy ==
While Widgets can be understood as small applications, the design philosophy for developing a Widget differs greatly from that of an application. Most notably, Widgets are '''not supposed to replace applications''' in terms of their use and feature set, '''rather compliment them'''; consider the following guidelines as the fundamental design goals of building an appropriate Widget:

* Widgets must provide information or controls '''quickly''' and in an '''obvious manner'''; every feature and command should be '''immediately understandable''', and '''accessible with a single tap'''.
* Widgets must provide only the '''most crucial features'''; they must be '''simple and efficient''', designed to accomplish only a few tasks – but accomplish those extremely well.
* Widgets must be as '''compact in size''' as possible; even though Maemo 5 offers a generous amount of screen space, users must be able to place several widgets on each screen to minimize the need for excessive screen switching. N.B. Due to the high pixel density of the physical screen, tappable elements must be at least 70x70 pixels in size for convenient finger use.

Due to the aforementioned design goals, not every application can be transformed into, or any data set presented with a legitimate Widget. Before starting development, consider whether the Widget provides any value for end‐users in comparison to existing applications or websites that can be one tap away via ''Application shortcuts'' or ''Web bookmarks''.

 

== Stock Widgets ==
Maemo 5 includes following Widgets, outlined in Table 1.

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor="#D9D9D9"|'''Widget name'''
|bgcolor="#D9D9D9"|'''Description'''
|bgcolor="#D9D9D9"|'''Dimensions (in px)'''

|-
|Application shortcut
|Provides one‐touch access to an application
|96x96

|-
|Calendar widget
|Displays the current date and upcoming calendar events
|352x252

|-
|Google widget
|Provides one-touch access to Google search
|176x146

|-
|Location widget
|Displays the current location of the user on a map
|316x368

|-
|Media Player widget
|Provides Media Player status and controls.
|338x148

|-
|Ovi widget
|Provides access to Ovi services
|490x88

|-
|RSS widget
|Displays the latest RSS feeds
|316x368

|-
|Tutorial widget
|Presents a tutorial on how to use the device
|800x72

|-
|Web bookmark
|Provides one‐touch access to a web bookmark
|176x146

|}

 '''Table 1. Overview of stock Widgets included in Maemo 5.'''

 

== Configuration options ==
Widgets that can be configured include a configuration‐button accessible in ''Edit mode''. Tapping on the button reveals a dialog containing all the available configuration options. Figure 2 presents a fictional example of a configuration dialog.

[[Image:configuration_dialog.png|Configuration dialog example|300px]]
 '''Figure 2. Example configuration dialog for a Widget.'''

 

= Interaction =
Within the Desktop, Widgets are interacted with by '''taps only''' (events should be initiated when the finger is released, not pressed down). Due to the prioritization of screen switching, Widgets '''do not support dragging or swiping gestures'''; this ensures that Desktop screens can be effortlessly panned even if they are filled with Widgets. Furthermore, '''long-tapping''' (tapping and holding the finger on the screen for an extended period of time) cannot be used for Widget interaction, since it activates the Edit mode by default.

N.B. Dragging gestures are naturally enabled in the ''Edit mode'' for repositioning Widgets, where screen switching is not supported.

In Maemo 5, Widgets '''do not support resizing'''. It is advised to not develop Widgets that dynamically change their size, because their visibility cannot be ensured; since Widgets can be placed near the edges of the screen, or near each other, any appearing elements can become occluded or entirely overlapped by other Widgets, or hidden outside the bounds of the screen.

All tappable elements on Widgets must contain a graphical highlight (pressed‐down) state for providing visual feedback on the action. If the entire Widget is a tappable element, such as with ''Web bookmarks'', the highlight state also encompasses the whole Widget. Examples of highlight states are shown in Figure 3.

[[Image:highlight_states.png|Highlight states|300px]]
 '''Figure 3. Examples of highlight states of various Widgets.'''

While text entries and areas (also known as text input fields) are supported UI widgets, they should be used with care; if several text entries are needed, they can also be provided either via a custom dialog, or utilizing the Widget’s configuration dialog.

 

= Visual look-and-feel =

== Size ==
Widgets must be designed to be as compact in their size as possible, avoiding any excessive graphical elements that do not provide any meaningful information or controls. As a rule of thumb, the footprint of a Widget '''must never exceed half of the Desktop space''' allocated for Widgets, including a 24px‐padding around the Widget (132,352 pixels total). The largest stock Widgets, ''Location'' and ''RSS'', are close to the maximum footprint of Widgets, as seen in Figure 4; another, ''Tutorial'', spans across the entire Desktop, but therefore remains limited in its height.

[[Image:location_widget.png|Location widget|300px]]
 '''Figure 4. The Location Widget is close to the maximum size of Widgets.'''

 

== Margins and positioning ==
Layouts in Maemo 5 utilize a standardized set of margins. The recommended margins for Widgets are outlined in Table 2.

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor = "#D9D9D9"|'''Logical name'''
|bgcolor = "#D9D9D9"|'''Size (in px)'''
|bgcolor = "#D9D9D9"|'''Additional information'''

|-
|HILDON_MARGIN_HALF
|4 px
|Marked as red bar in layout images

|-
|HILDON_MARGIN_DEFAULT
|8 px
|Marked as blue bar in layout images

|-
|HILDON_MARGIN_DOUBLE
|16 px
|Marked as cyan bar in layout images

|}

 '''Table 2. Standard margins for Widgets.'''

Stock widgets share common margins and positioning rules. Elements within Widgets are separated from each other by ''HILDON_MARGIN_HALF'', and Widgets are surrounded by ''HILDON_MARGIN_DEFAULT''; the surrounding area includes both the outer border of the Widget, as well as a drop shadow. Some examples are presented in Figure 5, and Figure 6.

[[Image:applet-wireframes+specs.png|Widget margins|800px]]
 '''Figure 5. Examples of margin use in stock Widgets.'''

 
[[Image:widgets+wireframes.png|Widget wireframes|800px]]
 '''Figure 6. Examples of visual Widget construction.'''

The positioning of graphical elements such as text labels, buttons, icons and so on must be in line with the rest of the Maemo 5 guidelines.

 

== Visuals ==
In Maemo 5, the overall graphical look‐and‐feel is designed as light‐colored text and icons on dark backgrounds. All of the default Widgets follow this principle; graphic themes also contain a so‐called ''reversed color palette'', which enable the use of dark text on light backgrounds.

 
== Typography ==
Due to their compact size, default Widgets generally use ''HomeSystemFont'' or ''SmallSystemFont'' as the font size, while ''DefaultTextColor'' is used as the default text color. There is also a standard Sans-Serif font available for use.

Text labels in Widgets should be separated with at least ''HILDON_MARGIN_HALF'' from the edges of their respective container elements to make sure that long labels do not end up touching element borders; see Figure 5 for visualizations.

Figure 7 presents an example of the use of typography in Widgets.

[[Image:widget_typography.png|Widget typography|300px]]
 '''Figure 7. An example of the use of typography in Widgets.'''

= Development =
== Packaging ==
Widgets are installed on the device using a normal Debian application package. As the package information of your desktop widget can be seen in Application manager (the application used to install Widgets), it is recommended to fill in the following information in the package:

• Application name – a descriptive name shown in the application package list view in Application manager

• Application short description – the first line (or 60 first characters) of the application description

• Application icon – a base64encoded PNG image (sized 48x48 px). This icon is only shown in Application manager

Unless the installation script of the Widget package contains commands to place the Widget on the Desktop, users have to manually do so via Edit mode. Since this is an unnecessary step for the user, it is advised that the installation script handles the placement automatically. It is also possible to direct the Widget onto a specific Desktop view; however, the exact placement of the Widget cannot be specified in the script.

= References =

* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/e778ba1f-2507-4672-be45-798359a3aea7/Fremantle_Master_Layout_Guide.html Fremantle Master Layout Guide]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]

Legacy Maemo 5 Documentation/Desktop Widget UI Guidelines

2009-11-24T08:27:02Z

192.100.124.156: /* Interaction */

= Purpose of this document =
The Desktop Widget Guidelines‐document is intended as an aid for developers to build Desktop Widgets according to the design philosophy, interaction model, and visual look‐and‐feel of Maemo 5.

By following these guidelines, developers are assured to build Widgets that are consistent, and accessible for end‐users.

This document is supported by the [http://www.forum.nokia.com/info/sw.nokia.com/id/e778ba1f-2507-4672-be45-798359a3aea7/Fremantle_Master_Layout_Guide.html Fremantle Master Layout Guide] and [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide] for visual guidance and references, as well as by the [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification] for interaction and technical background information.
 

= Introduction =
Desktop Widgets can be defined as miniature applications – or applets – that reside on the Desktop for convenient, fast access to useful information or controls. Maemo 5 contains up to '''four''' Desktops, as illustrated in Figure 1, totaling in 3200x424 pixels of screen real‐estate for Desktop Widgets.

[[Image:desktop-views.png|Desktop views|600px]]
 '''Figure 1. Maemo 5 includes up to four Desktops for Widgets.'''

N.B. In Maemo terminology, in addition to Widgets, Maemo 5 also includes ''Application shortcuts'', ''Web bookmarks'', and ''Contacts''. Technically, however, these are considered Desktop Widgets as well, and the same guidelines apply. Thus, for the sake of readability, the term “Widget” used in this document encompasses '''all''' the aforementioned applets.

 

= Widget design =

== Design philosophy ==
While Widgets can be understood as small applications, the design philosophy for developing a Widget differs greatly from that of an application. Most notably, Widgets are '''not supposed to replace applications''' in terms of their use and feature set, '''rather compliment them'''; consider the following guidelines as the fundamental design goals of building an appropriate Widget:

* Widgets must provide information or controls '''quickly''' and in an '''obvious manner'''; every feature and command should be '''immediately understandable''', and '''accessible with a single tap'''.
* Widgets must provide only the '''most crucial features'''; they must be '''simple and efficient''', designed to accomplish only a few tasks – but accomplish those extremely well.
* Widgets must be as '''compact in size''' as possible; even though Maemo 5 offers a generous amount of screen space, users must be able to place several widgets on each screen to minimize the need for excessive screen switching. N.B. Due to the high pixel density of the physical screen, tappable elements must be at least 70x70 pixels in size for convenient finger use.

Due to the aforementioned design goals, not every application can be transformed into, or any data set presented with a legitimate Widget. Before starting development, consider whether the Widget provides any value for end‐users in comparison to existing applications or websites that can be one tap away via ''Application shortcuts'' or ''Web bookmarks''.

 

== Stock Widgets ==
Maemo 5 includes following Widgets, outlined in Table 1.

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor="#D9D9D9"|'''Widget name'''
|bgcolor="#D9D9D9"|'''Description'''
|bgcolor="#D9D9D9"|'''Dimensions (in px)'''

|-
|Application shortcut
|Provides one‐touch access to an application
|96x96

|-
|Calendar widget
|Displays the current date and upcoming calendar events
|352x252

|-
|Google widget
|Provides one-touch access to Google search
|176x146

|-
|Location widget
|Displays the current location of the user on a map
|316x368

|-
|Media Player widget
|Provides Media Player status and controls.
|338x148

|-
|Ovi widget
|Provides access to Ovi services
|490x88

|-
|RSS widget
|Displays the latest RSS feeds
|316x368

|-
|Tutorial widget
|Presents a tutorial on how to use the device
|800x72

|-
|Web bookmark
|Provides one‐touch access to a web bookmark
|176x146

|}

 '''Table 1. Overview of stock Widgets included in Maemo 5.'''

 

== Configuration options ==
Widgets that can be configured include a configuration‐button accessible in ''Edit mode''. Tapping on the button reveals a dialog containing all the available configuration options. Figure 2 presents a fictional example of a configuration dialog.

[[Image:configuration_dialog.png|Configuration dialog example|300px]]
 '''Figure 2. Example configuration dialog for a Widget.'''

 

= Interaction =
Within the Desktop, Widgets are interacted with by '''taps only''' (events should be initiated when the finger is released, not pressed down). Due to the prioritization of screen switching, Widgets '''do not support dragging or swiping gestures'''; this ensures that Desktop screens can be effortlessly panned even if they are filled with Widgets. Furthermore, '''long-tapping''' (tapping and holding the finger on the screen for an extended period of time) cannot be used for Widget interaction, since it activates the Edit mode by default.

N.B. Dragging gestures are naturally enabled in the ''Edit mode'' for repositioning Widgets, where screen switching is not supported.

In Maemo 5, Widgets '''do not support resizing'''. It is advised to not develop Widgets that dynamically change their size, because their visibility cannot be ensured; since Widgets can be placed near the edges of the screen, or near each other, any appearing elements can become occluded or entirely overlapped by other Widgets, or hidden outside the bounds of the screen.

All tappable elements on Widgets must contain a graphical highlight (pressed‐down) state for providing visual feedback on the action. If the entire Widget is a tappable element, such as with ''Web bookmarks'', the highlight state also encompasses the whole Widget. Examples of highlight states are shown in Figure 3.

[[Image:highlight_states.png|Highlight states|300px]]
 '''Figure 3. Examples of highlight states of various Widgets.'''

While text entries and areas (also known as text input fields) are supported UI widgets, they should be used with care; if several text entries are needed, they can also be provided either via a custom dialog, or utilizing the Widget’s configuration dialog.

 

= Visual look-and-feel =

== Size ==
Widgets must be designed to be as compact in their size as possible, avoiding any excessive graphical elements that do not provide any meaningful information or controls. As a rule of thumb, the footprint of a Widget '''must never exceed half of the Desktop space''' allocated for Widgets, including a 24px‐padding around the Widget (132,352 pixels total). The largest stock Widgets, ''Location'' and ''RSS'', are close to the maximum footprint of Widgets, as seen in Figure 4; another, ''Tutorial'', spans across the entire Desktop, but therefore remains limited in its height.

[[Image:location_widget.png|Location widget|300px]]
 '''Figure 4. The Location Widget is close to the maximum size of Widgets.'''

 

== Margins and positioning ==
Layouts in Maemo 5 utilize a standardized set of margins. The supported margins for Widgets are outlined in Table 2.

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor = "#D9D9D9"|'''Logical name'''
|bgcolor = "#D9D9D9"|'''Size (in px)'''
|bgcolor = "#D9D9D9"|'''Additional information'''

|-
|HILDON_MARGIN_HALF
|4 px
|Marked as red bar in layout images

|-
|HILDON_MARGIN_DEFAULT
|8 px
|Marked as blue bar in layout images

|-
|HILDON_MARGIN_DOUBLE
|16 px
|Marked as cyan bar in layout images

|}

 '''Table 2. Standard margins for Widgets.'''

Stock widgets share common margins and positioning rules. Elements within Widgets are separated from each other by ''HILDON_MARGIN_HALF'', and Widgets are surrounded by ''HILDON_MARGIN_DEFAULT''; the surrounding area includes both the outer border of the Widget, as well as a drop shadow. Some examples are presented in Figure 5, and Figure 6.

[[Image:applet-wireframes+specs.png|Widget margins|800px]]
 '''Figure 5. Examples of margin use in stock Widgets.'''

 
[[Image:widgets+wireframes.png|Widget wireframes|800px]]
 '''Figure 6. Examples of visual Widget construction.'''

The positioning of graphical elements such as text labels, buttons, icons and so on must be in line with the rest of the Maemo 5 guidelines.

 

== Visuals ==
In Maemo 5, the overall graphical look‐and‐feel is designed as light‐colored text and icons on dark backgrounds. All of the default Widgets follow this principle; graphic themes also contain a so‐called ''reversed color palette'', which enable the use of dark text on light backgrounds.

 
== Typography ==
Due to their compact size, default Widgets generally use ''HomeSystemFont'' or ''SmallSystemFont'' as the font size, while ''DefaultTextColor'' is used as the default text color. There is also a standard Sans-Serif font available for use.

Text labels in Widgets should be separated with at least ''HILDON_MARGIN_HALF'' from the edges of their respective container elements to make sure that long labels do not end up touching element borders; see Figure 5 for visualizations.

Figure 7 presents an example of the use of typography in Widgets.

[[Image:widget_typography.png|Widget typography|300px]]
 '''Figure 7. An example of the use of typography in Widgets.'''

= Development =
== Packaging ==
Widgets are installed on the device using a normal Debian application package. As the package information of your desktop widget can be seen in Application manager (the application used to install Widgets), it is recommended to fill in the following information in the package:

• Application name – a descriptive name shown in the application package list view in Application manager

• Application short description – the first line (or 60 first characters) of the application description

• Application icon – a base64encoded PNG image (sized 48x48 px). This icon is only shown in Application manager

Unless the installation script of the Widget package contains commands to place the Widget on the Desktop, users have to manually do so via Edit mode. Since this is an unnecessary step for the user, it is advised that the installation script handles the placement automatically. It is also possible to direct the Widget onto a specific Desktop view; however, the exact placement of the Widget cannot be specified in the script.

= References =

* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/e778ba1f-2507-4672-be45-798359a3aea7/Fremantle_Master_Layout_Guide.html Fremantle Master Layout Guide]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]

Legacy Maemo 5 Documentation/Desktop Widget UI Guidelines

2009-11-24T08:26:21Z

192.100.124.156: /* Stock Widgets */

= Purpose of this document =
The Desktop Widget Guidelines‐document is intended as an aid for developers to build Desktop Widgets according to the design philosophy, interaction model, and visual look‐and‐feel of Maemo 5.

By following these guidelines, developers are assured to build Widgets that are consistent, and accessible for end‐users.

This document is supported by the [http://www.forum.nokia.com/info/sw.nokia.com/id/e778ba1f-2507-4672-be45-798359a3aea7/Fremantle_Master_Layout_Guide.html Fremantle Master Layout Guide] and [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide] for visual guidance and references, as well as by the [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification] for interaction and technical background information.
 

= Introduction =
Desktop Widgets can be defined as miniature applications – or applets – that reside on the Desktop for convenient, fast access to useful information or controls. Maemo 5 contains up to '''four''' Desktops, as illustrated in Figure 1, totaling in 3200x424 pixels of screen real‐estate for Desktop Widgets.

[[Image:desktop-views.png|Desktop views|600px]]
 '''Figure 1. Maemo 5 includes up to four Desktops for Widgets.'''

N.B. In Maemo terminology, in addition to Widgets, Maemo 5 also includes ''Application shortcuts'', ''Web bookmarks'', and ''Contacts''. Technically, however, these are considered Desktop Widgets as well, and the same guidelines apply. Thus, for the sake of readability, the term “Widget” used in this document encompasses '''all''' the aforementioned applets.

 

= Widget design =

== Design philosophy ==
While Widgets can be understood as small applications, the design philosophy for developing a Widget differs greatly from that of an application. Most notably, Widgets are '''not supposed to replace applications''' in terms of their use and feature set, '''rather compliment them'''; consider the following guidelines as the fundamental design goals of building an appropriate Widget:

* Widgets must provide information or controls '''quickly''' and in an '''obvious manner'''; every feature and command should be '''immediately understandable''', and '''accessible with a single tap'''.
* Widgets must provide only the '''most crucial features'''; they must be '''simple and efficient''', designed to accomplish only a few tasks – but accomplish those extremely well.
* Widgets must be as '''compact in size''' as possible; even though Maemo 5 offers a generous amount of screen space, users must be able to place several widgets on each screen to minimize the need for excessive screen switching. N.B. Due to the high pixel density of the physical screen, tappable elements must be at least 70x70 pixels in size for convenient finger use.

Due to the aforementioned design goals, not every application can be transformed into, or any data set presented with a legitimate Widget. Before starting development, consider whether the Widget provides any value for end‐users in comparison to existing applications or websites that can be one tap away via ''Application shortcuts'' or ''Web bookmarks''.

 

== Stock Widgets ==
Maemo 5 includes following Widgets, outlined in Table 1.

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor="#D9D9D9"|'''Widget name'''
|bgcolor="#D9D9D9"|'''Description'''
|bgcolor="#D9D9D9"|'''Dimensions (in px)'''

|-
|Application shortcut
|Provides one‐touch access to an application
|96x96

|-
|Calendar widget
|Displays the current date and upcoming calendar events
|352x252

|-
|Google widget
|Provides one-touch access to Google search
|176x146

|-
|Location widget
|Displays the current location of the user on a map
|316x368

|-
|Media Player widget
|Provides Media Player status and controls.
|338x148

|-
|Ovi widget
|Provides access to Ovi services
|490x88

|-
|RSS widget
|Displays the latest RSS feeds
|316x368

|-
|Tutorial widget
|Presents a tutorial on how to use the device
|800x72

|-
|Web bookmark
|Provides one‐touch access to a web bookmark
|176x146

|}

 '''Table 1. Overview of stock Widgets included in Maemo 5.'''

 

== Configuration options ==
Widgets that can be configured include a configuration‐button accessible in ''Edit mode''. Tapping on the button reveals a dialog containing all the available configuration options. Figure 2 presents a fictional example of a configuration dialog.

[[Image:configuration_dialog.png|Configuration dialog example|300px]]
 '''Figure 2. Example configuration dialog for a Widget.'''

 

= Interaction =
Within the Desktop, Widgets are interacted with by '''taps only''' (events should be initiated when the finger is released, not pressed down). Due to the prioritization of screen switching, Widgets '''do not support dragging or swiping gestures'''; this ensures that Desktop screens can be effortlessly panned even if they are filled with Widgets. Furthermore, '''long-tapping''' (tapping and holding the finger on the screen for an extended period of time) cannot be used for Widget interaction, since it activates the Edit mode by default.

N.B. Dragging gestures are naturally enabled in the ''Edit mode'' for repositioning Widgets, where screen switching is not supported.

In Maemo 5, Widgets '''do not support resizing'''. It is advised to not develop Widgets that dynamically change their size, because their visibility cannot be ensured; since Widgets can be placed near the edges of the screen, or near each other, any appearing elements can become occluded or entirely overlapped by other Widgets, or hidden outside the bounds of the screen.

All tappable elements on Widgets must contain a graphical highlight (pressed‐down) state for providing visual feedback on the action. If the entire Widget is a tappable element, such as with ''Web bookmarks'', the highlight state also encompasses the whole Widget. Examples of highlight states are shown in Figure 3.

[[Image:highlight_states.png|Highlight states|300px]]
 '''Figure 3. Examples of highlight states of various Widgets.'''

Text entries and areas (also known as text input fields) are not supported UI widgets. If text entry is required, such as for logging into a service, they can be provided either via a custom dialog, or utilizing the Widget’s configuration dialog.

 

= Visual look-and-feel =

== Size ==
Widgets must be designed to be as compact in their size as possible, avoiding any excessive graphical elements that do not provide any meaningful information or controls. As a rule of thumb, the footprint of a Widget '''must never exceed half of the Desktop space''' allocated for Widgets, including a 24px‐padding around the Widget (132,352 pixels total). The largest stock Widgets, ''Location'' and ''RSS'', are close to the maximum footprint of Widgets, as seen in Figure 4; another, ''Tutorial'', spans across the entire Desktop, but therefore remains limited in its height.

[[Image:location_widget.png|Location widget|300px]]
 '''Figure 4. The Location Widget is close to the maximum size of Widgets.'''

 

== Margins and positioning ==
Layouts in Maemo 5 utilize a standardized set of margins. The supported margins for Widgets are outlined in Table 2.

{|border="2" cellspacing="0" cellpadding="4" width="80%"
|bgcolor = "#D9D9D9"|'''Logical name'''
|bgcolor = "#D9D9D9"|'''Size (in px)'''
|bgcolor = "#D9D9D9"|'''Additional information'''

|-
|HILDON_MARGIN_HALF
|4 px
|Marked as red bar in layout images

|-
|HILDON_MARGIN_DEFAULT
|8 px
|Marked as blue bar in layout images

|-
|HILDON_MARGIN_DOUBLE
|16 px
|Marked as cyan bar in layout images

|}

 '''Table 2. Standard margins for Widgets.'''

Stock widgets share common margins and positioning rules. Elements within Widgets are separated from each other by ''HILDON_MARGIN_HALF'', and Widgets are surrounded by ''HILDON_MARGIN_DEFAULT''; the surrounding area includes both the outer border of the Widget, as well as a drop shadow. Some examples are presented in Figure 5, and Figure 6.

[[Image:applet-wireframes+specs.png|Widget margins|800px]]
 '''Figure 5. Examples of margin use in stock Widgets.'''

 
[[Image:widgets+wireframes.png|Widget wireframes|800px]]
 '''Figure 6. Examples of visual Widget construction.'''

The positioning of graphical elements such as text labels, buttons, icons and so on must be in line with the rest of the Maemo 5 guidelines.

 

== Visuals ==
In Maemo 5, the overall graphical look‐and‐feel is designed as light‐colored text and icons on dark backgrounds. All of the default Widgets follow this principle; graphic themes also contain a so‐called ''reversed color palette'', which enable the use of dark text on light backgrounds.

 
== Typography ==
Due to their compact size, default Widgets generally use ''HomeSystemFont'' or ''SmallSystemFont'' as the font size, while ''DefaultTextColor'' is used as the default text color. There is also a standard Sans-Serif font available for use.

Text labels in Widgets should be separated with at least ''HILDON_MARGIN_HALF'' from the edges of their respective container elements to make sure that long labels do not end up touching element borders; see Figure 5 for visualizations.

Figure 7 presents an example of the use of typography in Widgets.

[[Image:widget_typography.png|Widget typography|300px]]
 '''Figure 7. An example of the use of typography in Widgets.'''

= Development =
== Packaging ==
Widgets are installed on the device using a normal Debian application package. As the package information of your desktop widget can be seen in Application manager (the application used to install Widgets), it is recommended to fill in the following information in the package:

• Application name – a descriptive name shown in the application package list view in Application manager

• Application short description – the first line (or 60 first characters) of the application description

• Application icon – a base64encoded PNG image (sized 48x48 px). This icon is only shown in Application manager

Unless the installation script of the Widget package contains commands to place the Widget on the Desktop, users have to manually do so via Edit mode. Since this is an unnecessary step for the user, it is advised that the installation script handles the placement automatically. It is also possible to direct the Widget onto a specific Desktop view; however, the exact placement of the Widget cannot be specified in the script.

= References =

* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/e778ba1f-2507-4672-be45-798359a3aea7/Fremantle_Master_Layout_Guide.html Fremantle Master Layout Guide]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]

Maemo.org Sprints/April 09

2009-05-07T13:00:52Z

192.100.124.156: ferenc: layout fix

== April 2009 Sprint planning ==
* [[Maemo.org Sprints/April 09/Meeting|Planning meeting]]: Monday, 2009-04-06 at [http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=6&year=2009&hour=13&min=30&sec=0 13:30 UTC] in [[IRC|#maemo-meeting]].
* Right after [[Maemo.org Sprints/March 09]] review.
* Followed by [[Maemo.org Sprints/May 09]].
* This sprint will be formally reviewed on [http://timeanddate.com/worldclock/fixedtime.html?month=5&day=7&year=2009&hour=13&min=30&sec=0&p1=0 2009-0507 at 13:30 UTC] in [[IRC|#maemo-meeting]].

==Tasks==
[[:Category:Ongoing|Ongoing]] tasks carried here from the previous sprint + New tasks committed by their owners in the sprint meeting. They come from the tasks in the [[Maemo.org_backlog|Backlog]] and the [[Maemo.org_proposals|Proposals]].

{| class="wikitable"
| style="background:LightGreen" | Completed
| style="background:LightBlue" | Good progress
| Just standing
| style="background:Orange" | Some help needed!
| style="background:Tomato" | Really stuck/delayed
|}

{| class="wikitable sortable"
|-
! Task ID
! Committed
! Due date
! Task
! Sprint priority
! Owner
! Percentage complete
! Notes
|- style="background:Tomato"
|8.11-01
|2008-11-04
|[[Maemo.org Sprints/May 09|May 09]]
|[[Task:Texts for maemo.nokia.com|Texts for maemo.nokia.com]]
|Should
|qgil
|20%
|Maemo 5 beta and Danish Weekend ate most of the time I had prepared for this.
|- style="background:LightGreen"
|8.11-02
|2008-11-04
|[[Maemo.org Sprints/April 09|April 09]]
|[http://bugs.maemo.org/show_bug.cgi?id=2179 Karma for applications - publish proposal]
|Must
|Bergie
|100%
|[[Task:Karma for applications|Karma providers list]] done
|-
|9.02-01
|2009-02-04
|[[Maemo.org Sprints/April 09|April 09]]
|[http://bugs.maemo.org/show_bug.cgi?id=3846 List Maemo bugzilla patches - create patchset]
|Should
|andre
|?
|- style="background:LightBlue"
|9.03-01
|2009-03-05
|[[Maemo.org Sprints/May 09|May 09]]
|[[Maemo Summit 2009]] - finalise venue
|Should
|qgil
|33%
|Venues visited by Kees, Niels and Quim. Decision between [http://www.westergasfabriek.nl/english/engels_welcome.php WesterGasFabriek] (waiting for their budget) and [http://www.felixmeritis.nl/en/ Felix Meritis].
|-
|9.03-02
|2009-03-05
|[[Maemo.org Sprints/?|?]]
|Create maemian from lintian
|Could / Should
|jeremiah
|5%
|https://garage.maemo.org/projects/maemian/
|-
|9.03-03
|2009-03-10
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Reducing number of external repositories|Update canonical list of external repositories.]]
|Must
|jeremiah
|10%
|Include key packages not in any repo
|-
|9.03-04
|2009-03-10
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Reducing number of external repositories|Reducing number of external repositories - contact outstanding owners]]
|Should
|jeremiah
|5%
|Includes chinook -> diablo
|-
|9.04-01
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Talk:Git For Garage|Git For Garage - svn-git tooling]]
|Must
|ferenc
|50%
|Script done, and tested. Integration to the GForge UI is needed. Remaining tasks are to be pushed to May.
|-
|9.04-02
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Talk:Git For Garage|Git For Garage - garage integration]]
|Should
|ferenc
|90%
|Gitweb's skin is not matching garage, but other than that this is done. Remaining task is to be pushed to May.
|- style="background:LightGreen"
|9.04-03
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - midgard]]
|Must
|Niels
|100%
|Deployed
|- style="background:LightGreen"
|9.04-04
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - mediawiki]]
|Must
|Niels
|100%
|Deployed
|-
|9.04-05
|2009-04-06
|[[Maemo.org Sprints/May 09|May 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - bugs]]
|Should
|X-Fade
|0%
|
|-
|9.04-06
|2009-04-06
|[[Maemo.org Sprints/May 09|May 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - ?]]
|Could
|X-Fade
|?
|
|-
|9.04-07
|2009-04-06
|[[Maemo.org Sprints/May 09|May 09]]
|[http://bugs.maemo.org/show_bug.cgi?id=2179 Karma for applications - implement]
|Should
|Hirvinen
|0%
|
|- style="background:LightBlue"
|9.04-08
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|Propose ITP process/workflow
|Should
|jeremiah
|75%
|http://wiki.maemo.org/ITP
|-
|9.04-09
|2009-04-06
|[[Maemo.org Sprints/May 09|May 09]]
|Setup SSO testing environment
|Must
|danielwilms
|0%
|URL?
|-
|9.04-10
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|Port packages from diablo -> fremantle
|Could
|jeremiah
|0%
|Specific enough? Needs task URL
|- style="background:LightGreen"
|9.04-11
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Open Source Proof Points|Open Source Proof Points - tidy up and merge wiki pages]]
|Must
|qole
|100%
|Rewrote [[Alternative operating systems]], pointed [[Task:Open Source Proof Points]] there. Done as much as I can do for now. Willing to add [[Alternative desktop environments]] in the next sprint.
|- style="background:LightGreen"
|9.04-12
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - testing]]
|Must
|timsamoff
|100%
| Beta launch date set for 1200 UTC, Wednesday, 22-04-2009.
|-style="background:LightBlue"
|9.04-13
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Maemo brainstorm|Maemo brainstorm]]
|Must
|NetBlade
|80%
| Deployed on Internal for testing, soon to go public beta
|- style="background:LightGreen"
|9.04-14
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|Discuss sprint process improvements
|Must
|qole
|100%
|See [http://lists.maemo.org/pipermail//maemo-community/2009-April/thread.html#3636 thread]
|-style="background:LightGreen"
|9.04-10
|2009-04-07
|[[Maemo.org Sprints/April 09|April 09]]
|Reduce the number of packages in diablo through elimination of duplicate packages, old packages.
|Should
|jeremiah
|100%
|Script to do this [http://github.com/jeremiah/debian--package--array/blob/93bf80481e2a20c0fd0c0836dc4e5b9b19ee9e9a/pkg-parse.pl Now on github]
|-
|9.04-10
|2009-05-03
|[[Maemo.org Sprints/April 09|April 09]]
|Diagnose autobuilder issues
|Should
|jeremiah
|0%
| Autobuilder apparently removes source packages.
|-
|}

==Activity log==
Latest activity report goes on top.

;2006-05-07

* Niels
** Yesterday: Worked on dependency problem in autobuilder. Tried to debug login problem. Tested brainstorm.
** Today: Work on some documentation importing, continue debugging login issue. Attend meeting.

* Andre
** Yesterday: Mostly cleaning up older tickets & syncing
** Today: Continued cleaning up older tickets; bug 3846; meeting

* Dave
** Past 5 days: Working on a client project
** Since last report (21/4): May 1st long weekend. Working on content issues with new maemo.org, track newstyle fall-out & bugs, and dig into Midgard to allow me to start fixing some of these bugs on my own.

;2009-05-05
* Niels
** Yesterday: Visited possible summit locations in Amsterdam together with Quim and Kees
** Today: Catch up on email, look at autobuilder and dependency issues. Look at login issues.

* Jeremiah
** Updating external repos list
** Built search.maemo.org prototype -> [http://test.maemo.org/cgi-bin/search.cgi here]

;2009-05-04
* Niels
** Today: visit possible summit locations in Amsterdam together with Quim and Kees

* Jeremiah
** Started hacking on a search script for packages

;2009-05-01

* Ryan
** Past days: Dealing with [http://talk.maemo.org Talk] fallout, opened [http://bugs.maemo.org/describecomponents.cgi?product=Website bugzilla component] for Talk, filing Talk bugs.
** Today: Pushing Maemo School towards using the wiki, more Talk bugs.
** Problems: People hate change.
** Kudos: Reggie really kicks ass at bugzilla!

* Jeremiah
** A little community chatter in #maemo and on lists
** Gave the queue-manager a punch in the stomach to get it to index things.
** Re-installing fremantle 5 beta SDK

;2009-04-30

* Jeremiah
** Trying to get fremantle SDK to work on my machine
** re-indexing diablo on garage as it has stopped for some reason

; 2009-04-29

* Niels
** Yesterday: Beta SDK related work. Styled search.maemo.org and Extras Assistant. Forced new style on wiki. Helped on git.maemo.org issues and published qt4 fremantle binaries. Attended web meeting.
** Today: Try to get everything needed to upgrade the autobuilder to Maemo5 beta SDK. Look at login issues and fix bugs.

* Jeremiah
** Installing Beta SDK for testing.
** Removed 7 Gigs of old, duplicate packages from diablo

; 2009-04-28
* Niels
** Yesterday: Prepare for beta. Documentation related work
** Today: Beta SDK related work. Style search.maemo.org, style Extras Assistant.

* Andre
** Yesterdays: Prepare SDK beta ChangeLog; normal triaging work...
** Today: Potential Brainstorm tickets; SDK beta release it seems (reset Target Milestones etc); internal weekly report

* Jeremiah
** Beginning to sketch out maemian, reading lintian code
** Working on a python packaging tutorial
** tweaks to package removal code

* Tim
** maemo.org redesign meeting.

; 2009-04-27
* Niels
** Friday: Worked on and published wiki styling, fixed bugs in newstyle. Talk related things. Discussed app karma and brainstorm testing. Git work.
** Today: Fix login issues. Repository related work. Documentation related work. Some server administration related work. Work work work...

* Jeremiah
** Finished first version of package removal script. (Does not remove sources, that hill have to be done later)
** Removed about 3.5 gigs of duplicate packaging on a test server, about 25% reduction.

* Tim
** Created new graphical icons/buttons for talk.maemo.org.

; 2009-04-24

* Ryan
** Yesterday: Worked on front page, filed newstyle bugs.
** Today: Last touches on front page (Thanks, Niels!), prod Niels about last touches on wiki template, triage and file some more Newstyle bugs.

* Niels
** Yesterday: Worked on new wiki styling, some newstyle fixes. Debugged repository issues.
** Today: Work on new wiki styling, look at other templates too.

* Jeremiah
** Added a feature to pkg-parse.pl
** Lots of testing, none of it built in
** Largely feature complete for the moment - parses a Packages file and outputs the different package version of _all_ packages in the repository
** Need to be automated and combined with another script that moves packages from the repos to a "morgue"

; 2009-04-23

* Ryan
** Yesterday: Yet more wiki cleanup, filed a lot of bugs on newstyle, fixed up some of the content.
** Today: Even yet more wiki cleanup, put together and deploy new wiki front page, test and criticize new wiki style for Niels (:P), file more newstyle bugs.

* Andre
** Yesterday: Feature jar
** Today: Mostly syncing internal tickets with public tickets (esp. version information - different systems and workflows...)

* Niels
** Yesterday: Worked on newstyle, published website!
** Today: Fix some newstyle bugs, use static version of avatar everywhere to speed things up, work on wiki style.

* Jeremiah
** Lots of hacking and testing of pkg-parse.pl
** Pushed to github so anyone can fork ;)
; 2009-04-22

* Ryan
** Yesterday: More wiki cleanup.
** Today: Yet more wiki cleanup, test newstyle.

* Niels
** Yesterday: Work on newstyle
** Today: Work on newstyle .. publish website

* Tim
** A little newstyle bug testing -- more tomorrow.
** Wrote another [http://maemo.org/community/council/so_what_do_you_think/ blog post] about site launch.

* Jeremiah
** Did some repo removal of more qt packages
** Started hacking on pkg-parse.pl, a script to manage duplicate packages in the repos

; 2009-04-21

* Andre
** Yesterdays: Usual business; Some internal stuff; bug 3846
** Today: Usual business; Feature Jar; Internal weekly report

* Jeremiah
** Mail, repo reduction

* Dave
** Yesterday: Working on newstyle - Community page
** Today: Finish content review of Community, improve "Get involved" and IRC pages, run web devel meeting.

* Niels
** Yesterday: Work on newstyle
** Today: Work on newstyle .. getting close! :)

* Tim
** maemo.org redesign meeting.
** Wrote [http://maemo.org/community/council/the_final_countdown/ blog post] about new maemo.org launch.

; 2009-04-20

* Jeremiah
** Hacked on an automated script to move packages out of the repos to reduce the load on indexing
** Discussed the repos and managing packages with Niels who had a lot of good ideas and experience to share

* Ryan
** Last few days: Wiki cleanup.
** Today: More wiki cleanup.

* Niels
** Friday: Worked on newstyle, debugged some git repository issues.
** Today: Work on newstyle.

* Tim
** Various newstyle bug reports and conversations.

; 2009-04-17

* Quim
** Yesterday and before: Took officially the action of "Maemo Summit 2009 - finalise venue" from Dave. Kees and I have reduced the number of candidates to 3. I need to contact them and fix the timing for a visit by Kees and myself, hopefully on May 4th. I expect the decision about the venue to be made on that week of May.
** Today: Contact venues and update [[Maemo_Summit_2009]].

* Dave
** Yesterday: Mostly caught up with administravia. One expense report left :(
** Today: Meet accountant, content revision for http://newstyle.maemo.org - fix links in community page - [https://bugs.maemo.org/show_bug.cgi?id=4316 bug #4316], revise & review Support and Development pages & text.

;2009-04-16

* Dave
** Yesterday: Caught up on email and attended web design IRC meeting.
** Today: Catching up on expenses and accounts, tracking email, and meetings.

* Niels
** Yesterday: Worked on newstyle. Attended web meeting.
** Today: Work on newstyle.

* Tim
** Wrote a News [http://maemo.org/community/council/new_maemo-org_soon_to_launch/ blog post] about newstyle progress.

;2009-04-15

* Dave
** Last week: Travelled to San Francisco for the Collaboration Summit. Kept up with email & IRC, and co-ordinated with Quim on visiting possible locations (conclusion: too costly, I will travel if there is a need later to see the final venue)
** Yesterday: Long weekend for Easter, spent the day with my parents visiting from Ireland.
** Today: Catch up after lay-off, and commit something other than venue to this Sprint.

* Niels
** Yesterday: Followed up on some upgrades. Catched up on mail. Work on newstyle.
** Today: Work on newstyle.

* Andrew
** Moved discussion on releasing HAM update to maemo-developers

* Tim
** maemo.org redesign meeting.

;2009-04-14

* Niels
** Few days ago: Worked on Downloads styling for newstyle, small style fixes.
** Today: Follow up on some hardware upgrades, catch up on mail. Work on newstyle.

* Jeremiah
** Removing a host of qt packages (v. 4.4) from diablo - they are no longer needed.

;2009-04-13

* Tim
** 9.04-12: Moved all newstyle.maemo.org Checklist items to Bugzilla.
** 9.04-12: Updated newstyle wiki page to reflect said changes (i.e., verbiage, link, etc.).
** 9.04-12: Added (and continuing to add) new requests for newstyle to Bugzilla.

* Jeremiah
** Away for Easter

;2009-04-09

* Niels
** Yesterday: Downloads api improvements, registration testing/fixes, some downloads import script fixes.
** Today: Website bug fixes, work on newstyle.

* Jeremiah
** List mail, reading about the dput bug that maybe I can work on.
** Wiki work, specifically [[debmaster]] page
** Not much else I am afraid, I have to clean my office and get ready to go away for Easter.

;2009-04-08

* Dave
** This week: Attending the Collaboration Summit in San Francisco, so will be mostly unavailable (but reading email).
** Yesterday: Web development IRC meeting (arrived late). Thanks to Tim for running & minuting it. Slow progress.
** Problems: Wondering if Niels & Neithan have the new website as their top priority? Things seem to be taking so much longer than estimated.

* Andre
** Last days: Fiddling with setting up a test environment & start creating patchsets for [https://bugs.maemo.org/show_bug.cgi?id=3846 bug 3846]
** Today: Collect a list of potential tickets for a potential [http://wiki.maemo.org/Task:Maemo_brainstorm brainstorm]. Yes, I said "potential". ;-)

* Niels
** Yesterday: Set up test environment for Daniel, requested more disk space for test vm, fixed time synchronisation issues on webserver cluster, traced some performance issues on internal server, worked on event registration for Quim. Fixed mail for webserver cluster. Monitored autobuilder for qwerty12. Discussed rebuild ideas with Jeremiah. Attended website redesign meeting. Pinged Ferenc about git.maemo.org ssl issue with git.
** Today: Downloads API improvements. Work on wiki documentation importing.

* Jeremiah
** Reducing the number of packages in diablo, reduced the repo by about 310 Megs. needs to come down a bit more since the package file is large.
** Build order list refinements
** Scan of ITt, mailing lists and #maemo
** Preparing to package git for maemo

;2009-04-07

* Niels
** Yesterday: Ragnaroek performance tracing/testing together with bergie. Apply karma ghost fixes. Look at static cache issues. Attend Sprint meeting. Push on SDK issues.
** Today: Setup test environment for Daniel. More performance tracing. Work on styling issues open issues.

* Jeremiah
** Mailing lists with council
** Trying to reduce the number of packages in diablo

* Tim
** 9.04-12: Website redesign meeting.
** 9.04-12: Sent out meeting minutes.

;2009-04-06

* Tim
** 9.04-12: Sent [http://lists.maemo.org/pipermail/maemo-community/2009-April/003634.html email] to maemo-community asking about using Bugzilla to test/log [http://newstyle.maemo.org newstyle.maemo.org].

* Andrew
** Put up draft of April 09 task log and asked for feedback/blanks to be filled in.

* Jeremiah
** Moved build order file to garage, working on building packages for fremantle with dpkg-buildpackage, hope to confer with Niels about the autobuild after meeting today.

;2009-04-03

* Jeremiah
** Nothing maemoish, working on my local infrastructure and dev machines

[[Category:Community]]
[[Category:maemo.org]]

Maemo.org Sprints/April 09

2009-05-07T12:52:23Z

192.100.124.156: Ferenc: update of tasks

== April 2009 Sprint planning ==
* [[Maemo.org Sprints/April 09/Meeting|Planning meeting]]: Monday, 2009-04-06 at [http://www.timeanddate.com/worldclock/fixedtime.html?month=4&day=6&year=2009&hour=13&min=30&sec=0 13:30 UTC] in [[IRC|#maemo-meeting]].
* Right after [[Maemo.org Sprints/March 09]] review.
* Followed by [[Maemo.org Sprints/May 09]].
* This sprint will be formally reviewed on [http://timeanddate.com/worldclock/fixedtime.html?month=5&day=7&year=2009&hour=13&min=30&sec=0&p1=0 2009-0507 at 13:30 UTC] in [[IRC|#maemo-meeting]].

==Tasks==
[[:Category:Ongoing|Ongoing]] tasks carried here from the previous sprint + New tasks committed by their owners in the sprint meeting. They come from the tasks in the [[Maemo.org_backlog|Backlog]] and the [[Maemo.org_proposals|Proposals]].

{| class="wikitable"
| style="background:LightGreen" | Completed
| style="background:LightBlue" | Good progress
| Just standing
| style="background:Orange" | Some help needed!
| style="background:Tomato" | Really stuck/delayed
|}

{| class="wikitable sortable"
|-
! Task ID
! Committed
! Due date
! Task
! Sprint priority
! Owner
! Percentage complete
! Notes
|- style="background:Tomato"
|8.11-01
|2008-11-04
|[[Maemo.org Sprints/May 09|May 09]]
|[[Task:Texts for maemo.nokia.com|Texts for maemo.nokia.com]]
|Should
|qgil
|20%
|Maemo 5 beta and Danish Weekend ate most of the time I had prepared for this.
|- style="background:LightGreen"
|8.11-02
|2008-11-04
|[[Maemo.org Sprints/April 09|April 09]]
|[http://bugs.maemo.org/show_bug.cgi?id=2179 Karma for applications - publish proposal]
|Must
|Bergie
|100%
|[[Task:Karma for applications|Karma providers list]] done
|-
|9.02-01
|2009-02-04
|[[Maemo.org Sprints/April 09|April 09]]
|[http://bugs.maemo.org/show_bug.cgi?id=3846 List Maemo bugzilla patches - create patchset]
|Should
|andre
|?
|
|- style="background:LightBlue"
|9.03-01
|2009-03-05
|[[Maemo.org Sprints/May 09|May 09]]
|[[Maemo Summit 2009]] - finalise venue
|Should
|qgil
|33%
|Venues visited by Kees, Niels and Quim. Decision between [http://www.westergasfabriek.nl/english/engels_welcome.php WesterGasFabriek] (waiting for their budget) and [http://www.felixmeritis.nl/en/ Felix Meritis].
|-
|9.03-02
|2009-03-05
|[[Maemo.org Sprints/?|?]]
|Create maemian from lintian
|Could / Should
|jeremiah
|5%
|https://garage.maemo.org/projects/maemian/
|-
|9.03-03
|2009-03-10
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Reducing number of external repositories|Update canonical list of external repositories.]]
|Must
|jeremiah
|10%
|Include key packages not in any repo
|-
|9.03-04
|2009-03-10
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Reducing number of external repositories|Reducing number of external repositories - contact outstanding owners]]
|Should
|jeremiah
|5%
|Includes chinook -> diablo
|
|9.04-01
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Talk:Git For Garage|Git For Garage - svn-git tooling]]
|Must
|ferenc
|50%
|Script done, and tested. Integration to the GForge UI is needed. Remaining tasks are to be pushed to May.
|
|9.04-02
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Talk:Git For Garage|Git For Garage - garage integration]]
|Should
|ferenc
|90%
|Gitweb's skin is not matching garage, but other than that this is done. Remaining task is to be pushed to May.
|- style="background:LightGreen"
|9.04-03
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - midgard]]
|Must
|Niels
|100%
|Deployed
|- style="background:LightGreen"
|9.04-04
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - mediawiki]]
|Must
|Niels
|100%
|Deployed
|-
|9.04-05
|2009-04-06
|[[Maemo.org Sprints/May 09|May 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - bugs]]
|Should
|X-Fade
|0%
|
|-
|9.04-06
|2009-04-06
|[[Maemo.org Sprints/May 09|May 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - ?]]
|Could
|X-Fade
|?
|
|-
|9.04-07
|2009-04-06
|[[Maemo.org Sprints/May 09|May 09]]
|[http://bugs.maemo.org/show_bug.cgi?id=2179 Karma for applications - implement]
|Should
|Hirvinen
|0%
|
|- style="background:LightBlue"
|9.04-08
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|Propose ITP process/workflow
|Should
|jeremiah
|75%
|http://wiki.maemo.org/ITP
|-
|9.04-09
|2009-04-06
|[[Maemo.org Sprints/May 09|May 09]]
|Setup SSO testing environment
|Must
|danielwilms
|0%
|URL?
|-
|9.04-10
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|Port packages from diablo -> fremantle
|Could
|jeremiah
|0%
|Specific enough? Needs task URL
|- style="background:LightGreen"
|9.04-11
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Open Source Proof Points|Open Source Proof Points - tidy up and merge wiki pages]]
|Must
|qole
|100%
|Rewrote [[Alternative operating systems]], pointed [[Task:Open Source Proof Points]] there. Done as much as I can do for now. Willing to add [[Alternative desktop environments]] in the next sprint.
|- style="background:LightGreen"
|9.04-12
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - testing]]
|Must
|timsamoff
|100%
| Beta launch date set for 1200 UTC, Wednesday, 22-04-2009.
|-style="background:LightBlue"
|9.04-13
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|[[Task:Maemo brainstorm|Maemo brainstorm]]
|Must
|NetBlade
|80%
| Deployed on Internal for testing, soon to go public beta
|- style="background:LightGreen"
|9.04-14
|2009-04-06
|[[Maemo.org Sprints/April 09|April 09]]
|Discuss sprint process improvements
|Must
|qole
|100%
|See [http://lists.maemo.org/pipermail//maemo-community/2009-April/thread.html#3636 thread]
|-style="background:LightGreen"
|9.04-10
|2009-04-07
|[[Maemo.org Sprints/April 09|April 09]]
|Reduce the number of packages in diablo through elimination of duplicate packages, old packages.
|Should
|jeremiah
|100%
|Script to do this [http://github.com/jeremiah/debian--package--array/blob/93bf80481e2a20c0fd0c0836dc4e5b9b19ee9e9a/pkg-parse.pl Now on github]
|
|-
|9.04-10
|2009-05-03
|[[Maemo.org Sprints/April 09|April 09]]
|Diagnose autobuilder issues
|Should
|jeremiah
|0%
| Autobuilder apparently removes source packages.
|-
|}

==Activity log==
Latest activity report goes on top.

;2006-05-07

* Niels
** Yesterday: Worked on dependency problem in autobuilder. Tried to debug login problem. Tested brainstorm.
** Today: Work on some documentation importing, continue debugging login issue. Attend meeting.

* Andre
** Yesterday: Mostly cleaning up older tickets & syncing
** Today: Continued cleaning up older tickets; bug 3846; meeting

* Dave
** Past 5 days: Working on a client project
** Since last report (21/4): May 1st long weekend. Working on content issues with new maemo.org, track newstyle fall-out & bugs, and dig into Midgard to allow me to start fixing some of these bugs on my own.

;2009-05-05
* Niels
** Yesterday: Visited possible summit locations in Amsterdam together with Quim and Kees
** Today: Catch up on email, look at autobuilder and dependency issues. Look at login issues.

* Jeremiah
** Updating external repos list
** Built search.maemo.org prototype -> [http://test.maemo.org/cgi-bin/search.cgi here]

;2009-05-04
* Niels
** Today: visit possible summit locations in Amsterdam together with Quim and Kees

* Jeremiah
** Started hacking on a search script for packages

;2009-05-01

* Ryan
** Past days: Dealing with [http://talk.maemo.org Talk] fallout, opened [http://bugs.maemo.org/describecomponents.cgi?product=Website bugzilla component] for Talk, filing Talk bugs.
** Today: Pushing Maemo School towards using the wiki, more Talk bugs.
** Problems: People hate change.
** Kudos: Reggie really kicks ass at bugzilla!

* Jeremiah
** A little community chatter in #maemo and on lists
** Gave the queue-manager a punch in the stomach to get it to index things.
** Re-installing fremantle 5 beta SDK

;2009-04-30

* Jeremiah
** Trying to get fremantle SDK to work on my machine
** re-indexing diablo on garage as it has stopped for some reason

; 2009-04-29

* Niels
** Yesterday: Beta SDK related work. Styled search.maemo.org and Extras Assistant. Forced new style on wiki. Helped on git.maemo.org issues and published qt4 fremantle binaries. Attended web meeting.
** Today: Try to get everything needed to upgrade the autobuilder to Maemo5 beta SDK. Look at login issues and fix bugs.

* Jeremiah
** Installing Beta SDK for testing.
** Removed 7 Gigs of old, duplicate packages from diablo

; 2009-04-28
* Niels
** Yesterday: Prepare for beta. Documentation related work
** Today: Beta SDK related work. Style search.maemo.org, style Extras Assistant.

* Andre
** Yesterdays: Prepare SDK beta ChangeLog; normal triaging work...
** Today: Potential Brainstorm tickets; SDK beta release it seems (reset Target Milestones etc); internal weekly report

* Jeremiah
** Beginning to sketch out maemian, reading lintian code
** Working on a python packaging tutorial
** tweaks to package removal code

* Tim
** maemo.org redesign meeting.

; 2009-04-27
* Niels
** Friday: Worked on and published wiki styling, fixed bugs in newstyle. Talk related things. Discussed app karma and brainstorm testing. Git work.
** Today: Fix login issues. Repository related work. Documentation related work. Some server administration related work. Work work work...

* Jeremiah
** Finished first version of package removal script. (Does not remove sources, that hill have to be done later)
** Removed about 3.5 gigs of duplicate packaging on a test server, about 25% reduction.

* Tim
** Created new graphical icons/buttons for talk.maemo.org.

; 2009-04-24

* Ryan
** Yesterday: Worked on front page, filed newstyle bugs.
** Today: Last touches on front page (Thanks, Niels!), prod Niels about last touches on wiki template, triage and file some more Newstyle bugs.

* Niels
** Yesterday: Worked on new wiki styling, some newstyle fixes. Debugged repository issues.
** Today: Work on new wiki styling, look at other templates too.

* Jeremiah
** Added a feature to pkg-parse.pl
** Lots of testing, none of it built in
** Largely feature complete for the moment - parses a Packages file and outputs the different package version of _all_ packages in the repository
** Need to be automated and combined with another script that moves packages from the repos to a "morgue"

; 2009-04-23

* Ryan
** Yesterday: Yet more wiki cleanup, filed a lot of bugs on newstyle, fixed up some of the content.
** Today: Even yet more wiki cleanup, put together and deploy new wiki front page, test and criticize new wiki style for Niels (:P), file more newstyle bugs.

* Andre
** Yesterday: Feature jar
** Today: Mostly syncing internal tickets with public tickets (esp. version information - different systems and workflows...)

* Niels
** Yesterday: Worked on newstyle, published website!
** Today: Fix some newstyle bugs, use static version of avatar everywhere to speed things up, work on wiki style.

* Jeremiah
** Lots of hacking and testing of pkg-parse.pl
** Pushed to github so anyone can fork ;)
; 2009-04-22

* Ryan
** Yesterday: More wiki cleanup.
** Today: Yet more wiki cleanup, test newstyle.

* Niels
** Yesterday: Work on newstyle
** Today: Work on newstyle .. publish website

* Tim
** A little newstyle bug testing -- more tomorrow.
** Wrote another [http://maemo.org/community/council/so_what_do_you_think/ blog post] about site launch.

* Jeremiah
** Did some repo removal of more qt packages
** Started hacking on pkg-parse.pl, a script to manage duplicate packages in the repos

; 2009-04-21

* Andre
** Yesterdays: Usual business; Some internal stuff; bug 3846
** Today: Usual business; Feature Jar; Internal weekly report

* Jeremiah
** Mail, repo reduction

* Dave
** Yesterday: Working on newstyle - Community page
** Today: Finish content review of Community, improve "Get involved" and IRC pages, run web devel meeting.

* Niels
** Yesterday: Work on newstyle
** Today: Work on newstyle .. getting close! :)

* Tim
** maemo.org redesign meeting.
** Wrote [http://maemo.org/community/council/the_final_countdown/ blog post] about new maemo.org launch.

; 2009-04-20

* Jeremiah
** Hacked on an automated script to move packages out of the repos to reduce the load on indexing
** Discussed the repos and managing packages with Niels who had a lot of good ideas and experience to share

* Ryan
** Last few days: Wiki cleanup.
** Today: More wiki cleanup.

* Niels
** Friday: Worked on newstyle, debugged some git repository issues.
** Today: Work on newstyle.

* Tim
** Various newstyle bug reports and conversations.

; 2009-04-17

* Quim
** Yesterday and before: Took officially the action of "Maemo Summit 2009 - finalise venue" from Dave. Kees and I have reduced the number of candidates to 3. I need to contact them and fix the timing for a visit by Kees and myself, hopefully on May 4th. I expect the decision about the venue to be made on that week of May.
** Today: Contact venues and update [[Maemo_Summit_2009]].

* Dave
** Yesterday: Mostly caught up with administravia. One expense report left :(
** Today: Meet accountant, content revision for http://newstyle.maemo.org - fix links in community page - [https://bugs.maemo.org/show_bug.cgi?id=4316 bug #4316], revise & review Support and Development pages & text.

;2009-04-16

* Dave
** Yesterday: Caught up on email and attended web design IRC meeting.
** Today: Catching up on expenses and accounts, tracking email, and meetings.

* Niels
** Yesterday: Worked on newstyle. Attended web meeting.
** Today: Work on newstyle.

* Tim
** Wrote a News [http://maemo.org/community/council/new_maemo-org_soon_to_launch/ blog post] about newstyle progress.

;2009-04-15

* Dave
** Last week: Travelled to San Francisco for the Collaboration Summit. Kept up with email & IRC, and co-ordinated with Quim on visiting possible locations (conclusion: too costly, I will travel if there is a need later to see the final venue)
** Yesterday: Long weekend for Easter, spent the day with my parents visiting from Ireland.
** Today: Catch up after lay-off, and commit something other than venue to this Sprint.

* Niels
** Yesterday: Followed up on some upgrades. Catched up on mail. Work on newstyle.
** Today: Work on newstyle.

* Andrew
** Moved discussion on releasing HAM update to maemo-developers

* Tim
** maemo.org redesign meeting.

;2009-04-14

* Niels
** Few days ago: Worked on Downloads styling for newstyle, small style fixes.
** Today: Follow up on some hardware upgrades, catch up on mail. Work on newstyle.

* Jeremiah
** Removing a host of qt packages (v. 4.4) from diablo - they are no longer needed.

;2009-04-13

* Tim
** 9.04-12: Moved all newstyle.maemo.org Checklist items to Bugzilla.
** 9.04-12: Updated newstyle wiki page to reflect said changes (i.e., verbiage, link, etc.).
** 9.04-12: Added (and continuing to add) new requests for newstyle to Bugzilla.

* Jeremiah
** Away for Easter

;2009-04-09

* Niels
** Yesterday: Downloads api improvements, registration testing/fixes, some downloads import script fixes.
** Today: Website bug fixes, work on newstyle.

* Jeremiah
** List mail, reading about the dput bug that maybe I can work on.
** Wiki work, specifically [[debmaster]] page
** Not much else I am afraid, I have to clean my office and get ready to go away for Easter.

;2009-04-08

* Dave
** This week: Attending the Collaboration Summit in San Francisco, so will be mostly unavailable (but reading email).
** Yesterday: Web development IRC meeting (arrived late). Thanks to Tim for running & minuting it. Slow progress.
** Problems: Wondering if Niels & Neithan have the new website as their top priority? Things seem to be taking so much longer than estimated.

* Andre
** Last days: Fiddling with setting up a test environment & start creating patchsets for [https://bugs.maemo.org/show_bug.cgi?id=3846 bug 3846]
** Today: Collect a list of potential tickets for a potential [http://wiki.maemo.org/Task:Maemo_brainstorm brainstorm]. Yes, I said "potential". ;-)

* Niels
** Yesterday: Set up test environment for Daniel, requested more disk space for test vm, fixed time synchronisation issues on webserver cluster, traced some performance issues on internal server, worked on event registration for Quim. Fixed mail for webserver cluster. Monitored autobuilder for qwerty12. Discussed rebuild ideas with Jeremiah. Attended website redesign meeting. Pinged Ferenc about git.maemo.org ssl issue with git.
** Today: Downloads API improvements. Work on wiki documentation importing.

* Jeremiah
** Reducing the number of packages in diablo, reduced the repo by about 310 Megs. needs to come down a bit more since the package file is large.
** Build order list refinements
** Scan of ITt, mailing lists and #maemo
** Preparing to package git for maemo

;2009-04-07

* Niels
** Yesterday: Ragnaroek performance tracing/testing together with bergie. Apply karma ghost fixes. Look at static cache issues. Attend Sprint meeting. Push on SDK issues.
** Today: Setup test environment for Daniel. More performance tracing. Work on styling issues open issues.

* Jeremiah
** Mailing lists with council
** Trying to reduce the number of packages in diablo

* Tim
** 9.04-12: Website redesign meeting.
** 9.04-12: Sent out meeting minutes.

;2009-04-06

* Tim
** 9.04-12: Sent [http://lists.maemo.org/pipermail/maemo-community/2009-April/003634.html email] to maemo-community asking about using Bugzilla to test/log [http://newstyle.maemo.org newstyle.maemo.org].

* Andrew
** Put up draft of April 09 task log and asked for feedback/blanks to be filled in.

* Jeremiah
** Moved build order file to garage, working on building packages for fremantle with dpkg-buildpackage, hope to confer with Niels about the autobuild after meeting today.

;2009-04-03

* Jeremiah
** Nothing maemoish, working on my local infrastructure and dev machines

[[Category:Community]]
[[Category:maemo.org]]

100Days/Sprint4

2008-08-27T10:22:07Z

192.100.124.156: /* Activity log */

==Sprint 4 planning==
* Planning meeting organized in the [[IRC|#maemo-meeting IRC channel]] on Tuesday 2008/08/12 at [http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=12&year=2008&hour=19&min=0&sec=0&p1=0 19:00 UTC].
* Right after [[100Days/Sprint3]] review.
* Holidays: Quim (9-31/aug), Niels (14 aug/6 sept probably no internet, No activity expected in Sprint 4), Dave (15 aug/31 aug, no internet).

There will be an IRC review meeting of this sprint on Tuesday 2008/09/02 [http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=2&year=2008&hour=19&min=0&sec=0&p1=0 19:00 UTC].

==Tasks==
[[:Category:Ongoing|Ongoing]] tasks carried here from the previous sprint + New tasks committed by their owners in the sprint meeting. They come from the tasks [[:Category:Accepted|accepted]] in the Backlog or [[:Category:Proposed|(re)new(ed)]] proposals.

{| class="wikitable"
| style="background:LightGreen" | Completed
| style="background:LightBlue" | Good progress
| Just standing
| style="background:Orange" | Some help needed!
| style="background:Tomato" | Really stuck/delayed
|}

{| class="wikitable sortable"
|-
! Committed
! Task
! Owner
! %
! Highlights
|- style="background:LightGreen"
| 2008-05-10 || Who's who in Maemo || Dave || '''DONE''' || Need to find a final home for [[People#Module_maintainers|the maintainer list]]
|- style="background:Orange"
| 2008-06-10 || [[Package_Categories|Better extras categories and debtags]] || Niels || 50% || Proposal drafted in wiki page, need to discuss on maemo-developers. (No progress will be made by me in Sprint4, need help!)
|- style="background:Orange"
| 2008-06-10 || Forum interface to mailing lists released || Bergie || 50% || Bugs in discussion component fixed, email archives need to be imported by Niels
|- style="background:Tomato"
| 2008-07-22 || [[Task:Using garage.maemo.org]] || Ferenc || 0% || Ran out of time in Sprint3.
|-
| 2008-08-12 || [[Task:Getting Nokia involved in bugs.maemo.org]] || Andre || 0% || Work on better organization of components in some products to fit better the scope of the corresponding Nokia developer teams, see [https://bugs.maemo.org/show_bug.cgi?id=3557 bug 3557]
|-
| 2008-08-12 || [https://bugs.maemo.org/show_bug.cgi?id=3553 Work on Bugzilla weekly summary functionality] || Karsten || 0% ||
|-
| 2008-08-12 || Several smaller Bugzilla enhancements || Karsten || 30% || see [https://bugs.maemo.org/show_bug.cgi?id=1417 bug 1417], [https://bugs.maemo.org/show_bug.cgi?id=2463 bug 2463], [https://bugs.maemo.org/show_bug.cgi?id=3350 bug 3350]
|-
| 2008-08-13 || [[Task:Maemo brainstorm]] || Oskari || 0% || New feature to the site.
|- style="background:LightBlue"
| 2008-08-13 || [[Task:Community Council]] || Henri || 60% || Dave handed off to Henri. Need to deploy & test election software. Database has been populated with electorate. Electorate list is up on wiki. Election announced on opt-in "Community updates" with mass mailer.
|}

==Bugs in product Website==
The bugs assigned in the last sprint meeting are marked as [https://bugs.maemo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Website&component=Bugzilla&component=Calendar&component=Documentation&component=Downloads&component=Garage&component=General&component=News&component=Profile&component=Repositories&component=Wiki&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=High&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= HIGH]. The bugs proposed for the next sprint are marked as [https://bugs.maemo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Website&component=Bugzilla&component=Calendar&component=Documentation&component=Downloads&component=Garage&component=General&component=News&component=Profile&component=Repositories&component=Wiki&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&priority=Medium&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= MEDIUM]. Only product/component maintainers can change this status. Comment on a bug if you want to push it up. Check also those marked as [https://bugs.maemo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Website&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=easyfix&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= EASYFIX].

What follows are the bugs that need special attention/progress.

For the record:

{{#bugzilla:
|product=Website
|status=!(Closed,Resolved,Fixed,Verified)
|priority=High
|order=priority
|columns=id, priority, severity, modified, product, status, summary, to
}}

Proposed bugs for Sprint 4 (Medium priority):

{{#bugzilla:
|product=Website
|status=!(Closed,Resolved,Fixed,Verified)
|priority=Medium
|order=priority
|columns=id, priority, severity, modified, product, status, summary, to
}}

==Activity log==
Latest activity report goes on top.

; Wednesday 2008-08-27

* Andre
** Today: More discussions with Nokia, triaging new bugs and syncing, getting on a plane
** Yesterday: Internal meeting about Error management, presentation about the maemo.org Bugmaster work; removed useless "Next" Target Milestone; internal weekly report

; Tuesday 2008-08-26

* Bergie
** Today: Multiple email support for forums, preparing for email import tomorrow.

; Monday 2008-08-25

* Karsten
** Today: Hacking bugzilla, tackle the weekly reports.

* Andre
** Today: Discussions with Nokia on workflows/processes and process, triaging new bugs/syncing, more preparing for internal meeting
** Friday: Preparing for internal meeting, looking at Bugzilla code, triaging/syncing bugs

; Sunday 2008-08-24

* Karsten
** Today: Cold, headache. Need to blog.
** Last couple days: Hacking bugzilla, working on fixes and customizations.

; Friday 2008-08-22

* Andre
** Today: Preparing for internal meeting, looking at Bugzilla code, triaging/syncing bugs
** Tuesday: Syncing and reproducing issues, add moreinfo-closing policy to [https://wiki.maemo.org/Bugs:Triage_guide Triage guide], internal report

; Tuesday 2008-08-19

* Andre
** Today: Syncing and reproducing issues, add moreinfo-closing policy to [https://wiki.maemo.org/Bugs:Triage_guide Triage guide], internal report
** Yesterday: Reproducing issues, triage new bugs and syncing

* Karsten
** More bugs. More bugzilla.

* Andre
** Today: Reproducing issues, triage new bugs and syncing, work on [Task:Getting_Nokia_involved_in_bugs.maemo.org]
** Friday: Sync reports and triage new ones; bugmail followup

* Bergie
** Today: Packaging changes made for karma, QB pager functionalities and maemo.org layout for deployment
** Friday: Karma debugging, preparing for the community elections

* Rambo
** Today: Quick look at the new virtual servers based on info from Ixonos & Marcell, commented to Marcell.

; Sunday 2008-08-17

* Karsten
** Today, yesterday: Hacking bugzilla, working on fixes and customization.
** Attempting to become a laywer, just to understand branding policies. IANAL.

; Saturday 2008-08-16

* Dave
** Yesterday: (I'm cheating to report progress here before I go on holiday) Published and announced list of eligible voters in [[Task:Community_Council/Eligible_voters]]. Published scripts I used to extract eligible voters from list, and also some interesting karma stats (over 80% of maemo users have under 5 karma points). Populated a mysql database with the electorate, got all of the details of the GNOME election process, and published scripts, database schema and web app. Passed off deploying it to Henri, but it should be pretty much done - need only a host with a working local MTA to send voting tokens, and a web server with PHP enabled to host voting application. Also need to maemo theme the 3 web pages involved.
** Until 2008-08-31: On holiday.

; Friday 2008-08-15

* Andre
** Sync reports and triage new ones; bugmail followup
** Yesterday: Add Bugzilla version and Target Milestone "4.1.1" for 4.2008.30-2 and set fixed bugs correctly, work on [Task:Getting_Nokia_involved_in_bugs.maemo.org]

* Dave
** Yesterday: Got list of accounts, resolved some karma issues, published final list of eligible candidates, pushed forward the council elections, announced profile changes and community council elections.
** Today: Test-run & deploy election software, publish list of eligible voters, go on holiday.

; Thursday 2008-08-14

* Dave
** Yesterday: Pushed Community council elections, generate list of elligible candidates. Not helped by flaky maemo.org. Got voting software.
** Today: Get list of maemo.org accounts + creation date. Publish list of elligible voters. Get voting software working. Try to get accurate karma counts for eligible candidate list. I have a couple of articles to write too. Announce profile updates and council elections.
Problems: Karma has been a problematic measure - some obvious people did not meet the karma requirement. Propose dropping karma requirement for voting for this first election, but bringing it back for future elections when karma is improved.

* Andre
** Add Bugzilla version and Target Milestone "4.1.1" for 4.2008.30-2 and set fixed bugs correctly, work on Task:Getting_Nokia_involved_in_bugs.maemo.org
** Tuesday: bugmail followup, Internal report, work on Task:Getting_Nokia_involved_in_bugs.maemo.org, prepare and have 100Days/Sprint4 meeting

* Bergie
** Tracked site slowness and crashes, and missed user imports, karma recounts and social news updates to ISP's watchdog script that had gone out of control. Fixed the situation with Ferenc.
** Generated favicon.ico for the new logo and deployed it in Midgard style

; Wednesday 2008-08-13

* Dave
** Yesterday: Prepare & attend Sprint meeting
** Today: Push community council election, get election software, nail down election rules, and announce the election. Announce updates to profile lists and ask people to update profiles.

* Bergie
** Installed new discussion forum version to internal and upgraded database structure

==Tasks==
To be committed in the sprint meeting from those listed in the [[Maemo.org backlog]] or [[Maemo.org proposals]].

Bugs:Stock answers

2008-08-25T07:27:14Z

192.100.124.156: remove useless backslash

=Bugzilla stock answers=

A quick collection for anybody triaging bug reports in Maemo Bugzilla. These stock answers are meant to be copied and pasted to bug reports that could be more useful. Please keep the product specific ones alphabetically sorted, and feel free to edit/enhance! -[[User:Andre]]

==General==

===too vague and generally bad report===

Thanks for reporting this. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read https://bugs.maemo.org/page.cgi?id=bug-writing.html and add a more useful description to this bug.

===version number===

Thanks for reporting this. Can you please tell us exactly which version you are using (Control Panel > General > About product)? Does the crash give you any sort of error message? Was anything else running at the time?

===Need a stacktrace (for Notes)===
Is there any error message when it crashes?
Can you please run Notes in a terminal window (Applications Menu -> Utilities > X Terminal, then enter the command "maemo-summoner /usr/bin/osso_notes.launch > log 2>&1" and hit the Enter key) and attach the
resulting "log" file here after it has crashed?

Having a core dump could be even more useful. It requires installing the "sp-rich-core" package from the tools repository[1] and creating a "core-dumps" directory to the memory card with at least few megabytes of free space. You can get core dumps also without the rich-core package, but they are much less useful (and without it pre-installed applications core dumps are then named maemo-launcher-*).

[1] http://maemo.org/development/tools/
(also features information about valgrind and strace)

===Old Software version===
Thanks for reporting this.
Can you please test this again running the latest available release? Also see https://wiki.maemo.org/Upgrading_tablet_OS for more information on how to flash your tablet.

===Duplicate===

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

===Incomplete (after moreinfo keyword set)===

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for/if you can still reproduce this. Thanks!

===Become root===
To do this, you have to become root first. Please see http://wiki.maemo.org/Root_access for instructions.

===Packet capture for SIP issues===
A packet capture could help to clarify which party causes the problem. tcpdump can be used on the Nokia device, and Wireshark/Ethereal from another host (you would probably have to rig your network for the latter). I'm not sure if the users can enable syslog; if yes, exporting TPORT_LOG=1 in
the environment (e.g. by editing /etc/osso-af-init/af-defines.sh) for telepathy-sofiasip is a way to get SIP traffic logs dumped into syslog. Also, /usr/lib/telepathy/telepathy-sofiasip can be launched standalone in a terminal.

==Potential Product specific answers==

===Applets (debugging)===
The easiest way to debug your applets is to run the hildon-desktop on scratchbox currently:
run-standalone.sh /usr/bin/hildon-desktop
From console you can see then the printouts. Debugging on the device is a bit harder.
For Python applets you might want to check pyphantom.

With Valgrind on x86-scratchbox one can debug applet problems (e.g. memory leaks):
af-sb-init.sh start
<wait until desktop starts>
kill $(pidof maemo_af_desktop)
export G_SLICE="always-malloc"
run-standalone.sh valgrind --tool=memcheck --num-callers=60 --leak-check=yes /usr/bin/maemo-summoner /usr/bin/maemo_af_desktop.launch

===Bluetooth DUN issues===
Is there any error message displayed?
Could you maybe provide a syslog and a hcidump (package "bluez-hcidump", also see http://maemo.org/development/documentation/man_pages/hcidump.html ) of the situation?
Which exact osso-ic version are you using (osso-ic does not exist in Diablo anymore)?
For your interest, there is also http://maemo.org/community/wiki/BluetoothDUN/
listing devices that are expected to work.

===Browser===
* Can you please tell us which browser type this is (Opera vs MicroB) by providing the output of "cat /home/user/.browser"?
* Can you please create a browser logfile? Enter about:config?prefname=browser.consolelogfile&prefvalue=/tmp/browserlog in the browser location bar, set that preference, reproduce the browser problem and post the content of the file /tmp/browserlog here (you can for example start the terminal application, run "more /tmp/browserlog" and copy the output to this bug report).

===Busybox===
Do you have some 3rd party version of Busybox installed?

===Charger issues===
Does the reboot loop stops when you disconnect the charger? Are you using the original N800 charger or something else? If you have another compatible charger, does the problem occur also with that? Does the crash/reboot happen only if you boot with charger, or if you plug the charger in when the device is already running?

===Flasher===
Windows: What are current versions (Control Panel/Add or Remove Programs) of WinFlasher+ (Nokia Internet Tablet Update Wizard) and Nokia Connectivity Cable Driver? What OS (XP, Windows 2000)? What is the exact error message you get? Is .NET 2.0 framework installed (Control Panel -> Add or Remove Programs)?

===Internet Tablet Video Converter===
AVI is just a container format, what matters is the codec. Can you please find out which codec your camera uses? You might want to check the camera manual. Thanks!
Are there any error messages when the crash happens?
Did the application install cleanly with no problems? Could you try to uninstall and reinstall again from a clean download please?

===Input Methods===
http://maemo.org/development/documentation/how-tos/4-x/extending_hildon_input_methods.html

===MMC/SD card related (Product "System software/mmc-and-usb")===
Has this happened with any other card? What is your card manufacturer, model and size?

Could you check whether your card is corrupted (on device you can use "dosfsck -n" command, or you can plug USB cable and use your PC disk check utility) and save the information about the card configuration?
Would it also be possible for you to copy all the data from the card to safety[1], reformat the card using the device Filemanager (or if you do that from the PC, mention it) and try whether it still causes the lockup?
If not, copy the files back to the card to see whether it now causes lockup. So we can see whether lockup is caused by card itself, its formatting, the data on it, or corrupted file system.
[1] if you know Linux and don't mind some extra effort, it would be preferable to "dd" the whole mounted USB storage device content to an image file so that you get a disk image that can be copied directly back, otherwise you can use normal copy.

===Modest===
Does starting
/usr/bin/maemo-summoner /usr/bin/modest.launch showui
provide some output?
====Debugging the connection to the mail server====
Can you please start an X Terminal window and enter
export "CAMEL_DEBUG"="all"
to enable the debug mode of the mail library, and after that
/usr/bin/maemo-summoner /usr/bin/modest.launch showui > log 2>&1
to start the email application. Then try to connect to the mailserver.
Attach the logfile named "log" here (please check for confidential data before attached).

====Modest not exiting but eating CPU====
I assume you waited for 10 minutes to make sure that this wasn't any time taking resource freeing? Does this also happen if you are not using SSL?
Can you provide us a wireshark or pcap log? Can you maybe strace on the hanging process and post the information here? Can you kill the hanging process with signal=11 to provide us with a core dump?

===Power management===
https://maemo.org/community/wiki/poweranddevicemanagement/

Battery drain can have many potential reasons:
* bad 3rd party applet/application not idling when not used
* buggy WLAN access point (not implementing power management properly)
** setting device to offline mode when not in use helps
* Keeping device in RD mode
* Corrupted memory card
* Metalayer crawler related bugs (only currently known is about gstreamer/WMA)
* etc.

===Reboot related===
http://maemo.org/community/wiki/ReportingRebootIssues/

===Skype===
Please file Skype bugs against https://developer.skype.com/jira instead.

===Wifi/WLAN related===
Does running "/etc/init.d/networking restart" update the list of wifis?

Asking for more information:

* What AP you have?
** Make and model?
** Firmware version?
** Hardware revision?
** What are the encryption settings? (open/WEP/WPA-PSK/WPA-EAP)
* What's the distance to the AP?
* How many APs do you have?

PSM problems:

* Does disabling Power Save Mode (PSM) in N800/N810 help?
* AP settings:
** What's the beacon interval?
** What's the DTIM period?

Maemo Summit 2008

2008-07-03T18:42:17Z

192.100.124.156: /* Travel */

'''Join the first Maemo Summit'''

'''Berlin, September 19-20''' @ [http://c-base.org/ c-base] - right after http://www.osimworld.com
[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html Free registration].

Know more about Nokia's Linux platform and its evolution. Meet the core team, 3rd party professional developers and key community contributors. Showcase and discuss your work. Learn, share, hack. And have fun!

The [http://www.osimworld.com Open Source in Mobile World] conference is an interesting venue to know more about the business and technical context of the Maemo platform. Nokia is active in this event and invites the Maemo community to join it. After the conference we propose the first Maemo Summit calling to all contributors.

== Program ==

The program is still open. The basic idea is to have few and well executed session plus plenty of free time and free-form activities.

=== Scheduleton ===
These are just ideas for a schedule skeleton. You can propose improvements in the [[Talk:Maemo summit 2008|discussion]] page.

'''Friday 19'''

* 9:00 - Opening doors
* 9:30 - Welcome!, by [http://jaaksi.blogspot.com/ Ari Jaaksi] (VP - Maemo Software @ Nokia)
* 10:00 - The outside view, by A Well Known Speaker
* 10:30 - Hildon UI Vision, by Harri Kiljander (Director, User Experience - Maemo Software @ Nokia)
* 11:00 - What Maemo users want, by [http://tabletblog.com/2008/05/3rd-anniversary-community-spotlight.html Reggie Suplido] ([http://www.internettablettalk.com/ Internet Tablet Talk]) and [http://www.neoncherry.com/ Krisse] ([http://tabletschool.blogspot.com/ Internet Tablet School])
* 11:30 - The Maemo Proposition, by Peter Schneider (Head of Platform Marketing, Maemo Software @ Nokia)
* 12:00 - break
* 12:15 - Lightning sessions, 5-10 min each. ([[Talk:Maemo summit 2008#Lightning sessions|propose one]])
* 14:00 - Lunch!
* 15:00 - BoF meetings & workshops - Round 1 - several sessions at a time ([[Talk:Maemo summit 2008#BoFs and Workshops|propose one]])
* 16:00 - Round 2 - tbc
* 17:00 - Round 3 - tbc
* 18:00 - Chill out

Dinner, music, drinks tbd.

Dress code recommended: t-shirt with the maemo.org logo of [[Maemo.org_logo_contest_submissions|your choice]]. DISCLAIMER: can't be the winner logo. ;)

'''Saturday 20'''
100% community driven schedule. Space available. Just organize your activity and advertise it here.

== Venue ==

The Maemo Summit is held in the heeadquarter of '''[http://www.c-base.org c-base]''', a non-profit association located in Berlin, Germany which has about 300 members. The purpose of this association is to increase knowledge and know-how regarding computer software, hardware and data networks ([http://en.wikipedia.org/wiki/C-base more]).

c-base is in the very Mitte of Berlin.

== Participants ==
'''[https://maemo.org/news/events/registrations/register/2f91448248e711dd8bcbb7b26102ad49ad49.html REGISTER - FREE OF CHARGE'''

It's the first Maemo Summit and it is good to know in advance who plans to attend, to fine tune practicalities and have enough space, connection, drinks, food.

Yes, the entrance is free. Registration is still requested for planning purposes.

== Travel ==
[[Talk:Maemo_Summit_2008#Travel|Apparently]] there are options as affordable as 20€ including taxis from Stansted! [[Talk:Maemo_Summit_2008#Travel|Share your travel tips]] from different locations.

== Accommodation ==
'''We are looking for affordable accommodation options!''' (and we got [[Maemo_Summit_2008#Accommodation|some ideas]], thank you!) Tips are welcome. The budget for sponsoring contributors is fixed, which means that cheaper accommodation will bring more people to the Summit.

== Sponsoring community contributors ==

See [[Maemo Summit 2008/Sponsorship]].

== Maemo in the OSiM program ==
See [[Maemo in OSiM World 2008]].

== Links ==

Feel free to share/spread/forward/email...

* [http://upcoming.yahoo.com/event/839617/ Maemo summit on Upcoming!]
* [http://www.facebook.com/event.php?eid=16582874206 Maemo summit on Facebook - requires FB registration]

[[Events]]