MeeGo wiki - User contributions [en]

MeeGo Conference Spring 2011/Accommodation

2011-05-05T21:16:14Z

Jnwi:

The MeeGo Conference has a special rate with the [http://sf2011.meego.com/logistics/hotel San Francisco Hyatt Regency Embarcadero Center]. If you have been approved for sponsored travel, please ensure that you have booked a room at the Hyatt through the [https://www.eiseverywhere.com/ereg/index.php?eventid=19946 conference registration tool] already. The hotel will modify your reservation based upon the input provided below.

Sponsored participants will receive up to 4 nights in the conference hotel, in a dual occupancy room. MeeGo will pay for the room rate and taxes for 4 nights, and you will be responsible for any other charges to the room. Please note the total duration of your stay below (e.g., arriving early for Conference Warm Up or staying a night after the conference).

If sponsored attendees do not have a roommate preference, we'll assign one for you. All roommates must also be conference attendees. If you request a roommate that is not sponsored, they will be responsible for the remainder of the room fee.

If you plan to spend more time in San Francisco and would like to share costs with a roommate before or after the conference, please note it in the last table. This is for convenience and matching roommates only; you will need to manage your own hotel reservations for these nights.

{| border="1"
|-
!colspan="3"|Roommate 1
!colspan="3"| Roommate 2
!rowspan="2" style="width:200px"| Considerations
|-
!style="width:200px"|Name
!style="width:100px"|Arrive
!style="width:100px"|Depart
!style="width:200px"|Name
!style="width:100px"|Arrive
!style="width:100px"|Depart
|-
|Alan Bruce||May 22||May 25||Stephen Gadsby||May 22||May 25||
|-
|Andrea Grandi||May 21||May 25||Thomas Perl? || || ||
|-
|Andrew Flegg||21 May||26 May||Tim Samoff||20 May, 15:50||23 May (switching hotels, but will be in SF through the 26th)||
|-
|Andrew Olmsted||22 May||26 May || || || ||
|-
|Andrew Zhilin|| || || || || ||
|-
|Anselmo Lacerda S. de Melo|| || || || || ||
|-
|Arkadiusz Stopczynski|| || || || || ||
|-
|Artur Souza|| || || || || ||
|-
|Brendan Le Foll|| || || || || ||
|-
|Cornelius Hald|| || || || || ||
|-
|Dan Leinir Turthra Jensen|| || || || || ||
|-
|Dave Neary|| || || || || ||
|-
|Dimitris Glezos|| || || || || ||
|-
|Ed Page|| May 21st @ 10:00am || May 26th at 4:00pm || || || ||
|-
|Felipe Crochik||22nd ||25th || || || ||
|-
|Ferenc Szekely|| || || || || ||
|-
|Frank Karlitschek|| || || || || ||
|-
|Gabriel Beddingfield|| || || || || ||
|-
|Gustavo Padovan||May 22nd || May 26th || || || ||
|-
|Hashiq Nazir|| May 20th || May 25th || || || ||
|-
|Jakob Eg Larsen|| || || || || ||
|-
|Jarkko Moilanen|| || || || || ||
|-
|Josh Soref|| || || || || ||
|-
|Julian Fourgeaud|| || || || || ||
|-
|Maitrey Mishra|| || || || || ||
|-
|Michael Hasselmann|| || || || || ||
|-
|Michał Sawicz|| || || || || ||
|-
|Miia Ranta|| || || || || ||
|-
|Mitul Bhat|| || || || || ||
|-
|Niels Mayer|| || || || || ||
|-
|Randall Arnold||21 May 10:30 AM||26 May 5:30 PM||Jens Wiik|| 2011-05-21 21:30|| 2011-05-26 07:10 ||
|-
|Robert Bauer|| || || || || ||
|-
|Sivan Greenberg|| || || || || ||
|-
|Tatsiana Makava|| || || || || ||
|-
|Thomas Perl|| || || || || ||
|-
|Tom Swindell||21 May||25 May|| || || ||
|-
|Uladzislau Vasilyeu|| || || || || ||
|-
|Zak Borg||20 May ||25 May || || || ||

|}

== Non-Conference Lodging ==

If you plan to stay in San Francisco after May 26 and are looking for a roommate to share costs, note it here. You will be responsible for making your own lodging arrangements, and these nights are not eligible for MeeGo sponsorship.

{| border="1"
|-
!colspan="3"|Roommate 1
!colspan="3"| Roommate 2
!rowspan="2" style="width:200px"| Considerations
|-
!style="width:200px"|Name
!style="width:100px"|Arrive
!style="width:100px"|Depart
!style="width:200px"|Name
!style="width:100px"|Arrive
!style="width:100px"|Depart
|-
|Your name
|May 21
|May 25
|Your roommate's name
|May 21
|May 25
|Staying in different hotel, etc
|}

Yet Another GUI Project

2011-04-27T10:02:57Z

Jnwi: /* Getting involved */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
**Gokul. S. Kartha, everyourgokul ät the google-run mail service
**Naveen Verma, ernaveenverma ät the google-run mail service
*Graphics designers
**Johannes Siipola, joppu1 ät the google-run mail service
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
***Naveen Verma, ernaveenverma ät the google-run mail service
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

= Licensing =

All contributions must be licensed under [http://www.gnu.org/licenses/quick-guide-gplv3.html the third version of the GPL] in order to prevent Tivoization. Additionally, contributors grant the project's leaders the right to change the license on libraries and widgets to LGPLv3 should they so decide. (Why not choose LGPL immediately? [http://www.gnu.org/licenses/why-not-lgpl.html Read this].)

Yet Another GUI Project

2011-04-21T15:22:17Z

Jnwi: /* Getting involved */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
**Gokul. S. Kartha, everyourgokul ät the google-run mail service
**Naveen Verma, ernaveenverma ät the google-run mail service
*Graphics designers
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
***Naveen Verma, ernaveenverma ät the google-run mail service
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

= Licensing =

All contributions must be licensed under [http://www.gnu.org/licenses/quick-guide-gplv3.html the third version of the GPL] in order to prevent Tivoization. Additionally, contributors grant the project's leaders the right to change the license on libraries and widgets to LGPLv3 should they so decide. (Why not choose LGPL immediately? [http://www.gnu.org/licenses/why-not-lgpl.html Read this].)

Yet Another GUI Project

2011-04-20T12:18:58Z

Jnwi: /* Getting involved */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
**Gokul. S. Kartha, everyourgokul ät the google-run mail service
*Graphics designers
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
***Naveen Verma, ernaveenverma ät the google-run mail service
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

= Licensing =

All contributions must be licensed under [http://www.gnu.org/licenses/quick-guide-gplv3.html the third version of the GPL] in order to prevent Tivoization. Additionally, contributors grant the project's leaders the right to change the license on libraries and widgets to LGPLv3 should they so decide. (Why not choose LGPL immediately? [http://www.gnu.org/licenses/why-not-lgpl.html Read this].)

Yet Another GUI Project

2011-04-20T10:42:24Z

Jnwi: /* Licensing */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
**Gokul. S. Kartha, everyourgokul ät the google-run mail service
*Graphics designers
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

= Licensing =

All contributions must be licensed under [http://www.gnu.org/licenses/quick-guide-gplv3.html the third version of the GPL] in order to prevent Tivoization. Additionally, contributors grant the project's leaders the right to change the license on libraries and widgets to LGPLv3 should they so decide. (Why not choose LGPL immediately? [http://www.gnu.org/licenses/why-not-lgpl.html Read this].)

Yet Another GUI Project

2011-04-20T10:41:33Z

Jnwi: /* Licensing */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
**Gokul. S. Kartha, everyourgokul ät the google-run mail service
*Graphics designers
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

= Licensing =

All contributions must be licensed under [http://www.gnu.org/licenses/quick-guide-gplv3.html the third version of the GPL] in order to prevent Tivoization. Additionally, contributors grant the project's leaders the right to change the license on libraries and widgets to LGPLv3 should they so decide. (Why not choose LGPL immediately? [http://www.gnu.org/licenses/why-not-lgpl.html Read this])

Yet Another GUI Project

2011-04-20T10:37:12Z

Jnwi: /* Licensing */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
**Gokul. S. Kartha, everyourgokul ät the google-run mail service
*Graphics designers
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

= Licensing =

All contributions must be licensed under [http://www.gnu.org/licenses/quick-guide-gplv3.html the third version of the GPL] in order to prevent Tivoization. Additionally, contributors grant the project's leaders the right to change the license on libraries and widgets to LGPLv3 should they so decide.

Yet Another GUI Project

2011-04-20T10:36:58Z

Jnwi: /* Licensing */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
**Gokul. S. Kartha, everyourgokul ät the google-run mail service
*Graphics designers
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

= Licensing =

All contributions must be licensed under [http://www.gnu.org/licenses/quick-guide-gplv3.html the third version of the GPL] in order to prevent Tivoization.
Additionally, contributors grant the project's leaders the right to change the license on libraries and widgets to LGPLv3 should they so decide.

Yet Another GUI Project

2011-04-20T10:29:06Z

Jnwi:

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
**Gokul. S. Kartha, everyourgokul ät the google-run mail service
*Graphics designers
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

= Licensing =

All contributions must be licensed under [http://www.gnu.org/licenses/quick-guide-gplv3.html the third version of the GPL] in order to prevent Tivoization.

Yet Another GUI Project

2011-04-20T10:24:48Z

Jnwi: /* Getting involved */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
**Gokul. S. Kartha, everyourgokul ät the google-run mail service
*Graphics designers
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

Yet Another GUI Project

2011-04-20T10:21:06Z

Jnwi: /* Getting involved */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
*Graphics designers
*Packaging team
**Sushma Goutam, write2sushma ät the google-run mail service
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

Yet Another GUI Project

2011-04-16T12:38:55Z

Jnwi: /* Task switcher and application menus */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in fullscreen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

Yet Another GUI Project

2011-04-16T12:35:45Z

Jnwi: /* Scope */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too featureless or offered poor usability if advanced features are present.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**[[User:Wick3d|Jerry Jalava]], firstname . lastname ät iki.fi
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in full screen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

Yet Another GUI Project

2011-04-16T06:46:16Z

Jnwi: /* Desktop */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too simple or unnecessarily complicated.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**Jerry Jalava
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

In standby mode, pressing and holding the display will brighten the normal widgets without unlocking the phone.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in full screen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

Yet Another GUI Project

2011-04-16T01:06:06Z

Jnwi: /* Getting involved */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too simple or unnecessarily complicated.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]], firstname dot lastname ät kolumbus.fi
**Jerry Jalava
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in full screen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

Yet Another GUI Project

2011-04-16T00:34:47Z

Jnwi: /* Desktop */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too simple or unnecessarily complicated.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]]
**Jerry Jalava
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval (widgets for SMS etc. will be woken up when the event occurs). All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in full screen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

Yet Another GUI Project

2011-04-16T00:30:37Z

Jnwi: /* Preliminary UI Concept */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too simple or unnecessarily complicated.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]]
**Jerry Jalava
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval. All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in full screen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

== Text editing ==

All multiline text boxes run in Vi emulation mode by default, starting up in insert mode. This allows the novice to continue as usual, while the power user can quickly access advanced functionality that would be impossible to include in any kind of menu system.

Yet Another GUI Project

2011-04-16T00:24:54Z

Jnwi: /* Preliminary UI Concept */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too simple or unnecessarily complicated.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]]
**Jerry Jalava
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval. All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in full screen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

== Buttons ==

When buttons are used in applications with scrolling content, they tend to waste a lot of screen space. Our transparent buttons, labeled with a minimal font size and fading borders, let users see almost 100% of the content.

Pressing inside the bordered area activates the button like any other. Drags can be started from outside and end inside a button without focus shifting to the button.

In the example picture, a browser has chosen to provide immediately accesible back and forward functions, and use the rest of the buttons for tabs.

Only 5 buttons are available in both landscape and portrait mode. In portrait, 5 is still relatively easy to use. When overflow occurs, one button changes into a menu. Applications should avoid using more than 5 buttons.

[[File:YagpTransparentbuttons.png]]

File:YagpTransparentbuttons.png

2011-04-16T00:22:27Z

Jnwi: Transparent button concept for yet another gui project.

Transparent button concept for yet another gui project.

Yet Another GUI Project

2011-04-16T00:00:33Z

Jnwi: /* List view: multiple selection and secondary actions */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too simple or unnecessarily complicated.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]]
**Jerry Jalava
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval. All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in full screen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.

[[File:Multiselect.jpg]]

Yet Another GUI Project

2011-04-16T00:00:22Z

Jnwi: /* List view: multiple selection and secondary actions */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too simple or unnecessarily complicated.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]]
**Jerry Jalava
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval. All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in full screen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

The demo pic is using Maemo 5 - ignore the rest of the UI.
[[File:Multiselect.jpg]]

Yet Another GUI Project

2011-04-15T23:59:20Z

Jnwi: /* Preliminary UI Concept */

= Scope =

The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too simple or unnecessarily complicated.

To succeed, this project needs to provide:
*An overall vision and UI guidelines
*A set of QML widgets
*A task switcher and desktop
*Important core user interfaces like SMS, email, media player, etc.
*Good documentation for developers writing other applications

The above will ideally all run on a vanilla MeeGo image, avoiding the need to code more than a new GUI for most applications.

= Getting involved =

In order to move faster, teams should work in parallel on the different applications, after the widgets have reached a reasonable state. Feel free to add your name to non-management teams and even volunteer new apps to the list, but introduce yourself to the main organizers if you're new.

*Project management and UI design
**[[User:jnwi|Jens Wiik]]
**Jerry Jalava
*QML Widget developers
*Graphics designers
*Packaging team
*Application developers (vanilla MeeGo applications will be used at first, and replaced one by one)
**Address book
**SMS
**Media player
**File manager
**Terminal
**Web browser
**Email
**Photo gallery
**Task switcher
**Desktop
**Calendar

= Preliminary UI Concept =

== Desktop ==

AMOLED displays allow devices to display information on standby screens without wasting huge amounts of energy. Symbian^3 displays a clock, for example. We will not stop there. Our desktop widgets have two modes: normal, and standby. This allows the user to customize the look of the standby screen without having to access a separate configuration interface.

Desktop widgets should register a wakeup interval with the desktop manager for standby mode. Available intervals are kept simple: 1, 5, 10, 30, 60 minutes. In practice only the clock should need the smallest interval. All widgets registered for a certain interval are woken up at the same time so that the CPU can sleep for as long as possible.

We do not, however, deny CPU time to normal apps while in standby mode.

[[File:YagpDesktopstandby.jpg]]

== Task switcher and application menus ==

Mobile devices have limited screen space, and having menu bars visible all the time wastes a lot of it. Our applications are always in fullscreen mode, and the menu bar of the current application is instead visible in the task switcher. Combining the two reduces the amount of modes that are necessary.

Returning to the application is done by pressing in an empty area. Maemo 5 returns to the desktop when this is done, but in our case the desktop becomes just another window.

