MeeGo wiki - User contributions [en]

Application developer site

2011-01-26T08:12:02Z

Macron: /* Content management process matrix */

== Overview ==

From the experiences of Apple and Android, we can assume that, if we are successful, there will be many more application developers than platform developers. Their needs will be different, as they are more interested in using APIs than designing them. The audience will consist of both beginners who need simple, clear, tutorials/walkthroughs, and experienced developers more interested in code samples and reference documentations.

== Objectives ==

The goal of the developer.meego.com site is to present and market the Meego Application Developer offering. This needs to be of high quality on par with other application developer sites (Android, Palm, Drupal, KDE, Apple).

== Status ==

The current status can be found [[Application developer site/Status | here]].

A bugzilla version is available [http://bugs.meego.com/show_bug.cgi?id=7882 here].

{{#bugzilla:
|columns=id,priority,severity,status,summary
|product=developer.meego.com
|status=new,assigned,needinfo,reopened
|sort=priority,severity,id
}}

== Tasks ==

All [http://bugs.meego.com/buglist.cgi?quicksearch=developer.meego.com bugzilla tasks/bugs] for developer.meego.com.

=== Critical tasks ===

See bugzilla list above.

== Content Description ==

The content description can be found from [[Application developer site/Description | here]].

The site should link to the related content listed [[Application developer site/Related content | here]].

=== Content Process ===

The proposed content management process is based upon several community roles. These roles must first be defined before introducing the proposed content management matrix.

'''Concept owner'''

Responsibilities include:
* Manage the personas and user journeys across the ecosystem surrounding the site
* Identify main content and capability gaps and needs for these journeys
* Act as the primary advocate for the visitor

'''Design owner'''

Responsibilities include:
* To ensure the structure and capabilities of the developer.meego.com match the needs of personas and the business/community
* To ensure the site design fits the requirements and tonality of the MeeGo brand
* To ensure business/community and visitor requirements are captured, analyzed and prioritized

'''Production'''

Responsibilities include:
* Manage delivery of capabilities according to prioritized requirements
* Packaging requirements into releases, planning release timetables and communicating releases details

'''Content editor'''

Responsibilities include:
* Manage the actions resulting from the content plan for those personas and tasks that were prioritized for site launch (managed through Bugzilla)
* Monitor and manage scenario and persona expectations (around KPIs) and further develop the content plan around these expectations
* Validate user needs and remaining user tasks based on community/user needs (place content plan on wiki to get feedback, active use of Bugzilla to solicit needs)
* Create and manage content, onsite and across the ecosystem (for example Wikipedia and Youtube) resulting from the actions identified above
* Develop content needs from relationship with community, with people representing personas
* Ensure quality of content (grammar, style, tone of voice, etc.) and relevance

Note: In the future, this role may also be broken up by content area (example: Guides and tutorials editor, SDK and tools editor) or consist of an editorial team with members spaced over all the major geographic regions.

'''Business/community owner'''

Responsibilities include:
* Accountable for the overall performance, results and visibility of developer.meego.com site
* Prioritization of requirements according to business/community and visitor needs
* Approval of major editorial decisions
* Oversee and facilitate the developer community with a special focus on the primary community stakeholders
* Budget and budget allocation

'''Analytics manager'''
Responsibilities include:
* Development of the measurement framework according to personas
* Development of KPIs required for these personas
* Regular production of KPI results, baseline and recommended targets

'''Operations'''

Responsibilities include:
* Coordination and support for the team
* Ensuring effective tools and processes are in place and in use
* Managing meetings and ad-hoc workshops

==== Content management process matrix ====

Process for community-driven content.

{| border="1"
|Activity
|Accountable
|Responsible
|Contributor
|Informed
|Tool(s)
|----
|1. Content staged on Wiki as draft
|Content creator
|Content creator
|Content editor
|
|Wiki
|----
|2. Content drafted and staged on site (content source referenced, eg: Wiki revision referenced)
|Content editor
|Content creator
|Content editor, Concept owner
|
|Content plan, Bugziila, CMS
|----
|3. Content approved and released
|Business owner
|Content editor
|Content editor, Concept owner
|Community
|CMS, Bugzilla
|----
|}

Draft version of the content management process below is as follows. Note: that steps 1-5, 9-10, are for editor-driven content.

This is a highly detailed description based on the Scrum Use Story process, (1-5: Analyze need, prioritize, 6-8: Implement, 9-10:Test). In most cases these steps merged (for example steps 1,3,4,5 could be done in parallel by the Content editor).

(Suggestions on how to improve this, and make it more appropriate to a community driven site are welcome).

{| border="1"
|Activity
|Accountable
|Responsible
|Contributor
|Informed
|Tool(s)
|----
|1. Community or user need identified
|Stakeholders
|Content creator/editor
|Concept owner, Analytics manager, Content editor
|Community
|Survey and other tools as input Bugziila
|----
|2. Need recorded and classified
|Content editor
|Content editor
|
|Stakeholders Community
|Bugziila
|----
|3. Business prioritization done
|Business owner
|Business owner
|Concept owner, Content editor , Design owner, Analytics manager
|Community
|Bugziila
|----
|4. Effort analyzed for Bugzilla items
|Content editor
|Content editor
|Analytics manager, Design manager
|
|Bugziila
|----
|5. Site and ecosystem analysis to position content
|Content editor
|Content editor
|Design owner, Concept owner
|
|Bugziila
|----
|6. Content staged on Wiki as draft (optional)
|Content creator
|Content creator
|Content editor
|
|Wiki
|----
|7. Content drafted and staged on site (content source referenced, eg: Wiki revision referenced)
|Content editor
|Content creator
|Content editor, Concept owner
|
|Content plan, Bugziila, CMS
|----
|8. Content approved and released
|Business owner
|Content editor
|Content editor, Concept owner
|Community
|CMS, Bugzilla
|----
|9. Site conversion goals reviewed
|Content editor
|Analytics manager
|Concept owner, Business owner
|Community
|Google analytics
|----
|10. Need tested (did this change satisfy the need)
|Content editor
|Content editor
|Concept owner, Analytics manager
|Business owner, Community
|Bugzilla
|----
|}

Matrix legend:
* Accountable = person/people responsible for decision-making (a.k.a. the buck stops here)
* Responsible = person/people whose job is to see the activity happens
* Contributor = person/people whose input is needed to make the activity happen
* Informed = person/people who need to know what’s going on concerning the activity

'''About the tools used in the content management process'''

* Bugzilla is used to manage both content and capability needs, for example wishlists, future releases, current release maintenance fixes, incomplete areas, etc.
* Wiki is used for content drafting and staging for community content. Content in the wiki could be drafted and reviewed in iterations between the content creators and editor and placed on site when the creators and editors feel it is in a complete, quality assured format. For content that is under continual development, Wiki entries may also be divided into constant and variable sections, and linked accordingly in the site.
* Google Analytics may be used to track site use and conversion goals
* Roadmap, actions, issues are used to track development plans

=== Content Draft ===

A wiki version of the information architecture with draft content is available [[Application developer site/Draft content | here]].

=== Future Content ===

The current site could be enhanced with the following content.

# [[Application developer site/Active architecture diagram| Active meego architecture diagram]]

== Development Process ==

The process used to develop the site can be found [[Application developer site/Process | here]]

== Schedule ==

The original schedule was to have an initial site ready for Nokia Developer Summit, and Intel Developer Forum in mid-September. This has been change to match the schedule of the underlying project, so the site should be available in October aligned with the MeeGo 1.1 release.

== Site design ==

The draft information architecture can be found here [[Application developer site/Information architecture | here]]. It is open for comments and suggestions.

Some sample wireframe designs will be found [[Application developer site/WireFrames | here]]. These are open for comments/suggestions.

The full information architecture and complete wireframe set is available in .pdf here: [[File:DMC_Design.pdf]].

After discussion with the maintainers of www.meego.com and the TSG it was felt that developer.meego.com diverged too much from the www.meego.com look&feel. The designers of developer.meego.com have generated an example of this:

[[File:dev-meego.com-frontpage_update_2010-12-20.png|800px]]

== Project Team ==

=== MeeGo Project Manager ===

* [http://meego.com/users/macron Ronan Mac Laverty/macron,maclaver(IRC)] - Nokia's Maemo (Application) Developer Advocate

=== Project Members ===

... People working on the project part-time funded by Nokia ...

* [http://meego.com/users/ttlukkar Teemu Lukkari/ttlukar] / Activeark / Project management, Design manager
* [http://meego.com/users/harmaakinkku Graham Honeywill/harmaakinkku] / Activeark / Project Communications, Analytics manager, Concept owner
* [http://meego.com/users/verbosemode Tiffiny Rossi/verbosemode] / Activeark / Content editor
* [http://meego.com/users/mikaelkundert Mikael Kundert/mikaelkundert] / Activeark / Drupal developer

=== Community Members ===

... People from the community involved in this project .....

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org docmaster
* [http://meego.com/users/dawnfoster Dawn Foster/dawnfoster] - Community Manager
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - MeeGo wiki maintainer & MeeGo SDK content editor
* bspencer - Bob Spencer

== Contact People ==

== Associated activities ==

The [[DeveloperEngagement | Developer Engagement Framework]].

Application developer site

2011-01-04T10:17:46Z

Macron: /* Content Description */

Application developer site

2011-01-04T10:17:03Z

Macron: /* Critical tasks */

Community Office/Meetings/Brainstorm Jan 18 2011 Website Improvements

2011-01-04T10:15:58Z

Macron: /* developer.meego.com */

'''Meeting Logistics'''
* Meeting: 18 January 2010 at [http://www.timeanddate.com/worldclock/fixedtime.html?month=01&day=18&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC]
* More Details.: [[Community_Office/Meetings]]

== Reminder: Community Office Goals for 2011 ==
* Get more people actively contributing to the MeeGo Community (code, application developers, documentation, community facilitation, other participation - technical and non-technical) - [[Community_Office/Community_Management|more details]]
* Better marketing and promotion of MeeGo - [[Community_Office/Marketing|more details]]

'''Meeting Goal'''
* The purpose of these meetings is to help get people involved in the MeeGo community.
* The Community Office meetings are group brainstorming sessions designed to make improvements in the MeeGo community and find volunteers to help us implement our suggestions.
* '''Anyone can attend these meetings or participate in the process!'''

== Brainstorming Topics ==

Please add your feedback and ideas below about 24 hours before the meeting.

=== developer.meego.com ===

* Background Info: [[Application_developer_site/Beta_Process]] and [[Application_developer_site]]
* Website: http://developer.meego.com (Password protected to prevent search engine indexing, username="meego", password="developer")

'''Developer Website Brainstorming Ideas'''
* Add your ideas here.

=== meego.com/projects ===
* Background: [[Marketing/Meego.com_1.2_update#Projects]] (some ideas already posted here)
* Website: http://meego.com/projects

What do we want this section of meego.com to be? We'd like to get as many maintainers and developers to show up and contribute to the discussion.

'''Projects Brainstorming Ideas'''
* Add your ideas here.

=== meego.com homepage improvements ===
* Background: http://bugs.meego.com/show_bug.cgi?id=11513
* Website: http://meego.com

'''Homepage Brainstorming Ideas'''
* Add your ideas here.

Community Office/Meetings/Brainstorm Jan 18 2011 Website Improvements

2011-01-04T10:14:28Z

Macron: /* developer.meego.com */

'''Meeting Logistics'''
* Meeting: 18 January 2010 at [http://www.timeanddate.com/worldclock/fixedtime.html?month=01&day=18&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC]
* More Details.: [[Community_Office/Meetings]]

== Reminder: Community Office Goals for 2011 ==
* Get more people actively contributing to the MeeGo Community (code, application developers, documentation, community facilitation, other participation - technical and non-technical) - [[Community_Office/Community_Management|more details]]
* Better marketing and promotion of MeeGo - [[Community_Office/Marketing|more details]]

'''Meeting Goal'''
* The purpose of these meetings is to help get people involved in the MeeGo community.
* The Community Office meetings are group brainstorming sessions designed to make improvements in the MeeGo community and find volunteers to help us implement our suggestions.
* '''Anyone can attend these meetings or participate in the process!'''

== Brainstorming Topics ==

Please add your feedback and ideas below about 24 hours before the meeting.

=== developer.meego.com ===

* Background Info: [[Application_developer_site/Beta_Process]]
* Website: http://developer.meego.com (Password protected to prevent search engine indexing, username="meego", password="developer")

'''Developer Website Brainstorming Ideas'''
* Add your ideas here.

=== meego.com/projects ===
* Background: [[Marketing/Meego.com_1.2_update#Projects]] (some ideas already posted here)
* Website: http://meego.com/projects

What do we want this section of meego.com to be? We'd like to get as many maintainers and developers to show up and contribute to the discussion.

'''Projects Brainstorming Ideas'''
* Add your ideas here.

=== meego.com homepage improvements ===
* Background: http://bugs.meego.com/show_bug.cgi?id=11513
* Website: http://meego.com

'''Homepage Brainstorming Ideas'''
* Add your ideas here.

Application developer site

2010-12-21T10:17:07Z

Macron: /* Site design */

Application developer site

2010-12-21T10:16:25Z

Macron: /* Site design */

Application developer site

2010-12-21T10:15:58Z

Macron: /* Site design */

File:Dev-meego.com-frontpage update 2010-12-20.png

2010-12-21T10:14:18Z

Macron:

Application developer site

2010-12-21T10:13:53Z

Macron: /* Site design */

Application developer site/Beta Process

2010-12-16T11:12:41Z

Macron: /* How to give feedback? */

= Developer.MeeGo.Com Beta process =

== Introduction ==

developer.meego.com will be released first as a beta site before public release. The goal of this beta is to get feedback about the usability and design of the site. A secondary goal is to create content, and content ideas for the site.

Of particular importance is the ease of use for the guides and references, and general navigation throughout the site.

== How to give feedback? ==

The best way to give feedback about developer.meego.com is through bugzilla.

A blank bug is here:
* [http://bugs.meego.com/enter_bug.cgi?product=developer.meego.com http://bugs.meego.com/enter_bug.cgi?product=developer.meego.com ]

We have a "Content" component for bugs related to missing, wrong, or dead content.

== What happens to feedback? ==

The feedback gets reviewed and we will try to improve the site accordingly. Some items will obviously be easier to implement than others (for example, API searching was quite complex because we had to import the API reference as Drupal nodes, something that took time).

== How to get content on to developer.meego.com? ==

In the short-term for the content ramp-up we will use a very lightweight process.

For content on the actual site:
# Create the content on wiki.meego.com
# Create a "Content" bug with the suggested location of the content, and some description text.
(Be prepared to handle feedback related to the content).

For content linked from developer.meego.com:
# Create a "Content" bug with a reason for linking the content, the suggested location of the content, and some description text

Application developer site/Beta Process

2010-12-08T12:27:47Z

Macron: /* How to get content on to developer.meego.com? */

= Developer.MeeGo.Com Beta process =

== Introduction ==

developer.meego.com will be released first as a beta site before public release. The goal of this beta is to get feedback about the usability and design of the site. A secondary goal is to create content, and content ideas for the site.

Of particular importance is the ease of use for the guides and references, and general navigation throughout the site.

== How to give feedback? ==

The best way to give feedback about developer.meego.com is through bugzilla.

A blank bug is here:
* [http://bugs.meego.com/enter_bug.cgi?product=developer.meego.com http://bugs.meego.com/enter_bug.cgi?product=developer.meego.com ]

We are adding a "Content" component for bugs related to missing, wrong, or dead content.

== What happens to feedback? ==

The feedback gets reviewed and we will try to improve the site accordingly. Some items will obviously be easier to implement than others (for example, API searching was quite complex because we had to import the API reference as Drupal nodes, something that took time).

== How to get content on to developer.meego.com? ==

In the short-term for the content ramp-up we will use a very lightweight process.

For content on the actual site:
# Create the content on wiki.meego.com
# Create a "Content" bug with the suggested location of the content, and some description text.
(Be prepared to handle feedback related to the content).

For content linked from developer.meego.com:
# Create a "Content" bug with a reason for linking the content, the suggested location of the content, and some description text

Application developer site/Beta Process

2010-12-08T12:26:56Z

Macron:

= Developer.MeeGo.Com Beta process =

== Introduction ==

developer.meego.com will be released first as a beta site before public release. The goal of this beta is to get feedback about the usability and design of the site. A secondary goal is to create content, and content ideas for the site.

Of particular importance is the ease of use for the guides and references, and general navigation throughout the site.

== How to give feedback? ==

The best way to give feedback about developer.meego.com is through bugzilla.

A blank bug is here:
* [http://bugs.meego.com/enter_bug.cgi?product=developer.meego.com http://bugs.meego.com/enter_bug.cgi?product=developer.meego.com ]

We are adding a "Content" component for bugs related to missing, wrong, or dead content.

== What happens to feedback? ==

The feedback gets reviewed and we will try to improve the site accordingly. Some items will obviously be easier to implement than others (for example, API searching was quite complex because we had to import the API reference as Drupal nodes, something that took time).

== How to get content on to developer.meego.com? ==

In the short-term for the content ramp-up we will use a very lightweight process.

For content on the actual site:
1 Create the content on wiki.meego.com
1 Create a "Content" bug with the suggested location of the content, and some description text.
(Be prepared to handle feedback related to the content).

For content linked from developer.meego.com:
1 Create a "Content" bug with a reason for linking the content, the suggested location of the content, and some description text

Application developer site/Beta Process

2010-12-08T12:23:43Z

Macron:

MeeGo Conference 2010/Twitter list

2010-11-13T17:10:16Z

Macron: /* Add me to the Twitter list */

We've created a [http://twitter.com/MeeGoConference/attendees-2010 2010 Attendees Twitter list] for people who are attending the 2010 MeeGo Conference. If you are attending the 2010 conference and want to be added to our Twitter list, please add your Twitter name on this page.

You can also follow the [http://twitter.com/MeeGoConference/attendees-2010 2010 Attendees Twitter list] to get updates from all of the people attending the conference.

'''Instructions:'''
* You must include your Twitter name and a link to your Twitter account.
* Only people who are attending the 2010 MeeGo Conference should add themselves to this list.
* Add your name to the '''end''' of this list (do '''not''' add yourself in the middle or alphabetize).

== Add me to the Twitter list ==
# [http://twitter.com/geekygirldawn @geekygirldawn] - [[User:Dawnfoster|Dawn Foster]]
# [http://twitter.com/quimgil @quimgil] - Quim Gil
# [http://twitter.com/dhohndel @dhohndel] - Dirk Hohndel
# [http://twitter.com/jaffa2 @jaffa2] - Andrew Flegg
# [http://twitter.com/MeegoExperts @MeegoExperts] - Hashiq Nazir
# [http://twitter.com/nightrose @nightrose] - Lydia Pintscher
# [http://twitter.com/thp4 @thp4] - [[User:thp|Thomas Perl]]
# [http://twitter.com/texrat @texrat] - Randall Arnold
# [http://twitter.com/chippy @chippy] - [http://carrypad.com Steve 'Chippy' Paine]
# [http://twitter.com/barroca @barroca] - Leonardo 'barroca' da Mata
# [http://twitter.com/pdxideate/ @pdxideate] - Marc Anteparra-N
# [http://twitter.com/ausmusj @ausmusj] - James Ausmus
# [http://twitter.com/RevdKathy @RevdKathy] - Kathy Smith
# [http://twitter.com/h0pbeat @h0pbeat] - Arek Stopczynski
# [http://twitter.com/cmcgovern @cmcgovern] - Colin McGovern
# [http://twitter.com/jonquark @jonquark] - Jon Levell
# [http://twitter.com/aprilush @aprilush] - Laura Dragan
# [http://twitter.com/toninikkanen @toninikkanen] - Toni Nikkanen
# [http://twitter.com/andreagrandi @andreagrandi] - [http://meego.com/users/andreagrandi Andrea Grandi]
# [http://twitter.com/nearyd @nearyd] - [http://meego.com/users/dneary Dave Neary]
# [http://twitter.com/rsuplido @rsuplido] - [http://meego.com/users/reggie Reggie Suplido]
# [http://Twitter.com/muller999 @muller999]
# [http://Twitter.com/moon @moon] [http://neuronspark.com paul mooney]
# [http://twitter.com/VDVsx @VDVsx] - Valério Valério
# [http://twitter.com/generalantilles @GeneralAntilles] - [http://meego.com/users/generalanilles Ryan Abel]
# [http://twitter.com/ju_key @ju_key] - [http://meego.com/users/jukey Uwe Kaminski]
# [http://twitter.com/diegobz @diegobz] - Diego Búrigo Zacarão
# [http://twitter.com/ferwakeup @ferwakeup] - [http://meego.com/users/ferwakeup Fernando Martín]
# [http://twitter.com/andrei1089 @andrei1089] - [http://meego.com/users/andrei1089 Andrei Mirestean]
# [http://twitter.com/madeouk @madeouk] - [http://meego.com/users/arfoll Brendan Le Foll]
# [http://twitter.com/msinternet @msinternet] - [http://www.msinternet.co.uk Martin Saunders]
# [http://twitter.com/Le_PoUnT @Le_PoUnT] - [http://meego.com/users/lepount Olivier Rocat]
# [http://twitter.com/sjgadsby @sjgadsby] - [http://meego.com/users/sjgadsby Stephen Gadsby]
# [http://twitter.com/rasjani @rasjani] - [http://meego.com/users/rasjani Jani Mikkonen]
# [http://twitter.com/bergie @bergie] - Henri Bergius
# [http://twitter.com/ubkr @ubkr] - Bjarne Rosengren
# [http://twitter.com/vgrade @vgrade] - [http://meego.com/users/vgrade Martin Brook]
# [http://twitter.com/b0unc3 @b0unc3] - [http://meego.com/users/b0unc3 Daniele Maio]
# [http://twitter.com/eipi2 @eipi2] - [http://meego.com/users/eipi Sanjeev Visvanatha]
# [http://twitter.com/olea @olea] - [http://meego.com/users/olea Ismael Olea]
# [http://twitter.com/roosmaa @roosmaa] - [http://meego.com/users/roosmaa Mart Roosmaa]
# [http://twitter.com/w00teh @w00teh] - [http://meego.com/users/w00t Robin Burchell]
# [http://twitter.com/Savicq @Savicq] - [http://meego.com/users/Saviq Michał Sawicz]
# [http://twitter.com/anidel @anidel] - [http://meego.com/users/anidel Aniello Del Sorbo]
# [http://twitter.com/leinir @leinir] - [http://meego.com/users/leinir Dan Leinir Turthra Jensen] ([http://identi.ca/leinir @leinir] on identi.ca)
# [http://twitter.com/sassi67 @sassi67] - [http://meego.com/users/sassi67 Alessandro Sacilotto]
# [http://twitter.com/jsmanrique @jsmanrique] - [http://meego.com/users/jsmanrique Manrique Lopez]
# [http://twitter.com/aldnet @aldnet] - [http://meego.com/users/netoak Josep Roura]
# [http://twitter.com/markguim @markguim] - [http://meego.com/users/thenokiablog Mark Guim]
# [http://twitter.com/k0841889 @k0841889] - Adam Reviczky
# [http://twitter.com/jenlynifer @jenlynifer] - Jennifer Lyons
# [http://twitter.com/mardy @mardy] - [http://meego.com/users/mardy Alberto Mardegan]
# [http://twitter.com/karimtoubajie @karimtoubajie] - Karim Dia Toubajie
# [http://twitter.com/timsamoff @timsamoff] - Tim Samoff
# [http://twitter.com/stick84 @stick84] - [http://meego.com/users/stick Pavol Rusnak]
# [http://twitter.com/netvandal @netvandal] - [http://meego.com/users/netvandal Michele Tameni]*
# [http://twitter.com/f_jimenez @f_jimenez] - Fernando Jiménez
# [http://twitter.com/fkarlitschek @fkarlitschek] - [http://meego.com/users/frankkarlitschek Frank Karlitschek]*
# [http://twitter.com/uhef @uhef] - [http://meego.com/users/tuomjarv Tuomas Järvensivu]*
# [http://twitter.com/vivainio @vivainio] - [http://meego.com/users/vivainio Ville Vainio]*
# [http://twitter.com/jukkaeklund @jukkaeklund] - [http://meego.com/users/jukkaeklund Jukka Eklund]
# [http://twitter.com/semiot @semiot] - Victor Szilagyi
# [http://twitter.com/hhartz @hhartz] - [http://chaos.troll.no/~hhartz Henrik Hartz]
# [http://twitter.com/galouf @galouf] - Baptiste Gaultier
# [http://twitter.com/maclaver @maclaver] - Ronan Mac Laverty

==Hashtag==
The Twitter hashtag for the MeeGo Conference is '''#MeeGoConf'''

==Random Note==
* For those of you asking about the asterisk (*) that I keep moving around after people's names, it is just my way of marking the last name that I added to the Twitter list. This makes it easy for me to see where I left off the last time I added names to the list. Please do not add an asterisk after your name --[[User:Dawnfoster|Dawnfoster]] 15:46, 11 October 2010 (UTC)

MeeGo Conference 2010/Flight Information

2010-11-13T12:18:39Z

Macron: /* Thursday 18 */

== Flight Information ==

''Wouldn't it make sense to split the table for arrivals and departures and then sort each table by date and time as with the [http://wiki.maemo.org/Maemo_Summit_2009/Travel Maemo Summit 2009 travel wiki page]?''

Please move your entry from below to the new tables here. Keep the entries sorted by time and date.

===Meeting point===
Dublin airport has a meeting point highlighted on this page:

http://www.dublinairport.com/at-airport/airport-maps/arrivals.html

===Arrivals===

====Friday 12====

{| border="1"
! Time
! Name
! Place of arrival
! Means of transport
! Comments
|-
| 12:00
| [[user:Nightrose | Lydia Pintscher]]
| Airport (DUB)
| from FRA
|
|-
| 12:45
| [[user:pycage | Martin Grimme]]
| Airport (DUB)
| from MUC
|
|-
| 16:40
| [[user:InformatiQ | Ramez Hanna]]
| Airport (DUB)
| from FIN
|}

====Saturday 13====

{| border="1"
! Time
! Name
! Place of arrival
! Means of transport
! Comments
|-
| 06:50
| [[user:Epage | Ed Page]]
| Airport (DUB)
| from Atlanta
|
|-
| 08:45
| [http://meego.com/users/andreagrandi Andrea Grandi]
| Airport (DUB)
| Flight 9907 from Pisa
|
|-
| 08:55
| [[user:timsamoff | Tim Samoff]]
| Airport (DUB)
| from JFK
|
|-
| 09:00
| [[user:dawnfoster | Dawn Foster]]
| Airport (DUB)
| from ORD
|
|-
| 09:20
| [[user:texrat | Randall Arnold ]] ([http://meego.com/users/texrat texrat])
| Airport (DUB)
| United 3261 from EWR
|
|-
| 09:40
| Timo Rongas ([http://meego.com/users/ronksu ronksu])
| Airport (DUB)
| from CPH
|
|-
| 09:40
| Tatu Lahtela ([http://meego.com/users/tatlahte tatlahte])
| Airport (DUB)
| from CPH
|
|-
| 10:30
| David Greaves ([http://meego.com/users/lbt lbt])
| Airport (DUB)
| from LHR
|
|-
| 11:35
| Quim Gil
| Airport (DUB)
| Frankfurt
|
|-
| 12:05
| Dan Leinir Turthra Jensen ([http://meego.com/users/leinir leinir])
| Aurport (DUB)
| EI0235 from LGW
|
|-
| 13:05
| Michał Sawicz ([http://meego.com/users/saviq Saviq])
| Airport (DUB)
| FR1902 from KRK
|
|-
| 13:25
| Andrew Flegg ([http://meego.com/users/jaffa Jaffa])
| Airport (DUB)
| EI0267 from BHX
|
|-
| 13:50
| Wout Tankink ([http://meego.com/users/wtankink wtankink])
| Airport (DUB)
| EI0605 from AMS
|
|-
| 14:05
| Josep Roura ([http://meego.com/users/netoak netoak])
| Airport (DUB)
| FR7039 from GRO
|
|-
| 15:40
| Jon Levell ([http://meego.com/users/jonquark jonquark])
| Airport (DUB)
| BE384 from SOU
|
|-
| 15:45
| John Lehmann
| Airport (DUB)
| from LHR
|
|-
| 16:40
| Henri Bergius ([http://meego.com/users/bergie bergie])
| Airport (DUB)
| AF5014 from CDG
|
|-
| 16:40
| Susanna Huhtanen ([http://maemo.org/profile/view/ihmis-suski/ ihmis-suski])
| Airport (DUB)
| AF5014 from CDG
|
|-
| 17:20
| Attila Csipa ([http://meego.com/users/achipa achipa])
| Airport (DUB)
| LH980 from FRA
|
|-
| 17:35
| [[user:thp|thp]]
| Airport (DUB)
| from LHR
|
|-
| 18:50
| Leonardo da Mata ([http://meego.com/users/barroca barroca])
| Airport (DUB)
| JJ 7922 from LHR
|
|-
| 22:50
| Roger Wang and ~8 people from PRC
| Airport (DUB)
| LH982 from FRA
|
|-
| 14:25
| [[user:sivan|sivang]]
| Airport (DUB)
| From LHR
|
|-
| 16:40
| Sateesh Kavuri ([http://meego.com/users/kavuri kavuri])
| Airport (DUB)
| AF-1099 HKI-CDG, AF-5014 CDG-DUB
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number from airport
| ...
|}

====Sunday 14====

{| border="1"
! Time
! Name
! Place of arrival
! Means of transport
! Comments
|-
| 8:50
| Ryan Abel ([http://meego.com/users/generalantilles GeneralAntilles])
| Airport (DUB)
| US Air 722 from PHL
|
|-
| 08:50
| Stephen Gadsby ([http://meego.com/users/sjgadsby sjgadsby])
| Airport (DUB)
| US Air 722 from PHL
|
|-
| 08:50
| Felipe Crochik ([http://meego.com/users/fcrochik fcrochik])
| Airport (DUB)
| US Air 722 from PHL
|
|-
| 08:55
| Gary Birkett ([http://meego.com/users/lcuk lcuk])
| Airport (DUB)
| FR553 from MAN
|
|-
| 08:55
| Mike Jipping ([http://meego.com/users/frethop frethop])
| Airport (DUB)
| DL164 from JFK
|
|-
| 09:00
| Reggie Suplido ([http://meego.com/users/reggie reggie])
| Airport (DUB)
| EI124 from ORD (Chicago, IL)
|
|-
| 09:20
| Aniello Del Sorbo ([http://meego.com/users/anidel anidel])
| Airport (DUB)
| Flight 126 (Continental) from EWR (Newark, NJ)
|
|-
| 09:40
| Arek Stopczynski ([http://meego.com/users/hopbeat hopbeat])
| Airport (DUB)
| SK537 from CPH
|
|-
| 09:40
| Brendan Le Foll ([http://meego.com/users/arfoll arfoll])
| Airport (DUB)
| 6394 from BCN
|
|-
| 10:10
| Valério Valério ([http://meego.com/users/vdvsx VDVsx])
| Airport (DUB)
| KL3153 from AMS
|
|-
| 10:10
| Tatsiana Makava ([http://meego.com/user/12133 tanya])
| Airport (DUB)
| KL3153 from AMS
|
|-
| 10:10
| Uladzislau Vasilyeu ([http://meego.com/users/vasvlad vasvlad])
| Airport (DUB)
| KL3153 from AMS
|
|-
| 10:10
| Boudewijn Rempt([http://meego.com/users/boudewijn-rempt boudewijn])
| Airport (DUB)
| EI603 from AMS
|
|-
| 12:20
| Daniele Maio ([http://meego.com/users/b0unc3 b0unc3])
| Airport (DUB)
| FR 9427 from BGY
|
|-
| 12:20
| Michele Tameni ([http://meego.com/users/netvandal netvandal])
| Airport (DUB)
| FR 9427 from BGY
|
|-
| 12:35
| Oslo crowd (e.g. [http://meego.com/users/thiago thiago])
| Airport (DUB)
| SK4603 from OSL
|
|-
| 12:40
| Andrew Olmsted ([http://meego.com/users/fiferboy fiferboy])
| Airport (DUB)
| AC848/BMI123 from YYZ/LHR
|
|-
| 13.55
| Andrew Zhilin ([http://meego.com/users/wazd wazd])
| Airport (DUB)
| AF5006 from CDG
|
|-
| 13.55
| Graham Cobb ([http://meego.com/users/gcobb gcobb])
| Airport (DUB)
| EI159 from LHR
|
|-
| 14.10
| Carsten Munk ([http://meego.com/users/stskeeps Stskeeps])
| Airport (DUB)
| EI0363 from WAW
|
|-
| 14.15
| Kathy Smith ([http://meego.com/users/revdkathy RevdKathy])
| Airport (DUB)
| SZ585 from NQY
|
|-
| 15:00
| Julien Fourgeaud ([http://meego.com/users/jfourgeaud jfourgeaud])
| Airport (DUB)
| FR115 from LGW
|
|-
| 16:40
| timeless
| Airport (DUB)
| AF1099/AF5014
|
|-
| 16:40
| Jeremiah C. Foster ([http://meego.com/users/jeremiah jeremiah])
| Airport (DUB)
| AF 5014 from CDG
|
|-
| 16:40
| Mikael Söderberg
| Airport (DUB)
| AF 5014 from CDG
|
|-
| 17:20
| Eero af Heurlin ([http://meego.com/users/rambo rambo])
| Airport (DUB)
| LH 980
|
|-
| 17:20
| Lauri Manner
| Airport (DUB)
| LH 980
|
|-
| 17:25
| Andre Klapper ([http://meego.com/users/andre andre])
| Airport (DUB)
| EI0645 from PRG
|
|-
| 17:55
| Alan Bruce ([http://meego.com/users/qole qole])
| Airport (DUB)
| KL 3159 from AMS
|
|-
| 18:00
| Timo Härkönen ([http://meego.com/users/timoph timoph])
| Airport (DUB)
| SK2537 from CPH
|
|-
| 21:50
| Tomasz Sterna ([http://meego.com/users/smoku smoku])
| Airport (DUB)
| EI0595 from MAD
|
|-
| 21:55
| Piotr Pokora ([http://meego.com/users/piotras piotras])
| Airport (DUB)
| FR1979
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number from airport
| ...
|}

====Monday 15====

{| border="1"
! Time
! Name
! Place of arrival
! Means of transport
! Comments
|-
| 06:50
| Sanjeev Visvanatha ([http://meego.com/users/eipi eipi])
| Airport (DUB)
| Flight CO22 from EWR
|
|-
| 07:55
| Lucas Maneos ([http://meego.com/users/lm lm])
| Airport (DUB)
| Flight BD0121 from LHR
|
|-
| 08:55
| Mart Roosmaa ([http://meego.com/users/roosmaa roosmaa])
| Airport (DUB)
| Flight FR553 from MAN
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number from airport
| ...
|}

===Departures===

====Wednesday 17====

{| border="1"
! Time
! Name
! Place of departure
! Means of transport
! Comments
|-
| 06:35
| Michele Tameni ([http://meego.com/users/netvandal netvandal])
| Airport (DUB)
| FR 9426 to BGY
|
|-
| 09:00
| Sanjeev Visvanatha ([http://meego.com/users/eipi eipi])
| Airport (DUB)
| CO23 to EWR (Newark, NJ)
|
|-
| 09:00
| Aniello Del Sorbo ([http://meego.com/users/ anidel])
| Airport (DUB)
| to EWR (Newark, NJ)
|
|-
| 13:15
| [http://meego.com/users/andreagrandi Andrea Grandi]
| Airport (DUB)
| to London (BA5964), 16:45 to Pisa (BA602)
|
|-
| 13:45
| Kathy Smith ([http://meego.com/users/revdkathy RevdKathy])
| Airport (DUB)
| to NQY (Newquay, Cornwall)
|
|-
| 16:00
| Piotr Pokora ([http://meego.com/users/piotras piotras])
| Airport (DUB)
| FR1978
|
|-
| 16:00
| Tomasz Sterna ([http://meego.com/users/smoku smoku])
| Airport (DUB)
| EI0594 to MAD
|
|-
| 16:30
| [[user:thp|thp]]
| Airport (DUB)
| to VIE
|
|-
| 18:10
| Mart Roosmaa ([http://meego.com/users/roosmaa roosmaa])
| Airport (DUB)
| to MAN
|
|-
| 18:40
| Andrew Flegg ([http://meego.com/users/jaffa Jaffa])
| Airport (DUB)
| EI0276 to BHX
|
|-
| 18:45
| Eero af Heurlin ([http://meego.com/users/rambo rambo])
| Airport (DUB)
| SK 2538
|
|-
| 18:45
| Tatu Lahtela ([http://meego.com/users/tatlahte tatlahte])
| Airport (DUB)
| SK 2538
|
|-
| 18:45
| Lauri Manner
| Airport (DUB)
| SK 2538
|
|-
| 20:00
| Adam Reviczky ([[user:Reviczky|reviczky]])
| Airport (DUB)
| FR118 to LGW
|
|-
| 21:05
| Lucas Maneos ([http://meego.com/users/lm lm])
| Airport (DUB)
| BD0132 to LHR
|
|-
| 21:05
| Graham Cobb ([http://meego.com/users/gcobb gcobb])
| Airport (DUB)
| BD0132 to LHR
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number from airport
| ...
|}

====Thursday 18====

{| border="1"
! Time
! Name
! Place of departure
! Means of transport
! Comments
|-
| 06:00
| Valério Valério ([http://meego.com/users/vdvsx VDVsx])
| Airport (DUB)
| KL3152 to AMS
|
|-
| 06:35
| Daniele Maio ([http://meego.com/users/b0unc3 b0unc3])
| Airport (DUB)
| FR 9426 to BGY
|
|-
| 06:55
| Attila Csipa ([http://meego.com/users/achipa achipa])
| Airport (DUB)
| to FRA
|
|-
| 06:55
| Quim Gil
| Airport (DUB)
| to FRA
|
|-
| 07:00
| Lydia Pintscher ([http://meego.com/users/Nightrose Nightrose])
| Airport (DUB)
| to FRA
|
|-
| 07:20
| Carsten Munk ([http://meego.com/users/stskeeps Stskeeps])
| Airport (DUB)
| EI0362 to WAW
|
|-
| 09:10
| Henri Bergius ([http://meego.com/users/bergie bergie])
| Airport (DUB)
| AF5001 to CDG
|
|-
| 09:10
| Susanna Huhtanen ([http://maemo.org/profile/view/ihmis-suski/ ihmis-suski])
| Airport (DUB)
| AF5001 to CDG
|
|-
| 09:45
| Wout Takink ([http://meego.com/users/wtankink wtankink])
| Airport (DUB)
| EI0604 to AMS
|
|-
| 10:20
| Josep Roura ([http://meego.com/users/netoak NetOak])
| Airport (DUB)
| FR7038 to GRO
|
|-
| 10:45
| [http://meego.com/users/dawnfoster Dawn Foster]
| Airport (DUB)
| to JFK
|
|-
| 10:45
| Mike Jipping [http://meego.com/users/frethop frethop]
| Airport (DUB)
| DL165 to JFK
|
|-
| 11:05
| Reggie Suplido ([http://meego.com/users/reggie reggie])
| Airport (DUB)
| SK538 to CPH
|
|-
| 11:05
| Ronan Mac Laverty ([http://meego.com/users/macron macron])
| Airport (DUB)
| SK538 to CPH
|
|-
| 11:05
| Ryan Abel ([http://meego.com/users/generalantilles GeneralAntilles])
| Airport (DUB)
| US Air 723 to PHL
|
|-
| 11:05
| Stephen Gadsby ([http://meego.com/users/sjgadsby sjgadsby])
| Airport (DUB)
| US Air 723 to PHL
|
|-
| 11:40
| Andre Klapper ([http://meego.com/users/andre andre])
| Airport (DUB)
| IE0644 to PRG
|
|-
| 11:40
| Julien Fourgeaud ([http://meego.com/users/jfourgeaud jfourgeaud])
| Airport (DUB)
| FR114 to LGW
|
|-
| 11:55
| Andrew Zhilin ([http://meego.com/users/wazd wazd])
| Airport (DUB)
| AF5005 to CDG
|
|-
| 12:00
| Timo Härkönen ([http://meego.com/users/timoph timoph])
| Airport (DUB)
| SK536 to ARN
|
|-
| 12:10
| Thiago Macieira ([http://meego.com/users/thiago thiago])
| Airport (DUB)
| SK4604 to OSL
|
|-
| 12:20
| Roger Wang and ~8 people from PRC
| Airport (DUB)
| LH979 to FRA
|
|-
| 13:00
| Randall Arnold (texrat)
| Airport (DUB)
| United 4925 to ORD
|
|-
| 13:55
| Brendan Le Foll ([http://meego.com/users/arfoll arfoll])
| Airport (DUB)
| 6395
|
|-
| 14:50
| timeless
| Airport (DUB)
| AF5009/AF1798
|
|-
| 14:50
| [[user:jeremiah|Jeremiah Foster]]
| Airport (DUB)
| AF 5009 CDG -> GOT
|
|-
| 14:50
| Mikael Söderberg
| Airport (DUB)
| AF 5009 CDG -> GOT
|
|-
| 15:00
| Andrew Olmsted ([http://meego.com/users/fiferboy fiferboy])
| Airport (DUB)
| EI3296 to CWL
| Staying extra days after conference
|-
| 16:00
| Martin Grimme ([http://meego.com/users/pycage pycage])
| Airport (DUB)
| EI356 to MUC
|
|-
| 17:10
| Boudewijn Rempt ([http://meego.com/users/boudewijn-rempt Boudewijn])
| Airport (DUB)
| EI610 to AMS
|
|-
| 18:10
| Gary Birkett ([http://meego.com/users/lcuk lcuk])
| Airport (DUB)
| FR556 to MAN
|
|-
| 18:45
| Arek Stopczynski ([http://meego.com/users/hopbeat hopbeat])
| Airport (DUB)
| SK2538 to CPH
|
|-
| 19:35
| Tatsiana Makava ([http://meego.com/user/12133 tanya])
| Airport (DUB)
| AF5013 to CDG
|
|-
| 19:35
| Uladzislau Vasilyeu ([http://meego.com/users/vasvlad vasvlad])
| Airport (DUB)
| AF5013 to CDG
|
|-
| 20:30
| Dan Leinir Turthra Jensen ([http://meego.com/users/leinir leinir])
| Airport (DUB)
| EI0248 to LGW
|
|-
| 00:00
| [[user:username|Firstname Lastname]]
| Airport (DUB)
| Flight number to airport
| ...
|}

====Friday 19 ====

{| border="1"
! Time
! Name
! Place of departure
! Means of transport
! Comments
|-
| 08:40
| [[user:Epage | Ed Page]]
| Airport (DUB)
| to Atlanta
|
|-
| 13:15
| David Greaves ([http://meego.com/users/lbt lbt])
| Airport (DUB)
| to LHR
|
|-
|}

====Saturday 20====

{| border="1"
! Time
! Name
! Place of departure
! Means of transport
! Comments
|-
| 09:05
| [http://meego.com/users/jonquark Jon Levell]
| Airport (DUB)
| To SOU
|
|-
| 10:45
| [[user:timsamoff | Tim Samoff]]
| Airport (DUB)
| to JFK
| My wife arrives on the 17th and we're staying through Saturday.
|}

MeeGo Conference 2010/Volunteering

2010-11-09T11:57:48Z

Macron:

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!
; Breakout Room Table
: There is a room available for break-out sessions and BOFs, and we would like to ensure that people can schedule times for its use, to avoid different groups getting in each other's way. There will need to be people "manning" the schedule, and ensuring that when people arrive for a reserved session that they get priority.
; Hacking Lounge
: Some hackroom sessions may need helpers (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 Needs 2 all the time
! Session Tech Support
! Speaker Assistants
! Live Stream IRC Moderators
! Breakout Room Table
! Hacking Lounge
! 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 [[User:Chippy |Chippy]] Quim Gil [[User:thomas |thomas]] [[User:macron | Ronan Mac Laverty]]
|
|
|
|
|
|
|
|-
| Nov 14, 15:00-17:00
| Needed: 5 Andrew Flegg Aniello Del Sorbo [[User:timsamoff | timsamoff]]
|
|
|
|
|
|
|
|-
| Nov 14, 17:00-19:00
|
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Monday Nov 15
|-
| Nov 15, 8:00-10:00
|
| X [[User:Jsmanrique| Manrique López]]
| X
| Needed: 1 Quim Gil
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 10:00-12:00
|
| X
| X
| Needed: 1 [[User:Msinternet | Martin Saunders]]
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 12:00-14:00
|
| X
| X
| Needed: 5 [[User:mdamt | mdamt]] (preferably President then 1872 room) 
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 14:00-16:00
|
| X
| X
| Needed: 5 [[User:Vdvsx | Valerio Valerio]]
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 16:00-18:00
|
| [[User:timsamoff | timsamoff]]
| X
| Needed: 5
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|- style="background:LightBlue"
|colspan="9"| Tuesday Nov 16
|-
| Nov 16, 8:00-10:00
|
| X [[User:Jsmanrique | Manrique Lopez]]
| X
| Needed: 5
| X
| X
| X
|
|-
| Nov 16, 10:00-12:00
|
| X
| X
| Needed: 5 [[User:Vdvsx | Valerio Valerio]]
| X
| X
| X
|
|-
| Nov 16, 12:00-14:00
|
| X
| X
| Needed: 5 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 16, 14:00-16:00
|
| X
| X
| Needed: 5 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 16, 16:00-18:00
|
| [[User:timsamoff | timsamoff]]
| X
| Needed: 5
| X
| X
| X
|
|-
| Nov 16, 18:00-19:00
|
| X
|
|
| X
| X
| X
|
|- style="background:LightBlue"
|colspan="9"| Wednesday Nov 17
|-
| Nov 17, 8:00-10:00
|
| X
| X
| Needed: 2 [[User:Dneary | Dave Neary]]
| X
| X
| X
|
|-
| Nov 17, 10:00-12:00
|
| X
| X [[User:Saviq | Michał Sawicz]]
| Needed: 2 [[User: Chippy | Chippy]]
| X
| X
| X
|
|-
| Nov 17, 12:00-14:00
|
| X
| X
| Needed: 2 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 17, 14:00-16:00
| All hands on deck [[User:Chippy |Chippy]] Quim Gil [[User:macron | Ronan Mac Laverty]]
| X
| X
| X
| X
| X
| X
|
|}

MeeGo Conference 2010/Volunteering

2010-11-09T11:53:34Z

Macron:

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!
; Breakout Room Table
: There is a room available for break-out sessions and BOFs, and we would like to ensure that people can schedule times for its use, to avoid different groups getting in each other's way. There will need to be people "manning" the schedule, and ensuring that when people arrive for a reserved session that they get priority.
; Hacking Lounge
: Some hackroom sessions may need helpers (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 Needs 2 all the time
! Session Tech Support
! Speaker Assistants
! Live Stream IRC Moderators
! Breakout Room Table
! Hacking Lounge
! Other
|- style="background:LightBlue"
|colspan="9"| Saturday Nov 13
|-
| Nov 13, 13:00-15:00
|
|
|
|
|
|
|
|
|-
| 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 [[User:Chippy |Chippy]] Quim Gil [[User:thomas |thomas]] [[User:macron | Ronan Mac Laverty]]
|
|
|
|
|
|
|
|-
| Nov 14, 15:00-17:00
| Needed: 5 Andrew Flegg Aniello Del Sorbo [[User:timsamoff | timsamoff]]
|
|
|
|
|
|
|
|-
| Nov 14, 17:00-19:00
|
|
|
|
|
|
|
|
|- style="background:LightBlue"
|colspan="9"| Monday Nov 15
|-
| Nov 15, 8:00-10:00
|
| X [[User:Jsmanrique| Manrique López]]
| X
| Needed: 1 Quim Gil
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 10:00-12:00
|
| X
| X
| Needed: 1 [[User:Msinternet | Martin Saunders]]
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 12:00-14:00
|
| X
| X
| Needed: 5 [[User:mdamt | mdamt]] (preferably President then 1872 room) 
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 14:00-16:00
|
| X
| X
| Needed: 5 [[User:Vdvsx | Valerio Valerio]]
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|-
| Nov 15, 16:00-18:00
|
| [[User:timsamoff | timsamoff]]
| X
| Needed: 5
| X
| X
| [[User:Leinir | Dan Leinir ]]
|
|- style="background:LightBlue"
|colspan="9"| Tuesday Nov 16
|-
| Nov 16, 8:00-10:00
|
| X [[User:Jsmanrique | Manrique Lopez]]
| X
| Needed: 5
| X
| X
| X
|
|-
| Nov 16, 10:00-12:00
|
| X
| X
| Needed: 5 [[User:Vdvsx | Valerio Valerio]]
| X
| X
| X
|
|-
| Nov 16, 12:00-14:00
|
| X
| X
| Needed: 5 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 16, 14:00-16:00
|
| X
| X
| Needed: 5 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 16, 16:00-18:00
|
| [[User:timsamoff | timsamoff]]
| X
| Needed: 5
| X
| X
| X
|
|-
| Nov 16, 18:00-19:00
|
| X
|
|
| X
| X
| X
|
|- style="background:LightBlue"
|colspan="9"| Wednesday Nov 17
|-
| Nov 17, 8:00-10:00
|
| X
| X
| Needed: 2 [[User:Dneary | Dave Neary]]
| X
| X
| X
|
|-
| Nov 17, 10:00-12:00
|
| X
| X [[User:Saviq | Michał Sawicz]]
| Needed: 2 [[User: Chippy | Chippy]]
| X
| X
| X
|
|-
| Nov 17, 12:00-14:00
|
| X
| X
| Needed: 2 [[User:Chippy |Chippy]]
| X
| X
| X
|
|-
| Nov 17, 14:00-16:00
| All hands on deck [[User:Chippy |Chippy]] Quim Gil [[User:macron | Ronan Mac Laverty]]
| X
| X
| X
| X
| X
| X
|
|}

Application developer site/Design overview

2010-11-08T08:41:39Z

Macron: /* Overall goals */

= Developer.MeeGo.Com Design Overview =

During the first review of the developer.meego.com site there were several comments about the design. This page gives some background on the site design, or why it looks like it does.

== Overall goals ==

One of the observations made by an educational consultant regarding the developer.android.com site was that it lacks signposts, to guide a user through the site. So one goal of developer.meego.com was to provide a user with contextual information to help them orientate within the site. A crucial aspect of this is to reduce the number of links presented to a user at one time (the classic usability rule of 7+-2 forms some guidance here) and to provide text to explain the relevancy of the link. The header images+text in each of sections explains what the section is for. Another powerful for helping beginners is to emphasize the key links for a begineer (the accordion links in the home page does this).

A second goal was to allow an experience user to access the information they want quickly and easily. This could require placing a large number of links on the home page, or (as implemented) using a 2 level navigation, so that an experienced user can navigate to the API references with one click. One crucial aspect for developers is the API reference section, which (although currently missing a search function) has a nice floating menu bar for consistent navigation of the documentation.

A third goal has been to make the site "MeeGo" branded. This dictates the colors, fonts, and logos used inside the site. The result is a site that looks similar to MeeGo.Com, but has the additional features (mentioned above). Because the site úses similar colors to MeeGo.Com and has a fixed width layout it looks similar, just as bugs.meego.com looks similar to the MeeGo.Com site.

== Changes since the first TSG review ==

The biggest change has been to re-orient the relationship of the site to other sites in the MeeGo Application Development ecosystem. The major functionality change has been to allow external guides, and other content to be linked easily from developer.meego.com.

This change allows the site to be configured as a full-fledged standalone site, or as a MeeGo application developer dashboard, where other content on the web is selected and linked.

Application developer site/Design overview

2010-11-08T08:40:00Z

Macron: Created page with "= Developer.MeeGo.Com Design Overview = During the first review of the developer.meego.com site there were several comments about the design. This page gives some background on…"

= Developer.MeeGo.Com Design Overview =

During the first review of the developer.meego.com site there were several comments about the design. This page gives some background on the site design, or why it looks like it does.

== Overall goals ==

One of the observations made by an educational consultant regarding the developer.android.com site was that it lacks signposts, to guide a user through the site. So one goal of developer.meego.com was to provide a user with contextual information to help them orientate within the site. A crucial aspect of this is to reduce the number of links presented to a user at one time (the classic usability rule of 7+-2 forms some guidance here). Another powerful to tool is to mphasize the key links for a begineer (the accordion links in the home page does this).

A second goal was to allow an experience user to access the information they want quickly and easily. This could require placing a large number of links on the home page, or (as implemented) using a 2 level navigation, so that an experienced user can navigate to the API references with one click. One crucial aspect for developers is the API reference section, which (although currently missing a search function) has a nice floating menu bar for consistent navigation of the documentation.

A third goal has been to make the site "MeeGo" branded. This dictates the colors, fonts, and logos used inside the site. The result is a site that looks similar to MeeGo.Com, but has the additional features (mentioned above). Because the site úses similar colors to MeeGo.Com and has a fixed width layout it looks similar, just as bugs.meego.com looks similar to the MeeGo.Com site.

== Changes since the first TSG review ==

The biggest change has been to re-orient the relationship of the site to other sites in the MeeGo Application Development ecosystem. The major functionality change has been to allow external guides, and other content to be linked easily from developer.meego.com.

This change allows the site to be configured as a full-fledged standalone site, or as a MeeGo application developer dashboard, where other content on the web is selected and linked.

Application developer site/Beta Process

2010-11-08T08:17:56Z

Macron: Created page with "= Developer.MeeGo.Com Beta process = == Introduction == developer.meego.com will be released first as a beta site before public release. The goal of this beta is to get feedba…"

SDK/Docs/1.1/MeeGo overview

2010-11-03T16:02:53Z

Macron: /* SDK alternatives */

= MeeGo application development overview=

The MeeGo 1.1 release provides a toolset for application developers, supporting cross-platform development. These tools make it easy to enter the MeeGo application ecosystem, and are built, like MeeGo, on proven open-source technologies.

The big news for application developers is that '''Qt Quick''' is now part of the MeeGo release. This new technology allows rapid application UI development based on QML and JavaScript. It is also easily extendable with C++ objects, allowing a clear separation between UI logic (QML/JavaScript), and backend logic (Qt/C++). Qt Quick is ideal for MeeGo application development because it is highly flexible, allowing a developer to modify a UI easily so that it delivers an optimal user experience on all MeeGo devices. There are many Qt Quick examples and tutorials available already. For example, see [http://developer.qt.nokia.com/wiki/Qt_Quick_Tutorial the official Qt Quick tutorial].

MeeGo SDK, based on Qt Creator, allows developers to create native applications for a range of devices (such as the N900, Aava, and Netbook devices), using both the Qt/C++ and Qt Quick frameworks. The SDK supports using Qt 4.7 and MeeGo Touch Framework and is packaged with Qt Quick development libraries. It also supports multiple toolchains, allowing compilation for both the x86 and ARM processor architectures. This means the same code base can be used for N900, Aava, and Netbook devices.

MeeGo 1.1 also supports the Web Runtime (WRT) environment, which means developers can use web-based technologies (HTML/CSS/JavaScript) to create applications for MeeGo. It is also possible to embed WRT UIs into C++ applications using Qt wrapper objects such as QWebView from the QtWebKit module.

With a new set of tools, the availability of technologies such as WRT and Qt Quick, and accompanying developer documentation, MeeGo application development has become easier and more accessible.

The following sections outline the software development kits available for this MeeGo release.

= Development alternatives =

The following sections present options for starting application development. Note that it is also possible to combine the technologies presented in this section in hybrid applications, with parts implemented in C++ and others in JavaScript.

The key choice is between '''MeeGo SDK''' and web runtime development. MeeGo SDK supports Qt Quick development, making it the tool of choice for most application development.

==MeeGo native development==

MeeGo SDK is used to develop native applications with cross-platform compatibility.

The following table describes MeeGo SDK:

{| border="1" cellpadding="5" cellspacing="0"
|+
|-
! style="background:#efefef; width:120px;" | Name
! style="background:#efefef; width:120px;" | Technologies
! style="background:#efefef; width:170px;" | Intended users
! style="background:#efefef; width:400px;" | Where to get started
|-
|'''MeeGo SDK'''
|C/C++, Qt Quick (Windows, Linux)
|Developers who want to create native applications and developers who want their application to be compatible with multiple mobile platforms, and developers who want to use Qt Quick.
|
* Get MeeGo SDK for Linux [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux| <here>]].
* For more information on developing with MeeGo SDK, read [[SDK/Docs/1.1#Using_the_SDK:__Qt.2C_WRT.2C_Hello_World.2C_Debugging| this]].
|}

MeeGo SDK includes the following tools and components:
* '''Qt Creator''', the integrated development environment
** '''MADDE''' for easy cross-platform development

==Web runtime development==

[[SDK/Docs/1.1/Web SDK with WRT| You can find the instructions for getting the started with web runtime development and an introductory example here]]

= MeeGo 1.1 SDK web sites for application developers=

* [http://wiki.meego.com/SDK/Docs/1.1 MeeGo 1.1 developer documentation]
* [http://apidocs.meego.com/1.1-preview/html/index.html API references] //replace with direct links to MeeGo API and Platform API//
* [http://meego.com/developers MeeGo development page at meego.com]
* [http://www.meego.gitorious.org MeeGo git repository] contains the MeeGo platform source code.
* [http://bugs.meego.com Central location for bug reporting] which is also used as a simple task reporting tool.
* [http://forum.meego.com MeeGo Forum] enables users, developers and anybody interested in MeeGo to discuss about the MeeGo project and related issues.

[[Category: MeeGo 1.1]]

SDK/Docs/1.1/MeeGo overview

2010-11-03T15:59:24Z

Macron: /* MeeGo SDK overview */

= MeeGo application development overview=

The MeeGo 1.1 release provides a toolset for application developers, supporting cross-platform development. These tools make it easy to enter the MeeGo application ecosystem, and are built, like MeeGo, on proven open-source technologies.

The big news for application developers is that '''Qt Quick''' is now part of the MeeGo release. This new technology allows rapid application UI development based on QML and JavaScript. It is also easily extendable with C++ objects, allowing a clear separation between UI logic (QML/JavaScript), and backend logic (Qt/C++). Qt Quick is ideal for MeeGo application development because it is highly flexible, allowing a developer to modify a UI easily so that it delivers an optimal user experience on all MeeGo devices. There are many Qt Quick examples and tutorials available already. For example, see [http://developer.qt.nokia.com/wiki/Qt_Quick_Tutorial the official Qt Quick tutorial].

MeeGo SDK, based on Qt Creator, allows developers to create native applications for a range of devices (such as the N900, Aava, and Netbook devices), using both the Qt/C++ and Qt Quick frameworks. The SDK supports using Qt 4.7 and MeeGo Touch Framework and is packaged with Qt Quick development libraries. It also supports multiple toolchains, allowing compilation for both the x86 and ARM processor architectures. This means the same code base can be used for N900, Aava, and Netbook devices.

MeeGo 1.1 also supports the Web Runtime (WRT) environment, which means developers can use web-based technologies (HTML/CSS/JavaScript) to create applications for MeeGo. It is also possible to embed WRT UIs into C++ applications using Qt wrapper objects such as QWebView from the QtWebKit module.

With a new set of tools, the availability of technologies such as WRT and Qt Quick, and accompanying developer documentation, MeeGo application development has become easier and more accessible.

The following sections outline the software development kits available for this MeeGo release.

= SDK alternatives =

The following sections present options for starting application development. Note that it is also possible to combine the technologies presented in this section in hybrid applications, with parts implemented in C++ and others in JavaScript.

The key choice is between '''MeeGo SDK''' and '''Web SDK'''. Both provide an integrated development environment (IDE) that can be used to contribute to MeeGo. MeeGo SDK supports Qt Quick development, making it the tool of choice for most application development.

==MeeGo native development==

MeeGo SDK is used to develop native applications with cross-platform compatibility.

The following table describes MeeGo SDK:

{| border="1" cellpadding="5" cellspacing="0"
|+
|-
! style="background:#efefef; width:120px;" | Name
! style="background:#efefef; width:120px;" | Technologies
! style="background:#efefef; width:170px;" | Intended users
! style="background:#efefef; width:400px;" | Where to get started
|-
|'''MeeGo SDK'''
|C/C++, Qt Quick (Windows, Linux)
|Developers who want to create native applications and developers who want their application to be compatible with multiple mobile platforms, and developers who want to use Qt Quick.
|
* Get MeeGo SDK for Linux [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux| <here>]].
* For more information on developing with MeeGo SDK, read [[SDK/Docs/1.1#Using_the_SDK:__Qt.2C_WRT.2C_Hello_World.2C_Debugging| this]].
|}

MeeGo SDK includes the following tools and components:
* '''Qt Creator''', the integrated development environment
** '''MADDE''' for easy cross-platform development

==Web runtime development==

[[SDK/Docs/1.1/Web SDK with WRT| You can find the instructions for getting the started with web runtime development and an introductory example here]]

= MeeGo 1.1 SDK web sites for application developers=

* [http://wiki.meego.com/SDK/Docs/1.1 MeeGo 1.1 developer documentation]
* [http://apidocs.meego.com/1.1-preview/html/index.html API references] //replace with direct links to MeeGo API and Platform API//
* [http://meego.com/developers MeeGo development page at meego.com]
* [http://www.meego.gitorious.org MeeGo git repository] contains the MeeGo platform source code.
* [http://bugs.meego.com Central location for bug reporting] which is also used as a simple task reporting tool.
* [http://forum.meego.com MeeGo Forum] enables users, developers and anybody interested in MeeGo to discuss about the MeeGo project and related issues.

[[Category: MeeGo 1.1]]

SDK/Docs/1.1/MeeGo overview

2010-11-03T15:58:35Z

Macron: /* Web SDK overview */

= MeeGo application development overview=

The MeeGo 1.1 release provides a toolset for application developers, supporting cross-platform development. These tools make it easy to enter the MeeGo application ecosystem, and are built, like MeeGo, on proven open-source technologies.

The big news for application developers is that '''Qt Quick''' is now part of the MeeGo release. This new technology allows rapid application UI development based on QML and JavaScript. It is also easily extendable with C++ objects, allowing a clear separation between UI logic (QML/JavaScript), and backend logic (Qt/C++). Qt Quick is ideal for MeeGo application development because it is highly flexible, allowing a developer to modify a UI easily so that it delivers an optimal user experience on all MeeGo devices. There are many Qt Quick examples and tutorials available already. For example, see [http://developer.qt.nokia.com/wiki/Qt_Quick_Tutorial the official Qt Quick tutorial].

MeeGo SDK, based on Qt Creator, allows developers to create native applications for a range of devices (such as the N900, Aava, and Netbook devices), using both the Qt/C++ and Qt Quick frameworks. The SDK supports using Qt 4.7 and MeeGo Touch Framework and is packaged with Qt Quick development libraries. It also supports multiple toolchains, allowing compilation for both the x86 and ARM processor architectures. This means the same code base can be used for N900, Aava, and Netbook devices.

MeeGo 1.1 also supports the Web Runtime (WRT) environment, which means developers can use web-based technologies (HTML/CSS/JavaScript) to create applications for MeeGo. It is also possible to embed WRT UIs into C++ applications using Qt wrapper objects such as QWebView from the QtWebKit module.

With a new set of tools, the availability of technologies such as WRT and Qt Quick, and accompanying developer documentation, MeeGo application development has become easier and more accessible.

The following sections outline the software development kits available for this MeeGo release.

= SDK alternatives =

The following sections present options for starting application development. Note that it is also possible to combine the technologies presented in this section in hybrid applications, with parts implemented in C++ and others in JavaScript.

The key choice is between '''MeeGo SDK''' and '''Web SDK'''. Both provide an integrated development environment (IDE) that can be used to contribute to MeeGo. MeeGo SDK supports Qt Quick development, making it the tool of choice for most application development.

==MeeGo SDK overview==

MeeGo SDK is used to develop native applications with cross-platform compatibility.

The following table describes MeeGo SDK:

{| border="1" cellpadding="5" cellspacing="0"
|+
|-
! style="background:#efefef; width:120px;" | Name
! style="background:#efefef; width:120px;" | Technologies
! style="background:#efefef; width:170px;" | Intended users
! style="background:#efefef; width:400px;" | Where to get started
|-
|'''MeeGo SDK'''
|C/C++, Qt Quick (Windows, Linux)
|Developers who want to create native applications and developers who want their application to be compatible with multiple mobile platforms, and developers who want to use Qt Quick.
|
* Get MeeGo SDK for Linux [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux| <here>]].
* For more information on developing with MeeGo SDK, read [[SDK/Docs/1.1#Using_the_SDK:__Qt.2C_WRT.2C_Hello_World.2C_Debugging| this]].
|}

MeeGo SDK includes the following tools and components:
* '''Qt Creator''', the integrated development environment
** '''MADDE''' for easy cross-platform development

==Web runtime development==

[[SDK/Docs/1.1/Web SDK with WRT| You can find the instructions for getting the started with web runtime development and an introductory example here]]

= MeeGo 1.1 SDK web sites for application developers=

* [http://wiki.meego.com/SDK/Docs/1.1 MeeGo 1.1 developer documentation]
* [http://apidocs.meego.com/1.1-preview/html/index.html API references] //replace with direct links to MeeGo API and Platform API//
* [http://meego.com/developers MeeGo development page at meego.com]
* [http://www.meego.gitorious.org MeeGo git repository] contains the MeeGo platform source code.
* [http://bugs.meego.com Central location for bug reporting] which is also used as a simple task reporting tool.
* [http://forum.meego.com MeeGo Forum] enables users, developers and anybody interested in MeeGo to discuss about the MeeGo project and related issues.

[[Category: MeeGo 1.1]]

SDK/Docs/1.1/MeeGo overview

2010-11-03T15:56:54Z

Macron: /* MeeGo SDK overview */

= MeeGo application development overview=

The MeeGo 1.1 release provides a toolset for application developers, supporting cross-platform development. These tools make it easy to enter the MeeGo application ecosystem, and are built, like MeeGo, on proven open-source technologies.

The big news for application developers is that '''Qt Quick''' is now part of the MeeGo release. This new technology allows rapid application UI development based on QML and JavaScript. It is also easily extendable with C++ objects, allowing a clear separation between UI logic (QML/JavaScript), and backend logic (Qt/C++). Qt Quick is ideal for MeeGo application development because it is highly flexible, allowing a developer to modify a UI easily so that it delivers an optimal user experience on all MeeGo devices. There are many Qt Quick examples and tutorials available already. For example, see [http://developer.qt.nokia.com/wiki/Qt_Quick_Tutorial the official Qt Quick tutorial].

MeeGo SDK, based on Qt Creator, allows developers to create native applications for a range of devices (such as the N900, Aava, and Netbook devices), using both the Qt/C++ and Qt Quick frameworks. The SDK supports using Qt 4.7 and MeeGo Touch Framework and is packaged with Qt Quick development libraries. It also supports multiple toolchains, allowing compilation for both the x86 and ARM processor architectures. This means the same code base can be used for N900, Aava, and Netbook devices.

MeeGo 1.1 also supports the Web Runtime (WRT) environment, which means developers can use web-based technologies (HTML/CSS/JavaScript) to create applications for MeeGo. It is also possible to embed WRT UIs into C++ applications using Qt wrapper objects such as QWebView from the QtWebKit module.

With a new set of tools, the availability of technologies such as WRT and Qt Quick, and accompanying developer documentation, MeeGo application development has become easier and more accessible.

The following sections outline the software development kits available for this MeeGo release.

= SDK alternatives =

The following sections present options for starting application development. Note that it is also possible to combine the technologies presented in this section in hybrid applications, with parts implemented in C++ and others in JavaScript.

The key choice is between '''MeeGo SDK''' and '''Web SDK'''. Both provide an integrated development environment (IDE) that can be used to contribute to MeeGo. MeeGo SDK supports Qt Quick development, making it the tool of choice for most application development.

==MeeGo SDK overview==

MeeGo SDK is used to develop native applications with cross-platform compatibility.

The following table describes MeeGo SDK:

{| border="1" cellpadding="5" cellspacing="0"
|+
|-
! style="background:#efefef; width:120px;" | Name
! style="background:#efefef; width:120px;" | Technologies
! style="background:#efefef; width:170px;" | Intended users
! style="background:#efefef; width:400px;" | Where to get started
|-
|'''MeeGo SDK'''
|C/C++, Qt Quick (Windows, Linux)
|Developers who want to create native applications and developers who want their application to be compatible with multiple mobile platforms, and developers who want to use Qt Quick.
|
* Get MeeGo SDK for Linux [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux| <here>]].
* For more information on developing with MeeGo SDK, read [[SDK/Docs/1.1#Using_the_SDK:__Qt.2C_WRT.2C_Hello_World.2C_Debugging| this]].
|}

MeeGo SDK includes the following tools and components:
* '''Qt Creator''', the integrated development environment
** '''MADDE''' for easy cross-platform development

==Web SDK overview==

Web SDK is used to develop web-based applications. Windows developers of web-based content can use Web SDK. Later, the same will become possible for Linux developers.

The following table describes Web SDK:

{| border="1" cellpadding="5" cellspacing="0"
|+
|-
! style="background:#efefef; width:120px;" | Name
! style="background:#efefef; width:120px;" | Technologies
! style="background:#efefef; width:170px;" | Intended users
! style="background:#efefef; width:400px;" | Where to get started
|-
|'''Web SDK'''
|JavaScript, HTML, CSS
(Windows)
|Developers who want to create web-centric applications and combine web services with device data and are interested in HTML/JavaScript development.
| [[SDK/Docs/1.1/Web SDK with WRT| You can find the instructions for getting the Web SDK and an introductory example here]]
|}

= MeeGo 1.1 SDK web sites for application developers=

* [http://wiki.meego.com/SDK/Docs/1.1 MeeGo 1.1 developer documentation]
* [http://apidocs.meego.com/1.1-preview/html/index.html API references] //replace with direct links to MeeGo API and Platform API//
* [http://meego.com/developers MeeGo development page at meego.com]
* [http://www.meego.gitorious.org MeeGo git repository] contains the MeeGo platform source code.
* [http://bugs.meego.com Central location for bug reporting] which is also used as a simple task reporting tool.
* [http://forum.meego.com MeeGo Forum] enables users, developers and anybody interested in MeeGo to discuss about the MeeGo project and related issues.

[[Category: MeeGo 1.1]]

SDK/Docs/1.1/MeeGo developer story

2010-11-03T15:56:04Z

Macron: /* Debugging */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
* the MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
* the Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

//We take the image from www.meego.com/developers/Developer Story.//

==Developing==

With the MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device.

With the Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device, since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

The MeeGo SDK generates packages for deploying software to MeeGo devices. To run an application on a MeeGo device, package the application, send it to a device, and install the application.

With the Web SDK, package the WRT applications for MeeGo according to the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==

To distribute MeeGo applications you can use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction) or submit the application to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-03T15:55:40Z

Macron: /* Developing */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
* the MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
* the Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

//We take the image from www.meego.com/developers/Developer Story.//

==Developing==

With the MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device.

With the Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a MeeGo device simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

The MeeGo SDK generates packages for deploying software to MeeGo devices. To run an application on a MeeGo device, package the application, send it to a device, and install the application.

With the Web SDK, package the WRT applications for MeeGo according to the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==

To distribute MeeGo applications you can use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction) or submit the application to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:37:07Z

Macron: /* Debugging */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
* the MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
* the Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With the MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With the Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a MeeGo device simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

The MeeGo SDK generates packages for deploying software to MeeGo devices. To run an application on a MeeGo device, package the application, send it to a device, and install the application.

With the Web SDK, package the WRT applications for MeeGo according to the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==

To distribute MeeGo applications you can use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction) or submit the application to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:33:59Z

Macron: /* Update to developer story on www.meego.com/developers */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
* the MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
* the Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With the MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With the Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a Qt simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

The MeeGo SDK generates packages for deploying software to MeeGo devices. To run an application on a MeeGo device, package the application, send it to a device, and install the application.

With the Web SDK, package the WRT applications for MeeGo according to the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==

To distribute MeeGo applications you can use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction) or submit the application to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:33:34Z

Macron: /* Developing */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
• MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
• Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With the MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With the Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a Qt simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

The MeeGo SDK generates packages for deploying software to MeeGo devices. To run an application on a MeeGo device, package the application, send it to a device, and install the application.

With the Web SDK, package the WRT applications for MeeGo according to the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==

To distribute MeeGo applications you can use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction) or submit the application to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:33:18Z

Macron: /* Packaging */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
• MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
• Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a Qt simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

The MeeGo SDK generates packages for deploying software to MeeGo devices. To run an application on a MeeGo device, package the application, send it to a device, and install the application.

With the Web SDK, package the WRT applications for MeeGo according to the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==

To distribute MeeGo applications you can use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction) or submit the application to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:32:07Z

Macron: /* Packaging */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
• MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
• Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a Qt simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. To run an application on a MeeGo device, package the application, send it to a device, and install the application.

With Web SDK, package the WRT applications for MeeGo according to the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==

To distribute MeeGo applications you can use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction) or submit the application to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:31:45Z

Macron: /* Distributing */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
• MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
• Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a Qt simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

With Web SDK, package the WRT applications for MeeGo according to the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==

To distribute MeeGo applications you can use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction) or submit the application to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:31:10Z

Macron: /* Packaging */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
• MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
• Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a Qt simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

With Web SDK, package the WRT applications for MeeGo according to the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction); another approach is to submit the package to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:29:44Z

Macron: /* Debugging */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
• MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
• Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a Qt simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

The Web SDK also supports debugging WRT applications.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

WRT applications for MeeGo are packaged using the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction); another approach is to submit the package to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:29:34Z

Macron: /* Debugging */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
• MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
• Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

With MeeGo SDK, you can debug applications on the device and within a Qt simulator. Since debugging is integrated into the IDE, you can debug your applications, for instance, by stepping through your code and inserting breakpoints.

Web SDK also supports debugging WRT applications.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

WRT applications for MeeGo are packaged using the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction); another approach is to submit the package to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:28:52Z

Macron: /* Developing */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
• MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
• Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==

With MeeGo SDK, you can create applications for a range of devices from a single code base. Since the SDK supports the simulation of MeeGo devices, you can create software without an actual MeeGo device. Currently, MeeGo SDK supports the Linux and Windows operating systems.

With Web SDK, you can create MeeGo applications based on web technologies, such as JavaScript/HTML/CSS. This SDK is also available for several development platforms.

You can also create hybrid applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

MeeGo SDK supports on-device debugging, as well as debugging within a MeeGo device simulator. This is integrated into the IDE so developers can step through their code, insert breakpoints, and carry out other standard debugging activities.

Web SDK also supports debugging WRT applications.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

WRT applications for MeeGo are packaged using the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction); another approach is to submit the package to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T12:27:26Z

Macron: /* Update to developer story on www.meego.com/developers */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

As an application developer, you can use C++, Web technologies, and QML to write applications for MeeGo. Currently, the following SDKs are available:
• MeeGo SDK, which is the main development environment for creating native applications. This SDK allows you to use Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and supports Qt 4.7 and Qt Mobility 1.0.2 frameworks.
• Web SDK, which is the additional development environment for creating web-based applications. This SDK is based on open-source technology.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==
The MeeGo SDK is a tool that allows a developer to create binaries for a range of devices from a single code base. The SDK supports the simulation of MeeGo devices, so developers can create software without an actual MeeGo device. Currently, there are versions of MeeGo SDK for popular development platforms such as Linux and Windows(in future).

The Web SDK permits web technologies, such as JavaScript/HTML/CSS, to be used to create MeeGo applications. This SDK is also available for several development platforms.

It is also possible to create hybrid C++/WRT applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

MeeGo SDK supports on-device debugging, as well as debugging within a MeeGo device simulator. This is integrated into the IDE so developers can step through their code, insert breakpoints, and carry out other standard debugging activities.

Web SDK also supports debugging WRT applications.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

WRT applications for MeeGo are packaged using the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction); another approach is to submit the package to an application store.

SDK/Docs/1.1/MeeGo overview

2010-11-02T11:42:23Z

Macron: /* Web SDK overview */

= MeeGo application development overview=

The MeeGo 1.1 release provides a new toolset for application developers, supporting cross-platform development. These tools make it easy to enter the MeeGo application ecosystem, and are built, like MeeGo, on proven open-source technologies.

The big news for application developers is that '''Qt Quick''' is now part of the MeeGo release. This new technology allows rapid application UI development based on QML and JavaScript. It is also easily extendable with C++ objects, allowing a clear separation between UI logic (QML/JavaScript), and backend logic (Qt/C++). Qt Quick is ideal for MeeGo application development because it is highly flexible, allowing a developer to modify a UI easily so that it delivers an optimal user experience on all MeeGo devices. There are many Qt Quick examples and tutorials available already. For example, see [http://developer.qt.nokia.com/wiki/Qt_Quick_Tutorial the official Qt Quick tutorial].

MeeGo SDK, based on Qt Creator, allows developers to create native applications for a range of devices (such as the N900, Aava, and Netbook devices), using both the Qt/C++ and Qt Quick frameworks. The SDK supports using Qt 4.7 and MeeGo Touch Framework and is packaged with Qt Quick development libraries. It also supports multiple toolchains, allowing compilation for both the x86 and ARM processor architectures. This means the same code base can be used for N900, Aava, and Netbook devices.

MeeGo 1.1 also supports the Web Runtime (WRT) environment, which means developers can use web-based technologies (HTML/CSS/JavaScript) to create applications for MeeGo. It is also possible to embed WRT UIs into C++ applications using Qt wrapper objects such as QWebView from the QtWebKit module.

With a new set of tools, the availability of technologies such as WRT and Qt Quick, and accompanying developer documentation, MeeGo application development has become easier and more accessible.

The following sections outline the software development kits available for this MeeGo release.

= SDK alternatives =

The following sections present options for starting application development. Note that it is also possible to combine the technologies presented in this section in hybrid applications, with parts implemented in C++ and others in JavaScript.

The key choice is between '''MeeGo SDK''' and '''Web SDK'''. Both provide an integrated development environment (IDE) that can be used to contribute to MeeGo. MeeGo SDK supports Qt Quick development, making it the tool of choice for most application development.

==MeeGo SDK overview==

MeeGo SDK is used to develop native applications with cross-platform compatibility.

The following table describes MeeGo SDK:

{| border="1" cellpadding="5" cellspacing="0"
|+
|-
! style="background:#efefef; width:120px;" | Name
! style="background:#efefef; width:120px;" | Technologies
! style="background:#efefef; width:170px;" | Intended users
! style="background:#efefef; width:400px;" | Where to get started
|-
|'''MeeGo SDK'''
|C/C++, Qt Quick (Windows, Linux)
|Developers who want to create native applications and developers who want their application to be compatible with multiple mobile platforms, and developers who want to use Qt Quick.
|
* Get MeeGo SDK for Linux [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux| <here>]].
* Get MeeGo SDK for Windows [[MeeGo_SDK_for_Windows| <here>]].
* For more information on developing with MeeGo SDK, read [[SDK/Docs/1.1#Using_the_SDK:__Qt.2C_WRT.2C_Hello_World.2C_Debugging| this]].
|}

MeeGo SDK includes the following tools and components:
* '''Qt Creator''', the integrated development environment
** '''MADDE''' for easy cross-platform development
* '''simulator''' for quickly running and testing user interaction and functionality of applications that use Qt Mobility 1.0 and Qt 4.7 APIs
* '''emulators''' for handset and netbook running MeeGo applications on an environment practically identical to the device. Emulator not only provides the platform system but also emulates device hardware.

==Web SDK overview==

Web SDK is used to develop web-based applications. Windows developers of web-based content can use Web SDK. Later, the same will become possible for Linux developers.

The following table describes Web SDK:

{| border="1" cellpadding="5" cellspacing="0"
|+
|-
! style="background:#efefef; width:120px;" | Name
! style="background:#efefef; width:120px;" | Technologies
! style="background:#efefef; width:170px;" | Intended users
! style="background:#efefef; width:400px;" | Where to get started
|-
|'''Web SDK'''
|JavaScript, HTML, CSS
(Windows)
|Developers who want to create web-centric applications and combine web services with device data and are interested in HTML/JavaScript development.
| [[SDK/Docs/1.1/Web SDK with WRT| You can find the instructions for getting the Web SDK and an introductory example here]]
|}

= MeeGo 1.1 SDK web sites for application developers=

* [http://wiki.meego.com/SDK/Docs/1.1 MeeGo 1.1 developer documentation]
* [http://apidocs.meego.com/1.1-preview/html/index.html API references] //replace with direct links to MeeGo API and Platform API//
* [http://meego.com/developers MeeGo development page at meego.com]
* [http://www.meego.gitorious.org MeeGo git repository] contains the MeeGo platform source code.
* [http://bugs.meego.com Central location for bug reporting] which is also used as a simple task reporting tool.
* [http://forum.meego.com MeeGo Forum] enables users, developers and anybody interested in MeeGo to discuss about the MeeGo project and related issues.

[[Category: MeeGo 1.1]]

SDK/Docs/1.1/MeeGo overview

2010-11-02T11:35:41Z

Macron: /* MeeGo application development overview */

= MeeGo application development overview=

The MeeGo 1.1 release provides a new toolset for application developers, supporting cross-platform development. These tools make it easy to enter the MeeGo application ecosystem, and are built, like MeeGo, on proven open-source technologies.

The big news for application developers is that '''Qt Quick''' is now part of the MeeGo release. This new technology allows rapid application UI development based on QML and JavaScript. It is also easily extendable with C++ objects, allowing a clear separation between UI logic (QML/JavaScript), and backend logic (Qt/C++). Qt Quick is ideal for MeeGo application development because it is highly flexible, allowing a developer to modify a UI easily so that it delivers an optimal user experience on all MeeGo devices. There are many Qt Quick examples and tutorials available already. For example, see [http://developer.qt.nokia.com/wiki/Qt_Quick_Tutorial the official Qt Quick tutorial].

MeeGo SDK, based on Qt Creator, allows developers to create native applications for a range of devices (such as the N900, Aava, and Netbook devices), using both the Qt/C++ and Qt Quick frameworks. The SDK supports using Qt 4.7 and MeeGo Touch Framework and is packaged with Qt Quick development libraries. It also supports multiple toolchains, allowing compilation for both the x86 and ARM processor architectures. This means the same code base can be used for N900, Aava, and Netbook devices.

MeeGo 1.1 also supports the Web Runtime (WRT) environment, which means developers can use web-based technologies (HTML/CSS/JavaScript) to create applications for MeeGo. It is also possible to embed WRT UIs into C++ applications using Qt wrapper objects such as QWebView from the QtWebKit module.

With a new set of tools, the availability of technologies such as WRT and Qt Quick, and accompanying developer documentation, MeeGo application development has become easier and more accessible.

The following sections outline the software development kits available for this MeeGo release.

= SDK alternatives =

The following sections present options for starting application development. Note that it is also possible to combine the technologies presented in this section in hybrid applications, with parts implemented in C++ and others in JavaScript.

The key choice is between '''MeeGo SDK''' and '''Web SDK'''. Both provide an integrated development environment (IDE) that can be used to contribute to MeeGo. MeeGo SDK supports Qt Quick development, making it the tool of choice for most application development.

==MeeGo SDK overview==

MeeGo SDK is used to develop native applications with cross-platform compatibility.

The following table describes MeeGo SDK:

{| border="1" cellpadding="5" cellspacing="0"
|+
|-
! style="background:#efefef; width:120px;" | Name
! style="background:#efefef; width:120px;" | Technologies
! style="background:#efefef; width:170px;" | Intended users
! style="background:#efefef; width:400px;" | Where to get started
|-
|'''MeeGo SDK'''
|C/C++, Qt Quick (Windows, Linux)
|Developers who want to create native applications and developers who want their application to be compatible with multiple mobile platforms, and developers who want to use Qt Quick.
|
* Get MeeGo SDK for Linux [[SDK/Docs/1.1/Getting_started_with_the_MeeGo_SDK_for_Linux| <here>]].
* Get MeeGo SDK for Windows [[MeeGo_SDK_for_Windows| <here>]].
* For more information on developing with MeeGo SDK, read [[SDK/Docs/1.1#Using_the_SDK:__Qt.2C_WRT.2C_Hello_World.2C_Debugging| this]].
|}

MeeGo SDK includes the following tools and components:
* '''Qt Creator''', the integrated development environment
** '''MADDE''' for easy cross-platform development
* '''simulator''' for quickly running and testing user interaction and functionality of applications that use Qt Mobility 1.0 and Qt 4.7 APIs
* '''emulators''' for handset and netbook running MeeGo applications on an environment practically identical to the device. Emulator not only provides the platform system but also emulates device hardware.

==Web SDK overview==

Web SDK is used to develop web-based applications. Windows developers of web-based content can use Web SDK. Later, the same will become possible for Linux developers.

The following table describes Web SDK:

{| border="1" cellpadding="5" cellspacing="0"
|+
|-
! style="background:#efefef; width:120px;" | Name
! style="background:#efefef; width:120px;" | Technologies
! style="background:#efefef; width:170px;" | Intended users
! style="background:#efefef; width:400px;" | Where to get started
|-
|'''Web SDK'''
|JavaScript, HTML, CSS
(Windows)
|Developers who want to create web-centric applications and combine web services with device data and are interested in HTML/JavaScript development.
| [[SDK/Docs/1.1/Web SDK with WRT| You can find the instructions for getting Web SDK and an introductory example here]]
|}

= MeeGo 1.1 SDK web sites for application developers=

* [http://wiki.meego.com/SDK/Docs/1.1 MeeGo 1.1 developer documentation]
* [http://apidocs.meego.com/1.1-preview/html/index.html API references] //replace with direct links to MeeGo API and Platform API//
* [http://meego.com/developers MeeGo development page at meego.com]
* [http://www.meego.gitorious.org MeeGo git repository] contains the MeeGo platform source code.
* [http://bugs.meego.com Central location for bug reporting] which is also used as a simple task reporting tool.
* [http://forum.meego.com MeeGo Forum] enables users, developers and anybody interested in MeeGo to discuss about the MeeGo project and related issues.

[[Category: MeeGo 1.1]]

SDK/Docs/1.1/MeeGo developer story

2010-11-02T11:33:57Z

Macron: /* Distributing */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

MeeGo applications are written in C++, Web technologies, and QML with tools provided by the MeeGo community:
* Currently, the main development environment is MeeGo SDK, which allows developers to create native applications using Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and contains support for Qt 4.7 and Qt Mobility 1.0.2 frameworks.
* Web Runtime (WRT) developers can use an additional SDK based on open-source technology, called Web SDK.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==
The MeeGo SDK is a tool that allows a developer to create binaries for a range of devices from a single code base. The SDK supports the simulation of MeeGo devices, so developers can create software without an actual MeeGo device. Currently, there are versions of MeeGo SDK for popular development platforms such as Linux and Windows(in future).

The Web SDK permits web technologies, such as JavaScript/HTML/CSS, to be used to create MeeGo applications. This SDK is also available for several development platforms.

It is also possible to create hybrid C++/WRT applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

MeeGo SDK supports on-device debugging, as well as debugging within a MeeGo device simulator. This is integrated into the IDE so developers can step through their code, insert breakpoints, and carry out other standard debugging activities.

Web SDK also supports debugging WRT applications.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

WRT applications for MeeGo are packaged using the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications (under construction); another approach is to submit the package to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T11:33:13Z

Macron: /* Debugging */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

MeeGo applications are written in C++, Web technologies, and QML with tools provided by the MeeGo community:
* Currently, the main development environment is MeeGo SDK, which allows developers to create native applications using Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and contains support for Qt 4.7 and Qt Mobility 1.0.2 frameworks.
* Web Runtime (WRT) developers can use an additional SDK based on open-source technology, called Web SDK.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==
The MeeGo SDK is a tool that allows a developer to create binaries for a range of devices from a single code base. The SDK supports the simulation of MeeGo devices, so developers can create software without an actual MeeGo device. Currently, there are versions of MeeGo SDK for popular development platforms such as Linux and Windows(in future).

The Web SDK permits web technologies, such as JavaScript/HTML/CSS, to be used to create MeeGo applications. This SDK is also available for several development platforms.

It is also possible to create hybrid C++/WRT applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

MeeGo SDK supports on-device debugging, as well as debugging within a MeeGo device simulator. This is integrated into the IDE so developers can step through their code, insert breakpoints, and carry out other standard debugging activities.

Web SDK also supports debugging WRT applications.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

WRT applications for MeeGo are packaged using the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications; another approach is to submit the package to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T11:32:33Z

Macron: /* Debugging */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

MeeGo applications are written in C++, Web technologies, and QML with tools provided by the MeeGo community:
* Currently, the main development environment is MeeGo SDK, which allows developers to create native applications using Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and contains support for Qt 4.7 and Qt Mobility 1.0.2 frameworks.
* Web Runtime (WRT) developers can use an additional SDK based on open-source technology, called Web SDK.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==
The MeeGo SDK is a tool that allows a developer to create binaries for a range of devices from a single code base. The SDK supports the simulation of MeeGo devices, so developers can create software without an actual MeeGo device. Currently, there are versions of MeeGo SDK for popular development platforms such as Linux and Windows(in future).

The Web SDK permits web technologies, such as JavaScript/HTML/CSS, to be used to create MeeGo applications. This SDK is also available for several development platforms.

It is also possible to create hybrid C++/WRT applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

MeeGo SDK supports on-device debugging, as well as debugging within a MeeGo device simulator. This is integrated into the IDE so developers can step through their code, insert breakpoints, and carry out other standard debugging activities.

Web SDK supports debugging WRT applications within a simulated MeeGo device web runtime.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

WRT applications for MeeGo are packaged using the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications; another approach is to submit the package to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T11:32:08Z

Macron: /* Developing */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

MeeGo applications are written in C++, Web technologies, and QML with tools provided by the MeeGo community:
* Currently, the main development environment is MeeGo SDK, which allows developers to create native applications using Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and contains support for Qt 4.7 and Qt Mobility 1.0.2 frameworks.
* Web Runtime (WRT) developers can use an additional SDK based on open-source technology, called Web SDK.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==
The MeeGo SDK is a tool that allows a developer to create binaries for a range of devices from a single code base. The SDK supports the simulation of MeeGo devices, so developers can create software without an actual MeeGo device. Currently, there are versions of MeeGo SDK for popular development platforms such as Linux and Windows(in future).

The Web SDK permits web technologies, such as JavaScript/HTML/CSS, to be used to create MeeGo applications. This SDK is also available for several development platforms.

It is also possible to create hybrid C++/WRT applications by wrapping a WRT application with a Qt/C++ object.

==Debugging==

MeeGo SDK supports on-device debugging, as well as debugging within a MeeGo simulator. This is integrated into the IDE so developers can step through their code, insert breakpoints, and carry out other standard debugging activities.

Web SDK supports debugging WRT applications within a simulated MeeGo device web runtime.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

WRT applications for MeeGo are packaged using the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications; another approach is to submit the package to an application store.

SDK/Docs/1.1/MeeGo developer story

2010-11-02T11:06:48Z

Macron: /* Developing */

[[category:Meego-1.1]]

'''This is a draft (2010-10-21)'''

= Update to developer story on www.meego.com/developers =

MeeGo applications are written in C++, Web technologies, and QML with tools provided by the MeeGo community:
* Currently, the main development environment is MeeGo SDK, which allows developers to create native applications using Qt/C++ and Qt Quick. MeeGo SDK is based on the Qt Creator and contains support for Qt 4.7 and Qt Mobility 1.0.2 frameworks.
* Web Runtime (WRT) developers can use an additional SDK based on open-source technology, called Web SDK.

Both SDKs integrate into the standard development process:
# Developing
# Debugging
# Packaging
# Distributing

 We take the image from www.meego.com/developers/Developer Story.

==Developing==
The MeeGo SDK is a tool that allows a developer to create binaries for a range of devices from a single code base. The SDK supports the simulation of MeeGo devices, so developers can create software without an actual MeeGo device. Currently, there are versions of MeeGo SDK for popular development platforms such as Linux and Windows(in future).

The Web SDK permits web technologies, such as JavaScript/HTML/CSS, to be used to create MeeGo applications. It is also possible to create hybrid applications by wrapping a WRT application with a Qt/C++ object. This SDK is also available for several development platforms.

==Debugging==

MeeGo SDK supports on-device debugging, as well as debugging within a MeeGo simulator. This is integrated into the IDE so developers can step through their code, insert breakpoints, and carry out other standard debugging activities.

Web SDK supports debugging WRT applications within a simulated MeeGo device web runtime.

==Packaging==

MeeGo SDK generates packages for deploying software to MeeGo devices. For example, when testing software on a MeeGo device from MeeGo SDK, the software is packaged, sent to the device and installed.

WRT applications for MeeGo are packaged using the standards-based [http://www.w3.org/TR/widgets/ W3C Widget Packaging and Configuration specification].

==Distributing==
Once a MeeGo application has been packaged, it can be distributed in different ways. One approach is to use the infrastructure supplied by the MeeGo project for the distribution of free, open-source applications; another approach is to submit the package to an application store.

Community Office

2010-11-01T13:43:14Z

Macron: /* Committed Tasks */

== Mission ==

The Community Office (CO) defines and implements the strategy for community collaboration and project promotion.

The work of the CO is organized at the [http://meego.com/community/mailing-lists meego-community mailing list].

== Structure ==
=== Coordination ===
The goals of the Community Office coordination are:

* Overall guidance on tasks and priorities.
* Decision-making, when needed.
* Appointments within the Community Office.
* Connection with the MeeGo Technical Steering Group (TSG).

The coordinators are appointed by the TSG:
* [http://meego.com/users/dawnfoster Dawn Foster], since March 24, 2010. ''MeeGo community manager employed by Intel.''
* [http://meego.com/users/qgil Quim Gil], since March 24, 2010. ''MeeGo advocate, employed by Nokia.''

=== Community Management and Collaboration ===
Coordinated by Dawn Foster
* Processes - community communication channels, contributions and collaboration.
* [[Events]] - [[MeeGo Conference 2010]], community involvement and more. Coordination: Amy Leeland.
* [[Metrics]] - data gathering and analysis, measurements of community health. Coordination: Dawn Foster. Volunteers: [http://meego.com/users/texrat Randall Arnold/Texrat], [http://meego.com/users/dneary Dave Neary/dneary], [http://meego.com/users/bergie Henri Bergius/Bergie].

=== Project Marketing and Promotion ===
Coordinated by Quim Gil
* [[Web infrastructure/Meego.com|meego.com]] content - homepage, announcements, background info, media kit.
* Promotion - merchandising, grassroots [[campaigns]], open source advocacy.
* [[Events]] - sponsoring events, supporting speakers and more.

More at [[Community Office/Marketing|Marketing]]

== Neighborhood ==
Related areas outside of the Community Office:
* [[Web infrastructure]]
* Trademark - definition, legal aspects, abuse. Ibrahim Haddad.
* Brand - Logotype, guidelines, characters. Claire Alexandre.
* Compliance - OS & application compliance program. Mark Skarpness.

== Process ==

=== Meetings ===

Logistics for bi-weekly [[/Meetings|Community Office meetings]] on the first and third Tuesdays of every month. This meeting is open to anyone who wants to attend and contribute.

The purpose of this meeting is to coordinate tasks by moving proposed tasks to committed tasks with clear owners and prioritization. We hope that this meeting will make it easier for us to get more organized about how we accomplish work in the CO, and avoid the duplicated / wasted effort that we have been seeing at least in these early days of the project while we merge the two communities.

=== Tasks ===

Work and tasks will be broken down into '''Committed Tasks''' and '''Proposed Tasks'''.

Committed tasks will have a clear owner and have been approved in a [[Community_Office/Meetings|Community Office meeting]]. The list of committed tasks may also include prioritization to make sure that we are working actively on the most important tasks.

Proposed tasks include all other work that we would someday like to do, but that has not yet been approved by the CO. Anyone can add a proposed task to this page. If you have a proposed topic that you are ready to start working on, please put together a proposal and request a spot on an upcoming [[Community_Office/Meetings|Community Office meeting]] agenda.

==== Regular Ongoing Tasks ====

* [[Metrics]] - [http://meego.com/users/dawnfoster Dawn]
* Planning for the [[MeeGo Conference 2010]]: [http://meego.com/users/qgil Quim] and [http://meego.com/users/dawnfoster Dawn]
* [[MeeGo Greeters]] program - [http://meego.com/users/texrat Texrat]
* [[Community_Office/Marketing|MeeGo marketing plan]] - [[User:Qgil|Qgil]]

==== Committed Tasks ====
Our backlog. Every task must point to a bug report and/or a wiki page describing the task, where to help and the progress. One coordinator is assigned to each task but more people might be involved (check the link).

# '''[[Web infrastructure/Planning Security Review|Web Infrastructure Planning and Review]] with servers moved to OSUOSL''' - [http://meego.com/users/mshaver Mike Shaver]
# '''[[Proposal for Community Application Support]]''' - [http://meego.com/users/tekojo Tero Kojo]
#: Please get a "Current status" section in the wiki page or open a bug and report status at least before each CO meeting - thanks! --[[User:Qgil|Qgil]] 04:24, 31 August 2010 (UTC)
# '''[[Community Office/Collaboration and Contribution Improvements|Collaboration and Contribution Improvements]]''' - [http://meego.com/users/dawnfoster Dawn Foster]
# '''[http://bugs.meego.com/show_bug.cgi?id=2258 Complete the Community Office structure with people in charge for each area]''': [http://meego.com/users/qgil Quim]
# '''[[Application developer site]] on meego.com - [http://bugs.meego.com/show_bug.cgi?id=7882 status here]''' - Input requested for related content [[Application_developer_site/Related_content| here]] - [http://meego.com/users/macron Ronan]
# [[Community Office/Community device program|Community device program]] - [[User:Dawnfoster|Dawn Foster]]
# '''Mail/Forum integration'''. [http://forum.meego.com/showthread.php?t=85 Forum thread] - See [http://talk.maemo.org/showthread.php?t=28924 maemo.org test] - [http://meego.com/users/reggie Reggie] and [http://meego.com/users/bergie Bergie]
#: On hold until OSU migration --[[User:Dawnfoster|Dawnfoster]] 14:47, 20 September 2010 (UTC)
# [[DeveloperEngagement|Developer Engagement]] - educating and engaging new & old application developers --[[User:W00t|W00t]]
# '''[http://forum.meego.com/showthread.php?t=177 Decision on MeeGo marketing budget 2010]''': [http://meego.com/users/qgil Quim]
# '''Implementation of social [[News and Planet]]''' - [http://meego.com/users/mshaver Mike Shaver]
#: On hold until OSU migration --[[User:Dawnfoster|Dawnfoster]] 14:47, 20 September 2010 (UTC)
# '''[http://bugs.meego.com/show_bug.cgi?id=6080 Web Content team with identified owners]''' - [http://meego.com/users/qgil Quim]
#: Completed and ready to be moved away from the backlog. Details in the bug report.--[[User:Qgil|Qgil]] 13:54, 21 September 2010 (UTC)
# '''[[meego.com]] documentation''' - [http://meego.com/users/mshaver Mike Shaver]
#: On hold until OSU migration --[[User:Dawnfoster|Dawnfoster]] 14:47, 20 September 2010 (UTC)
# Push fixes for the [http://bugs.meego.com/show_bug.cgi?id=4898 MeeGo openness meta-bug] - [http://meego.com/users/qgil Quim]

Basic rule of prioritization: every coordinator gets one task prioritized before a second task from a same coordinator.

Examples:
* CORRECT: 1 Mary - 2 John - 3 Mary
* WRONG: 1 Mary - 2 Mary - 3 John

==== Proposed Tasks: not committed yet ====

Please click on the button "Your signature with codestamp" at the end of your proposed task to keep a record of who made each proposal when.

* [[Single sign-on|SSO]] decision - needs clarification.
* MeeGo jobs - combine with http://jobs.linux.com
* MeeGo marketplace - combine with http://store.linux.com
* Project Management (recommend Bugzilla integration; see [https://wiki.mozilla.org/Bugzilla:Addons#Project_management_software_integration PM Options].
* MeeGo document templates - priority on OpenOffice.org & MS Office presentation slides.
* Something along the lines of http://djangopeople.net/ (note that although that implementation has job-market features the idea is to have an easy-access "Who's Who")
* List activities for which rankings of MeeGo users will be provided (see [[reputation]] page for ongoing list)
* Agreement on 'Should meego.com offer mailing lists to open source community projects?' --[[User:Qgil|Qgil]] 04:15, 20 May 2010 (UTC)
* Agreement on 'Should meego.com offer a bug tracker tool to open source community projects?' --[[User:Qgil|Qgil]] 04:36, 20 May 2010 (UTC)
* [http://bugs.meego.com/show_bug.cgi?id=3641 MeeGo Press Kit] --[[User:Qgil|Qgil]] 22:42, 3 August 2010 (UTC)

==== Tasks completed ====
* 2010-08-31 '''[http://meego.com/about/public-support-meego How to handle company endorsements at meego.com]''' - [http://meego.com/users/dawnfoster Dawn Foster] - Completed a while ago. Contact Dawn, Quim or Mike to get public endorsements list on the page.
* 2010-08-23 '''[[Forum Triage]]''' to coordinate answering user questions in the forum - anyone can help. Update: Replaced by [[MeeGo Greeters]] program -- [[User:Dawnfoster|Dawnfoster]] 17:23, 23 August 2010 (UTC)
* 2010-08-10 - '''MeeGo Conference - [http://conference2010.meego.com/ registration and proposal website]''' -[http://meego.com/users/amyleeland Amy Leeland]
#:registration and proposal submission should be live first week of August
* 2010-06-30 [http://www.linuxfoundation.org/about/linux-foundation-trademark-usage-guidelines MeeGo trademark and logo usage guidelines ([http://bugs.meego.com/show_bug.cgi?id=1303 Details]) - [http://meego.com/users/ibrahim Ibrahim]
* 2010-06-22 [http://wiki.meego.com/images/MeeGo_Introduction.pdf Article on MeeGo for the Linux Journal (pdf link)] - [http://meego.com/users/ibrahim Ibrahim]
* 2010-05-26 - '''[[Community_Office/Meego.com/May_2010_release_website_update|May 2010 release website update]]''' - [http://meego.com/users/qgil Quim]
* 2010-05-26 - [[help.meego.com]] - [http://help.meego.com] - [http://meego.com/users/mshaver Mike Shaver]
* 2010-05-18 - [http://forum.meego.com/showpost.php?p=1421&postcount=8 License to adopt for MeeGo documentation] - [http://meego.com/users/ibrahim Ibrahim] - Recommendations from the Linux Foundation were delivered to Intel and Nokia and are inline with http://meego.com/about/terms-service.
* 2010-05-18 - [http://forum.meego.com/showpost.php?p=1444&postcount=47 Karma decision] - [http://meego.com/users/dneary Dave Neary]
* 2010-05-06 - Fix [http://bugs.meego.com/show_bug.cgi?id=1560 Wiki login fails for newly-created meego.com accounts] - [http://meego.com/users/mshaver Mike Shaver]
* 2010-05-04 - [[Community_Office#Process|Community Office process]] - [http://meego.com/users/dawnfoster Dawn Foster]
* 2010-05-04 - [http://bugs.meego.com/show_bug.cgi?id=1536 meego.gitorious.org documentation] - [[Git_Infrastructure]] - [http://meego.com/users/nashif Anas Nashif]
* 2010-04-07 - [http://forum.meego.com forum.meego.com] launched - [http://meego.com/users/reggie Reggie Suplido] & [http://meego.com/users/mshaver Mike Shaver]

==== Tasks dropped ====
* 2010-05-04 - MeeGo presentations, processes and other ''internal'' materials published. [http://meego.com/users/qgil Quim Gil]
** Chasing the TSG but it's a slow task since it requires discussion from the future roles and the people actually assuming the software development responsibilities. I feel this is going well over my head. I am pushing, but I'm not the actual re3spoble. The TSG is. Proposing to drop this task from my list.--[[User:Qgil|Qgil]] 13:00, 4 May 2010 (UTC)
* 2010-06-15 - Ask Nokia to modify licence on Maemo documentation to CC BY 3.0 + BSD for code samples, to allow reuse of relevant parts in MeeGo documentation
** Quim says "if something is 100% produced by Nokia and useful to MeeGo, copy it over." The general opinion (Quim, Tero) is that not much Maemo documentation is useful for MeeGo.
* '''MeeGo Compliance Program''' - [http://meego.com/users/mskarpne Mark Skarpness]
** Removing from this list, since the compliance program is [http://meego.com/about/governance/quality-assurance outside of the CO scope residing under QA]. --[[User:Dawnfoster|Dawnfoster]] 14:03, 31 August 2010 (UTC)

== How to contribute ==

See the Process section above for current approved work and proposed tasks. You might also find this guide for [[Contributing to MeeGo]] helpful.

=== Contributors looking for a team ===

MeeGo members interested in taking an active role in this team. Please move your names to the team(s) where you want to contribute regularly. Better to choose one than many.

* [http://meego.com/users/xfade Niels Breet] - maemo.org webmaster and long time maemo.org community member. Liberated by Nokia to work on community infra and community repository infrastructure for maemo.org. Interested in doing the same for meego.com.

* [http://meego.com/users/lbt David Greaves/lbt] - Mer build guy and maemo.org member. Introduced OBS to Maemo and working on Nokia build infrastructure.

* [http://meego.com/users/Jaffa Andrew Flegg/Jaffa] - Long term Maemo community member and developer and twice Maemo Community Council member. Interested in bringing the best of the Maemo and Moblin communities together in the nascent MeeGo community and ensuring that cross-community facilitation happens.

* [http://meego.com/users/ksanjeet Sanjeet Kumar] Willing to contribute as server admin.

* [http://meego.com/users/Elliot Elliot Smith/townxelliot] - meego.com websites techie, worked on moblin.org Moblin SDK materials, contributor to Moblin SDK tools. Intel pays me. Can get time to rework content from moblin.org for this site.

* [http://meego.com/users/bergie Henri Bergius] - contributor to the [http://bergie.iki.fi/blog/maemo-s_community_involvement_infrastructure_is_what_meego_needs/ maemo.org community infrastructure], behind services like Brainstorm, Karma, and Social News. Working on maemo.org projects through Nemein, and interested in doing the same for meego.com

* [http://meego.com/users/amby Gabor Ambrozy/amby] - recently joined maemo.org community member; would like to contribute to transition, community infrastructure and community marketing. Can bring virtual project mgmt and organization transition experience; IT system integration, sw development and learning projects practices. And a lot of end-user enthusiasm ;)

* [http://meego.com/users/lm Lucas Maneos/lm] - member of the maemo.org bugsquad, happy to contribute in any way to the bugzilla transition.

* [http://meego.com/users/tekojo Tero Kojo] - One of the Nokia people involved in the Maemo community and maemo.org. My area has been working with the liberated community members and the infrastructure for maemo.org. Interested in making sure that MeeGo.com provides the necessary tools and services to both developers and active users. I work in Nokia Maemo developer platform team as project manager responsible for communities.

* [http://meego.com/users/margie Margie Foster] - I am the localization project manager for Moblin and also work on the MeeGo website. I am an Intel employee. I am really looking forward to helping create and maintain a vibrant MeeGo localization community using Transifex.
[[Category:Community]]

* [http://meego.com/users/revdkathy Kathy Smith] - maemo.org community member, non-technical end user. Special interest in community building, project management and channeling the input of end users.

* [http://meego.com/users/qole Qole] - Two-term Maemo Community Council member, enthusiastic hacker and Linux user, primary maintainer of the Easy Debian project, and very active in the Maemo forums. Interested in helping out where I can to make MeeGo have the kind of powerhouse community that has made Maemo so special.

* [http://meego.com/users/vdvsx VDVsx] - Maemo Community member and developer, willing to keep helping everybody inside this new community from developers to end users.

* [http://meego.com/users/texrat Randall Arnold/Texrat] - Maemo Community Council member, former Nokia QA engineer for Maemo devices, originator of maemo.org community outreach efforts, maemo.org forum moderator and best practices blogger. Ready to translate lessons learned from maemo.org to whatever develops here!

* [http://meego.com/users/generalantilles Ryan Abel] - Long-term Maemo Community member and former two-term Maemo Community Council member. Interested in leveraging the strengths of the large maemo.org community into the growing MeeGo community. Also interested in helping to develop strong web infrastructure and tooling.

* [http://meego.com/users/mshaver Mike Shaver/mshaver] - Moblin.org webmaster and developer behind the current meego.com site. I am an Intel employee. Would love to see this list of people contributing and directing what we build and support for the meego.com community.

* [http://meego.com/users/sulamita Sulamita Garcia] - MeeGo Technical Marketing Engineer. I work at Open Source Technology Center at Intel and I've involved with Moblin from the beginning. I produce documentation, training, and support for costumers and developers.

* [http://meego.com/users/sjgadsby Stephen Gadsby/sjgadsby] - Maemo community member, poster of weekly Bugzilla activity reports, and forum moderator. Interest in community building and communication channels between users and developers.

* [http://meego.com/users/reggie Reggie Suplido] - [http://wiki.maemo.org/Maemo.org_team#Talkmaster maemo.org Talkmaster], primary administrator of [http://talk.maemo.org/ talk.maemo.org]. Founded [http://www.internettablettalk.com/ Internet Tablet Talk] where it's forum later on became talk.maemo.org. Can help run the forums section of MeeGo, or perform integration with talk.maemo.org if the need arises.

* [http://meego.com/users/timeless timeless] - regular Nokia Browser contact with the Maemo community, contributor to Maemo, Mer, Mozilla, Transifex. Runs [http://mxr.meego.com mxr.meego.com]

* [http://meego.com/users/danielwilms danielwilms] - working in Nokia on the maemo.org community developer support. Taking over community tasks, working on documentation and support. Interested in helping out, by working on MeeGo.com services, support developers and users, and documentation.

* [http://meego.com/users/th0br0 Andreas Osowski/th0br0] - Interested in helping with infrastructure and community marketing. Currently working in Fedora as Ambassador and packager. ~4 years of C++ experience (with some Qt), RoR and Java experience

* [http://meego.com/users/timsamoff Tim Samoff / timsamoff] - Designer (graphic, UI, interaction, web), long-time Maemo Community member (two-term Maemo Community Council Member), and forever open source advocate

* [http://meego.com/users/gadgety Gadgety] - maemo.org community member, business end user; I'd like to contribute to making the MeeGo community an easy place to join for newbies, fans, enthusiasts and creating a community where everyone feels welcome to contribute regardless of technical skill level

* [http://meego.com/users/mikael Mikael Söderberg/mksoderberg] - I am Chair of the [http://genivi.org/ GENIVI Alliance] Reference System Work Group. I would like to contribute by assisting in development of the MeeGo Platform Infrastructure.

* [http://meego.com/users/dneary Dave Neary/dneary] - maemo.org community developer support with a specific documentation slant. Experienced community development consultant, event organiser & general busybody. I want to make sure that MeeGo makes the right strategic decisions related to transparency and participation guidelines at the project inception to avoid major issues later.

* [http://meego.com/users/solt Marcin Sołtysiak/solt] - Open to help with community. Aligned with l10n efforts I would see a place for language/country sub sections. Also, have experience with Midgard. I could help with geek-to-human relations :)

* [http://meego.com/users/vilvo Ville Ilvonen/vilvo] - Nokia's Maemo Test Tools - responsible for advocating and coordinating development of test tools and test automation inside Maemo. Looking forward to continue with MeeGo. I can help with tools contribution and evangelism within this working group. Nokia pays me to spend time with this.

* [http://meego.com/users/dannybe Danny Bennett] - maemo.org community member, Nokia application architect for maemo sw. I'm interested in architecture and the technology components that make up the MeeGo distro. This is where and how I can contribute.

* [http://meego.com/users/auke Auke Kok] - Intel MeeGo developer, working on releases, fastboot, l10n project.

* [http://meego.com/users/glezos Dimitris Glezos] - [http://www.transifex.net/ Transifex] developer, [http://www.indifex.com/ Indifex] employee, working on L10n engineering. I'm interested in developing the L10n infrastructure of MeeGo.

* [http://meego.com/users/freppas Fredrik Öqvist] - Swedish/Finnish tech-loving marketing guy currently studying some MBA classes in China. Hoping to add a lot to the marketing and marketing strategy for Meego.

* [http://meego.com/users/mitsutaka Mitsutaka Amano] - Moblin community member from Moblin 1.x, [http://git.moblin.org/cgit.cgi/moblin-image-creator Moblin Image Creator] maintainer, MeeGo/Moblin contributor, l10n(Japanese), Japanese evangelist, MIRACLE LINUX CORPORATION.

* [http://meego.com/users/gaveen Gaveen Prabhasara / gaveen] - a DevOps guy. Planning to become a Fedora packager soon. FOSS / Linux / Ruby advocate

* [http://meego.com/users/baloo Jamie Bennett] - Ubuntu Mobile developer for Canonical, long-term Maemo user/contributor/promoter looking to help develop, advocate and ensure that the whole mobile ecosphere benefits from the MeeGo initiative.

* [http://meego.com/users/chippy Chippy / Steve Paine] - Full time mobile technology blogger (Carrypad, UMPCPortal) can assist with communication, presentations, meetings.

* [http://meego.com/users/thp Thomas Perl / thp] - Application developer, interested in user experience design and development in multiple languages

* [http://meego.com/users/andre Andre Klapper] - [http://wiki.maemo.org/Bugsquad maemo.org Bugmaster]. Also active in Maemo user support ([http://talk.maemo.org forum] and mailing lists). Former member of [http://l10n.gnome.org/languages/de/ German] and current member of [http://l10n.gnome.org/languages/cs/ Czech] GNOME translation team.

* [http://meego.com/users/dvalfre Daniel Valfre] - Software engineer, based in Argentina. Work for Intel but not related to MeeGo. Will like to help on having Community efforts replicated in the Latin América Region.

* [http://meego.com/users/amjad Amjad Syed]- Build Engineer. Will like to contribute in packaging and porting meego to new hardware.

*[[User:Kyber| Jarkko Moilanen]] - Researcher and Post Grad student at the University of Tampere, Finland. Member of Tampere Meego Network. Interested about 'community building' and general hacking.

* [http://meego.com/users/jussiml Jussi Lahdenniemi]- Sr Test engineer located in Tampere, Finland - I'd like to contribute in testing and QA tools development

== History ==
The creation of the Community working group was approved by the Technical Steering Group on March 24, 2010. See the [http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-03-24-19.58.html meeting minutes] for more details.

There was a first [[Community_website_meeting_2010_2_24|Community website meeting]] on February 24, 2010.

The role of working groups in the MeeGo project are explained at http://meego.com/about/governance.

Application developer site/Related content

2010-11-01T13:40:30Z

Macron: Created page with "= Application Developer Related Content= == Overview == The MeeGo platform makes extensive use of upstream projects, similarly the application developer support should also mak…"

= Application Developer Related Content=

== Overview ==

The MeeGo platform makes extensive use of upstream projects, similarly the application developer support should also make use of upstream projects. This means that the developer.meego.com project should link or adapt upstream documentation like Qt tutorials, in order to provide a beginner developer for MeeGo a single point of entry to MeeGo application development.

The goal of this section is to list content that application developers might be interested in that could be linked from the developer.meego.com.

To contribute to the list please add to the content below, if there are several articles from one site, list the site as a header (some description would be nice). If there is only one, please just add it to the "Other Sources" header below.

== Related Content ==

=== Qt.nokia.com ===

This is the home site for the Qt project hosted by Nokia. This site has a range of tutorials applicable to MeeGo.

* http://doc.qt.nokia.com/4.7/how-to-learn-qt.html - A basic tutorial on Qt
* http://doc.qt.nokia.com/4.7/qml-tutorial.html - A basic QML tutorial
* http://doc.qt.nokia.com/qtmobility-1.0-beta/examples.html - Some mobility examples from Qt

=== Forum Nokia ===

Forum Nokia supports development on Nokia platforms (Maemo/MeeGo included), and so it has some information about how to use Qt technologies on Nokia handsets. A lot of this information is applicable to other MeeGo devices.

* http://wiki.forum.nokia.com/index.php/Qt_Quick_examples_for_porting - A set of QML examples.
* http://wiki.forum.nokia.com/index.php/Porting_Mobile_Applications_to_Qt - A how-to for porting

=== Other sources ===

* http://quitcoding.com/?page=work#qtquick - A Qt Quick gaming tutorial

Application developer site

2010-11-01T13:27:15Z

Macron: /* Content Description */

Application developer site

2010-11-01T13:26:50Z

Macron: /* Content Description */

Application developer site/Status

2010-11-01T13:22:58Z

Macron: /* Current Status */

== Current Status ==

=== Week starting 1st November 2010===

It is almost 1.5 months since the last status report, so I apologize for my tardiness.

1.5 weeks ago the pilot site was send for review by an internal team, to check whether it matches the MeeGo branding, etc. It also tested its readiness for release. The outcome of the review was that the site was not ready for release and lacked content. It also had some usability issues.

Since the review the development team has been working on the issues raised during the review, and hopefully the site will be in a condition for re-review this week. For those that are interested, access can be arranged to the pilot site.

== Old statuses ==

=== Week starting 20th September 2010 ===

There is a prototype drupal site that will be used to create the necessary themeing etc. This week the plan is to improve the quality of this site and set up access for additional testers.

=== FW 37 ===

The Drupal implementation work has started and a pilot site with some functionality is expected this week. The initial reference guide for the MeeGo API has been produced, mapping the MeeGo architectural services to lower-level APIs, to make the MeeGo API a conceptual whole. This needs theme-ing to match the rest of the site, this work has started, and is ongoing.

=== FW 35 ===

The wireframe design for the developer.meego.com site have been approved by the Maemo UI Lead. There was one comment: the 3rd level landing pages might be too heavy for continuous maintenance. The response to this comment is to use the pilot test site for checking the level of drupal experience required to edit content.

=== FW27 ===

There is a draft information architecture available for review and feedback [[Application_developer_site/Information_architecture | here]], this has been bounced around between Nokia and the maintainers of the www.meego.com site. There will be wireframe designs for the top level of the hierarchy available for review soon (scheduled for FW28, but it's the holiday season).

One outcome of the discussion is that this site will lose its marketing focus and become more like other development sites, such as developer.android.com, so there will be less emphasis on attracting new developers.

=== Status FW24 ===

We have a partner for the development of the developer.meego.com site, ActiveArk. In addition to ActiveArk, there is another company involved, Datafisher, that specialized in online pedagogical design. Both companies have a strong Drupal background, and during the selection process, both companies had clear ideas on how to differentiate from other developer sites.

So far this week we have had some meeting about the way of working (basecamp has been chosen as a project management tool), and are putting together the project team.

=== Status FW22 ===

The current status is that Nokia has contacted several design agencies who are capable of creating web site design with additional material. The initial offers have been received, and Nokia is now choosing which subcontractor to use for this work.

The key criteria for choosing the subcontractor:

# Expertise, especially Drupal knowledge and knowledge of open source development
# Flexibility, especially on the ability to response to community feedback, and to change plans as necessary
# Creativity, especially on ideas to differentiate this site from other developer sites, and on how to make the site attractive to new application developers.

The deadline for the decision on the subcontractor will be FW22-23.

Application developer site/Status

2010-11-01T13:22:46Z

Macron: /* Old statuses */

== Current Status ==

=== Week starting 1st November 2010

It is almost 1.5 months since the last status report, so I apologize for my tardiness.

1.5 weeks ago the pilot site was send for review by an internal team, to check whether it matches the MeeGo branding, etc. It also tested its readiness for release. The outcome of the review was that the site was not ready for release and lacked content. It also had some usability issues.

Since the review the development team has been working on the issues raised during the review, and hopefully the site will be in a condition for re-review this week. For those that are interested, access can be arranged to the pilot site.

== Old statuses ==

=== Week starting 20th September 2010 ===

There is a prototype drupal site that will be used to create the necessary themeing etc. This week the plan is to improve the quality of this site and set up access for additional testers.

=== FW 37 ===

The Drupal implementation work has started and a pilot site with some functionality is expected this week. The initial reference guide for the MeeGo API has been produced, mapping the MeeGo architectural services to lower-level APIs, to make the MeeGo API a conceptual whole. This needs theme-ing to match the rest of the site, this work has started, and is ongoing.

=== FW 35 ===

The wireframe design for the developer.meego.com site have been approved by the Maemo UI Lead. There was one comment: the 3rd level landing pages might be too heavy for continuous maintenance. The response to this comment is to use the pilot test site for checking the level of drupal experience required to edit content.

=== FW27 ===

There is a draft information architecture available for review and feedback [[Application_developer_site/Information_architecture | here]], this has been bounced around between Nokia and the maintainers of the www.meego.com site. There will be wireframe designs for the top level of the hierarchy available for review soon (scheduled for FW28, but it's the holiday season).

One outcome of the discussion is that this site will lose its marketing focus and become more like other development sites, such as developer.android.com, so there will be less emphasis on attracting new developers.

=== Status FW24 ===

We have a partner for the development of the developer.meego.com site, ActiveArk. In addition to ActiveArk, there is another company involved, Datafisher, that specialized in online pedagogical design. Both companies have a strong Drupal background, and during the selection process, both companies had clear ideas on how to differentiate from other developer sites.

So far this week we have had some meeting about the way of working (basecamp has been chosen as a project management tool), and are putting together the project team.

=== Status FW22 ===

The current status is that Nokia has contacted several design agencies who are capable of creating web site design with additional material. The initial offers have been received, and Nokia is now choosing which subcontractor to use for this work.

The key criteria for choosing the subcontractor:

# Expertise, especially Drupal knowledge and knowledge of open source development
# Flexibility, especially on the ability to response to community feedback, and to change plans as necessary
# Creativity, especially on ideas to differentiate this site from other developer sites, and on how to make the site attractive to new application developers.

The deadline for the decision on the subcontractor will be FW22-23.