The task switcher is activated either through a hardware button or by a touch gesture. There are no hints when in full screen mode - they waste space and this action is so frequent it should be memorized.

[[File:Taskswitcher.jpg]]

== List view: multiple selection and secondary actions ==

Many mobile applications do not include support for multiple selection even though they could greatly benefit from it. This probably has two main causes: checkboxes waste space and look ugly.

We can do better. All list views will support multiple selection by default wherever it makes sense. It is both attractive and unobtrusive if done right: by having a separate background stripe that triggers the selection action.

Even better, the same interface can be used to provide secondary actions - something which is often extremely annoying in touch interfaces. When even a one item selection is made, a bar of buttons slides out from somewhere with the actions that can be performed.

[[File:Multiselect.jpg]]

File:Multiselect.jpg

2011-04-15T23:58:06Z

Jnwi: Multiple selection concept for yet another gui project.

Multiple selection concept for yet another gui project.

Yet Another GUI Project

2011-04-15T23:50:01Z

Jnwi: /* Preliminary UI Concept */

File:Taskswitcher.jpg

2011-04-15T23:43:07Z

Jnwi: Task switcher concept for yet another gui project.

Task switcher concept for yet another gui project.

Yet Another GUI Project

2011-04-15T23:38:18Z

Jnwi: Created page with "= Scope = The purpose is to provide a fully functional mobile GUI for power users that is both efficient and moderately easy to learn. Previous GUI:s have often been either too..."

File:YagpDesktopstandby.jpg

2011-04-15T23:28:38Z

Jnwi: uploaded a new version of "File:YagpDesktopstandby.jpg"

Desktop concept for yet another gui project.

File:YagpDesktopstandby.jpg

2011-04-15T23:26:44Z

Jnwi: Desktop concept for yet another gui project.

Desktop concept for yet another gui project.

Local MeeGo Networks/MeeGo Network Finland/Meeting Agenda 2011 04 03

2011-04-02T11:14:44Z

Jnwi: /* Team reports */

Local MeeGo Networks/MeeGo Network Finland/Meeting Agenda 2011 04 03

2011-04-02T11:14:00Z

Jnwi: /* Team reports */

User:Jnwi

2011-03-25T11:21:38Z

Jnwi: Created page with "*Organizer, [http://www.meetup.com/Helsinki-MeeGo-Network Helsinki MeeGo Network] *Head of marketing team, [http://summit.meegonetwork.fi/ MeeGo Summit FI] *M.Sc. International B…"

*Organizer, [http://www.meetup.com/Helsinki-MeeGo-Network Helsinki MeeGo Network]
*Head of marketing team, [http://summit.meegonetwork.fi/ MeeGo Summit FI]
*M.Sc. International Business
*Free Software enthusiast

Local MeeGo Networks/MeeGo Network Finland/MeeGo Summit FI

2011-03-25T11:10:43Z

Jnwi: /* Marketing Team */

<div style="float:right;background-color:#fff;width:400px;height:520px;border: solid 1px #ddd;padding:15px;font-size:1.3em;"><b>Sponsors:</b><ul style="list-style:none;"><li>[[File:Ixonos-logo.gif]] (Platinum)</li><li>[[File:Tieto.jpg]] (Gold)</li><li>[[File:Intel-logo.png‎]] (Gold)</li><li>[[File:futurice_logo.png]] (Silver)</li><li>[[File:ICS-logo.gif‎]] (Silver)</li><li>[[File:Nomovok.png‎]] (Silver)</li><li>[[File:Symbio.png‎]] (Silver)</li></ul></div>

= Developer to developer =
Tampere initiated the first [[Local_MeeGo_Networks|Local Meego Network]] in Europe, [http://www.meetup.com/Tampere-MeeGo-Network/ Tampere Meego Network]. This is annual summit which is held in different locations around Finland. Tampere will host the first Regional Meego Summit in the world. Although the first Summit is at Tampere, this is a joined effort.

<div style="float:right;background-color:#fff;width:280px;height:160px;border: solid 1px #ddd;padding:15px;font-size:1.3em;">[[Image:MeeGoSummitNetworkLogo-RGB-72_Summit-01.jpg‎|link=http://summit.meegonetwork.fi]]</div>

'''[http://www.meetup.com/Tampere-MeeGo-Network/ Tampere] and [http://www.meetup.com/Helsinki-MeeGo-Network/ Helsinki] local networks have joined forces and other local networks are also welcome to participate! Furthermore, this conference will host Finnish hacker & OSS event ''Finhack'' (16th Apr) '''

The summit is free of charge, but the amount of seats is limited! Program includes:
* Keynotes
* Three tracks
* Meegathon competition
* Party
* BoFs & Workshops
* Quadricopter fun

== Details ==
* Location: Tampere, Finland. Finlayson area (Plevna, [http://www.uusitehdas.fi/en/ New Factory])
* Time: 15.-16. April 2011
* Duration: 2 days (Fri-Sat)
* Registration fee: Free!
* Seat amount: max 300
* Registration required: yes (address here)
* Web: http://summit.meegonetwork.fi
* '''[[Local_MeeGo_Networks/MeeGo_Network_Finland/roadmap | Roadmap/important dates]]'''

== Organizers ==
'''Main organizer:'''
{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"|Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Ilkka Lehtinen
| General, sponsors
| Head
| [http://www.coss.fi/en COSS]
|}

'''Co-Organizers:'''

{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"| Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Jarkko Moilanen
| General + Program (Community & hackers)
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Jukka Matikainen
| ?
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Matti Saastamoinen
| General, sponsors
| Organizer
| [http://www.coss.fi/en COSS]
|-
| Ville Kairamo
| Facilities
| Organizer
| [http://www.uusitehdas.fi/en NewFactory]
|}

== Teams ==
MNFI community needs different type of teams and task-forces to arrange activities. Members of the teams should be from the member networks but foreign members are also welcome. Some of the teams are active throughout the year, but some are active only before and during our annual Summits.

All teams (should) have a lead which coordinates the team efforts. To join a team is simple:
* add your name to the team member list and
* if possible contact the lead in IRC-channel (#meego-fi)

=== Program Task-force ===
The committee has been formed by inviting suitable MeeGo Network Finland -community members to it.

'''Members'''
* [http://meego.com/users/bergie Henri Bergius] (bergie)
* [http://meego.com/users/jukkaeklund Jukka Eklund] (jukkaeklund)
* [http://meego.com/users/timoph Timo Härkönen] (timoph)
* (lead) [[User:Kyber | Jarkko Moilanen ]] (kyb3R)



=== Marketing Team ===
Responsible mainly for:
*Marketing material such as posters and leaflets
*Media policy
*Press releases and other press issues
*Website content policy
*Social media accounts

If you want to join, contact jnwi. More information [[Local_MeeGo_Networks/MeeGo_Network_Finland/Marketing_Team|here]].

=== Tech Team ===
Effective and open communication has two sides: internal and external. This team is responsible for internal communication tools which include methods to share information among local networks and members. Working and transparent communication is vital to our community since our activities are coordinated with virtual tools such as email, IRC and portal.

External communication refers to the different tools we use to communicate with the public and global MeeGo community. For these purposes we use various social media services such as [http://twitter.com/meegofi twitter.com/meegofi], [http://facebook.com/meegofi facebook.com/meegofi] and [http://identi.ca/meegofi identi.ca/meegofi].

* More information, tasks and how to join can be found [[Local_MeeGo_Networks/MeeGo_Network_Finland/Communication_Team|here]]

=== Hosting Team ===
Team is active mostly before and during the annual MeeGo Summit FI events. Team's duties include comprehensive management of items which affect speaker's enjoyment. Such items are for example arranging hotel rooms, providing information and assisting in session preparations. Managing pre-registration and registration (including portal) is one of the key responsibilities of this team.

Team also manages the information desk at the summit venue. They are the people to go to when you have lost your precious laptop, Tux/MeeGon figure or hacking buddy. Information desk is also the correct place to inform the organizers about different activities which summit participants are encouraged to arrange at the venue. Such activities include hands-on sessions for small groups, unconference/barcamp sessions and workhops (or in this case hack-shops). When in doubt, turn to these people.

* More information, tasks and how to join can be found [[Local_MeeGo_Networks/MeeGo_Network_Finland/MeeGo_Summit_FI_Hosting_Team | here]]

=== Party MeeGons ===
This is probably 'teh' team for all party-MeeGons. If you have talent in being a VJ, DJ or you have ideas for stunning laser shows, this team is for you. Parties are important part of any summit or conference. We do not want to offer our summit participants fancy dinners at mansions or rigid and boring wine tasting. We prefer to have more casual and relaxed parties, which can include ad hoc competitions and shows. MeeGo Summit FI evening party is on Friday night. Join the party-MeeGons!

While bouncers are handy to control the crowd, we believe that they are not needed in this case :)

Responsible for:
* Evening party at MeeGo Summit FI
* DJ/VJ (1+1 volunteers)
* ...

'''Members:'''
* Juha "[[User:Riussi|Riussi]]" Ristolainen. I can also help in organizing the party but we need an experienced team lead for this team.
* Jukka Eklund ([http://meego.com/users/jukkaeklund jukkaeklund]). I can't VJ or anything but will help to get the party going (won't be a bouncer however)
* [http://meego.com/users/smoinen Matti Saastamoinen] (smoinen) - [http://www.coss.fi/en/contact contact] // I can be the interface to party sponsors and bring my knowledge from our past event parties

''' Ideas & Tasks'''
* Invent a leet name for the party!

=== Hack3r Team ===
To be labelled as Hacker is an honor among us. The word hacker means to us the same as 'Sir' does for the royalty. Members of this team are
talented in different technical areas and posses deep knowledge. If you're not overwhelmed in front of technical problems, this is your team.
Ability to think outside-the-box and to find a solution is important. Your solution to problems do not need to be most
elegant and polished, it just needs to work.

If you want to join the hack3r team, send an e-mail to Topi Santakivi (first_nameD0Tlastname _AT_ gmail.com)

This team will coordinate efforts related to:
* '''Meegathon''' competition which is part of MeeGo Summit FI 2011
* Helps competition teams in technical issues. (4-5 volunteers)
* Responsible for the USB-sticks ('Developer stick') which is given to all participants (contains latest developer tools) (1-2 volunteers)
* Coordinates tool-shop usage (1 volunteer)
* Manages our (meego-fi) Intel AppUp developer program services and members.

'''Members:'''
* Laszlo Papp (djszapi)
* (lead) [http://meego.com/users/sandst1 Topi Santakivi] (sandst1) first_nameD0Tlastname _AT_ gmail.com
* [http://meego.com/users/timoph Timo Härkönen] (timoph)
* [http://meego.com/users/samposa Sampo Saaristo] (sampos)
...

''' Ideas & Tasks: '''
* Sign to be attached in the entry-point of Meegathon teams: [http://dl.dropbox.com/u/7717672/Meegonetwork.fi/hackland-sign.png hackland-sign.png]
* Polish/Define the competition (Meegathon) [[Local_MeeGo_Networks/MeeGo_Network_Finland/MeeGo_Summit_FI#Meegathon |rules]].
* Define the content of 'Developer USB-stick'
* Create new LAN/WLAN solutions which might help.

== Program ==
The summit program includes keynotes, three tracks, workshops, evening party on Friday and Meegathon competition. On Saturday we have Finhack (http://www.finhack.org) annual conference on the second floor.

=== Confirmed Speakers ===
Topics will be set later, in February - March.
* [http://meego.com/users/stskeeps Carsten Munk] (keynote)
* [http://fi.linkedin.com/in/valhalla Valtteri Halla] (keynote)
* [http://conference2010.meego.com/people/lbt David Greaves]
* [http://conference2010.meego.com/people/vilvo Ville Ilvonen]
* [http://meego.com/users/kate Kate Alhola]
* [http://fi.linkedin.com/pub/jan-krebber/5/957/2b Jan Krebber]
* [http://www.linkedin.com/pub/justin-noel/5/a5b/95a Justin Noel]
* [http://meego.com/users/abustany Adrien Bustany] & [http://fi.linkedin.com/pub/ivan-frade/4/984/903 Ivan Frade]

=== Tracks ===
In every organization, there are people who just have the knack for getting the most out of certain software and tools. These tracks are where those people shine -- it is the place to show off the newest tools, share creative uses for old favorites, and of course pass on hacks, tips and tricks. Sessions may include demonstrations, pilot projects, examples, techniques, and lessons learned.

# '''Core & Future''' - Apps and possibilities with latest tools (Fri - Sat)
# '''Hacks & Tricks''' - HW inventions, unconventional experiments (Fri - Sat)
# '''Biz Buzz''' - MeeGo Ecosystem and Open Source (Fri)

=== Hackshops and BoFs ===
Also known as lame Workshops. Participating to Hackshops requires sufficient amount of hack attitude and enthusiasm. We have some facilities (small meeting rooms) for hackshops. If you get an idea about what to teach/show to others (preferably hands-on stuff), book yourself a hackshop space and let the organizers know about it by dropping at the information desk! Your hackshop will be announced in twitter and on the venue screens. If you already know a topic, put it below.

'''Ideas for Workshops and BoFs'''

Add your ideas for workshops below. Also add your name if willing to run the workshop.
* UX helpdesk (whole day)
* MeeGo SDK (getting started)
* ...

=== Meegathon ===
Meegathon is a hacker type of competition, much like a hack-a-thon. The following competition will take place between Fri 12:00am and Sat 12:00am. In other words, teams have 24 hours time to finish their project. You have the possibility to sleep in hackerspace (big hall), so take your sleeping bag with you.

Meegathon is both a software development and hardware innovation competition, with the emphasis on software. Teams participating in the competition can choose their own topic or use the one provided below. The purpose of the competition is to produce new open innovative software or improvements to existing open source projects. The judges will expect the projects to be targeted at MeeGo but if the project is useful for the larger open source community - even better.

NOTE: We need people who will do shifts in supervising the Meegathon. This doesn't have to be technical support, there just needs to be somebody present with a key who can let people in and make sure that things are going smoothly.

Put your name on the task list if you want to help:
[http://doodle.com/n8dbwzzis7iawwty Meegathon shifts in doodle]

See different page for full details & rules: [[Local_MeeGo_Networks/MeeGo_Network_Finland/meegathon | Meegathon Competetion]]

=== Party ===
* Friday night, detailed time will be announced later
* Location: coordinates will be announced later
* name of the party?



=== Quadricopter/MeeGo games ===
We might be able to arrange a possibility to hold small-scale playful games with couple of Quadricopters. More will be revealed later. Needs 1-3 volunteers.



== Sponsoring ==
Sponsoring opportunities and packages, contact Ilkka Lehtinen (ilkka dot lehtinen @ hermia dot fi)

'''Sponsors:'''

* Ixonos (Platinum)
* Tieto (Gold)
* Futurice (Silver)
* Sasken (Silver)
* ICS (Silver)
* Nomovok (Silver)

== How to contribute? ==
Interested in helping? Great! Contributing is easy and you can give as little or as much time as you want.

Here are just a few ways you can get started:
* Check the TODO list below to find something that needs to be done.
* Join discussion at our IRC channel: #meego-fi (irc.freenode.org) and ask what you can do. If you don't have a IRC client, you can access the channel from this free service: http://webchat.freenode.net/
* Join our mailing list (add here)

Here are some of the volunteer opportunities:
* IRC Chat Moderators
* Information Desk Helpers
* Session Tech Support
* Conference Setup - 14th Apr.
* Conference Cleanup - 16th Apr
* Speaker Assistants
* Hacking Session Helpers

Not sure where you want to volunteer yet until the conference schedule is finalized? Put your name here and we'll add more detailed volunteer tables in the months to come.

'''Volunteers:'''

* Juha "[[User:Riussi|Riussi]]" Ristolainen
* Jukka [http://twitter.com/jukkaeklund @jukkaeklund] Eklund
* Carol [http://twitter.com/cybette @cybette] Chen
* Ville [http://twitter.com/jykae_ @jykae] Jyrkkä -- tha 'all-around' aMeeGo for the Summit arrangements, kick me in the IRC!

== TODO ==
List of tasks etc that needs to be done by organizers or volunteers. Add your name after a task if you want to do it.
* Define and collect software package (collected about a week before Summit) given for every attendee in a USB stick. 300 pcs. Cuts back the need to download all software from the net. USB-sticks will be provided by New Factory. - Topi Santakivi (sandst1)
* Marketing material: t-shirts, stickers, flyers....
** Matti Saastamoinen (smoinen) and Ilkka Lehtinen (among other guys from the community and sponsors) will attend [http://fosdem.org/ FOSDEM] on Feb 5-6, 2011. Leaflets and summit t-shirts for marketing should be ready before that.

* Activate MeeGo bloggers to write about this community and MeeGo Summit FI 2011. This could be done be sending 'inside' information to key bloggers once in a while. That way they get the feeling of being 'special' and in the frontline.
* Photographs and/or video from the venue site. Sneak-peak about the facilities which will be transformed to for Summit needs. Place the images somewhere public so they can be used in tweets.

Local MeeGo Networks/MeeGo Network Finland/MeeGo Summit FI

2011-03-25T11:10:18Z

Jnwi: /* Marketing Team */

<div style="float:right;background-color:#fff;width:400px;height:520px;border: solid 1px #ddd;padding:15px;font-size:1.3em;"><b>Sponsors:</b><ul style="list-style:none;"><li>[[File:Ixonos-logo.gif]] (Platinum)</li><li>[[File:Tieto.jpg]] (Gold)</li><li>[[File:Intel-logo.png‎]] (Gold)</li><li>[[File:futurice_logo.png]] (Silver)</li><li>[[File:ICS-logo.gif‎]] (Silver)</li><li>[[File:Nomovok.png‎]] (Silver)</li><li>[[File:Symbio.png‎]] (Silver)</li></ul></div>

= Developer to developer =
Tampere initiated the first [[Local_MeeGo_Networks|Local Meego Network]] in Europe, [http://www.meetup.com/Tampere-MeeGo-Network/ Tampere Meego Network]. This is annual summit which is held in different locations around Finland. Tampere will host the first Regional Meego Summit in the world. Although the first Summit is at Tampere, this is a joined effort.

<div style="float:right;background-color:#fff;width:280px;height:160px;border: solid 1px #ddd;padding:15px;font-size:1.3em;">[[Image:MeeGoSummitNetworkLogo-RGB-72_Summit-01.jpg‎|link=http://summit.meegonetwork.fi]]</div>

'''[http://www.meetup.com/Tampere-MeeGo-Network/ Tampere] and [http://www.meetup.com/Helsinki-MeeGo-Network/ Helsinki] local networks have joined forces and other local networks are also welcome to participate! Furthermore, this conference will host Finnish hacker & OSS event ''Finhack'' (16th Apr) '''

The summit is free of charge, but the amount of seats is limited! Program includes:
* Keynotes
* Three tracks
* Meegathon competition
* Party
* BoFs & Workshops
* Quadricopter fun

== Details ==
* Location: Tampere, Finland. Finlayson area (Plevna, [http://www.uusitehdas.fi/en/ New Factory])
* Time: 15.-16. April 2011
* Duration: 2 days (Fri-Sat)
* Registration fee: Free!
* Seat amount: max 300
* Registration required: yes (address here)
* Web: http://summit.meegonetwork.fi
* '''[[Local_MeeGo_Networks/MeeGo_Network_Finland/roadmap | Roadmap/important dates]]'''

== Organizers ==
'''Main organizer:'''
{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"|Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Ilkka Lehtinen
| General, sponsors
| Head
| [http://www.coss.fi/en COSS]
|}

'''Co-Organizers:'''

{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"| Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Jarkko Moilanen
| General + Program (Community & hackers)
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Jukka Matikainen
| ?
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Matti Saastamoinen
| General, sponsors
| Organizer
| [http://www.coss.fi/en COSS]
|-
| Ville Kairamo
| Facilities
| Organizer
| [http://www.uusitehdas.fi/en NewFactory]
|}

== Teams ==
MNFI community needs different type of teams and task-forces to arrange activities. Members of the teams should be from the member networks but foreign members are also welcome. Some of the teams are active throughout the year, but some are active only before and during our annual Summits.

All teams (should) have a lead which coordinates the team efforts. To join a team is simple:
* add your name to the team member list and
* if possible contact the lead in IRC-channel (#meego-fi)

=== Program Task-force ===
The committee has been formed by inviting suitable MeeGo Network Finland -community members to it.

'''Members'''
* [http://meego.com/users/bergie Henri Bergius] (bergie)
* [http://meego.com/users/jukkaeklund Jukka Eklund] (jukkaeklund)
* [http://meego.com/users/timoph Timo Härkönen] (timoph)
* (lead) [[User:Kyber | Jarkko Moilanen ]] (kyb3R)



=== Marketing Team ===
Responsible mainly for:
*Marketing material such as posters and leaflets
*Media policy
*Press releases and other press issues
*Website content policy
*Social media accounts

If you want to join, contact jnwi. More information [[Local_MeeGo_Networks/MeeGo_Network_Finland/Marketing_Team|here]]

=== Tech Team ===
Effective and open communication has two sides: internal and external. This team is responsible for internal communication tools which include methods to share information among local networks and members. Working and transparent communication is vital to our community since our activities are coordinated with virtual tools such as email, IRC and portal.

External communication refers to the different tools we use to communicate with the public and global MeeGo community. For these purposes we use various social media services such as [http://twitter.com/meegofi twitter.com/meegofi], [http://facebook.com/meegofi facebook.com/meegofi] and [http://identi.ca/meegofi identi.ca/meegofi].

* More information, tasks and how to join can be found [[Local_MeeGo_Networks/MeeGo_Network_Finland/Communication_Team|here]]

=== Hosting Team ===
Team is active mostly before and during the annual MeeGo Summit FI events. Team's duties include comprehensive management of items which affect speaker's enjoyment. Such items are for example arranging hotel rooms, providing information and assisting in session preparations. Managing pre-registration and registration (including portal) is one of the key responsibilities of this team.

Team also manages the information desk at the summit venue. They are the people to go to when you have lost your precious laptop, Tux/MeeGon figure or hacking buddy. Information desk is also the correct place to inform the organizers about different activities which summit participants are encouraged to arrange at the venue. Such activities include hands-on sessions for small groups, unconference/barcamp sessions and workhops (or in this case hack-shops). When in doubt, turn to these people.

* More information, tasks and how to join can be found [[Local_MeeGo_Networks/MeeGo_Network_Finland/MeeGo_Summit_FI_Hosting_Team | here]]

=== Party MeeGons ===
This is probably 'teh' team for all party-MeeGons. If you have talent in being a VJ, DJ or you have ideas for stunning laser shows, this team is for you. Parties are important part of any summit or conference. We do not want to offer our summit participants fancy dinners at mansions or rigid and boring wine tasting. We prefer to have more casual and relaxed parties, which can include ad hoc competitions and shows. MeeGo Summit FI evening party is on Friday night. Join the party-MeeGons!

While bouncers are handy to control the crowd, we believe that they are not needed in this case :)

Responsible for:
* Evening party at MeeGo Summit FI
* DJ/VJ (1+1 volunteers)
* ...

'''Members:'''
* Juha "[[User:Riussi|Riussi]]" Ristolainen. I can also help in organizing the party but we need an experienced team lead for this team.
* Jukka Eklund ([http://meego.com/users/jukkaeklund jukkaeklund]). I can't VJ or anything but will help to get the party going (won't be a bouncer however)
* [http://meego.com/users/smoinen Matti Saastamoinen] (smoinen) - [http://www.coss.fi/en/contact contact] // I can be the interface to party sponsors and bring my knowledge from our past event parties

''' Ideas & Tasks'''
* Invent a leet name for the party!

=== Hack3r Team ===
To be labelled as Hacker is an honor among us. The word hacker means to us the same as 'Sir' does for the royalty. Members of this team are
talented in different technical areas and posses deep knowledge. If you're not overwhelmed in front of technical problems, this is your team.
Ability to think outside-the-box and to find a solution is important. Your solution to problems do not need to be most
elegant and polished, it just needs to work.

If you want to join the hack3r team, send an e-mail to Topi Santakivi (first_nameD0Tlastname _AT_ gmail.com)

This team will coordinate efforts related to:
* '''Meegathon''' competition which is part of MeeGo Summit FI 2011
* Helps competition teams in technical issues. (4-5 volunteers)
* Responsible for the USB-sticks ('Developer stick') which is given to all participants (contains latest developer tools) (1-2 volunteers)
* Coordinates tool-shop usage (1 volunteer)
* Manages our (meego-fi) Intel AppUp developer program services and members.

'''Members:'''
* Laszlo Papp (djszapi)
* (lead) [http://meego.com/users/sandst1 Topi Santakivi] (sandst1) first_nameD0Tlastname _AT_ gmail.com
* [http://meego.com/users/timoph Timo Härkönen] (timoph)
* [http://meego.com/users/samposa Sampo Saaristo] (sampos)
...

''' Ideas & Tasks: '''
* Sign to be attached in the entry-point of Meegathon teams: [http://dl.dropbox.com/u/7717672/Meegonetwork.fi/hackland-sign.png hackland-sign.png]
* Polish/Define the competition (Meegathon) [[Local_MeeGo_Networks/MeeGo_Network_Finland/MeeGo_Summit_FI#Meegathon |rules]].
* Define the content of 'Developer USB-stick'
* Create new LAN/WLAN solutions which might help.

== Program ==
The summit program includes keynotes, three tracks, workshops, evening party on Friday and Meegathon competition. On Saturday we have Finhack (http://www.finhack.org) annual conference on the second floor.

=== Confirmed Speakers ===
Topics will be set later, in February - March.
* [http://meego.com/users/stskeeps Carsten Munk] (keynote)
* [http://fi.linkedin.com/in/valhalla Valtteri Halla] (keynote)
* [http://conference2010.meego.com/people/lbt David Greaves]
* [http://conference2010.meego.com/people/vilvo Ville Ilvonen]
* [http://meego.com/users/kate Kate Alhola]
* [http://fi.linkedin.com/pub/jan-krebber/5/957/2b Jan Krebber]
* [http://www.linkedin.com/pub/justin-noel/5/a5b/95a Justin Noel]
* [http://meego.com/users/abustany Adrien Bustany] & [http://fi.linkedin.com/pub/ivan-frade/4/984/903 Ivan Frade]

=== Tracks ===
In every organization, there are people who just have the knack for getting the most out of certain software and tools. These tracks are where those people shine -- it is the place to show off the newest tools, share creative uses for old favorites, and of course pass on hacks, tips and tricks. Sessions may include demonstrations, pilot projects, examples, techniques, and lessons learned.

# '''Core & Future''' - Apps and possibilities with latest tools (Fri - Sat)
# '''Hacks & Tricks''' - HW inventions, unconventional experiments (Fri - Sat)
# '''Biz Buzz''' - MeeGo Ecosystem and Open Source (Fri)

=== Hackshops and BoFs ===
Also known as lame Workshops. Participating to Hackshops requires sufficient amount of hack attitude and enthusiasm. We have some facilities (small meeting rooms) for hackshops. If you get an idea about what to teach/show to others (preferably hands-on stuff), book yourself a hackshop space and let the organizers know about it by dropping at the information desk! Your hackshop will be announced in twitter and on the venue screens. If you already know a topic, put it below.

'''Ideas for Workshops and BoFs'''

Add your ideas for workshops below. Also add your name if willing to run the workshop.
* UX helpdesk (whole day)
* MeeGo SDK (getting started)
* ...

=== Meegathon ===
Meegathon is a hacker type of competition, much like a hack-a-thon. The following competition will take place between Fri 12:00am and Sat 12:00am. In other words, teams have 24 hours time to finish their project. You have the possibility to sleep in hackerspace (big hall), so take your sleeping bag with you.

Meegathon is both a software development and hardware innovation competition, with the emphasis on software. Teams participating in the competition can choose their own topic or use the one provided below. The purpose of the competition is to produce new open innovative software or improvements to existing open source projects. The judges will expect the projects to be targeted at MeeGo but if the project is useful for the larger open source community - even better.

NOTE: We need people who will do shifts in supervising the Meegathon. This doesn't have to be technical support, there just needs to be somebody present with a key who can let people in and make sure that things are going smoothly.

Put your name on the task list if you want to help:
[http://doodle.com/n8dbwzzis7iawwty Meegathon shifts in doodle]

See different page for full details & rules: [[Local_MeeGo_Networks/MeeGo_Network_Finland/meegathon | Meegathon Competetion]]

=== Party ===
* Friday night, detailed time will be announced later
* Location: coordinates will be announced later
* name of the party?



=== Quadricopter/MeeGo games ===
We might be able to arrange a possibility to hold small-scale playful games with couple of Quadricopters. More will be revealed later. Needs 1-3 volunteers.



== Sponsoring ==
Sponsoring opportunities and packages, contact Ilkka Lehtinen (ilkka dot lehtinen @ hermia dot fi)

'''Sponsors:'''

* Ixonos (Platinum)
* Tieto (Gold)
* Futurice (Silver)
* Sasken (Silver)
* ICS (Silver)
* Nomovok (Silver)

== How to contribute? ==
Interested in helping? Great! Contributing is easy and you can give as little or as much time as you want.

Here are just a few ways you can get started:
* Check the TODO list below to find something that needs to be done.
* Join discussion at our IRC channel: #meego-fi (irc.freenode.org) and ask what you can do. If you don't have a IRC client, you can access the channel from this free service: http://webchat.freenode.net/
* Join our mailing list (add here)

Here are some of the volunteer opportunities:
* IRC Chat Moderators
* Information Desk Helpers
* Session Tech Support
* Conference Setup - 14th Apr.
* Conference Cleanup - 16th Apr
* Speaker Assistants
* Hacking Session Helpers

Not sure where you want to volunteer yet until the conference schedule is finalized? Put your name here and we'll add more detailed volunteer tables in the months to come.

'''Volunteers:'''

* Juha "[[User:Riussi|Riussi]]" Ristolainen
* Jukka [http://twitter.com/jukkaeklund @jukkaeklund] Eklund
* Carol [http://twitter.com/cybette @cybette] Chen
* Ville [http://twitter.com/jykae_ @jykae] Jyrkkä -- tha 'all-around' aMeeGo for the Summit arrangements, kick me in the IRC!

== TODO ==
List of tasks etc that needs to be done by organizers or volunteers. Add your name after a task if you want to do it.
* Define and collect software package (collected about a week before Summit) given for every attendee in a USB stick. 300 pcs. Cuts back the need to download all software from the net. USB-sticks will be provided by New Factory. - Topi Santakivi (sandst1)
* Marketing material: t-shirts, stickers, flyers....
** Matti Saastamoinen (smoinen) and Ilkka Lehtinen (among other guys from the community and sponsors) will attend [http://fosdem.org/ FOSDEM] on Feb 5-6, 2011. Leaflets and summit t-shirts for marketing should be ready before that.

* Activate MeeGo bloggers to write about this community and MeeGo Summit FI 2011. This could be done be sending 'inside' information to key bloggers once in a while. That way they get the feeling of being 'special' and in the frontline.
* Photographs and/or video from the venue site. Sneak-peak about the facilities which will be transformed to for Summit needs. Place the images somewhere public so they can be used in tweets.

Local MeeGo Networks/MeeGo Network Finland/Meeting Agenda 2011 02 20

2011-02-17T14:55:13Z

Jnwi: /* Restructuring of Marketing, communication and tech teams (jnwi presenting) */

= MNFI irc-meeting =

<pre>
Add items to be discussed (as the last item on agenda), do the ground work
eg write something about it to wiki and be prepared to present the issue too.
Issues given 24 hours before meeting are postponed to next meeting.

Team leads: add whatever needs to be told about your activity. The section
'Team reports' will be a permanent section in future agendas.

NOTE: Let's try to keep meeting no longer than 1 hour. Read the given information
before meeting, so that decision making is fluent and more decisions can be made.
</pre>
* Date: 2011 Feb 20th Sun
* Time: 18:00 UTC+2
* Place: #meego-meeting (web-browser [http://webchat.freenode.net/?channels=meego-meeting Ajax-IRC])
* Chair: ? volunteer here
* Assist: ? volunteer here

== Agenda ==

=== Team reports ===

'''Program Task-force'''
* Due to recent news, we most likely need to restructure the program and get new speakers. Hopefully things gain some clarity before meeting or in the near future.

'''Marketing & PR Team '''
* nothing to report

'''Communication & Tech Team '''
* nothing to report

'''Hosting Team'''
* nothing to report

'''Party MeeGons'''
* nothing to report

'''Hack3r Team'''
* MNFI is now also part of [http://appdeveloper.intel.com/en-us/ Intel AppUp developer program]. Joining this is not mandatory to any of our members. Our organisation name in AppUp is 'meego-fi' and it is open to all (includes non-Finnish people).
** '''Proposition:''' Hack3r Team will manage our (meego-fi) Intel AppUp developer program services and members.

=== Restructuring of Marketing, communication and tech teams (jnwi presenting) ===
A more natural division of tasks is proposed. The preliminary plan is:

'''Marketing team''': Marketing material such as posters and leaflets, media policy, website content policy, social media, IRC channel(s) (ops), mailing lists (freelists.org, meegonetwork.fi).

'''Tech team''': MNFI portal development, summit venue IT infrastructure/connections, live streaming of presentations during the summit, video interviews (speakers etc.), app for summit program, summit registration tech.

=== Other issues ===
* ...<add item (your name)>

Local MeeGo Networks/MeeGo Network Finland/Meeting Agenda 2011 02 20

2011-02-17T14:52:25Z

Jnwi: /* Restructuring of Marketing, communication and tech teams (jnwi presenting) */

= MNFI irc-meeting =

<pre>
Add items to be discussed (as the last item on agenda), do the ground work
eg write something about it to wiki and be prepared to present the issue too.
Issues given 24 hours before meeting are postponed to next meeting.

Team leads: add whatever needs to be told about your activity. The section
'Team reports' will be a permanent section in future agendas.

NOTE: Let's try to keep meeting no longer than 1 hour. Read the given information
before meeting, so that decision making is fluent and more decisions can be made.
</pre>
* Date: 2011 Feb 20th Sun
* Time: 18:00 UTC+2
* Place: #meego-meeting (web-browser [http://webchat.freenode.net/?channels=meego-meeting Ajax-IRC])
* Chair: ? volunteer here
* Assist: ? volunteer here

== Agenda ==

=== Team reports ===

'''Program Task-force'''
* Due to recent news, we most likely need to restructure the program and get new speakers. Hopefully things gain some clarity before meeting or in the near future.

'''Marketing & PR Team '''
* nothing to report

'''Communication & Tech Team '''
* nothing to report

'''Hosting Team'''
* nothing to report

'''Party MeeGons'''
* nothing to report

'''Hack3r Team'''
* MNFI is now also part of [http://appdeveloper.intel.com/en-us/ Intel AppUp developer program]. Joining this is not mandatory to any of our members. Our organisation name in AppUp is 'meego-fi' and it is open to all (includes non-Finnish people).
** '''Proposition:''' Hack3r Team will manage our (meego-fi) Intel AppUp developer program services and members.

=== Restructuring of Marketing, communication and tech teams (jnwi presenting) ===
A more natural division of tasks is proposed. The preliminary plan is:
'''Marketing team'''
- Marketing material such as posters and leaflets
- Media policy
- Website content policy
- Social media accounts
- IRC channel(s) (ops)
- Mailing lists (freelists.org, meegonetwork.fi).
'''Tech team.'''
- MNFI portal development
- Summit venue IT infrastructure/connections
- Live streaming of presentations during the summit
- video interviews (speakers etc.)
- App for summit program
- Summit registration tech

=== Other issues ===
* ...<add item (your name)>

Local MeeGo Networks/MeeGo Network Finland/MeeGo Summit FI

2011-01-03T19:13:10Z

Jnwi: /* Marketing & PR Team */

<div style="float:right;background-color:#fff;width:300px;height:250px;border: solid 1px #ddd;padding:15px;font-size:1.3em;"><b>Sponsors:</b><ul style="list-style:none;"><li>[[File:Ixonos-logo.gif]] (Main Sponsor)</li><li>[[File:Tieto.jpg]]</li></ul></div>

= Developer to developer =
Tampere initiated the first [[Local_MeeGo_Networks|Local Meego Network]] in Europe, [http://www.meetup.com/Tampere-MeeGo-Network/ Tampere Meego Network]. This is annual summit which is held in different locations around Finland. Tampere will host the first Regional Meego Summit in the world. Although the first Summit is at Tampere, this is a joined effort.

<div style="float:right;background-color:#fff;width:160px;height:160px;border: solid 1px #ddd;padding:15px;font-size:1.3em;">[[Image:Fmni-matrixcode-thumb.png‎|link=http://summit.meegonetwork.fi]]</div>

'''[http://www.meetup.com/Tampere-MeeGo-Network/ Tampere] and [http://www.meetup.com/Helsinki-MeeGo-Network/ Helsinki] local networks have joined forces and other local networks are also welcome to participate! Furthermore, this conference will host Finnish hacker & OSS event ''Finhack'' (16th Apr) '''

The summit is open, but the amount of seats is limited!

Meego Summit FI includes also a 'hackathon' type of competition, which includes two categories: 'Hard Core' (Both HW and SW) and 'Quick & Dirty' (Just SW). Competition is called: "Meegathon" and more details can be found below.

== Details ==
* Location: Tampere, Finland. Finlayson area (Plevna, [http://www.uusitehdas.fi/en/ New Factory])
* Time: 15.-16. April 2011
* Duration: 2 days (Fri-Sat)
* Registration fee: Free!
* Seat amount: max 300
* Registration required: yes (address here)
* Web: http://summit.meegonetwork.fi

== Organizers ==
'''Main organizer:'''
{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"|Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Ilkka Lehtinen
| General, sponsors
| Head
| [http://www.coss.fi/en COSS]
|}

'''Co-Organizers:'''

{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"| Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Jarkko Moilanen
| General + Program (Community & hackers)
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Jukka Matikainen
| ?
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Matti Saastamoinen
| General, sponsors
| Organizer
| [http://www.coss.fi/en COSS]
|-
| Ville Kairamo
| Facilities
| Organizer
| [http://www.uusitehdas.fi/en NewFactory]
|}

== Teams ==
MNFI community needs different type of teams and task-forces to arrange activities. Members of the teams should be from the member networks but foreign members are also welcome. Some of the teams are active throughout the year, but some are active only before and during our annual Summits.

All teams (should) have a lead which coordinates the team efforts. To join a team is simple:
* add your name to the team member list and
* if possible contact the lead in IRC-channel (#meego-fi)

=== Program Task-force ===
The committee has been formed by inviting suitable MeeGo Network Finland -community members to it. Current composition is (in alphabetical order):
* [http://meego.com/users/bergie Henri Bergius] (bergie)
* [http://meego.com/users/jukkaeklund Jukka Eklund] (jukkaeklund)
* [http://meego.com/users/timoph Timo Härkönen] (timoph)
* (lead) [http://forum.meego.com/member.php?u=12703 Jarkko Moilanen] (kyb3R)

More about the committee work can found [[Meego Summit FI Program|here]]

=== Marketing & PR Team ===
To be formed ASAP.
* (lead) [http://meego.com/users/jnwi Jens Wiik] (jnwi) - firstnameDOTlastname ät kolumbus.fi
More information can be found [[Meego Summit FI Marketing|here]]

''' Ideas & Tasks '''
* leaflets
* banners for webpages
* (T-) shirts for participants - kyber
* (T-) shirts for Teams (design logos for teams, which will also be used in portal). -kyber
* Texrat will do the images/logos for teams -kyber
** color will also indicate whether shirt owner belongs to organizers or not - kyber
* Design stickers (logo will come soon) - kyber
* Image which indicates the spirit of the Summit - [http://dl.dropbox.com/u/7717672/Meegonetwork.fi/dev2dev.png 'developer to developer'] -kyber
* team could write blog entries about events such as Summits, Local Network Meetups, etc. -kyber

=== Communication & Tech Team ===
Effective and open communication has two sides: internal and external. This team is responsible for internal communication tools which include methods to share information among local networks and members. Working and transparent communication is vital to our community since our activities are coordinated with virtual tools such as email, IRC and portal.

External communication refers to different tools we use to communicate to the public and global MeeGo community. For these purposes we use various social media services such as [http://twitter.com/meegofi twitter.com/meegofi], [http://facebook.com/meegofi facebook.com/meegofi] and [http://identi.ca/meegofi identi.ca/meegofi]

Responsible for:
* Social media accounts
* IRC channel(s) (ops)
* portal development
* Summit venue infrastructure & connections
* Mailing lists
* Summit registration (technical)

'''Members:'''
* [http://meego.com/users/cybette Carol Chen] ([http://twitter.com/cybette @cybette]) - team lead
* Heikki Ilvespakka - venue IT lead (no nick?)
* Ilkka Lehtinen - venue IT (no nick?)
* [http://forum.meego.com/member.php?u=12703 Jarkko Moilanen] (kyb3R) - IRC op & chan owner
* Nina Kuisma (ninnnu) (wants to participate registration system development)
* your name here


'''Guidelines and policy'''
* Social media: [[Regional_MeeGo_Networks/MeeGo_Network_Finland/Social_Media_Plan | Social Media Plan]]

=== Hosting Team ===
Team is active mostly before and during the annual MeeGo Summit FI events. Team's duties include comprehensive management of items which affect speaker's enjoyment. Such items are for example arranging hotel rooms, providing information and assisting in session preparations. Managing pre-registration and registration (including portal) is one of the key responsibilities of this team.

Team also manages the information desk at the summit venue. They are the people to go to when you have lost your precious laptop, Tux/MeeGon figure or hacking buddy. Information desk is also the correct place to inform the organizers about different activities which summit participants are encouraged to arrange at the venue. Such activities include hands-on sessions for small groups, unconference/barcamp sessions and workhops (or in this case hack-shops). When in doubt, turn to these people.

Responsible for:
* helping the speakers (hosts for the tracks: 3+1)
* manages info desk (4 volunteers),
* (assists in catering) Catering will be delivered as package (lunches, coffees, etc.) from [http://www.juvenes.fi/In_English/Juvenes_Catering Juvenes].
* reception/registration (also portal registration development/management).
* handles videorecording of the sessions and live video broadcast (1 volunteer).
* handles summit notifications at the venue.
* hotel arrangements (1 volunteer)
* babysitters for press, divas (yes, there’s always these too) (2 volunteers)

In total: 11+1 volunteers

'''Members:'''
* Juha Ristolainen (Riussi)
* add your name here

=== Party MeeGons ===
This is probably 'teh' team for all party-MeeGons. If you have talent in being a VJ, DJ or you have ideas for stunning laser shows, this team is for you. Parties are important part of any summit or conference. We do not want to offer our summit participants fancy dinners at mansions or rigid and boring wine tasting. We prefer to have more casual and relaxed parties, which can include ad hoc competitions and shows. MeeGo Summit FI evening party is on Friday night. Join the party-MeeGons!

While bouncers are handy to control the crowd, we believe that they are not needed in this case :)

Responsible for:
* Evening party at MeeGo Summit FI
* DJ/VJ (1+1 volunteers)
* ...

'''Members:'''
* Juha Ristolainen (Riussi)
* Jukka Eklund (jukkaeklund). I can't VJ or anything but will help to get the party going (won't be a bouncer however)

''' Ideas & Tasks'''
* Invent a leet name for the party!

=== Hack3r Team ===
To be labelled as Hacker is an honor among us. The word hacker means to us the same as 'Sir' does for the royalty. Members of this team are talented in different technical areas and posses deep knowledge. If you're not overwhelmed in front of technical problems, this is your team. Ability to think outside-the-box and to find a solution is important. Your solution to problems do not need to be most elegant and polished, it just needs to work.

This team will coordinate efforts related to:
* '''Meegathon''' competition which is part of MeeGo Summit FI 2011
* Helps competition teams in technical issues. (4-5 volunteers)
* Responsible for the USB-sticks ('Developer stick') which is given to all participants (contains latest developer tools) (1-2 volunteers)
* Coordinates tool-shop usage (1 volunteer)

'''Members:'''
* Laszlo Papp (djszapi)
* Topi Santakivi (sandst1)
* ...

''' Ideas & Tasks: '''
* Sign to be attached in the entry-point of Meegathon teams: [http://dl.dropbox.com/u/7717672/Meegonetwork.fi/hackland-sign.png hackland-sign.png] -kyber
* Polish/Define the competition (Meegathon) [[Local_MeeGo_Networks/MeeGo_Network_Finland/MeeGo_Summit_FI#Meegathon |rules]]. -kyber
* Define the content of 'Developer USB-stick' -kyber
* Create new LAN/WLAN solutions which might help.

== Program ==
The summit program includes keynotes, three tracks, workshops, evening party on Friday and Meegathon competition. On Saturday we have Finhack (http://www.finhack.org) annual conference on the second floor.

=== Confirmed Speakers ===
Topics will be set later, in February - March.
* Carsten Munk (keynote) - http://meego.com/users/stskeeps
* Valtteri Halla (keynote) - http://fi.linkedin.com/in/valhalla
* Thiago Macieira (keynote) - http://conference2010.meego.com/people/thiago
* David Greaves - http://conference2010.meego.com/people/lbt
* Dave Neary - http://conference2010.meego.com/people/dneary
* Ville Ilvonen - http://conference2010.meego.com/people/vilvo

=== Tracks ===
In every organization, there are people who just have the knack for getting the most out of certain software and tools. These tracks are where those people shine -- it is the place to show off the newest tools, share creative uses for old favorites, and of course pass on hacks, tips and tricks. Sessions may include demonstrations, pilot projects, examples, techniques, and lessons learned.

# '''Core & Future''' - Apps and possibilities with latest tools (Fri - Sat)
# '''Hacks & Tricks''' - HW inventions, unconventional experiments (Fri - Sat)
# '''Biz Buzz''' - MeeGo Ecosystem and Open Source (Fri)

=== Hackshops ===
Also known as lame Workshops. Participating to Hackshops requires sufficient amount of hack attitude and enthusiasm. We have some facilities (small meeting rooms) for hackshops. If you get an idea about what to teach/show to others (preferably hands-on stuff), book yourself a hackshop space and let the organizers know about it by dropping at the information desk! Your hackshop will be announced in twitter and on the venue screens. If you already know a topic, put it below.

'''Ideas for Workshop.'''

Add your ideas for workshops below. Also add your name if willing to run the workshop.
* ...

=== Meegathon ===
Meegathon is a hacker type of competition, much like a hack-a-thon. The following competition takes place between Fri 12:00am and Sat 12:00am. All teams demonstrate their results Saturday to all event participants. Best inventions and innovations are rewarded. Competition includes two categories:
* Hardcore (HW & SW)
* Quick & Dirty (SW only)

''' Hardcore '''
* the end-product must include and use MeeGo OS (1.1 or above) as one of the main components.
* the end-product HW must be self-made (may include manufactured circuits, wires, connectors, etc)
* keep the size in reasonable limits, eg no monster cars or full scale helicopters.
* all pyrotechnics and acid based solutions are forbidden!
* the agenda of your project is not limited in anyway (except the above).

''' Quick & Dirty '''
* must include only software.
* the end-product must include and use MeeGo OS (1.1 or above) as one of the main components.
* hardware available: web cameras, wires,...
* the agenda for the software is given in the beginning of Meegathon and is the same for all.
* software produced must run on one of the following hardware:
** Nokia N900
** Lenovo Ideapad S10-3t Tablet or similar
** The list of devices will be updated later.

All teams have a dedicated space where to build stuff in the second floor. The space is a big hall, which is divided into smaller areas.

''' Team rules '''
* max 5 persons
* no limitations to member origin (eg from corporate, hackerspaces, LUG's, etc) If the team is sponsored by corporation or includes only corporation employees, it MUST be stated in project description.
*

=== Party ===
* Friday night, detailed time will be announced later
* Location: coordinates will be announced later
* name of the party?

=== Quadricopter/MeeGo games ===
We might be able to arrange a possibility to hold small-scale playful games with couple of Quadricopters. More will be revealed later. Needs 1-3 volunteers.



== Sponsoring ==
Sponsoring opportunities and packages, contact Ilkka Lehtinen (ilkka dot lehtinen @ hermia dot fi)

'''Sponsors:'''

* Ixonos (Main Sponsor)
* Tieto

== How to contribute? ==
Interested in helping? Great! Contributing is easy and you can give as little or as much time as you want.

Here are just a few ways you can get started:
* Check the TODO list below to find something that needs to be done.
* Join discussion at our IRC channel: #meego-fi (irc.freenode.org) and ask what you can do. If you don't have a IRC client, you can access the channel from this free service: http://webchat.freenode.net/
* Join our mailing list (add here)

Here are some of the volunteer opportunities:
* IRC Chat Moderators
* Information Desk Helpers
* Session Tech Support
* Conference Setup - 14th Apr.
* Conference Cleanup - 16th Apr
* Speaker Assistants
* Hacking Session Helpers

Not sure where you want to volunteer yet until the conference schedule is finalized? Put your name here and we'll add more detailed volunteer tables in the months to come.

'''Volunteers:'''

* Juha [http://twitter.com/#!/riussi @Riussi] Ristolainen
* Jukka [http://twitter.com/jukkaeklund @jukkaeklund] Eklund
* Carol [http://twitter.com/cybette @cybette] Chen
* Ville [http://identi.ca/jykae @jykae] Jyrkkä

== TODO ==
List of tasks etc that needs to be done by organizers or volunteers. Add your name after a task if you want to do it.
* Define and collect software package (collected about a week before Summit) given for every attendee in a USB stick. 300 pcs. Cuts back the need to download all software from the net. USB-sticks will be provided by New Factory. - Topi Santakivi (sandst1)
* Marketing material: t-shirts, stickers, flyers....
*

Local MeeGo Networks/MeeGo Network Finland/MeeGo Summit FI

2011-01-03T19:12:45Z

Jnwi: /* Marketing & PR Team */

<div style="float:right;background-color:#fff;width:300px;height:250px;border: solid 1px #ddd;padding:15px;font-size:1.3em;"><b>Sponsors:</b><ul style="list-style:none;"><li>[[File:Ixonos-logo.gif]] (Main Sponsor)</li><li>[[File:Tieto.jpg]]</li></ul></div>

= Developer to developer =
Tampere initiated the first [[Local_MeeGo_Networks|Local Meego Network]] in Europe, [http://www.meetup.com/Tampere-MeeGo-Network/ Tampere Meego Network]. This is annual summit which is held in different locations around Finland. Tampere will host the first Regional Meego Summit in the world. Although the first Summit is at Tampere, this is a joined effort.

<div style="float:right;background-color:#fff;width:160px;height:160px;border: solid 1px #ddd;padding:15px;font-size:1.3em;">[[Image:Fmni-matrixcode-thumb.png‎|link=http://summit.meegonetwork.fi]]</div>

'''[http://www.meetup.com/Tampere-MeeGo-Network/ Tampere] and [http://www.meetup.com/Helsinki-MeeGo-Network/ Helsinki] local networks have joined forces and other local networks are also welcome to participate! Furthermore, this conference will host Finnish hacker & OSS event ''Finhack'' (16th Apr) '''

The summit is open, but the amount of seats is limited!

Meego Summit FI includes also a 'hackathon' type of competition, which includes two categories: 'Hard Core' (Both HW and SW) and 'Quick & Dirty' (Just SW). Competition is called: "Meegathon" and more details can be found below.

== Details ==
* Location: Tampere, Finland. Finlayson area (Plevna, [http://www.uusitehdas.fi/en/ New Factory])
* Time: 15.-16. April 2011
* Duration: 2 days (Fri-Sat)
* Registration fee: Free!
* Seat amount: max 300
* Registration required: yes (address here)
* Web: http://summit.meegonetwork.fi

== Organizers ==
'''Main organizer:'''
{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"|Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Ilkka Lehtinen
| General, sponsors
| Head
| [http://www.coss.fi/en COSS]
|}

'''Co-Organizers:'''

{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"| Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Jarkko Moilanen
| General + Program (Community & hackers)
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Jukka Matikainen
| ?
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Matti Saastamoinen
| General, sponsors
| Organizer
| [http://www.coss.fi/en COSS]
|-
| Ville Kairamo
| Facilities
| Organizer
| [http://www.uusitehdas.fi/en NewFactory]
|}

== Teams ==
MNFI community needs different type of teams and task-forces to arrange activities. Members of the teams should be from the member networks but foreign members are also welcome. Some of the teams are active throughout the year, but some are active only before and during our annual Summits.

All teams (should) have a lead which coordinates the team efforts. To join a team is simple:
* add your name to the team member list and
* if possible contact the lead in IRC-channel (#meego-fi)

=== Program Task-force ===
The committee has been formed by inviting suitable MeeGo Network Finland -community members to it. Current composition is (in alphabetical order):
* [http://meego.com/users/bergie Henri Bergius] (bergie)
* [http://meego.com/users/jukkaeklund Jukka Eklund] (jukkaeklund)
* [http://meego.com/users/timoph Timo Härkönen] (timoph)
* (lead) [http://forum.meego.com/member.php?u=12703 Jarkko Moilanen] (kyb3R)

More about the committee work can found [[Meego Summit FI Program|here]]

=== Marketing & PR Team ===
To be formed ASAP.
* (lead) [http://meego.com/users/jnwi Jens Wiik] (jnwi) - firstnameDOTlastname at kolumbus.fi
More information can be found [[Meego Summit FI Marketing|here]]

''' Ideas & Tasks '''
* leaflets
* banners for webpages
* (T-) shirts for participants - kyber
* (T-) shirts for Teams (design logos for teams, which will also be used in portal). -kyber
* Texrat will do the images/logos for teams -kyber
** color will also indicate whether shirt owner belongs to organizers or not - kyber
* Design stickers (logo will come soon) - kyber
* Image which indicates the spirit of the Summit - [http://dl.dropbox.com/u/7717672/Meegonetwork.fi/dev2dev.png 'developer to developer'] -kyber
* team could write blog entries about events such as Summits, Local Network Meetups, etc. -kyber

=== Communication & Tech Team ===
Effective and open communication has two sides: internal and external. This team is responsible for internal communication tools which include methods to share information among local networks and members. Working and transparent communication is vital to our community since our activities are coordinated with virtual tools such as email, IRC and portal.

External communication refers to different tools we use to communicate to the public and global MeeGo community. For these purposes we use various social media services such as [http://twitter.com/meegofi twitter.com/meegofi], [http://facebook.com/meegofi facebook.com/meegofi] and [http://identi.ca/meegofi identi.ca/meegofi]

Responsible for:
* Social media accounts
* IRC channel(s) (ops)
* portal development
* Summit venue infrastructure & connections
* Mailing lists
* Summit registration (technical)

'''Members:'''
* [http://meego.com/users/cybette Carol Chen] ([http://twitter.com/cybette @cybette]) - team lead
* Heikki Ilvespakka - venue IT lead (no nick?)
* Ilkka Lehtinen - venue IT (no nick?)
* [http://forum.meego.com/member.php?u=12703 Jarkko Moilanen] (kyb3R) - IRC op & chan owner
* Nina Kuisma (ninnnu) (wants to participate registration system development)
* your name here


'''Guidelines and policy'''
* Social media: [[Regional_MeeGo_Networks/MeeGo_Network_Finland/Social_Media_Plan | Social Media Plan]]

=== Hosting Team ===
Team is active mostly before and during the annual MeeGo Summit FI events. Team's duties include comprehensive management of items which affect speaker's enjoyment. Such items are for example arranging hotel rooms, providing information and assisting in session preparations. Managing pre-registration and registration (including portal) is one of the key responsibilities of this team.

Team also manages the information desk at the summit venue. They are the people to go to when you have lost your precious laptop, Tux/MeeGon figure or hacking buddy. Information desk is also the correct place to inform the organizers about different activities which summit participants are encouraged to arrange at the venue. Such activities include hands-on sessions for small groups, unconference/barcamp sessions and workhops (or in this case hack-shops). When in doubt, turn to these people.

Responsible for:
* helping the speakers (hosts for the tracks: 3+1)
* manages info desk (4 volunteers),
* (assists in catering) Catering will be delivered as package (lunches, coffees, etc.) from [http://www.juvenes.fi/In_English/Juvenes_Catering Juvenes].
* reception/registration (also portal registration development/management).
* handles videorecording of the sessions and live video broadcast (1 volunteer).
* handles summit notifications at the venue.
* hotel arrangements (1 volunteer)
* babysitters for press, divas (yes, there’s always these too) (2 volunteers)

In total: 11+1 volunteers

'''Members:'''
* Juha Ristolainen (Riussi)
* add your name here

=== Party MeeGons ===
This is probably 'teh' team for all party-MeeGons. If you have talent in being a VJ, DJ or you have ideas for stunning laser shows, this team is for you. Parties are important part of any summit or conference. We do not want to offer our summit participants fancy dinners at mansions or rigid and boring wine tasting. We prefer to have more casual and relaxed parties, which can include ad hoc competitions and shows. MeeGo Summit FI evening party is on Friday night. Join the party-MeeGons!

While bouncers are handy to control the crowd, we believe that they are not needed in this case :)

Responsible for:
* Evening party at MeeGo Summit FI
* DJ/VJ (1+1 volunteers)
* ...

'''Members:'''
* Juha Ristolainen (Riussi)
* Jukka Eklund (jukkaeklund). I can't VJ or anything but will help to get the party going (won't be a bouncer however)

''' Ideas & Tasks'''
* Invent a leet name for the party!

=== Hack3r Team ===
To be labelled as Hacker is an honor among us. The word hacker means to us the same as 'Sir' does for the royalty. Members of this team are talented in different technical areas and posses deep knowledge. If you're not overwhelmed in front of technical problems, this is your team. Ability to think outside-the-box and to find a solution is important. Your solution to problems do not need to be most elegant and polished, it just needs to work.

This team will coordinate efforts related to:
* '''Meegathon''' competition which is part of MeeGo Summit FI 2011
* Helps competition teams in technical issues. (4-5 volunteers)
* Responsible for the USB-sticks ('Developer stick') which is given to all participants (contains latest developer tools) (1-2 volunteers)
* Coordinates tool-shop usage (1 volunteer)

'''Members:'''
* Laszlo Papp (djszapi)
* Topi Santakivi (sandst1)
* ...

''' Ideas & Tasks: '''
* Sign to be attached in the entry-point of Meegathon teams: [http://dl.dropbox.com/u/7717672/Meegonetwork.fi/hackland-sign.png hackland-sign.png] -kyber
* Polish/Define the competition (Meegathon) [[Local_MeeGo_Networks/MeeGo_Network_Finland/MeeGo_Summit_FI#Meegathon |rules]]. -kyber
* Define the content of 'Developer USB-stick' -kyber
* Create new LAN/WLAN solutions which might help.

== Program ==
The summit program includes keynotes, three tracks, workshops, evening party on Friday and Meegathon competition. On Saturday we have Finhack (http://www.finhack.org) annual conference on the second floor.

=== Confirmed Speakers ===
Topics will be set later, in February - March.
* Carsten Munk (keynote) - http://meego.com/users/stskeeps
* Valtteri Halla (keynote) - http://fi.linkedin.com/in/valhalla
* Thiago Macieira (keynote) - http://conference2010.meego.com/people/thiago
* David Greaves - http://conference2010.meego.com/people/lbt
* Dave Neary - http://conference2010.meego.com/people/dneary
* Ville Ilvonen - http://conference2010.meego.com/people/vilvo

=== Tracks ===
In every organization, there are people who just have the knack for getting the most out of certain software and tools. These tracks are where those people shine -- it is the place to show off the newest tools, share creative uses for old favorites, and of course pass on hacks, tips and tricks. Sessions may include demonstrations, pilot projects, examples, techniques, and lessons learned.

# '''Core & Future''' - Apps and possibilities with latest tools (Fri - Sat)
# '''Hacks & Tricks''' - HW inventions, unconventional experiments (Fri - Sat)
# '''Biz Buzz''' - MeeGo Ecosystem and Open Source (Fri)

=== Hackshops ===
Also known as lame Workshops. Participating to Hackshops requires sufficient amount of hack attitude and enthusiasm. We have some facilities (small meeting rooms) for hackshops. If you get an idea about what to teach/show to others (preferably hands-on stuff), book yourself a hackshop space and let the organizers know about it by dropping at the information desk! Your hackshop will be announced in twitter and on the venue screens. If you already know a topic, put it below.

'''Ideas for Workshop.'''

Add your ideas for workshops below. Also add your name if willing to run the workshop.
* ...

=== Meegathon ===
Meegathon is a hacker type of competition, much like a hack-a-thon. The following competition takes place between Fri 12:00am and Sat 12:00am. All teams demonstrate their results Saturday to all event participants. Best inventions and innovations are rewarded. Competition includes two categories:
* Hardcore (HW & SW)
* Quick & Dirty (SW only)

''' Hardcore '''
* the end-product must include and use MeeGo OS (1.1 or above) as one of the main components.
* the end-product HW must be self-made (may include manufactured circuits, wires, connectors, etc)
* keep the size in reasonable limits, eg no monster cars or full scale helicopters.
* all pyrotechnics and acid based solutions are forbidden!
* the agenda of your project is not limited in anyway (except the above).

''' Quick & Dirty '''
* must include only software.
* the end-product must include and use MeeGo OS (1.1 or above) as one of the main components.
* hardware available: web cameras, wires,...
* the agenda for the software is given in the beginning of Meegathon and is the same for all.
* software produced must run on one of the following hardware:
** Nokia N900
** Lenovo Ideapad S10-3t Tablet or similar
** The list of devices will be updated later.

All teams have a dedicated space where to build stuff in the second floor. The space is a big hall, which is divided into smaller areas.

''' Team rules '''
* max 5 persons
* no limitations to member origin (eg from corporate, hackerspaces, LUG's, etc) If the team is sponsored by corporation or includes only corporation employees, it MUST be stated in project description.
*

=== Party ===
* Friday night, detailed time will be announced later
* Location: coordinates will be announced later
* name of the party?

=== Quadricopter/MeeGo games ===
We might be able to arrange a possibility to hold small-scale playful games with couple of Quadricopters. More will be revealed later. Needs 1-3 volunteers.



== Sponsoring ==
Sponsoring opportunities and packages, contact Ilkka Lehtinen (ilkka dot lehtinen @ hermia dot fi)

'''Sponsors:'''

* Ixonos (Main Sponsor)
* Tieto

== How to contribute? ==
Interested in helping? Great! Contributing is easy and you can give as little or as much time as you want.

Here are just a few ways you can get started:
* Check the TODO list below to find something that needs to be done.
* Join discussion at our IRC channel: #meego-fi (irc.freenode.org) and ask what you can do. If you don't have a IRC client, you can access the channel from this free service: http://webchat.freenode.net/
* Join our mailing list (add here)

Here are some of the volunteer opportunities:
* IRC Chat Moderators
* Information Desk Helpers
* Session Tech Support
* Conference Setup - 14th Apr.
* Conference Cleanup - 16th Apr
* Speaker Assistants
* Hacking Session Helpers

Not sure where you want to volunteer yet until the conference schedule is finalized? Put your name here and we'll add more detailed volunteer tables in the months to come.

'''Volunteers:'''

* Juha [http://twitter.com/#!/riussi @Riussi] Ristolainen
* Jukka [http://twitter.com/jukkaeklund @jukkaeklund] Eklund
* Carol [http://twitter.com/cybette @cybette] Chen
* Ville [http://identi.ca/jykae @jykae] Jyrkkä

== TODO ==
List of tasks etc that needs to be done by organizers or volunteers. Add your name after a task if you want to do it.
* Define and collect software package (collected about a week before Summit) given for every attendee in a USB stick. 300 pcs. Cuts back the need to download all software from the net. USB-sticks will be provided by New Factory. - Topi Santakivi (sandst1)
* Marketing material: t-shirts, stickers, flyers....
*

Local MeeGo Networks/MeeGo Network Finland/MeeGo Summit FI

2010-12-02T19:24:30Z

Jnwi: /* Marketing & PR */

= Meegolandia Open 2011 Tampere=
Tampere initiated the first [[Local_MeeGo_Networks|Local Meego Network]] in Europe, [http://www.meetup.com/Tampere-MeeGo-Network/ Tampere Meego Network]. This is annual summit which is held in different locations around Finland. Tampere will host the first Regional Meego Summit in the world. Although the first Summit is at Tampere, this is a joined effort.

'''[http://www.meetup.com/Tampere-MeeGo-Network/ Tampere] and [http://www.meetup.com/Helsinki-MeeGo-Network/ Helsinki] local networks have joined forces and other local networks are also welcome to participate!'''

The summit is open, but the amount of seats is limited!

MeegoLandia Open includes also a 'hackathon' type of competition, which includes two categories: 'Hard Core' (Both HW and SW) and 'Quick & Dirty' (Just SW). Competition is called: "MeeGathon" and more details can be found below.

== Details ==
* Location: Tampere, Finland. Finlayson area (Plevna, [http://www.uusitehdas.fi/en/ New Factory])
* Time: 15.-16. April 2011
* Duration: 2 days (Fri-Sat)
* Registration fee: Free!
* Seat amount: max 300
* Registration required: yes (address here)
* Web: http://meegolandia.com

== Organizers ==
'''Main organizer:'''
{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"|Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Ilkka Lehtinen
| General
| Head
| [http://www.coss.fi/en COSS]
|}

'''Co-Organizers:'''

{| class="wikitable sortable" border="1" cellpadding="3" cellspacing="0" style="width:800px;"
|-
!width="25%"| Contact Person(s)
!width="25%"| Sector
!width="25%"| Role
!width="25%"| Organization
|-
| Jarkko Moilanen
| General + Program (Community & hackers)
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Jukka Matikainen
| ?
| Organizer
| [http://www.oske.net/en/ OSKE]
|-
| Matti Saastamoinen
| ?
| Organizer
| [http://www.coss.fi/en COSS]
|-
| Ville Kairamo
| Facilities
| Organizer
| [http://www.uusitehdas.fi/en NewFactory]
|}

== Program Committee ==
The committee has been formed by inviting suitable MeeGo community members to it. Current composition is (in alphabetical order):
* [http://meego.com/users/bergie Henri Bergius]
* Jukka [http://twitter.com/jukkaeklund @jukkaeklund] Eklund
* Timo Härkönen
* [http://forum.meego.com/member.php?u=12703 Jarkko Moilanen] (Head)

More about the committee work can found [[Meego Summit FI Program|here]]

== Marketing & PR ==
To be formed ASAP.
* [http://meego.com/users/jnwi Jens Wiik]
More about the committee work can found [[Meego Summit FI Marketing|here]]

== Communication ==
* cybette (head)



== Program ==
The summit program includes keynotes, three tracks, workshops, evening party on Friday and Meegathon competition.

=== Keynotes ===
Topics will be set later, in February - March.
* Carsten Munk

=== Tracks ===
In every organization, there are people who just have the knack for getting the most out of certain software and tools. This track is where those people shine -- it is the place to show off the newest tools, share creative uses for old favorites, and of course pass on hacks, tips and tricks. Sessions may include demonstrations, pilot projects, examples, techniques, and lessons learned.

# '''Core & Future''' - Apps and possibilities with latest tools (Fri - Sat)
# '''Hacks & Tricks''' - HW inventions, unconventional experiments (Fri - Sat)
# '''Biz Buzz''' - MeeGo Ecosystem and Open Source (Fri)

=== Workshops ===
* ad hoc and/or preset?

=== Party ===
* name of the party?

=== Session types ===

'''Hands-on'''

Hands-on sessions are a central focus of the summit and attendees will have the opportunity to learn a wide range of new skills and software in these special sessions. Seating for hands-on sessions is limited and admittance requires pre-registration and a ticket. Sessions are 75(?) minute presentations in a dedicated room. Topics for a session should include any of the previously mentioned Session Tracks.

== Sponsors ==
Sponsoring opportunities and packages

List of sponsors

etc....

== MeeGathon ==
More information about categories etc here later.

== How to contribute? ==
Interested in helping? Great! Contributing is easy and you can give as little or as much time as you want.

Here are just a few ways you can get started:
* Check the TODO list below to find something that needs to be done.
* Join discussion at our IRC channel: #meegolandia (irc.freenode.org) and ask what you can do. If you don't have a IRC client, you can access the channel from this free service: http://webchat.freenode.net/
* Join our mailing list (add here)

Here are some of the volunteer opportunities:
* IRC Chat Moderators
* Information Desk Helpers
* Session Tech Support
* Conference Setup - 14th Apr.
* Conference Cleanup - 16th Apr
* Speaker Assistants
* Hacking Session Helpers

Not sure where you want to volunteer yet until the conference schedule is finalized? Put your name here and we'll add more detailed volunteer tables in the months to come.

'''Volunteers:'''

* Juha [http://twitter.com/#!/riussi @Riussi] Ristolainen
* Jukka [http://twitter.com/jukkaeklund @jukkaeklund] Eklund
* Carol [http://twitter.com/cybette @cybette] Chen
* Ville [http://identi.ca/jykae @jykae] Jyrkkä

== TODO ==
List of tasks etc that needs to be done by organizers or volunteers.
* ...
* ...

MeeGo Conference 2010/Volunteering

2010-11-13T12:41:08Z

Jnwi:

Your help is needed to make the MeeGo Conference 2010 a success! Please fill in your name for any of the 2 hour needed slots.

We need volunteers in the following roles:

; Conference Setup/Cleanup
: Setting up banners, installing wires, tables, chairs, ensuring that the conference hall is looking great for the early arrivals on Monday morning; and then packing everything up again on Wednesday evening. Lots of hands needed!
; Info Desk
: We need volunteers to take a couple of hours out of their conference to ensure that people know what's going on, give directions to newcomers, help co-ordinate with the conference staff when small issues arise.
; Session Tech Support
: Work with the conference center audio/visual staff, ensure that speakers are wired up with mics, that video is working, that presenters have the technical assistance they need (for example, if they need to play audio).
; Speaker Assistants
: Co-ordinate with speakers, organise a signal to let them know when they are running out of time, introduce them before their presentation, and handle audience questions on their behalf.
; Live Stream IRC Moderators
: Sit on IRC and ensure everything stays clean and on-topic. Be op for an hour! - Contact Stskeeps on IRC (#meego , irc.freenode.net) once signed up. If you have a mobile device with WiFi and a capable IRC client, that's all you need during the shift (and a watchful eye on the IRC channel)
; Hacking Lounge
: We need a volunteer to supervise the hacking lounge schedule outside conference hours, if people want to get together for a hackfest. (I don't really understand what is involved here --[[User:Dneary|Dneary]] 09:44, 9 November 2010 (UTC))
; Other
: You'd like to help, but don't want to do any of the tasks above, or can't decide? Add your name here, and we will put you to use somewhere!

X = needs a volunteer

{| class="wikitable" cellpadding="5" cellspacing="0" border="1"
|- style="background:LightGrey"
! Day/Time
! Conference Setup/Cleanup
! Info Desk<br/>Needs 2 all the time on 15th & 16th
! Session Tech Support
! Speaker Assistants<br/>Need one per track, except for keynote track
! Live Stream IRC Moderators<br/>Needs 1 during live streaming talks
! Hacking Lounge<br/>Needs 1 outside conference hours
! Other
|- style="background:LightBlue"
|colspan="9"| Saturday Nov 13
|-
| Nov 13, 13:00-15:00
|
| [[User:macron | Ronan Mac Laverty]]
|
|
|
|
|
|-
| Nov 13, 15:00-17:00
|
|
|
|
|
|
|
|-
| Nov 13, 17:00-19:00
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Sunday Nov 14
|-
| Nov 14, 9:00-11:00
|
|
|
|
|
|
|
|-
| Nov 14, 11:00-13:00
|
|
|
|
|
|
|
|-
| Nov 14, 13:00-15:00
| Needed: >=5<br/>[[User:Chippy |Chippy]]<br/>Quim Gil <br> [[User:thomas |thomas]] <br> [[User:macron | Ronan Mac Laverty]]<br> [[User:ymb |Mike Bradshaw]]<br/>
|
|
|
|
|
|
|-
| Nov 14, 15:00-17:00
| Needed: >=5<br/>[[User:Jaffa | Jaffa]]<br/>Aniello Del Sorbo<br/>[[User:timsamoff | timsamoff]]<br/>[[User:jukey | jukey]]<br/>[[user:thp|thp]]<br/>[[User:ymb |Mike Bradshaw]]<br/> [[User:nitingarg|Nitin Garg]] <br/>
|
|
|
|
|
|
|-
| Nov 14, 17:00-19:00
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Monday Nov 15
|-
| Nov 15, 8:00-10:00
|
| Needed: 2<br/>[[User:Jsmanrique| Manrique López]] <br/> Iñigo Gonzalez
| X
| Quim Gil
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 10:00-12:00
|
|Needed: 2<br/>[[User:RevdKathy| Kathy Smith]]<br/>[[User:ymb |Mike Bradshaw]]<br/>
| X
| [[User:Msinternet | Martin Saunders]]
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 12:00-14:00
|
| Needed: 2
| X
| Needed: 4 <br/>[[User:mdamt | mdamt]] (preferably President then 1872 room)<br/> [[User:Chippy |Chippy]] <br/>
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 14:00-16:00
|
| Needed: 2<br/>[[User:frethop| Mike Jipping]]
| X
| Needed: 4<br/>[[User:Vdvsx | Valerio Valerio]] [[User:Chippy |Chippy]]
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 16:00-18:00
|
| Needed: 2<br/>[[User:timsamoff | timsamoff]]<br/>[[User:RevdKathy| Kathy Smith]]
| X
| Needed: 4
| X
| [[User:Leinir | Dan Leinir ]]
|
|- style="background:LightBlue"
|colspan="9"| Tuesday Nov 16
|-
| Nov 16, 8:00-10:00
|
| Needed: 2<br/>[[User:Jsmanrique | Manrique Lopez]] <br/> Iñigo Gonzalez
| X
| Needed: 4
| X
|
|
|-
| Nov 16, 10:00-12:00
|
| Needed: 2<br/>[[User:ymb |Mike Bradshaw]]<br/>[[User:jnwi |Jens Wiik]]
| X
| Needed: 4<br/>[[User:Vdvsx | Valerio Valerio]]
| X
|
|
|-
| Nov 16, 12:00-14:00
|
| Needed: 2<br/>[[User:RevdKathy| Kathy Smith]]<br/>[[User:nitingarg | Nitin Garg]]
| X
| Needed: 4<br/>[[User:Chippy |Chippy]]
| X
| X
|
|-
| Nov 16, 14:00-16:00
|
| Needed: 2<br/>[[User:ymb |Mike Bradshaw]]<br/>[[User:frethop |Mike Jipping]]
| X
| Needed: 4<br/>[[User:Chippy |Chippy]]
| X
|
|
|-
| Nov 16, 16:00-18:00
|
| Needed: 2<br/>[[User:timsamoff | timsamoff]]<br/>[[User:jnwi |Jens Wiik]]
| X
| Needed: 4
| X
|
|
|-
| Nov 16, 18:00-19:00
|
|
|
|
| X
| X
|
|- style="background:LightBlue"
|colspan="9"| Wednesday Nov 17
|-
| Nov 17, 8:00-10:00
|
| Needed: 2
| X
| Needed: 2<br/>[[User:Dneary | Dave Neary]]
| X
|
|
|-
| Nov 17, 10:00-12:00
|
| Needed: 2
| X [[User:Saviq | Michał Sawicz]]
| Needed: 2<br/>[[User: Chippy | Chippy]]
|
| X
|
|-
| Nov 17, 12:00-14:00
|
| Needed: 2
| X
| Needed: 2<br/>[[User:Chippy |Chippy]]
|
| X
|
|-
| Nov 17, 14:00-16:00
| All hands on deck<br/>[[User:Chippy |Chippy]]<br/>Quim Gil <br> [[User:macron | Ronan Mac Laverty]]<br/>[[User:ymb |Mike Bradshaw]]<br/>
| Needed: 2<br/>
| X
| X
|
| X
|
|}

MeeGo Conference 2010/Early Bird Events

2010-10-11T15:53:53Z

Jnwi: /* Volunteers */

== Introduction ==

It would be nice to organize a weekend like the [http://wiki.maemo.org/Maemo-Barcelona_Long_Weekend Barcelona Long Weekend] we (the Maemo Community) organized on October 2009. These two days should be completly organized by the community and for the community. No formal conferences or talks, but interactive activities and hacking sessions where you, the participant, are the main actor.

What about the content of these two days? We could have (for example) programming tutorials, Qt tutorials, hacking sessions on a specific task, round tables where a developer explains his difficoulties implementing a feature and the others help him, ecc...

The first thing to do is spreading this and asking people (users, developers ecc...) what they would like to find during these two days. Once we've gathered some nice ideas we can organize them better.

=== List of people who would like to attend ===

'''Update: We have added a [http://conference2010.meego.com/program/early-bird-events registration page] for the Early Bird event. Please [http://conference2010.meego.com/program/early-bird-events register on the conference website] instead of adding your name below.'''

Please make sure to be registered to the MeeGo Conference. If you'd like to attend, please add your name here - no strings attached, just to get a rough overview of the number of people interested. If you are also interested in helping organizing the event, please also add your name at the bottom of this Wiki page in the Volunteers section.

* [http://meego.com/users/andreagrandi Andrea Grandi]
* [http://meego.com/users/thp Thomas Perl]
* [http://meego.com/users/dneary Dave Neary]
* [http://meego.com/users/jnwi Jens Wiik]
* [http://meego.com/users/texrat Randall Arnold] (coming in Sunday, but can arrive Saturday if someone can share a room...?)
* [http://meego.com/users/pycage Martin Grimme]
* [http://meego.com/users/b0unc3 Daniele Maio]
* [http://meego.com/users/dawnfoster Dawn Foster]
* [http://meego.com/users/sivan Sivan Greenberg]
* [http://meego.com/users/anidel Aniello Del Sorbo]
* [http://meego.com/users/lcuk Gary Birkett]
* [http://meego.com/users/achipa Attila Csipa]
* [http://meego.com/users/ferwakeup Fernando Martin]
* [http://meego.com/users/macron Ronan Mac Laverty]
* [http://meego.com/users/qgil Quim Gil]
* [http://meego.com/users/leinir Dan Leinir Turthra Jensen]
* [http://meego.com/users/monoceros Francesco Baldassarri]
* [http://meego.com/users/jukey Uwe Kaminski]
* [http://meego.com/users/warter Jens Bocklage]
* [http://meego.com/users/timsamoff Tim Samoff]
* [http://meego.com/users/unknowndevice Shane Marks]
* [http://meego.com/users/moon paul mooney]

=== When and Where ===

The basic idea is to organize these two days on '''November 13th, 14th'''. About the location that will host us we still have no idea. Probably it will be possible to use the same [http://www.d4hotels.ie hotel] used for the MeeGo Conference, but this must be confirmed yet.

== Provisional program ==

All sessions are subject to confirmation or change. As we confirm workshop & tutorial leaders, we will add more details. [[#Ideas_for_the_program | Other session ideas]] proposed below may end up being included, based on popular demand.

Tutorials are 3 hour sessions with a trainer going over the basics and getting participants using tools. Participants should bring a laptop for development.

Workshops are hands-on, meet-the-experts sessions, where you can work in small groups brainstorming application design, getting help porting your application to MeeGo, or coding.

Both workshops and tutorials will be limited depending on the space we can get in the hotel. we are hoping to get 2 rooms each of which can handle 20 to 30 attendees.

The Geocache will be outside the hotel. The meeting place and time will be announced closer to the event (probably as GPS co-ordinates ;)

The Maker's Contest will be a team competition limited to 10 teams of up to 5 people. The contest subject matter will be announced closer to the contest. The ideal space requirements are basically a bar, someplace where interested spectators can look on, and 10 tables which participants can work on.

{| style=" border-spacing: 0;" border="1"
! Time !! Workshop !! Tutorial !! Other
|-
| Sat 14:00-17:00
| SCRUM sprint / coding contest?
| Linux Developer Tools
|
|-
| Sat 17:00-18:30
| colspan="3" | Maker's Contest (after workshops, with beer)
|-
| Sun 10:00-13:00
| UX experts: Hands-on application design
| Introduction to Qt
| BOFs
|-
| Sun 14:00-17:00
| Hands-on Qt
| Getting started with MeeGo on ARM
| Geocache treasure hunt
|-
| Sun 20:00-?
|
|
| [http://www.portlandwerewolf.com/rules Werewolf Games] - no prior experience needed
|}

== Tasks ==

* Spread this idea around the community (in Maemo and MeeGo mailing lists and forums)
* Gather ideas and feedback from users and developers
* Create a public poll so the people can vote the most interesting content and we'll have a more realistic idea of what users want
* Thinking about a proper name for these two days (sounds "Dublin MeeGo Weekend" good?)
* Maybe create a customized logo for "Dublin MeeGo Weekend" ?
* Implementation of a registration form for this event
* ecc...

=== Ideas for the program ===

Overall program structure:

* Active participation in the event - less talk, more code. No powerpoints - just you, the editor and the compiler. Be productive!
* A two-day Hackathon: Start putting your ideas into fresh code, or finish a project that has been on the back burner for some time
* Participants are encouraged to share their progress at the end of each day - what they accomplished, where they need further help, etc.

Session ideas:

* Gentle introduction to Qt through PySide and QML, exploring the object hierarchy through the improved interactive interpreter IPython (-sivan)
* A short but intensive indroduction to Qt/C++ (something like 3-4 hours course, offered by some expert developer)
* Round tables to discuss about UI improvements or features implementation: a developer could have found some difficoult implementing the UI for his application or to provide a particular feature. Other expert developers could try to help him with his problem.
* A workshop for x86 developers on getting started with MeeGo development for ARM - end goal: By the end of the session, everyone has a sample application running in an emulator on their laptop
* Developer tools training - a half day on using git, valgrind, oprofile
* One night coding competition.
* ...
* Workshop about libmeegotouch[http://meego.gitorious.org/meegotouch/libmeegotouch], [http://conference2010.meego.com/session/libmeegotouch-meego-touch-framework-application-scratch table of contents], taught by [http://conference2010.meego.com/people/ayanes ayanes] & [http://conference2010.meego.com/people/matusz matusz]. Due to we don't have enough time in the second day of the conference, maybe is a good idea to teach also the workshop on the weekend in a long session (~2 hours and 30 minutes).
Extra-curricular activities:

* A variety of team competitions with some small prizes
** Geocache treasure hunt
** Maker's contest - some ideas: build a good mousetrap powered car, a bridge with glue & lollipop sticks, or the best paper airplane (details to be announced on-site)
** A quiz??

== Dublin Weekend Program ==

(the program has still to be defined)

* As this is the first meeting between many Nokia and Intel developers maybe we should all go [http://www.dublinpubscene.com/thepubs/thestagshead.html to the Pub on Saturday]
* On Sunday a trip to [http://www.knowth.com/newgrange.htm Newgrange] would be enjoyable and enlightening

== Volunteers ==

* [http://meego.com/users/andreagrandi Andrea Grandi]
* [http://meego.com/users/thp Thomas Perl]
* [http://meego.com/users/dneary Dave Neary]
* [http://meego.com/users/texrat Randall Arnold]
* [http://meego.com/users/sivan Sivan Greenberg]
* [http://meego.com/users/anidel Aniello Del Sorbo]
* [http://meego.com/users/achipa Attila Csipa]
* [http://meego.com/users/timsamoff Tim Samoff]
* [http://meego.com/users/unknowndevice Shane Marks]
* [http://meego.com/users/saviq Michał Sawicz]

== Links and discussions ==

* [http://forum.meego.com/showthread.php?t=1342 MeeGo Forum thread]
* [http://talk.maemo.org/showthread.php?t=61708 talk.maemo.org thread]

Local MeeGo Networks

2010-09-11T20:05:33Z

Jnwi: /* Networks in the World */

Local MeeGo Networks organize face to face meetings and other activities on the real ground. They bring what no online social network can provide: real handshakes, real kudos, real applause, real face to face chat. They are free as in beer and you might even get some real drinks for free as well!

== Networks in the World ==

* [http://forum.meego.com/showthread.php?t=1398 Bangalore, India] (CANDIDATE)
* [http://www.linkedin.com/groups?homeNewMember=&gid=3381912&trk= Buenos Aires, Argentina] (CANDIDATE)
* [http://forum.meego.com/showthread.php?t=1377 Cambridge (Cambridgeshire UK)] (CANDIDATE)
* [http://www.meetup.com/DFW-MeeGo-Network/ Dallas / Fort Worth, USA]
* [http://forum.meego.com/showthread.php?t=1383 Delhi, India] (CANDIDATE)
* [http://forum.meego.com/showthread.php?p=9135#post9135 Helsinki, Finland] (CANDIDATE)
* [http://forum.meego.com/showthread.php?t=1405 Montréal, QC, Canada] (CANDIDATE)
* [http://forum.meego.com/showthread.php?p=9118#post9118 Toronto, ON, Canada] (CANDIDATE)
* [http://www.meetup.com/SFBay-MeeGo-Network/ San Francisco Bay Area, USA]
* [http://www.meetup.com/Tampere-MeeGo-Network/ Tampere, Finland]

== Calendar ==
The local events can be found at http://meego.com/community/events with the prefix [LMN].

== The Monthly Meetup ==

Local MeeGo Networks keep a routine of monthly meetups open to everybody combined with activities focused on specific audiences.

For the monthly meetups there is a common framework:
* Short Welcome: announcements and applause to the meetup host.
* Up to 5 lightning sessions of 5 minutes each: demos, intros, insights... Low-tech or No-tech is welcome.
* Applause. ;) Next meeting announcement. More applause.
* Plenty of time just to chat and have a good time. If possible, find a sponsor for local drinks and food.

We encourage the local networks to improve the formula and adapt it to the local taste. Remember to contribute your improvements to this page!

== Other activities ==

Local MeeGo Networks are encouraged to organize specific activities according to the local agenda and the community needs. Some ideas:

* Peer training.
* Install party.
* MeeGo localization sprint.
* Promotion in a local [[Events|event]].
* Full presentation of a product or project.
* Session starring a special guest.
* Your idea here.

== Starting a new network ==

'''Starting is simple''': find 4 MeeGo peers and organize a dinner or a social meetup once a month. That's it. If things deserve to grow they will grow.

=== Listing new candidate networks ===

If you are in the process of creating a new network advertising your intentions will only help. Start a new thread at the [http://forum.meego.com/forumdisplay.php?f=5 Community Matters forum] and list it above following this example:

* [http://forum.meego.com/your-thread City or Region] (CANDIDATE)

The forum thread starter can be really simple. Please add any info relevant to the locals. Non-English speakers: after the intro in English consider adding a translation in your local language, and feel free continuing the discussion in the language(s) you prefer:

'''Title:''' ''$PLACE MeeGo Network''

'''Body:''' ''Hi, there is an interest creating a Local MeeGo Network at $PLACE. If you are interested please answer here. The first goal is to get 5 aMeeGos in order to consider the group formally created. See http://wiki.meego.com/Community_Office/Marketing/Local_MeeGo_Networks ''

=== Once you are 5 aMeeGos ===

Next steps once you have reached the critical mass:

# Find a date and a place for a first monthly meetup.
# Find 4 more peers confirming to attend.
# Choose the right tool to organize the network.
# Publish your network including a link to this page.
# Link your network from this page.
# Add your events to http://meego.com/community/events with the prefix [LMN]

Done!

== Tools for meetups ==
Choose the tool that will work better in your own context. You can go for a wiki page + forum thread, you can use a specialized tool or you can do something else. If a certain social network is very popular in your area consider that. Just make it easy for others to join the network and get involved.

The tools currently used are:

* [http://meetup.com Meetup] - All-in-one solution, popular at least in some parts of the US. Requires a small monthly fee. You are encouraged to find a local sponsor but the MeeGo project can subsidize the first 6 months if your proposal is convincing.

MeeGo Greeters

2010-09-07T16:52:50Z

Jnwi: /* List of Greeters */

==Welcome to the MeeGo Greeters Page==

This is a voluntary initiative by members of the MeeGo community, designed to leverage the strength of forum (and even email) signatures to spread links to helpful MeeGo community resources.

Greeters here at MeeGo.com can be recognized by their distinctive (often multilingual) signatures within which are several useful links for the newcomer/beginner/curious. If you're new or curious, feel free to click through those links.

As well, Greeters are encouraged (but not expected) to perform typical help desk activities in the MeeGo Forum.

Some notes for potential greeters:

* This program is strictly voluntary
* There is no official status conferred by this "title"
* There are no offers or guarantees of any reward
* There are currently no plans for formal scoring of participation
* Try to remain courteous at all times

Notes for newcomers:

* Please Thank any post that assists you, directly or indirectly
* Keep in mind that every Greeter is a volunteer
* Feel free to suggest ideas to any Greeter

It is expected that Greeter participation will result in Thanks from those who directly benefit, as well as anyone appreciative of the effort.

==The Concept==

By including links to helpful resources in post signatures, Greeters provide an extremely easy yet effective way of spreading access to knowledge. No technical expertise is required, no further engagement necessary. Just identify yourself as a MeeGo Greeter, include pointers to knowledge centers, and provide a useful service just by posting in the Forum!

Any member can volunteer for this activity, and it can be implemented by simply using the following (or similar) for your posting signature:

Hi, I'm a [http://wiki.meego.com/MeeGo_Greeters MeeGo Greeter]! Welcome to the world of MeeGo!

Useful links: [http://forum.meego.com/showthread.php?t=3 Members say Hello] | [http://meego.com/about/contribution-guidelines How to contribute to MeeGo] | [http://wiki.meego.com/MeeGo_FAQ Frequently Asked Questions (FAQ)] | [http://wiki.meego.com/Glossary Glossary] | [http://wiki.meego.com/Developers Developer's Guide]

If I can help with anything else, just ask!

''in progress''

==Multilingual Approach==

Some readers feel more accepted if they are welcomed in their own language. To that end, Greeters are strongly encouraged to create signatures in their native language.

== List of Greeters ==

(Note - if you want to be a Greeter, see below and feel free to add your name (linked to your profile) to this list...)

* [http://meego.com/users/texrat texrat/Randall Arnold] (coordinator)
* Stskeeps/Carsten Munk
* eipi/Sanjeev Visvanatha
* timoph
* revdkathy
* [http://meego.com/users/jnwi jnwi/Jens Wiik]
* [http://forum.meego.com/member.php?u=6459 lindqvust]
* macek
* [http://meego.com/users/vkvraju vkvraju]

MeeGo Conference 2010/Early Bird Events

2010-09-06T19:38:12Z

Jnwi: /* Ideas for the program */

MeeGo Conference 2010/Early Bird Events

2010-09-06T19:37:43Z

Jnwi: /* Ideas for the program */

MeeGo Conference 2010/Early Bird Events

2010-09-06T19:22:25Z

Jnwi: /* List of people who would like to attend */

MeeGo Conference 2010/Early Bird Events

2010-09-06T19:20:38Z

Jnwi: /* Volunteers */

MeeGo Conference 2010

2010-09-03T18:35:18Z

Jnwi: /* General */

The information below is work-in-progress.

== About ==

''' MeeGo Conference will be held at Aviva Stadium in Dublin, Ireland November 15-17th, 2010'''

The MeeGo Conference replaces the Maemo Summit. We're using the term "conference" because The Linux Foundation usually uses the term "summit" to refer to invitation-only events, and since the MeeGo conference is open to anyone who would like to attend, we decided to refer to it as the MeeGo Conference to avoid confusion.

Our Call for Proposals has begun! Would you like to speak at the first MeeGo Conference? Anyone who wants to speak at the conference must [http://conference2010.meego.com/news/call-session-proposals-has-started submit a proposal]!

Submit your proposals on a variety of topics including:
*Hardware support
*Platform development
*Application development
*MeeGo project, process and progress
*and any other MeeGo related topics

Call for proposals closes August 23rd and you will receive an email on whether or not your session is approved by September 24, 2010.

Registration is open now and there is an [[/FAQ|FAQ]] for attendees (and potential attendees)

== Sponsors ==

Prospectus is now available, please send to anyone who is interested in sponsoring MeeGo Conference 2010! [http://wiki.meego.com/images/MeeGo_Prospectus_2010_%282%29.pdf MeeGo Conference Prospectus]

== Audience ==

The MeeGo Conference targets a technical audience of:
* MeeGo developers
* OSVs, OEMs, and other integrators
* Other MeeGo project contributors

'''Other target audience suggestions'''
* Relevant media representatives (bloggers, promoters)

== Format and Logistical Details ==

* 3 day event, begins Monday Nov. 15th thru Wednesday Nov. 17th
* We currently have events planned on Monday Nov. 15th at the Stadium, and Tuesday Nov. 16th at Guinness Storehouse, but are welcoming the community to put together events on Sunday Nov. 14th and Wednesday Nov. 17th
* Conference Held at Aviva stadium
* Conference Space that we have:
** Presidents Terrace for Keynotes Day 1 sits 1200 theatre style or 580 cab ([http://www.lmc.ac.uk/home/hiring/seating.php cabaret style]) - suggesting theatre style for the keynotes
** Breakout session will be used as follows:
*** Level 02
**** 1. Presidents area split in half area 1 sits 300 cab
**** 2. Presidents area 2 sits 280 cab
**** 3. Vavasour suite sits 80 cab
*** Level 03 (where you enter)
**** The Atrium- registration/welcome/tea and coffee breaks
**** The flow between the Atrium and the next break out area called the Henry suite will be an area for a proposed Technology Showcase for MeeGo projects to be displayed and demo's.
**** 4. 1872 area sits 120 cab is the 4th breakout area opposite the atrium on the other side of the stadium.
*** Level 04 (stairs/elevator from the atrium)
**** 5. Havelock suite sits 130 cab- 5th breakout area
**** 6. Media center- in another part of the stadium: Perfect for a Graphics track or UI track based on the space.
* Hotels being used are the D4 hotels and you may book through registration site (read about details on site below)
* Registration site is planned to go up no later than August 7. but we are aiming for it to be up mid-July.
* The Registration will have a place for submissions to the call for papers (including submissions from Intel / Nokia) and a small selection committee will be responsible for choosing the presentations based on the merits of each submission.
* Anyone is welcome to submit a proposal or attend the event.
* The event will be free for attendees
* Sponsorship Prospectus is attached under Sponsor section, please send to anyone interested
* Updated 6/22/10 AL

== Location ==

Aviva Stadium in Dublin, Ireland- November 15-17th, 2010

Contract is in place and planning information will be updated online for your involvement:)

* [http://www.avivastadiumevents.ie/stadium.aspx Aviva Stadium]
* Conference facility has held for us one plenary room for the keynote session, and 6-8 breakout rooms to seat 100, I will be creating a presentation to place online, so everyone will see where and what rooms we will be the seesions of the conference in.
* We will be holding 530 rooms at the D4 hotels- 5 min walk from stadium, literally across the street, these are 3* and 4* hotels and will be around 115 euros/ night, to save money you could split a room with someone, as they do have double rooms. We will also have a 24hr networking room set up in the D4 hotels for ppl to get together at the hotel facilities http://www.d4hotels.ie/
* We are also holding 100 rooms at the Herbert Park hotel again only a couple blocks from the stadium
* Dublin is an easy city to get to for international travelers
* Venue is right on mass transit line (DART)
* Outside of Schengen area, non-EU citizens would require visa [http://www.dfa.ie/home/index.aspx?id=8777 Visa information for Ireland]

== Team ==
* Coordination: [http://meego.com/users/dawnfoster Dawn Foster] and [http://meego.com/users/qgil Quim Gil].
* Logistics: [http://meego.com/users/amyleeland Amy Leeland] coordinates. Specific areas and people in charge to be listed below.
** Specific areas go here.
* Content committee: [http://meego.com/users/hohndel Dirk Hohndel] (coordination), [http://meego.com/users/thiago Thiago Macieira], [http://meego.com/users/mmeeks Michael Meeks] and [http://meego.com/users/stskeeps Carsten Munk].

=== Sponsoring Committee ===
'''PROPOSAL'''
The Sponsoring Committee is in charge of reviewing the sponsorship requests sent by individuals registering to the conference. It is formed by five members: [http://meego.com/users/qgil Quim Gil] (coordinator, [http://wiki.meego.com/Community_Office Community Office]), [http://meego.com/users/dawnfoster Dawn Foster] ([http://wiki.meego.com/Community_Office Community Office]), Angela Brown (Linux Foundation), [http://meego.com/users/slaine Glen Gray] (Moblin/netbook bg) and [http://meego.com/users/jaffa Andrew Flegg] (Maemo/handset bg).

The idea is to handle the approvals through several rounds of acceptance: first the speakers approved, then the requesters obtaining unanimous support, then the rest until all the sponsorship budget is allocated. An private online spreadsheet will be used to register the votes of the committee members. The discussion will be held through mail and we will organize IRC or conference meetings if needed.

== Volunteering ==

To run a smooth and successful MeeGo Conference will require a number of volunteers. If you want to volunteer for a certain part of the conference, please add your name below that heading, linked to your meego.com profile. You can follow the conference organization work at the [http://forum.meego.com/forumdisplay.php?f=5 Community Matters forum] (specifically [http://forum.meego.com/showthread.php?t=95 this thread]).

=== General ===
Not sure where you want to volunteer yet until the conference schedule is finalized? Put your name here and we'll add more detailed volunteer tables in the months to come.

'''Volunteers:''' [http://meego.com/users/dneary Dave Neary/dneary], [http://meego.com/users/texrat Randall Arnold/Texrat], [http://meego.com/users/chippy Steve Paine/Chippy], [http://meego.com/users/timsamoff Tim Samoff/timsamoff], [http://meego.com/users/andreagrandi Andrea Grandi/andy80], [http://meego.com/users/ferwakeup Fernando Martin/ferwakeup], [http://meego.com/users/jnwi Jens Wiik/jnwi].

=== Scheduled Opportunities ===
There are a number of volunteer opportunities that people can signup for specific time slots, such as manning the information desk or session tech support. Since the final conference schedule isn't available yet, people can signup for the tasks now and then shift around the times they are available later. These are the types of volunteer opportunities:

* IRC Chat Moderators
* Information Desk Helpers
* Session Tech Support
* Conference Setup - Sunday 14
* Conference Cleanup - Wednesday 17
* Speaker Assistants
* Conference Room Reservation Table
* Hacking Session Helpers

'''Volunteers:'''

=== Organizing Opportunities ===
A number of the conference activities have yet to be fully organized and the conference committee would love help with these tasks. Here is a list of activities still needing to be organized. It might be best to start forum threads for each of the specific organizing tasks and then document here the decisions.

* Organize Early Bird Events
* Organize Hacking Sessions
* Organize Temple Bar Night
* Organize Signup for Guinness Shuttles
* Reach out to local businesses for conference deals

'''Volunteers:'''

* [http://meego.com/users/andreagrandi Andrea Grandi/andy80]: I propose myself for '''Organize Early Bird Events'''. I'd like to lead the organization of two days ('''November 13th, 14th''') in the similar way we (Maemo Community) organized the [http://wiki.maemo.org/Maemo-Barcelona_Long_Weekend Barcelona Long Weekend]. More details soon.
* [http://meego.com/users/thp thp] - Early Bird Events w/ Andrea

== Topics ==

Potential themes for the conference which suit a first conference.

; MeeGo for Maemo & Moblin application developers
: Bringing developers from old platform to new
: please define here how the old differs from the new. I am assuming the new platform includes using the Qt framework as the standard, but what else? What is the smooth way to move RPM -> DEB?
; MeeGo for N900 and N8x0 owners
: What is MeeGo in a concrete way? Is it a set of userland libraries and applications that you can run on your N900 in a chrooted environment for example?
: Bring our old power users over
: dual booting a "Meego flash image" on your N?x? device? What about MER?
; New developers coming to MeeGo
: Qt and WRT, and maybe Clutter
; Distributing MeeGo software
: yes, please explain how to do this in light of the current system of uploading Debian packages & promoting?
: What comes after Extras?
; MeeGo platform
: Getting more developers involved in the MeeGo platform, and reaching out to upstream to have a critical mass of MeeGo middleware developers there
; Cool stuff (hardware & software) coming out of Helsinki & Portland
: Target press & new users
; Building a healthy MeeGo community
: Involving Intel and Nokia engineers, upstream, platform hackers, application developers and power users in the MeeGo community - covering things like outreach and events, community infrastructure (including the Technical Steering Group, working groups, council?), social dynamics & policies, and community involvement in product roadmaps, etc
;Testing with MeeGo
:Test development, image creation, test execution and debugging as a smooth ride along development.
;The Community Development Ecosystem around MeeGo (lbt)
: Building against MeeGo - the Maemo and MeeGo community OBSes
: Application development and community application QA - Extras and PPAs(?)
: Experimental development - MeeGo on N8x0

'''''A first draft of the Call for Papers is up: [[MeeGo_Conference_2010/DraftCFP]]'''''

== Other suggestions for the event ==
* 3 days event, 2 days organized by the community and one organized by the companies involved. Developers, platform and power users tracks. --[[User:Vdvsx|Vdvsx]] 22:24, 12 March 2010 (UTC)
* In addition to 20 minute talks and 5 minute lightning talks, a provision for talks that fit in between (10 minutes) --[[User:Texrat|Texrat]] 03:47, 14 March 2010 (UTC)
* team-building, brainstorming exercises on a large scale (like the [http://maemo.nokia.com/news/maemo-co-creation-workshop-video/ Co-Creation Workshop held before Maemo Summit 2009] --[[User:Texrat|Texrat]] 03:47, 14 March 2010 (UTC)
* themed tracks with breakout sessions between X sets of presentations (where X can be number of sessions or time duration). --[[User:Texrat|Texrat]] 05:41, 27 April 2010 (UTC)
* Birds Of Feather [http://en.wikipedia.org/wiki/Birds_of_a_Feather_(computing) (BOFs)]- for casual non formal feature planning and development specification: --[[User:sivan|sivan]]
** A group of people interested in a feature or a process gather around a round table.
** A driver for the discussion presents the topic he wants to spec out or a topic assigned to him to present from the list of process and features desired.
** Input is arriving from participants, and is ironed out as "[http://en.wikipedia.org/wiki/User_story user stories]" , as well as leads, references tips and hints for undertaking the development.
** The driver after finishing the session sets to finish the spec in terms of completeness and publish it on the wiki for peer review of the BOF participants and/or a review board that accepts features and new takes for the project.
* Recognize the '''non-technical''' contributor of the year. This is important since we have so many needs on the community side. --[[User:Texrat|Texrat]] 01:35, 17 August 2010 (UTC)
* Recognize the most popular presentations. There should be a formal survey for every talk and workshop, as well as a summary survey. Use the findings to reward those who stood out. --[[User:Texrat|Texrat]] 01:35, 17 August 2010 (UTC)
* Games. Some sort of intramural sports or activities. Hey, we're in a stadium, right? Let's take advantage! Okay, maybe we can't use the field, but surely we can come up with something... even tug-of-war would be fun --[[User:Texrat|Texrat]] 01:35, 17 August 2010 (UTC)
** Treasure/scavenger hunt for meego goodies and prizes.
* [http://wiki.meego.com/MeeGo_Greeters MeeGo Greeters] would make great volunteers! --[[User:Texrat|Texrat]] 19:58, 31 August 2010 (UTC)