MeeGo wiki - User contributions [en]

MeeGo Conference Spring 2011

2011-05-15T05:55:01Z

Margie: /* MeeGo localisation */

The main Conference site is: [http://sf2011.meego.com/ San Francisco Meego Conference 2011]

== Logistics ==
May 23 - 25: San Francisco Regency Hyatt
* Annual industry event
* Announcements / Information focus
* Broader industry audience
* Call for Proposals and Registration will open early February

== Organizing Committee ==
[[File:Organizing committee.pdf]]

'''Team Lead: Amy Leeland'''

Advisory and Community Interface:
* Dawn Foster - Community Management
* Quim Gil - Marketing Management

Program Committee:
* Lead: Dirk Hohndel
* Carsten Munk
* Thiago Maciera
* Ashley Walker (Speaker Management)

Coordination:
* Lead: Brian Warner Sponsorships
* AJ Reed: Post Event management
* Mike Shaver: Web Management
* Dave Neary: Early Bird Events

== Call for proposals ==

* [http://sf2011.meego.com/program/call-session-proposals CfP]
* [[MeeGo Conference Spring 2011/CfP Drafting|Draft CfP]]

== Hyatt Space details==

Link to conference area map:[http://sanfranciscoregency.hyatt.com/hyatt/images/hotels/sfors/floorplan.pdf]

'''2nd Floor ''Street Level'' entrance'''
*Grand Ballroom A+B+C will be used as our Keynote room with redundant Screens/Sound in Market Street Foyer and Grand Ballroom Foyer (Seats 1300, with 100 standing in lobby spaces and feeds coming out)
Breakouts and room descriptions as follows:
*1 Grand Ballroom A (700 theater)
*2 Grand Ballroom B (200 cab)
*3 Grand Ballroom C (200 cab)
*Tech Showcase will take place in Market Street Foyer and Grand Ballroom Foyer. Not to be just single table tops, requested 3 different orientations to choose from. Tea and Coffee will be available in Tech showcase area
*Registration + Welcome Kit fulfillment: Market Street Foyer and Grand Ballroom Foyer. Kits will be organized based upon gender/size, not name
*Media/Blogger Room: Regency A
*Keynote Prep Room: Regency B
*Event Office: Plaza Room

'''3rd floor ''Bay Level'''''
*4 Seacliff A-B (110 cab)
*5 Seacliff C-D (110 cab)
*6 Bayview Room A-B (200 cab)
*Platinum Meeting Rooms: Marina Room and Golden Gate room on Bay Level

'''4th floor ''Atrium Lobby Level'''''
*All Catering Breakfast, Lunch, breaks and receptions will be held in Atrium of Hotel
This includes Garden Room A+B, 13 Views Lounge, and Hospitality Room can seat up to 1400 in this area.
*Nokia Boardroom: Boardroom A [atrium]
*Intel Boardroom: Boardroom B [atrium]

'''1st Floor ''Pacific Concourse Level'''''
*This will all be used as Early Bird space partitioned rooms A-O (17,000 sq ft all partitionable) Saturday until Sunday evening then it will be………
*Hacker Lounge: Pacific Concourse K—O
*Meeting rooms partitioned in Pacific Concourse: A, B, C, D, E
*Gold sponsors get A and B
*Spaces F and G will be used as a meeting room bookable space

== Attendee information ==

For flight arrival & departure times, please see [[MeeGo Conference Spring 2011/Flight Information]] - feel free to add your own arrival & departure times, contact people to share taxis or meet up at the airport.

For sponsored attendees sharing rooms, please choose your sharing partner on the [[/Accommodation | accommodation page]], or we will assign the person sharing a room with you.

== MeeGo Conference Warm-Up ==

The MeeGo Conference Warm-Up will include workshops catering to MeeGo application developers, and tutorials to help people get started developing for the platform. We also plan to have some fun extra-curricular activities involving building things. The warm-up sessions will be held at the Hyatt in San Francisco (the conference hotel/ conference facility) on May 21-22, the weekend before the conference begins.

We will have two parallel tutorial tracks, on a range of topics related to MeeGo, and one workshop track where people can get together and work on programming problems or brainstorm application designs.

And we plan some fun activities throughout the weekend, including a Maker's Contest where contestants will have to use raw materials including balsa wood, paper clips, string, paper and glue to build a machine capable of launching a projectile (Trebuchet, slingshot, catapult, whatever) over a distance of ~10m. The results will be judged with a live-action Angry Birds contest. And every evening we'll be running Werewolf sessions.

=== Schedule ===

{| class="wikitable"
! Date/Time
! Tutorial 1
! Tutorial 2
! Workshop
|-
|Sat 21, 09:00 - 12:30
| [[#Introduction_to_Qt | Introduction to Qt ]]
| [[#Harmattan_for_developers | Harmattan for developers]]
| [[#UX_workshop | UX workshop ]]
|-
|Sat 21, 14:00 - 17:30
| [[#Introduction_to_Qt | Introduction to Qt]]
| [[#Community OBS | Community OBS & Software Distribution]]
| [[#UX_workshop | UX workshop]]
|-
|Sat 21, 18:00 - 19:30
| colspan="3" align="center" | [[#Makers_contest | Siege weapon building, live action Angry Birds]]
|-
|Sat 21, 21:00 - late
| colspan="3" align="center" | [[/Werewolf | Mini Werewolf]]
|-
|Sun 22, 09:00 - 12:30
| [[#Introduction_to_MeeGo_SDK | Introduction to MeeGo SDK]] ([http://appdeveloper.intel.com/events registration required])
| [[#Linux_developer_tools | Linux developer tools]]
| [[#Qt_development_workshop | Qt development workshop]]
|-
|Sun 22, 14:00 - 17:30
| [[#Introduction_to_MeeGo_SDK | Introduction to MeeGo SDK]] ([http://appdeveloper.intel.com/events registration required])
| [[#MeeGo_localisation | MeeGo localisation]]
| [[#Qt_development_workshop | Qt development workshop]]
|-
|Sun 22, 20:00 - late
| colspan="3" align="center" | [[/Werewolf | Mass Werewolf, MeeGo Conference 2011 version]]
|}

=== Introduction to Qt ===

Training course offered by Roland Krause from ICS and MeeGo community member Thomas Perl.

Topics covered include:
* Setting up the MeeGo SDK
* Installing MeeGo on the Device
* Installing and Configurating Qt SDK
* Configuring Qt Creator
* Intro to Qt Creator
* Understanding QMake
* Building your First Application
* Introduction to PySide
* Introduction to QML
** Elements
** Properties and Types
** Signals
** Anchoring and Positioning
** States
** Transitions
** Simple Animations

=== Harmattan for developers ===
Presented by Daniel Wilms

... description pending ...

=== Community OBS ===
David Greaves, Niels Breet and Henri Bergius will take you through the basics of using Community OBS, uploading your project, getting it built and packaged automatically, fixing any build issues, and making the software available on the community software downloads site.

This will be part tutorial, part hands-on workshop, part BOF.

=== UX workshop ===

Developers are invited to turn up and present their applications to other attendees and our UX experts, and identify together areas of improvement and possible designs for presenting the same functionality to the use.

=== Makers contest ===

10 teams of 3 to 4 people will have one hour to build the best siege weapon possible for a live action Angry Birds round which will decide the winner. Trebuchet, catapult or slingshot, the weapon must be able to send an Angry Bird bean-bag into a pre-arranged structure containing evil snorting pigs. The winner will be determined by our impartial judges and comperes, Dave Neary, Alison Chaiken & Julien Fourgeaud.

Equipment available to teams will include: various balsa wood cuts, glue guns and glue sticks, twine, paper clips, plain brown paper and elastic bands. There may be some other surprise materials thrown in on the day, if we're feeling generous.

=== Introduction to MeeGo SDK ===

'''Important: You need to [http://appdeveloper.intel.com/events register in advance] if you want to attend this session'''

The Intel AppUpSM Application Lab: MeeGo series will be in San Francisco for the MeeGo Conference Warm Up! Register now to Meet Bob Spencer from the MeeGo SDK team and members of the Intel AppUpSM developer program team to learn how to create and deploy MeeGo applications using the MeeGo SDK and the Intel AppUpTM SDK for MeeGo. Discover how to create exciting user experiences with MeeGo* and the Intel AppUpSM developer program. MeeGo promotes innovation and portability across multiple device types, such as tablets, netbooks and smartphones. Developing for MeeGo presents a great opportunity to make money and deploy your applications quickly and easily. You don't have to be attending the MeeGo Conference to attend this event!

Join us at The Hyatt Regency San Francisco Embarcadero Centre on Sunday, May 22, 2011 for one of our FREE training sessions to learn how to develop applications for MeeGo and the benefits of the Intel AppUpSM developer program. Two sessions are available to choose from:

Sunday, May 22: 9:00am - 12:30pm
Sunday, May 22: 2:00pm - 5:30pm

General Agenda:
* Doors open 30 minutes before each session start for check-in (check-in closes 10 minutes after start)
* Session Content
** Overview of the Intel AppUpSM center & Intel AppUpSM developer program
** Introduction to the MeeGo SDK
** Introduction to the Intel AppUpTM SDK Suite for MeeGo
** Application packaging and submission
* Talk to Intel engineers about your specific code & questions with an information Q&A session

Seating is limited so [http://appdeveloper.intel.com/events register today] at http://appdeveloper.intel.com/events

=== Linux developer tools ===

An overview of common Linux developer tools, including git, gdb and valgrind, by timeless.

'''Using MXR'''

* For Triagers -- when you get a crash trace
** Using identifier searches to walk through a stack trace
** When you get a bug report in a foreign language, using text
searches to work from the foreign report to the codebase's native
language
* For Architects -- when you want to understand the ramifications of
changing an API
** Using text searches to find
** Using identifier searches to
* For Linguists
** Using filtered text searches to get more awareness of context
* For themers
** When you see an image in the ui and need to find its name
* Aiding MXR
** Fields packagers can use to provide directory descriptions

=== MeeGo localisation ===

Margie Foster will discuss the localisation process for MeeGo. This is not a "formal" tutorial, since Dimitris Glezos cannot be there. Margie hopes to have an active discussion about the localisation process, and share upcoming milestones in the MeeGo UX localisation schedule. She plans to cover:
* How to extract translatable strings from an application--both QML-based and using "gettext"
* The process of using QTLinguist and Transifex to translate the strings
* Describe how the strings get from Transifex into MeeGo
* Describe how the language packs are generated
* Discuss how you as a developer can compile and test your translated application

=== Qt development workshop ===

A programming problem will be presented, and attendees will have a hands-on programming lab, with amateurs and experts on hand to help you out when you get into trouble. If you'd like to help out as an assistant during this training session, please add your name here:

'''Qt/QML/UI experts'''

* Thomas Perl
* Sampo Savola

== Hacker Lounge ==
Was a very popular activity for community members. Having it stocked with beer and snacks was perfect, and we'd love to do something similar for spring.

== Ideas for fun activities ==
* [http://www.bahiker.com/northbayhikes/stinson.html Hike in Marin County on Mt. Tamalpais] just across the Golden Gate Bridge and get great views of San Francisco (when it's not foggy). Potentially led by [[User:Alison| Alison Chaiken]]. Would require transportation to the trailhead from the hotel, perhaps a 45-minute drive.
* [http://www.blazingsaddles.com/store/?catid=7 Cycle across the Golden Gate Bridge], potentially guided by [[User:Alison| Alison Chaiken]]. The route is pancake flat but is on a regular city street with low-speed traffic. [http://www.blazingsaddles.com/maps-and-rides/san-francisco-self-guided-tours.aspx Riding across the Bridge] does require some caution on foggy days due to a wet surface. (Foggy days can occur any time of year.) I have inquired about group discounts. The bike rental is walkable from the hotel.
* The [[MeeGo_Conference_2010/Werewolf]] was popular, and we're scheming on some additional [[MeeGo_Conference_Spring_2011/Werewolf]] MeeGo Werewolf variations for 2010.

[[File:Example.jpg]]

QtInternationalizationOld

2011-05-09T14:30:14Z

Margie:

MAY 9, 2011: THIS IS AN OUTDATED DOCUMENT THAT IS NOT THE WAY L10N IS DONE FOR MEEGO. PLEASE SEE: [[Internationalization]]
===Purpose===
The goal of this document is to educate translators to use QtCreator and Linguist with the Qt/MTF-based MeeGo reference applications that have followed the [http://wiki.meego.com/Internationalization MeeGo Internationalization wiki]. This will not apply to '''all''' applications or libraries. The need for these steps is driven by the [http://wiki.meego.com/Internationalization recommended steps for internationalization of the Qt/MTF-based MeeGo Reference Applications]. Please read those instructions for any necessary context or explanation as to why it is the way it is.

As of the writing of this HOWTO (Septemper 22, 2010) the list of applications with translation projects already created include:
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-music-translations meego-handset-music-translations]
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-sms-translations meego-handset-sms-translations]
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-diaer-translations meego-handset-dialer-translations]
* [http://meego.gitorious.org/meego-handset-ux/fennec-qt-translations fennec-qt-translations]
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-chat-translations meego-handset-chat-translations]
* [http://meego.gitorious.org/meego-handset-ux/meegotouchcp-chat-translations meegotouchcp-chat-translations]
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-socialweb-translations meego-handset-socialweb-translations]
* [http://meego.gitorious.org/meego-handset-ux/meegotouchcp-socialweb-translations meegotouchcp-socialweb-translations]

===Assumptions===
This process assumes the following environment will be used to perform translations:
* The project to be translated is structured according to the [http://wiki.meego.com/Internationalization Internationalization] wiki
* Translation is happening on a Linux OS (MeeGo and Ubuntu were tested, Fedora ''should'' work too)
* QtCreator package is installed
* Linguist package is installed
* The xdg-utils package is installed
* Git package is installed

It is also assumed that the translator is:
* Completely familiar with Linquist. It is beyond the scope of this document to help with the use of Linquist.
* Familiar with Linux-based OSes and how to install packages into the Linux OS they are using
* Familiar in principle with the basic concepts of Version Control Systems, in particular, Git.
* Has the necessary accounts and rights to push changes to source trees for translations hosted on gitorious.org

Finally, it is assumed that once Transifex has support for Qt projects and Linguist, this process will become obsolete and all further translations will occur through Transifex.

===Process Summary===
The basic process, detailed below is:
# Customize QtCreator to launch Linguist
# Check out project sources (read-only) to provide code context. This step is optional, but recommended
# Check out project translations (read-write)
# Make changes to .ts files
# Publish updated translations back to upstream translation project

==Set External Editor==
# Start QtCreator
# Select "Options..." from the "Tools" menu:

:[[Image:QtCreator-Tools-Options.png]]
# Select "Environment" -> "General" option
# Change the value of "External Editor:" as follows:
## Erase the default setting (can be restored by clicking the "Back Arrow" button to the right)
## Type in "xdg-open %f"
##* Assumes you have the xdg-utils package installed
##* %f will be replaced with the file name to be opened
## Click "OK"

:[[Image:QtCreator-Tools-Options-Environment-General.png]]

==Clone Project Source==
For Qt/MTF-based projects that used the [http://wiki.meego.com/Internationalization MeeGo Internationalization wiki] to prepare their code for translation, you must first clone the base project sources if you want Linguist to be able to load the code in the context pane while translating.
* Start QtCreator (if not already running)
* Select "New File or Project" from the "File" menu:

:[[Image:QtCreator-New.png]]

* Select "Git Repository Clone"

:[[Image:QtCreator-New-Git.png]]

* Click "OK"
* Set clone options as follows:
** Clone URL example: git://gitorious.org/meego-handset-ux/meego-handset-dialer.git
** '''NOTE:''' We are using the "git" protocol here since we really '''do not''' want to be able to push changes to this project. It is only being cloned for contextual reference
** Checkout Directory: meego-handset-dialer
** Path: ~/dev/translations/

:[[Image:QtCreator-New-Git-Clone-Options.png]]

* Click "Next"
* Click "Finish"

You will now have a new project opened that is cloned from the upstream sources. For translation purposes, there is never any need to edit any of these files, so for simplicity sake, and to avoid confusion, it would be safest to close this project now.

==Clone Project Translations==
Now you must open a new project that is a clone of the above projects' translation sources.
* Start QtCreator (if not already running)
* Select "New File or Project" from the "File" menu:

:[[Image:QtCreator-New.png]]

* Select "Git Repository Clone"

:[[Image:QtCreator-New-Git.png]]

* Click "OK"
* Set clone options as follows:
** Clone URL example: git@gitorious.org:meego-handset-ux/meego-handset-dialer-translations.git
*: '''NOTE:''' We are using the "ssh" protocol here since we '''do''' want to be able to push changes to this project.
**: This assumes you've properly configured your local system's git configuration to work with gitorious.org and the SSH key-based authentication (this is beyond the scope of this document).
** Checkout Directory: meego-handset-dialer-translations
** Path: ~/dev/translations/

:[[Image:QtCreator-New-Git-Clone-Options-2.png]]

* Click "Next"
* Click "Finish"

You are now using the new project for the translations you want to work on. To see the list of files in QtCreator, change the "Projects" pane to "File System" and you will see the list of .ts files available to work on.

Now let's get to editing and saving your work.

==Edit a Translation File==
* Open the .ts file to work on (double-click its entry in the "File System" list)
* Open a file in the ([[#Set External Editor|previously configured]]) external editor by selecting "Open in External Editor" from the "Edit" -> "Advanced" menu:
*:''Alternatively, press <alt-v><alt-i> on the keyboard''

:[[Image:QtCreator-Open-External.png]]

* Linguist should now launch, with the file opened above loaded and ready for translation.

:[[Image:QtCreator-External-Linguist.png]]

* Begin your translation work and proceed to [[#Publish Changes]] when ready to save and push your changes to the upstream translation project.

==Publish Changes==
===Sync Changes to QtCreator===
Now that you have completed a set of changes, you must save them and re-sync QtCreator to be aware the file has changed.
* Select "Save" (or "Exit") from the "File" menu to save your changes (and, optionally, exit Linguist)
* QtCreator will notice that the file has changed and ask if you want to reload the changes:

:[[Image:QtCreator-File-Changed.png]]

* Select "Yes"
* You should now see the changes reflected in the source view panel in QtCreator.

===Commit Changes to GIT===
Assuming you want to keep these changes, you must "commit" them to your local clone of the translation git tree:
* Select "Commit" from the "Tool" -> "Git" menu:

:[[Image:QtCreator-Git-Commit.png]]

* Provide details about the changes you are about to commit:
*: Commit Information:
*:: Please use your '''Full Name''' and '''valid email''' address
*: Description:
*:: A complete and detailed description is best, though for initial translations, simply stating so is enough
*: Files:
*:: Don't forget to "check" the file(s) in the list that are associated with the above set of changes. If you do not, changes to files not "checked" will not get published!
* Click "Commit"

:[[Image:QtCreator-Git-Commit-Options.png]]

* Confirm the commit (un-check the "Prompt to Submit" if you want to avoid this dialog in the future):

:[[Image:QtCreator-Git-Commit-Confirm.png]]

===Push Commits Upstream===
Finally, in order for these changes to be visible to others, especially those responsible for packaging new versions, you must "push" (publish) them back to the upstream git tree
** Select "Push" from the "Tool" -> "Git" menu:

:[[Image:QtCreator-Git-Commit-Push.png]]

'''NOTE:''' The process for getting updated translations packaged and published in the MeeGo RPM repos is beyond the scope of this document.

[[Category:Localization]]

L10N Chatter

2011-04-25T14:55:48Z

Margie: /* Let's use this page for miscellaneous items */

== Let's use this page for miscellaneous items ==

25 April 2011: Planning is underway for the MeeGo Conference in San Francisco in May. I hope that many of you will be able to attend. Let's plan on meeting at some point to talk about the MeeGo Translation Project and milestones for the next few months.

12 February 2010: Our l10n mailing list seems to be considered spam at Yahoo. Periodically, my inbox gets dozens of bounces, all from Yahoo email addresses. I have tried to reason with the folks at Yahoo, that we are a legitimate mailing list and not a spammer, to no avail. So, if you have a Yahoo address, you might not get the emails from this list.

[[Category:Localization]]

L10N Chatter

2011-04-25T14:54:24Z

Margie: /* Let's use this page for miscellaneous items */

== Let's use this page for miscellaneous items ==

Our l10n mailing list seems to be considered spam at Yahoo. Periodically, my inbox gets dozens of bounces, all from Yahoo email addresses. I have tried to reason with the folks at Yahoo, that we are a legitimate mailing list and not a spammer, to no avail. So, if you have a Yahoo address, you might not get the emails from this list.

25 April 2011: Planning is underway for the MeeGo Conference in San Francisco in May. I hope that many of you will be able to attend. Let's plan on meeting at some point to talk about the MeeGo Translation Project and milestones for the next few months.

[[Category:Localization]]

QtInternationalization

2011-04-11T16:33:14Z

Margie: /* Supported locales */

This is a developer's guide to internationalization (i18n) within the MeeGo UX project.

==Localizable Strings==

The most basic step in internationalization is to identify any user-visible strings in your application and replace them with code that looks up the appropriate string for the current locale. The way this is accomplished in Qt C++ code is to simply wrap the string with tr():

<pre>QString label = tr("Ring tone:");</pre>

This is accomplished in Qt Quick (QML) code by wrapping the string with qsTr():

<pre>Text {
id: dialogTitle
text: qsTr("Find contacts")
...</pre>

There is a Qt command-line tool ''lupdate'' that scans source code for these tr() and qsTr() macros and pulls out the identified strings. It writes them into a ".ts file," an XML-format file that lists information about where the strings were found. In ux projects, we generate these TS files automatically when creating the dist tarball that we push to OBS.

Your top-level .pro file should have lines like these:

<pre>TRANSLATIONS += .qml lib/.h lib/*.cpp
PROJECT_NAME = meego-app-example

dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += git clone . $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION}/.git &&
dist.commands += rm -f $${PROJECT_NAME}-$${VERSION}/.gitignore &&
dist.commands += mkdir -p $${PROJECT_NAME}-$${VERSION}/ts &&
dist.commands += lupdate $${TRANSLATIONS} -ts $${PROJECT_NAME}-$${VERSION}/ts/$${PROJECT_NAME}.ts &&
dist.commands += tar jcpvf $${PROJECT_NAME}-$${VERSION}.tar.bz2 $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += echo; echo Created $${PROJECT_NAME}-$${VERSION}.tar.bz2</pre>

Make sure that TRANSLATIONS is set to include all files with translatable strings (you may need to include other subdirectories and .js files, for instance). Make sure that PROJECT_NAME is set to your application name.

Whenever you check in an update to OBS, you should create a clean tarball to check in by running "make dist" from your toplevel directory which will execute the commands above. Then copy the generated tarball up to OBS. Bump the version up once a week. You should never submit an "sr" for the same version twice. But you can push to OBS multiple times throughout the week without doing an "sr."

Later these TS files are translated into various languages, and each one is compiled into a .qm binary file that allows efficient string lookup at runtime. Elsewhere you need to load a translator for each .qm file in your app, but this is handled automatically by our meego-qml-launcher for QML applications, so you generally don't have to think about. You just name your .ts file with your package name and it will be handled correctly.

==String Concatentation==

A common pitfall for i18n is building up strings by concatenation. You do this using assumptions about grammar and order that are true for your own language, but may not be true for another language. For example, consider this code:

<pre>function getBestPepperColor() {
return qsTr("red")
}

var message = qsTr("Tabasco is made from peppers selected using a ") + getBestPepperColor() + qsTr(" stick")</pre>

But in French, "red stick" is "bâton rouge". If you use concatenation as above, it will come out as "rouge bâton" in translation... incorrect!

So here's the solution:

<pre>var message = qsTr("Tabasco is made from peppers selected using a %1 stick").arg(getBestPepperColor())</pre>

Now the French translator will come up with something like:
<source>Tabasco est faite à partir de piments sélectionnés à l'aide d'un bâton %1.</source>
They are able to move the %1 around to the right place for their language.

Another example is where there are multiple variables in the string. The order of the variables may need to change in translation. This cannot happen if you're concatenating.

Wrong:

<pre>// dateHeader will be e.g. "March 14th"
var dateHeader = getLocalizedMonth() + " " + getLocalizedDay()</pre>

This looks right because the month and day are localized, but in another language maybe the day needs to come first, like "14??? ?????" in Russian.

Right:

<pre>// localized date header: %1 is month, %2 is day of month
var dateHeader = qsTr("%1 %2").arg(getLocalizedMonth()).arg(getLocalizedDay())</pre>

'''Note:''' There is a problem with the tools in QML in that the translator will only see "%1 %2" so they won't know what to do with it. In Qt, you can pass a second argument to tr() to give the translator a hint, for example:

<pre>QString dateFormat(tr("%1 %2", "%1 is the month, %2 is the day of the month"));
QString dateHeader = dateFormat.arg(getLocalizedMonth(), getLocalizedDay());</pre>

Also notice that the "arg()" function on QString can take multiple arguments, unlike in QML (to my knowledge).

==Supported locales==

The locales which must be enabled, per http://bugs.meego.com, are:
* American English (en_US)
* British English (en_GB)
* French (fr)
* Spanish (es)
* German (de)
* Italian (it)
* Polish (pl)
* Dutch (nl)
* Russian (ru)
* Swedish (sv)
* Finnish (fi)
* Brazilian-Portuguese (pt_BR)
* Canadian-French (fr_CA)
* Portuguese (pt)
* Japanese (ja)
* Korean (ko)
* Chinese Simplified (zh_CN)
* Chinese Traditional (zh_TW)

If in doubt of a language code, see here: http://www.transifex.net/languages/

[[Category: Localization]]

QtInternationalization

2011-04-11T16:30:46Z

Margie:

This is a developer's guide to internationalization (i18n) within the MeeGo UX project.

==Localizable Strings==

The most basic step in internationalization is to identify any user-visible strings in your application and replace them with code that looks up the appropriate string for the current locale. The way this is accomplished in Qt C++ code is to simply wrap the string with tr():

<pre>QString label = tr("Ring tone:");</pre>

This is accomplished in Qt Quick (QML) code by wrapping the string with qsTr():

<pre>Text {
id: dialogTitle
text: qsTr("Find contacts")
...</pre>

There is a Qt command-line tool ''lupdate'' that scans source code for these tr() and qsTr() macros and pulls out the identified strings. It writes them into a ".ts file," an XML-format file that lists information about where the strings were found. In ux projects, we generate these TS files automatically when creating the dist tarball that we push to OBS.

Your top-level .pro file should have lines like these:

<pre>TRANSLATIONS += .qml lib/.h lib/*.cpp
PROJECT_NAME = meego-app-example

dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += git clone . $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION}/.git &&
dist.commands += rm -f $${PROJECT_NAME}-$${VERSION}/.gitignore &&
dist.commands += mkdir -p $${PROJECT_NAME}-$${VERSION}/ts &&
dist.commands += lupdate $${TRANSLATIONS} -ts $${PROJECT_NAME}-$${VERSION}/ts/$${PROJECT_NAME}.ts &&
dist.commands += tar jcpvf $${PROJECT_NAME}-$${VERSION}.tar.bz2 $${PROJECT_NAME}-$${VERSION} &&
dist.commands += rm -fR $${PROJECT_NAME}-$${VERSION} &&
dist.commands += echo; echo Created $${PROJECT_NAME}-$${VERSION}.tar.bz2</pre>

Make sure that TRANSLATIONS is set to include all files with translatable strings (you may need to include other subdirectories and .js files, for instance). Make sure that PROJECT_NAME is set to your application name.

Whenever you check in an update to OBS, you should create a clean tarball to check in by running "make dist" from your toplevel directory which will execute the commands above. Then copy the generated tarball up to OBS. Bump the version up once a week. You should never submit an "sr" for the same version twice. But you can push to OBS multiple times throughout the week without doing an "sr."

Later these TS files are translated into various languages, and each one is compiled into a .qm binary file that allows efficient string lookup at runtime. Elsewhere you need to load a translator for each .qm file in your app, but this is handled automatically by our meego-qml-launcher for QML applications, so you generally don't have to think about. You just name your .ts file with your package name and it will be handled correctly.

==String Concatentation==

A common pitfall for i18n is building up strings by concatenation. You do this using assumptions about grammar and order that are true for your own language, but may not be true for another language. For example, consider this code:

<pre>function getBestPepperColor() {
return qsTr("red")
}

var message = qsTr("Tabasco is made from peppers selected using a ") + getBestPepperColor() + qsTr(" stick")</pre>

But in French, "red stick" is "bâton rouge". If you use concatenation as above, it will come out as "rouge bâton" in translation... incorrect!

So here's the solution:

<pre>var message = qsTr("Tabasco is made from peppers selected using a %1 stick").arg(getBestPepperColor())</pre>

Now the French translator will come up with something like:
<source>Tabasco est faite à partir de piments sélectionnés à l'aide d'un bâton %1.</source>
They are able to move the %1 around to the right place for their language.

Another example is where there are multiple variables in the string. The order of the variables may need to change in translation. This cannot happen if you're concatenating.

Wrong:

<pre>// dateHeader will be e.g. "March 14th"
var dateHeader = getLocalizedMonth() + " " + getLocalizedDay()</pre>

This looks right because the month and day are localized, but in another language maybe the day needs to come first, like "14??? ?????" in Russian.

Right:

<pre>// localized date header: %1 is month, %2 is day of month
var dateHeader = qsTr("%1 %2").arg(getLocalizedMonth()).arg(getLocalizedDay())</pre>

'''Note:''' There is a problem with the tools in QML in that the translator will only see "%1 %2" so they won't know what to do with it. In Qt, you can pass a second argument to tr() to give the translator a hint, for example:

<pre>QString dateFormat(tr("%1 %2", "%1 is the month, %2 is the day of the month"));
QString dateHeader = dateFormat.arg(getLocalizedMonth(), getLocalizedDay());</pre>

Also notice that the "arg()" function on QString can take multiple arguments, unlike in QML (to my knowledge).

==Supported locales==

The locales which must be enabled, per http://bugs.meego.com, are:
* American English (en_US)
* British English (en_GB)
* French (fr)
* Spanish (es)
* German (de)
* Italian (it)
* Polish (pl)
* Dutch (nl)
* Russian (ru)
* Swedish (sv)
* Finnish (fi)
* Brazilian-Portuguese (pt_BR)
* Canadian-French (fr_CA)
* Portuguese (pt)
* Japanese (ja)
* Korean (ko)
* Chinese Simplified (zh_CN)
* Chinese Traditional (zh_TW)

If in doubt of a language code, see here: http://www.meego.transifex.net/languages/

[[Category: Localization]]

LocalizationMeetings

2011-02-23T01:20:18Z

Margie: /* Next L10N meeting */

== '''Next L10N meeting''' ==

==== February 23, 2011 ====CANCELED

Margie has very early morning jury duty. The meeting will be rescheduled as soon as she knows her schedule. 
The L10N team is having an IRC meeting on Wednesday 23 February 2011,[http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=23&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* MeeGo 1.2 update
* Transifex update
* Conference in May in San Francisco

Full log from the meeting: will be posted 
Summary of the meeting: will be posted

== Older meetings ==

==== January 26, 2011 ====

The L10N team is having an IRC meeting on Wednesday 26 January 2011,[http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=26&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* Overview of what's been happening
* MeeGo 1.2 string freeze
* Transifex update

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-15.00.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-15.00.html

==== November 4, 2010 ====

The L10N team is having an IRC meeting on Thursday 4 November 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=4&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* MeeGo 1.1 release
* MeeGo 1.2 schedule
* New process for langpacks using Transifex

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.html

==== October 28, 2010 ====

CANCELED

==== October 14, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 14 October 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Status of beta testing of the new version of Transifex
* Qt localization process update
* MeeGo releases: 1.1, 1.2
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.html

==== September 23, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 23 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=23&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex update (Dimitris, Diego)
* Update on OBS requirements for TX (Margie)
* Update on wiki pages for release timeline (code freeze, integrating translations)
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.html

==== September 9, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 9 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=9&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex testing
* MeeGo schedule and roadmap updates
* Margie's action items from last meeting
* Dublin conference update
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.txt

==== August 19, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 19 August 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=19&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Dublin conference in November
* Update on qt support in Transifex (Dimitris, Diego)
* MeeGo 1.1 schedule
* Adding new languages to MeeGo
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.log.html 
Summary of the meeting: Minutes (text): http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.txt

==== July 29, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 29 July 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Report on meego.transifex.net
* Bugzilla features/requests
* MeeGo roadmap update
* OSCON update: who all went?
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.html

==== July 15, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 15 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=15&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

We had a last minute change of agenda. We devoted the meeting to questions and answers on our new hosted Transifex server: http://meego.transifex.net.

* Update on qt translation process
* Update on GNOME and Transifex
* Report on meego.transifex.net
* OSCON update
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.html

==== July 1, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 1 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=1&year=2010&hour=14&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex migration update
* Update on online help translation process
* Update on MeeGo 1.0 update release
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.html

==== June 17, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 17 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=17&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Mallard report out: Og Maciel
* Drupal report out: Claudius
* Update on the migration to meego.transifex.net
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.html

==== June 3, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 3 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=3&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* MeeGo release status
* Migration to meego.transifex.net
* Language criteria: essential packages versus 100% translated
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.html

==== April 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the fourth IRC meeting on Monday 19 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* Dimitris and Margie report-out on Collaboration Summit
* Community integration updates (related to Transifex migration)
* MeeGo schedule and translation status update
* Some ramblings from the BOF at the summit last week: [[L10N_BOF_at_the_Collaboration_Summit]]

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.log.html
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.html

==== April 2, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the third IRC meeting on Friday 2 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* L10N plan update ([[L10n_plan]])
* Status of Transifex migration
* Collaboration Summit: MeeGo Day with a L10N session at the end
* MeeGo schedule and translation status update

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.html

==== March 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the second IRC meeting on Friday 19 March 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review minutes from last meeting
* L10N plan update ([[L10n_plan]])
* Transifex migration
* Collaboration Summit
* Increasing participation (contacting other community L10N groups, etc.)
* MeeGo translation status
* Next meeting
* Opens

Full log from the meeting: [[L10N_IRC_Meeting_March_19,_2010]] 
Summary of the meeting: [[L10n_meeting_summary_19_March]]

==== March 5, 2010 ====

Meeting time: 1600 UTC on March 5th

Meeting log posted here: [[L10N_IRC_Meeting_March_5,_2010]]

Meeting minutes summary here: [[L10n_meeting_summary]]

Agenda: (suggestions welcome)

* Steering group members/scope/accountability
* Localization teams
* Where to host project?
* L10n project plan
* Next steps

Issues:

* Do we inherit strings from Moblin? If so, how do we migrate existing strings to Transifex? By whom, by when?
* Should there be a sequence of providing translations by localization team like core things first, optional components later.
* Do we localize the web sites?

Full log from the meeting: [[L10N_IRC_Meeting_March_5,_2010]] 
Summary of the meeting: [[L10n_meeting_summary]]

[[Category:Localization]]

Events/Linux Foundation Collaboration Summit planning

2011-02-02T20:37:49Z

Margie: /* Please add additional, specific or new suggestions to this section */

'''Status: Work in Progress, not final plans.'''

==Overview==

[http://events.linuxfoundation.org/events/collaboration-summit Linux Foundation Collaboration Summit] will be held April 6 - 8, and we will have a full day MeeGo Workgroup at the event. We did something similar last year: [http://events.linuxfoundation.org/lfcs2010/meego-workgroup MeeGo Workgroup Agenda for LFCS 2010].

===Logistics===

* Date: April 6 - 8
* Location: Hotel Kabuki in San Francisco, CA
* Time: 9am - 6pm (need to confirm times)

===Decisions / Options===

To be decided after we do more work on the proposed sessions (below):
* Stick to a one day conference with a tight schedule that applies to everyone?
* OR have a 2 day workgroup with more information?
* IF we did a 2 day workgroup, we could have the broad, general sessions on Day 1 and more detailed, specific sessions on Day 2.

==Content Overview==

The purpose of this day is to give people who are new to MeeGo more information while also providing new updates to current contributors and people already participating in MeeGo.

Presentations should be:
* Mostly technical or relevant to MeeGo platform developers, application developers and other community contributors.
* Relevant to a broad audience - we only have one track, so we won't be able to accommodate niche topics (save those for the [[MeeGo Conference]] in May).

==Session Plan==

Please do not add new suggestions to this section (use the sections below for new suggestions).

* TSG Q&A with Imad / Valtteri
* MeeGo Architecture
* Compliance
* 1-2 application development / SDK talks
* Vertical program and / or WG updates and maybe demos (IVI, Handset, core, etc.) - maybe just 20-30 minutes each?
* Community Office update (metrics, events & marketing)
* Product Showcase: 5 or 10 minute talks or demos from people working on interesting MeeGo products or applications.
* Breakouts / BOFs: 4 breakout sessions in each corner of the room (no projector or microphones used).

===Product Showcase Suggestions===
5 or 10 minute talks or demos for people working on interesting MeeGo products or applications.

* Live demo of Transifex, the web-based, open source translation management tool we use for MeeGo.

===Breakouts / BOFs Suggestions===
4 breakout sessions for teams or hot topics. These would need to be in 4 corners of the same room, so (no projector or microphones used). This would also need to be at the end of the last day, since we'll need to rearrange the room a bit to accommodate.

* Localization session explaining the new langpacks for 1.2 and the new features of Transifex

===Please add additional, specific or new suggestions to this section===

Extra credit for suggesting a speaker for your suggestion.

* Dimitris Glezos or me (Margie Foster) for the localization session.
* Dimitris Glezos for the live Transifex demo.

==Other Ideas or Feedback==

Add any general ideas or feedback as bullets here.

* Your idea here.

Events/Linux Foundation Collaboration Summit planning

2011-02-02T20:36:51Z

Margie: /* Product Showcase Suggestions */

'''Status: Work in Progress, not final plans.'''

==Overview==

[http://events.linuxfoundation.org/events/collaboration-summit Linux Foundation Collaboration Summit] will be held April 6 - 8, and we will have a full day MeeGo Workgroup at the event. We did something similar last year: [http://events.linuxfoundation.org/lfcs2010/meego-workgroup MeeGo Workgroup Agenda for LFCS 2010].

===Logistics===

* Date: April 6 - 8
* Location: Hotel Kabuki in San Francisco, CA
* Time: 9am - 6pm (need to confirm times)

===Decisions / Options===

To be decided after we do more work on the proposed sessions (below):
* Stick to a one day conference with a tight schedule that applies to everyone?
* OR have a 2 day workgroup with more information?
* IF we did a 2 day workgroup, we could have the broad, general sessions on Day 1 and more detailed, specific sessions on Day 2.

==Content Overview==

The purpose of this day is to give people who are new to MeeGo more information while also providing new updates to current contributors and people already participating in MeeGo.

Presentations should be:
* Mostly technical or relevant to MeeGo platform developers, application developers and other community contributors.
* Relevant to a broad audience - we only have one track, so we won't be able to accommodate niche topics (save those for the [[MeeGo Conference]] in May).

==Session Plan==

Please do not add new suggestions to this section (use the sections below for new suggestions).

* TSG Q&A with Imad / Valtteri
* MeeGo Architecture
* Compliance
* 1-2 application development / SDK talks
* Vertical program and / or WG updates and maybe demos (IVI, Handset, core, etc.) - maybe just 20-30 minutes each?
* Community Office update (metrics, events & marketing)
* Product Showcase: 5 or 10 minute talks or demos from people working on interesting MeeGo products or applications.
* Breakouts / BOFs: 4 breakout sessions in each corner of the room (no projector or microphones used).

===Product Showcase Suggestions===
5 or 10 minute talks or demos for people working on interesting MeeGo products or applications.

* Live demo of Transifex, the web-based, open source translation management tool we use for MeeGo.

===Breakouts / BOFs Suggestions===
4 breakout sessions for teams or hot topics. These would need to be in 4 corners of the same room, so (no projector or microphones used). This would also need to be at the end of the last day, since we'll need to rearrange the room a bit to accommodate.

* Localization session explaining the new langpacks for 1.2 and the new features of Transifex

===Please add additional, specific or new suggestions to this section===

Extra credit for suggesting a speaker for your suggestion.

* Your suggestions here.

==Other Ideas or Feedback==

Add any general ideas or feedback as bullets here.

* Your idea here.

Events/Linux Foundation Collaboration Summit planning

2011-02-02T20:35:50Z

Margie: /* Breakouts / BOFs Suggestions */

'''Status: Work in Progress, not final plans.'''

==Overview==

[http://events.linuxfoundation.org/events/collaboration-summit Linux Foundation Collaboration Summit] will be held April 6 - 8, and we will have a full day MeeGo Workgroup at the event. We did something similar last year: [http://events.linuxfoundation.org/lfcs2010/meego-workgroup MeeGo Workgroup Agenda for LFCS 2010].

===Logistics===

* Date: April 6 - 8
* Location: Hotel Kabuki in San Francisco, CA
* Time: 9am - 6pm (need to confirm times)

===Decisions / Options===

To be decided after we do more work on the proposed sessions (below):
* Stick to a one day conference with a tight schedule that applies to everyone?
* OR have a 2 day workgroup with more information?
* IF we did a 2 day workgroup, we could have the broad, general sessions on Day 1 and more detailed, specific sessions on Day 2.

==Content Overview==

The purpose of this day is to give people who are new to MeeGo more information while also providing new updates to current contributors and people already participating in MeeGo.

Presentations should be:
* Mostly technical or relevant to MeeGo platform developers, application developers and other community contributors.
* Relevant to a broad audience - we only have one track, so we won't be able to accommodate niche topics (save those for the [[MeeGo Conference]] in May).

==Session Plan==

Please do not add new suggestions to this section (use the sections below for new suggestions).

* TSG Q&A with Imad / Valtteri
* MeeGo Architecture
* Compliance
* 1-2 application development / SDK talks
* Vertical program and / or WG updates and maybe demos (IVI, Handset, core, etc.) - maybe just 20-30 minutes each?
* Community Office update (metrics, events & marketing)
* Product Showcase: 5 or 10 minute talks or demos from people working on interesting MeeGo products or applications.
* Breakouts / BOFs: 4 breakout sessions in each corner of the room (no projector or microphones used).

===Product Showcase Suggestions===
5 or 10 minute talks or demos for people working on interesting MeeGo products or applications.

* Your suggestions here.

===Breakouts / BOFs Suggestions===
4 breakout sessions for teams or hot topics. These would need to be in 4 corners of the same room, so (no projector or microphones used). This would also need to be at the end of the last day, since we'll need to rearrange the room a bit to accommodate.

* Localization session explaining the new langpacks for 1.2 and the new features of Transifex

===Please add additional, specific or new suggestions to this section===

Extra credit for suggesting a speaker for your suggestion.

* Your suggestions here.

==Other Ideas or Feedback==

Add any general ideas or feedback as bullets here.

* Your idea here.

LocalizationMeetings

2011-01-28T18:00:51Z

Margie: /* November 4, 2010 */

== '''Next L10N meeting''' ==

==== February 23, 2011 ====

The L10N team is having an IRC meeting on Wednesday 23 February 2011,[http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=23&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* MeeGo 1.2 update
* Transifex update
* Conference in May in San Francisco

Full log from the meeting: will be posted 
Summary of the meeting: will be posted

== Older meetings ==

==== January 26, 2011 ====

The L10N team is having an IRC meeting on Wednesday 26 January 2011,[http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=26&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* Overview of what's been happening
* MeeGo 1.2 string freeze
* Transifex update

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-15.00.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2011/meego-meeting.2011-01-26-15.00.html

==== November 4, 2010 ====

The L10N team is having an IRC meeting on Thursday 4 November 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=4&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* MeeGo 1.1 release
* MeeGo 1.2 schedule
* New process for langpacks using Transifex

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.html

==== October 28, 2010 ====

CANCELED

==== October 14, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 14 October 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Status of beta testing of the new version of Transifex
* Qt localization process update
* MeeGo releases: 1.1, 1.2
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.html

==== September 23, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 23 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=23&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex update (Dimitris, Diego)
* Update on OBS requirements for TX (Margie)
* Update on wiki pages for release timeline (code freeze, integrating translations)
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.html

==== September 9, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 9 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=9&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex testing
* MeeGo schedule and roadmap updates
* Margie's action items from last meeting
* Dublin conference update
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.txt

==== August 19, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 19 August 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=19&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Dublin conference in November
* Update on qt support in Transifex (Dimitris, Diego)
* MeeGo 1.1 schedule
* Adding new languages to MeeGo
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.log.html 
Summary of the meeting: Minutes (text): http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.txt

==== July 29, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 29 July 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Report on meego.transifex.net
* Bugzilla features/requests
* MeeGo roadmap update
* OSCON update: who all went?
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.html

==== July 15, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 15 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=15&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

We had a last minute change of agenda. We devoted the meeting to questions and answers on our new hosted Transifex server: http://meego.transifex.net.

* Update on qt translation process
* Update on GNOME and Transifex
* Report on meego.transifex.net
* OSCON update
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.html

==== July 1, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 1 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=1&year=2010&hour=14&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex migration update
* Update on online help translation process
* Update on MeeGo 1.0 update release
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.html

==== June 17, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 17 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=17&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Mallard report out: Og Maciel
* Drupal report out: Claudius
* Update on the migration to meego.transifex.net
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.html

==== June 3, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 3 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=3&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* MeeGo release status
* Migration to meego.transifex.net
* Language criteria: essential packages versus 100% translated
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.html

==== April 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the fourth IRC meeting on Monday 19 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* Dimitris and Margie report-out on Collaboration Summit
* Community integration updates (related to Transifex migration)
* MeeGo schedule and translation status update
* Some ramblings from the BOF at the summit last week: [[L10N_BOF_at_the_Collaboration_Summit]]

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.log.html
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.html

==== April 2, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the third IRC meeting on Friday 2 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* L10N plan update ([[L10n_plan]])
* Status of Transifex migration
* Collaboration Summit: MeeGo Day with a L10N session at the end
* MeeGo schedule and translation status update

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.html

==== March 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the second IRC meeting on Friday 19 March 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review minutes from last meeting
* L10N plan update ([[L10n_plan]])
* Transifex migration
* Collaboration Summit
* Increasing participation (contacting other community L10N groups, etc.)
* MeeGo translation status
* Next meeting
* Opens

Full log from the meeting: [[L10N_IRC_Meeting_March_19,_2010]] 
Summary of the meeting: [[L10n_meeting_summary_19_March]]

==== March 5, 2010 ====

Meeting time: 1600 UTC on March 5th

Meeting log posted here: [[L10N_IRC_Meeting_March_5,_2010]]

Meeting minutes summary here: [[L10n_meeting_summary]]

Agenda: (suggestions welcome)

* Steering group members/scope/accountability
* Localization teams
* Where to host project?
* L10n project plan
* Next steps

Issues:

* Do we inherit strings from Moblin? If so, how do we migrate existing strings to Transifex? By whom, by when?
* Should there be a sequence of providing translations by localization team like core things first, optional components later.
* Do we localize the web sites?

Full log from the meeting: [[L10N_IRC_Meeting_March_5,_2010]] 
Summary of the meeting: [[L10n_meeting_summary]]

[[Category:Localization]]

LocalizationMeetings

2011-01-28T18:00:06Z

Margie: /* January 26, 2011 */

== '''Next L10N meeting''' ==

==== February 23, 2011 ====

The L10N team is having an IRC meeting on Wednesday 23 February 2011,[http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=23&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* MeeGo 1.2 update
* Transifex update
* Conference in May in San Francisco

Full log from the meeting: will be posted 
Summary of the meeting: will be posted

== Older meetings ==

==== November 4, 2010 ====

The L10N team is having an IRC meeting on Thursday 4 November 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=4&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* MeeGo 1.1 release
* MeeGo 1.2 schedule
* New process for langpacks using Transifex

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.html

==== October 28, 2010 ====

CANCELED

==== October 14, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 14 October 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Status of beta testing of the new version of Transifex
* Qt localization process update
* MeeGo releases: 1.1, 1.2
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.html

==== September 23, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 23 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=23&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex update (Dimitris, Diego)
* Update on OBS requirements for TX (Margie)
* Update on wiki pages for release timeline (code freeze, integrating translations)
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.html

==== September 9, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 9 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=9&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex testing
* MeeGo schedule and roadmap updates
* Margie's action items from last meeting
* Dublin conference update
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.txt

==== August 19, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 19 August 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=19&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Dublin conference in November
* Update on qt support in Transifex (Dimitris, Diego)
* MeeGo 1.1 schedule
* Adding new languages to MeeGo
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.log.html 
Summary of the meeting: Minutes (text): http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.txt

==== July 29, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 29 July 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Report on meego.transifex.net
* Bugzilla features/requests
* MeeGo roadmap update
* OSCON update: who all went?
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.html

==== July 15, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 15 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=15&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

We had a last minute change of agenda. We devoted the meeting to questions and answers on our new hosted Transifex server: http://meego.transifex.net.

* Update on qt translation process
* Update on GNOME and Transifex
* Report on meego.transifex.net
* OSCON update
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.html

==== July 1, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 1 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=1&year=2010&hour=14&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex migration update
* Update on online help translation process
* Update on MeeGo 1.0 update release
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.html

==== June 17, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 17 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=17&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Mallard report out: Og Maciel
* Drupal report out: Claudius
* Update on the migration to meego.transifex.net
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.html

==== June 3, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 3 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=3&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* MeeGo release status
* Migration to meego.transifex.net
* Language criteria: essential packages versus 100% translated
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.html

==== April 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the fourth IRC meeting on Monday 19 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* Dimitris and Margie report-out on Collaboration Summit
* Community integration updates (related to Transifex migration)
* MeeGo schedule and translation status update
* Some ramblings from the BOF at the summit last week: [[L10N_BOF_at_the_Collaboration_Summit]]

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.log.html
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.html

==== April 2, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the third IRC meeting on Friday 2 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* L10N plan update ([[L10n_plan]])
* Status of Transifex migration
* Collaboration Summit: MeeGo Day with a L10N session at the end
* MeeGo schedule and translation status update

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.html

==== March 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the second IRC meeting on Friday 19 March 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review minutes from last meeting
* L10N plan update ([[L10n_plan]])
* Transifex migration
* Collaboration Summit
* Increasing participation (contacting other community L10N groups, etc.)
* MeeGo translation status
* Next meeting
* Opens

Full log from the meeting: [[L10N_IRC_Meeting_March_19,_2010]] 
Summary of the meeting: [[L10n_meeting_summary_19_March]]

==== March 5, 2010 ====

Meeting time: 1600 UTC on March 5th

Meeting log posted here: [[L10N_IRC_Meeting_March_5,_2010]]

Meeting minutes summary here: [[L10n_meeting_summary]]

Agenda: (suggestions welcome)

* Steering group members/scope/accountability
* Localization teams
* Where to host project?
* L10n project plan
* Next steps

Issues:

* Do we inherit strings from Moblin? If so, how do we migrate existing strings to Transifex? By whom, by when?
* Should there be a sequence of providing translations by localization team like core things first, optional components later.
* Do we localize the web sites?

Full log from the meeting: [[L10N_IRC_Meeting_March_5,_2010]] 
Summary of the meeting: [[L10n_meeting_summary]]

[[Category:Localization]]

LocalizationMeetings

2011-01-21T16:31:52Z

Margie: /* Agenda */

== '''Next L10N meeting''' ==

==== January 26, 2011 ====

The L10N team is having an IRC meeting on Wednesday 26 January 2011,[http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=26&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* Overview of what's been happening
* MeeGo 1.2 string freeze
* Transifex update

Full log from the meeting: will be posted 
Summary of the meeting: will be posted

== Older meetings ==

==== November 4, 2010 ====

The L10N team is having an IRC meeting on Thursday 4 November 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=4&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* MeeGo 1.1 release
* MeeGo 1.2 schedule
* New process for langpacks using Transifex

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.html

==== October 28, 2010 ====

CANCELED

==== October 14, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 14 October 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Status of beta testing of the new version of Transifex
* Qt localization process update
* MeeGo releases: 1.1, 1.2
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.html

==== September 23, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 23 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=23&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex update (Dimitris, Diego)
* Update on OBS requirements for TX (Margie)
* Update on wiki pages for release timeline (code freeze, integrating translations)
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.html

==== September 9, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 9 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=9&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex testing
* MeeGo schedule and roadmap updates
* Margie's action items from last meeting
* Dublin conference update
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.txt

==== August 19, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 19 August 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=19&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Dublin conference in November
* Update on qt support in Transifex (Dimitris, Diego)
* MeeGo 1.1 schedule
* Adding new languages to MeeGo
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.log.html 
Summary of the meeting: Minutes (text): http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.txt

==== July 29, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 29 July 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Report on meego.transifex.net
* Bugzilla features/requests
* MeeGo roadmap update
* OSCON update: who all went?
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.html

==== July 15, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 15 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=15&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

We had a last minute change of agenda. We devoted the meeting to questions and answers on our new hosted Transifex server: http://meego.transifex.net.

* Update on qt translation process
* Update on GNOME and Transifex
* Report on meego.transifex.net
* OSCON update
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.html

==== July 1, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 1 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=1&year=2010&hour=14&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex migration update
* Update on online help translation process
* Update on MeeGo 1.0 update release
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.html

==== June 17, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 17 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=17&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Mallard report out: Og Maciel
* Drupal report out: Claudius
* Update on the migration to meego.transifex.net
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.html

==== June 3, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 3 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=3&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* MeeGo release status
* Migration to meego.transifex.net
* Language criteria: essential packages versus 100% translated
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.html

==== April 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the fourth IRC meeting on Monday 19 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* Dimitris and Margie report-out on Collaboration Summit
* Community integration updates (related to Transifex migration)
* MeeGo schedule and translation status update
* Some ramblings from the BOF at the summit last week: [[L10N_BOF_at_the_Collaboration_Summit]]

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.log.html
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.html

==== April 2, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the third IRC meeting on Friday 2 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* L10N plan update ([[L10n_plan]])
* Status of Transifex migration
* Collaboration Summit: MeeGo Day with a L10N session at the end
* MeeGo schedule and translation status update

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.html

==== March 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the second IRC meeting on Friday 19 March 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review minutes from last meeting
* L10N plan update ([[L10n_plan]])
* Transifex migration
* Collaboration Summit
* Increasing participation (contacting other community L10N groups, etc.)
* MeeGo translation status
* Next meeting
* Opens

Full log from the meeting: [[L10N_IRC_Meeting_March_19,_2010]] 
Summary of the meeting: [[L10n_meeting_summary_19_March]]

==== March 5, 2010 ====

Meeting time: 1600 UTC on March 5th

Meeting log posted here: [[L10N_IRC_Meeting_March_5,_2010]]

Meeting minutes summary here: [[L10n_meeting_summary]]

Agenda: (suggestions welcome)

* Steering group members/scope/accountability
* Localization teams
* Where to host project?
* L10n project plan
* Next steps

Issues:

* Do we inherit strings from Moblin? If so, how do we migrate existing strings to Transifex? By whom, by when?
* Should there be a sequence of providing translations by localization team like core things first, optional components later.
* Do we localize the web sites?

Full log from the meeting: [[L10N_IRC_Meeting_March_5,_2010]] 
Summary of the meeting: [[L10n_meeting_summary]]

[[Category:Localization]]

MeeGo-Meeting IRC Schedule

2011-01-21T15:22:05Z

Margie: /* Regular Meetings */

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

== Regular Meetings ==

'''Monday'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|MeeGo Core Bug Triage Meetings]]: Every Monday at '''7:00 UTC'''

'''Tuesday'''
* [[Quality/meetings| QA Meetings]]: Every Tuesday at '''07:00 UTC'''
* [[SDK/Meetings/Release| SDK Meeting (Release)]]: Every Tuesday at '''08:00 UTC''', 10:00 EEST
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Netbook Bug Triage Meetings]]: Every Tuesday at '''13:00 UTC'''
* [[Community_Office/Meetings| Community Office Meeting]]: The 1st and 3rd Tuesday, alternating between '''20:00 UTC and 15:00 UTC'''
* [[Events/Meetings|Events Meeting]]: Every other Tuesday at '''17:00 UTC'''

'''Wednesday'''
* [[SDK/Meetings| SDK Meeting]]: Every Wednesday at '''05:30 UTC'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Handset Bug Triage Meetings]]: Every Wednesday at '''7:00 UTC'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MCTS Bug Triage Meetings]]: Every Wednesday at '''8:00 UTC'''
* [[L10n_meeting_schedule| Localization / L10n Meetings]]: monthly at '''15:00 UTC'''
* [[Technical_Steering_Group_meetings| Technical Steering Group Meeting]]: Every other Wednesday at '''20:00 UTC'''

'''Thursday'''
* [[ARM/N900/Meetings| MeeGo N900 Hardware Adaptation Meetings]]: Every Thursday at '''8:00 UTC'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Core Bug Triage Meetings]]: Every Thursday at '''13:00 UTC'''

'''Friday'''

'''Sunday'''
* [[Local_MeeGo_Networks/MeeGo_Network_Finland#Online_Community_Meetings | MeeGo Network Finland Meetings]]: The 1st and 3rd Sunday at '''16:00 UTC'''

== Ad Hoc Meetings ==

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

=== Guidelines ===

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

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

LocalizationMeetings

2011-01-21T15:21:24Z

Margie: /* October 28, 2010 */

== '''Next L10N meeting''' ==

==== January 26, 2011 ====

The L10N team is having an IRC meeting on Wednesday 26 January 2011,[http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=26&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* Overview of what's been happening
* MeeGo 1.1 string freeze
* Transifex update

Full log from the meeting: will be posted 
Summary of the meeting: will be posted

== Older meetings ==

==== November 4, 2010 ====

The L10N team is having an IRC meeting on Thursday 4 November 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=11&day=4&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* MeeGo 1.1 release
* MeeGo 1.2 schedule
* New process for langpacks using Transifex

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-11-04-13.59.html

==== October 28, 2010 ====

CANCELED

==== October 14, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 14 October 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Status of beta testing of the new version of Transifex
* Qt localization process update
* MeeGo releases: 1.1, 1.2
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.html

==== September 23, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 23 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=23&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex update (Dimitris, Diego)
* Update on OBS requirements for TX (Margie)
* Update on wiki pages for release timeline (code freeze, integrating translations)
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.html

==== September 9, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 9 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=9&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex testing
* MeeGo schedule and roadmap updates
* Margie's action items from last meeting
* Dublin conference update
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.txt

==== August 19, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 19 August 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=19&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Dublin conference in November
* Update on qt support in Transifex (Dimitris, Diego)
* MeeGo 1.1 schedule
* Adding new languages to MeeGo
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.log.html 
Summary of the meeting: Minutes (text): http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.txt

==== July 29, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 29 July 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Report on meego.transifex.net
* Bugzilla features/requests
* MeeGo roadmap update
* OSCON update: who all went?
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.html

==== July 15, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 15 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=15&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

We had a last minute change of agenda. We devoted the meeting to questions and answers on our new hosted Transifex server: http://meego.transifex.net.

* Update on qt translation process
* Update on GNOME and Transifex
* Report on meego.transifex.net
* OSCON update
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.html

==== July 1, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 1 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=1&year=2010&hour=14&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex migration update
* Update on online help translation process
* Update on MeeGo 1.0 update release
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.html

==== June 17, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 17 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=17&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Mallard report out: Og Maciel
* Drupal report out: Claudius
* Update on the migration to meego.transifex.net
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.html

==== June 3, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 3 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=3&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* MeeGo release status
* Migration to meego.transifex.net
* Language criteria: essential packages versus 100% translated
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.html

==== April 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the fourth IRC meeting on Monday 19 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* Dimitris and Margie report-out on Collaboration Summit
* Community integration updates (related to Transifex migration)
* MeeGo schedule and translation status update
* Some ramblings from the BOF at the summit last week: [[L10N_BOF_at_the_Collaboration_Summit]]

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.log.html
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.html

==== April 2, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the third IRC meeting on Friday 2 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* L10N plan update ([[L10n_plan]])
* Status of Transifex migration
* Collaboration Summit: MeeGo Day with a L10N session at the end
* MeeGo schedule and translation status update

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.html

==== March 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the second IRC meeting on Friday 19 March 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review minutes from last meeting
* L10N plan update ([[L10n_plan]])
* Transifex migration
* Collaboration Summit
* Increasing participation (contacting other community L10N groups, etc.)
* MeeGo translation status
* Next meeting
* Opens

Full log from the meeting: [[L10N_IRC_Meeting_March_19,_2010]] 
Summary of the meeting: [[L10n_meeting_summary_19_March]]

==== March 5, 2010 ====

Meeting time: 1600 UTC on March 5th

Meeting log posted here: [[L10N_IRC_Meeting_March_5,_2010]]

Meeting minutes summary here: [[L10n_meeting_summary]]

Agenda: (suggestions welcome)

* Steering group members/scope/accountability
* Localization teams
* Where to host project?
* L10n project plan
* Next steps

Issues:

* Do we inherit strings from Moblin? If so, how do we migrate existing strings to Transifex? By whom, by when?
* Should there be a sequence of providing translations by localization team like core things first, optional components later.
* Do we localize the web sites?

Full log from the meeting: [[L10N_IRC_Meeting_March_5,_2010]] 
Summary of the meeting: [[L10n_meeting_summary]]

[[Category:Localization]]

LocalizationMeetings

2011-01-21T15:20:31Z

Margie: /* Next L10N meeting */

== '''Next L10N meeting''' ==

==== January 26, 2011 ====

The L10N team is having an IRC meeting on Wednesday 26 January 2011,[http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=26&year=2011&hour=15&min=0&sec=0&p1=0 15:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

===== Agenda =====
* Overview of what's been happening
* MeeGo 1.1 string freeze
* Transifex update

Full log from the meeting: will be posted 
Summary of the meeting: will be posted

== Older meetings ==

==== October 28, 2010 ====

CANCELED

==== October 14, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 14 October 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Status of beta testing of the new version of Transifex
* Qt localization process update
* MeeGo releases: 1.1, 1.2
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-10-14-13.57.html

==== September 23, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 23 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=23&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex update (Dimitris, Diego)
* Update on OBS requirements for TX (Margie)
* Update on wiki pages for release timeline (code freeze, integrating translations)
* Dublin conference update
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-23-13.57.html

==== September 9, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 9 September 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=9&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex testing
* MeeGo schedule and roadmap updates
* Margie's action items from last meeting
* Dublin conference update
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-09-09-13.58.txt

==== August 19, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 19 August 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=19&year=2010&hour=14&min=0&sec=0&p1=0 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Dublin conference in November
* Update on qt support in Transifex (Dimitris, Diego)
* MeeGo 1.1 schedule
* Adding new languages to MeeGo
* Opens

Full log from the meeting: Log: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.log.html 
Summary of the meeting: Minutes (text): http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-19-13.57.txt

==== July 29, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 29 July 2010,14:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Report on meego.transifex.net
* Bugzilla features/requests
* MeeGo roadmap update
* OSCON update: who all went?
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-29-13.59.html

==== July 15, 2010 ====

Location: #meego-meeting

The L10N team is having an IRC meeting on Thursday 15 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=15&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

We had a last minute change of agenda. We devoted the meeting to questions and answers on our new hosted Transifex server: http://meego.transifex.net.

* Update on qt translation process
* Update on GNOME and Transifex
* Report on meego.transifex.net
* OSCON update
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-15-13.59.html

==== July 1, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 1 July 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=1&year=2010&hour=14&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Transifex migration update
* Update on online help translation process
* Update on MeeGo 1.0 update release
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-07-01-13.59.html

==== June 17, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 17 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=17&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* Mallard report out: Og Maciel
* Drupal report out: Claudius
* Update on the migration to meego.transifex.net
* Review of other action items
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-17-13.59.html

==== June 3, 2010 ====

Location: #meego-meeting

The L10N Working Group is having an IRC meeting on Thursday 3 June 2010,[http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=3&year=2010&hour=7&min=0&sec=0&p1=224 14:00 UTC time]. The meeting will be held in the #meego-meeting IRC channel.

* MeeGo release status
* Migration to meego.transifex.net
* Language criteria: essential packages versus 100% translated
* Opens

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-06-03-13.59.html

==== April 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the fourth IRC meeting on Monday 19 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* Dimitris and Margie report-out on Collaboration Summit
* Community integration updates (related to Transifex migration)
* MeeGo schedule and translation status update
* Some ramblings from the BOF at the summit last week: [[L10N_BOF_at_the_Collaboration_Summit]]

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.log.html
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-19-15.57.html

==== April 2, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the third IRC meeting on Friday 2 April 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review To-Do items from previous meetings
* L10N plan update ([[L10n_plan]])
* Status of Transifex migration
* Collaboration Summit: MeeGo Day with a L10N session at the end
* MeeGo schedule and translation status update

Full log from the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.log.html 
Summary of the meeting: http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-04-02-15.57.html

==== March 19, 2010 ====

Location: #meego-meeting

The L10N Working Group is having the second IRC meeting on Friday 19 March 2010, 16:00 UTC time. The meeting will be held in the #meego-meeting IRC channel.

* Review minutes from last meeting
* L10N plan update ([[L10n_plan]])
* Transifex migration
* Collaboration Summit
* Increasing participation (contacting other community L10N groups, etc.)
* MeeGo translation status
* Next meeting
* Opens

Full log from the meeting: [[L10N_IRC_Meeting_March_19,_2010]] 
Summary of the meeting: [[L10n_meeting_summary_19_March]]

==== March 5, 2010 ====

Meeting time: 1600 UTC on March 5th

Meeting log posted here: [[L10N_IRC_Meeting_March_5,_2010]]

Meeting minutes summary here: [[L10n_meeting_summary]]

Agenda: (suggestions welcome)

* Steering group members/scope/accountability
* Localization teams
* Where to host project?
* L10n project plan
* Next steps

Issues:

* Do we inherit strings from Moblin? If so, how do we migrate existing strings to Transifex? By whom, by when?
* Should there be a sequence of providing translations by localization team like core things first, optional components later.
* Do we localize the web sites?

Full log from the meeting: [[L10N_IRC_Meeting_March_5,_2010]] 
Summary of the meeting: [[L10n_meeting_summary]]

[[Category:Localization]]

MeeGo-Meeting IRC Schedule

2011-01-21T15:16:18Z

Margie: /* Regular Meetings */

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

== Regular Meetings ==

'''Monday'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings|MeeGo Core Bug Triage Meetings]]: Every Monday at '''7:00 UTC'''

'''Tuesday'''
* [[Quality/meetings| QA Meetings]]: Every Tuesday at '''07:00 UTC'''
* [[SDK/Meetings/Release| SDK Meeting (Release)]]: Every Tuesday at '''08:00 UTC''', 10:00 EEST
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Netbook Bug Triage Meetings]]: Every Tuesday at '''13:00 UTC'''
* [[Community_Office/Meetings| Community Office Meeting]]: The 1st and 3rd Tuesday, alternating between '''20:00 UTC and 15:00 UTC'''
* [[Events/Meetings|Events Meeting]]: Every other Tuesday at '''17:00 UTC'''

'''Wednesday'''
* [[SDK/Meetings| SDK Meeting]]: Every Wednesday at '''05:30 UTC'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Handset Bug Triage Meetings]]: Every Wednesday at '''7:00 UTC'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MCTS Bug Triage Meetings]]: Every Wednesday at '''8:00 UTC'''
* [[L10n_meeting_schedule| Localization / L10n Meetings]]: monthly at '''14:00 UTC'''
* [[Technical_Steering_Group_meetings| Technical Steering Group Meeting]]: Every other Wednesday at '''20:00 UTC'''

'''Thursday'''
* [[ARM/N900/Meetings| MeeGo N900 Hardware Adaptation Meetings]]: Every Thursday at '''8:00 UTC'''
* [[Quality/Bugtriage#MeeGo_Bug_Triage_Meetings| MeeGo Core Bug Triage Meetings]]: Every Thursday at '''13:00 UTC'''

'''Friday'''

'''Sunday'''
* [[Local_MeeGo_Networks/MeeGo_Network_Finland#Online_Community_Meetings | MeeGo Network Finland Meetings]]: The 1st and 3rd Sunday at '''16:00 UTC'''

== Ad Hoc Meetings ==

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

=== Guidelines ===

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

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

Community communication

2010-12-20T15:47:07Z

Margie: /* MeeGo IRC Channels */

'''This is a work in progress - we are still in the process of creating some of these new mailing lists, but most of this document is accurate.'''

Visit [[Community communication/Status]] for updates.

==Read Before Posting - Helping Yourself==

===Search for existing answers===
'''IMPORTANT: Before you post to any of our mailing lists or forums, be sure that you have done a thorough search and read our FAQs to see if your question has already been answered.''' We've already answered many questions, and you will get a better response from people if you have already done your due diligence to find obvious or partial answers.
* '''[[MeeGo FAQ]]''': Main frequently asked questions document with links to specialized FAQs.
* '''[http://forum.meego.com/search.php Forum Search]''': Use the [http://forum.meego.com/search.php forum search page] to find answers to user questions.
* '''[http://wiki.meego.com/index.php?title=Special%3ASearch&search=&fulltext=Search Wiki Search]: Find existing documentation and helpful tips.
* '''Mailing list search''': In Google type: ''my search terms site:lists.meego.com''
* '''Search Everything''' (meego.com, mailing lists, forums, wiki, etc.): In Google type: ''my search terms site:meego.com''

===Etiquette: What to know before you post===
* '''Post in the right place''': Read the section below carefully to find the right place to post your question or comment. For example, posting user questions to developer lists annoys developers and you are less likely to get a good response if you don't take the time to find the right place for your post.
* '''Adhere to our [[Community guidelines]]''': [[Mailing list guidelines]], [[Forum/Guidelines|forum guidelines]], [[Gitorious guidelines]] and [[Wiki contribution guidelines]].
* '''File bugs in the right place''': If you found a bug, just go ahead and file it in [http://bugs.meego.com/ bugs.meego.com] ([http://wiki.meego.com/Bugzilla/how-report-bugs instructions for how to report bugs])

==Mailing Lists and Forums==
Discussions about MeeGo, asynchronous project collaboration and answers to questions across a variety of mailing lists and forums. Please note that you must subscribe before you can post to a mailing list, and you need to have a meego.com account to post in our forums. You can learn more by reading our [[Forum/Guidelines|Forum guidelines]] and [[Mailing list guidelines]].

===Announcements===
Subscribe to these lists to receive announcements.

* '''[http://lists.meego.com/listinfo/meego-announce MeeGo-announce Mailing List]''': General announcements related to the MeeGo project (announcement list - general interest)
* '''[http://lists.meego.com/listinfo/meego-security MeeGo-security Mailing List]''': MeeGo Security Announcements (announcement list for security professionals and developers)

===Users===
Issues with installation, user level bugs, or general questions about MeeGo. This is where users of MeeGo can ask questions and discuss MeeGo with other users in our forums.

* '''[http://forum.meego.com/forumdisplay.php?f=2 General]''': MeeGo related topics not classified in a specific subforum.
* '''[http://forum.meego.com/forumdisplay.php?f=7 Handset]''': MeeGo Handset related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=9 In-Vehicle]''': MeeGo In-Vehicle Infotainment (IVI) related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=6 Netbook]''': MeeGo Netbook related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=8 Tablet]''': MeeGo Tablet related topics.
* '''[http://forum.meego.com/forumdisplay.php?f=5 Community Matters]''': Discussion about infrastructure, processes, marketing, events, and other community matters for the MeeGo project.
* '''[http://forum.meego.com/forumdisplay.php?f=4 Off-Topic]''': Totally unrelated but still worth discussing between ameegos.

===Application Developers===
Ask questions and discuss techniques for developing applications to run on top of MeeGo.

* '''[http://forum.meego.com/forumdisplay.php?f=3 Application Developer Support Forum]''': Offer/get help dealing with application developer tools and APIs.
* '''[http://lists.meego.com/listinfo/meego-sdk MeeGo-sdk Mailing List]''': MeeGo application development.

===Contributors===
People who are contributing to the MeeGo project collaborate on these lists.

* '''[http://lists.meego.com/listinfo/meego-community MeeGo-Community Mailing List]''': Community, general operations, openness, events and other general interest questions.
* '''[http://lists.meego.com/listinfo/meego-dev MeeGo-dev Mailing List]''': Development on the MeeGo distribution - '''not''' for application development or user level questions (high volume).
* '''[http://lists.meego.com/listinfo/meego-il10n MeeGo-il10n Mailing List]''': Localization list for MeeGo community.
* '''[http://lists.meego.com/listinfo/meego-packaging MeeGo-Packaging Mailing List]''': Communication about packaging and the build system.
* '''[http://lists.meego.com/listinfo/meego-pm MeeGo-pm Mailing List]''': Program management, product management and general coordination for people working in key roles in the project.
* '''[http://lists.meego.com/listinfo/meego-touch-dev MeeGo-touch-dev Mailing List]''': MeeGo Touch Framework Development.
* '''[http://lists.meego.com/listinfo/meego-releases MeeGo-releases Mailing List]''': Collaboration list on daily activities for Release Engineering and Quality Assurance teams.
* '''[http://lists.meego.com/listinfo/meego-qa MeeGo-qa Mailing List]''': Collaboration list on daily activities for the Quality Assurance team.
* '''[http://lists.meego.com/listinfo/meego-commits MeeGo-commits Mailing List]''': Broadcast list with auto-generated posts by people committing code into MeeGo.
* '''[http://lists.meego.com/listinfo/meego-kernel MeeGo-kernel Mailing List]''': MeeGo kernel discussions and patches.
* '''[http://lists.meego.com/listinfo/meego-architecture MeeGo-architecture Mailing List]''': MeeGo architecture discussions.
* '''[http://lists.meego.com/listinfo/meego-handset MeeGo-handset Mailing List]''': MeeGo handset program management, product management and development.
* '''MeeGo-netbook Mailing List''': MeeGo netbook program management, product management and development.
* '''[http://lists.meego.com/listinfo/meego-ivi MeeGo-ivi Mailing List]''': MeeGo In-Vehicle Infotainment program management, product management and development.
* '''MeeGo-mirrors Mailing List''': Communication with people who are mirroring our downloads.
* '''[http://lists.meego.com/listinfo/meego-security-discussion MeeGo-security-discussion Mailing List]''': Discussion about the MeeGo Security Framework and other security topics.
* '''[http://lists.meego.com/listinfo/meego-it MeeGo-it Mailing List]''': Discussion about IT and infrastructure for MeeGo.
* '''[http://lists.meego.com/listinfo/meego-porting MeeGo-porting Mailing List]''': Discussions about porting MeeGo to various platforms / devices.
* '''MeeGo-meetups Mailing List''': Discussions about best practices and organizing [[Community_Office/Marketing/Local_MeeGo_Networks|Local MeeGo Network]] events. (Note - holding off on creating this list until we have a little more momentum.
* '''[http://lists.meego.com/listinfo/meego-distribution-tools MeeGo-distribution-tools Mailing List]''': Discussion list for the [http://meego.gitorious.org/meego-developer-tools distribution development] and [http://meego.gitorious.org/meego-infrastructure-tools distribution infrastructure] tools used in MeeGo release and packaging.
* '''[http://lists.meego.com/listinfo/meego-python MeeGo-python Mailing List]''': Discuss Python in the MeeGo project and using Python as a prominent choice for third party development (using PySide and QML).

Note: Lists without links may still be tentative and have not been created or configured yet.

==IRC==

Internet Relay Chat (IRC) for real-time discussions about MeeGo and online meetings. All of our IRC channels are hosted at [http://freenode.net/ irc.freenode.net].

===MeeGo IRC Channels===

* '''#meego''': 24/7 open discussion.
* '''#meego-meeting''': scheduled IRC meetings ([[MeeGo-Meeting IRC Schedule]]).
* '''#meego-meeting-questions''': used for questions during moderated IRC meetings (rarely used).
* '''#meego-arm''': MeeGo ARM team channel as well as home to the MeeGo N900 hardware adaptation team.
* '''#meego-dev''': MeeGo project collaboration for developers contributing to MeeGo.
* '''#meego-sdk''': Discussion about the MeeGo SDK.
* '''#meego-handset''': Collaboration for the MeeGo Handset team.
* '''#meego-art''': Graphics and theming.
* '''#meego-qa-tools''': MeeGo QA-tools team channel focused on test tools development
* '''#meego-qa''': MeeGo QA channel
* '''#meego-python''': The MeeGo Python project - Developing and packaging Python for MeeGo + application development using Python
* '''#meego-l10n''': Used for questions and discussion on localizing MeeGo

===IRC How-to===

* '''MeeGo [[IRC guidelines]]'''
* '''[http://irchelp.org/irchelp/ircprimer.html IRC Primer]''': Read this if you are new to IRC.
* '''[http://freenode.net/channel_guidelines.shtml Freenode Guidelines]'''.
* '''[http://webchat.freenode.net/ IRC Webchat]''': If you are new to IRC and don't already use an IRC client, you can get into IRC using any browser.
* '''[http://en.wikipedia.org/wiki/Internet_Relay_Chat_client#Clients IRC Clients]'''.

==Bugs==

Quite a bit of discussion happens in Bugzilla to discuss bugs and possible solutions.

* '''[[Bugzilla/how-report-bugs|How to Report Bugs]]''': Instructions, process and guidelines
* '''[http://bugs.meego.com/ bugs.meego.com]''': MeeGo Bugzilla

==Documentation==

Some of our documentation can be found on [http://meego.com MeeGo.com], but most of the documentation can be found in the [[Main Page|MeeGo Wiki]] where you can contribute by:
* Adding new documentation to help other people in the MeeGo community
* Correcting technical errors or adding additional information in the documentation
* Cleaning up the language and correcting typos

==Contributing to MeeGo==

There are also many ways that you can contribute to MeeGo beyond just discussions. See our [http://meego.com/about/contribution-guidelines Contribution Guidelines] page for more details.

QtInternationalization

2010-11-29T18:38:10Z

Margie:

This page is a draft work in progress and not complete; mainly a stream of consciousness...
'''UPDATE 10/25/2010: This process is under massive reconstruction--please come back soon for the revised process. 
'''UPDATE 11/29/2010: Please see this page for i18n info for QML-based apps: http://wiki.meego.com/QML/Internationalisation
'''
=Overview=
MeeGo applications are are to be internationalized by the application developer. For information on how to write internationalized code, see the [http://apidocs.meego.com/mtf/i18n.html MeeGo Touch Framework: i18n] documentation. In its simplest form, the developer should use qtTrId() to wrap all of the user visible strings. If the application uses any type of concatenation, make sure it uses the argument version of QString(). For example:
//% "Displayed contact name %1 is first name. %2 is last name"
QString name = qtTrId("%1 %2").arg(contact.firstName()).arg(contact.lastName());
Make sure you provide a contextual comment describing the string before its usage (as is done in the above example) This facilitates the translation process. The string comment is also used when generating the "engineering English" which is displayed when no translation exist.
==Engineering English==
The engineering English strings are prefixed with '!!' to ensure they are visibly identifiable as having not been officially translated.

The base application projects do not provide '''localized''' translations. Language packages will be installed which provide the various language translations. Lacking a translation, the translation ID will be shown by the system if a translation is not found.

Application packages should install the engineering English translation file into the system. See the section [http://wiki.meego.com/Internationalization#Packaging_engineering_English Packaging engineering English].

The following attempts to describe the general process used by MeeGo to create localized language packs.

==Supported locales==
The locales which must be enabled, per http://bugs.meego.com, are:
American English (en_US), British English (en_GB), French (fr), Spanish (es), German (de), Italian (it), Polish (pl), Dutch (nl), Russian (ru), Swedish (sv), Finnish (fi), Brazilian-Portuguese (pt_BR), Canadian-French (fr_CA), Portuguese (pt), Japanese (ja), Korean (ko), Chinese Simplified (zh_CN), Chinese Traditional (zh_TW).

If in doubt of a language code, see here: http://www.transifex.net/languages/

Also, for assistance on handling the various number forms in different languages (e.g. singular and plural in English), refer to: http://www.qtcentre.org/wiki/index.php?title=Grammatical_number

=Step-by-Step=
For this example, we will create the language package project for the meego-handset-sms application.

The naming convention used is that the GIT tree and OBS package for a translation project are named based on the application GIT tree + -translations. In this case meego-handset-sms-translations.

At the end of this sample, you will have the following directories:
${BASE}/meego-handset-sms <---- application .git project
${BASE}/meego-handset-sms-translations <---- translation .git project for application
${BASE}/obs/meego-handset-sms-translations <---- OBS project for translation package

The following exports are used throughout these script snippets; you can export them once to your shell and then paste the other script components. If you later come back to run an individual step, make sure you set these variables back up.
export BASE='''~''' # Root directory for the various projects
export APP_PACKAGE='''meego-handset-sms''' # Name of the application project
export APP_BINARY='''sms''' # TARGET binary created by application project
export SOURCE_SUBDIR='''/src''' # Subdirectory under ${APP_PACKAGE} which contains the package source files
export PACKAGE=${APP_PACKAGE}-translations
export LANGUAGES="en en_US en_GB fr es de it pl nl ru sv fi pt_BR fr_CA pt ja ko zh_CN zh_TW"
'''BOLD''' items are the ones you need to change for your project.
==Checkout the application .git project==
The first step is to obtain the application project that we'll be creating the translation project for.
cd ${BASE}
git clone git://gitorious.org/meego-handset-ux/${APP_PACKAGE}
Look in the meego-handset-sms directory and you will notice that all of the sources are in the src/ directory. Look at the project files for meego-handset-sms -- notice that while the project is called meego-handset-sms, the binary it installs is called '''sms'''.

You can typically tell the binary name by looking for the TARGET= line in the source's .pro file.

Knowing the location of the source is important when we define the SOURCES variable in the translations.pro file, which is used to derive the translation files from the sources. Knowing the binary installed is important when we define the APP_BINARY value.

The name of the binary is important as it is used by Qt to find the translation file. The translation file used can be overridden by passing a 3rd parameter to MApplication(). The compiled translation files (.qm) are installed using the binary name as their filename base.

==Create the initial translations .git project==
The following snippet will create a blank translations .git repository for you:
cd ${BASE}
[ ! -d ${PACKAGE} ] && mkdir ${PACKAGE}
cd ${PACKAGE}
cat << EOF >> translations.pro
LANGUAGES = ${LANGUAGES}
CATALOGNAME = ${APP_BINARY}
SOURCEDIR = '''\$\$PWD/../${APP_PACKAGE}${SOURCE_SUBDIR}'''
TRANSLATIONDIR = \$\$PWD
DISABLE_QTTRID_ENGINEERING_ENGLISH=yes
include(\$\$[QT_INSTALL_DATA]/mkspecs/features/meegotouch_defines.prf)
include(\$\$[QT_INSTALL_DATA]/mkspecs/features/meegotouch_translations.prf)
EOF
git init
git add *
git commit -s -a -m "Initial translation package commit for ${APP_PACKAGE}"
qmake
make updatets
git add *.ts Makefile
git commit -s -a -m "Initial .ts files generated from ${APP_PACKAGE}"
'''NOTE:''' Do not check in the '.qm' files. Those are generated during package build time and should not be managed in GIT.
'''NOTE2:''' The 'dummy-dependency-this-file-will-never-be-created' file is created and committed to the GIT tree to keep the build process from attempting to update the .ts files every time the .qm files are compiled.

===What is the license for the translation package?===
Translation files (.ts) are derived from the source package. The original author of the source package therefore holds a copyright interest in the derived translation package. In order to comply with the license terms of the source application package, typically the translation package must use the same license as the base source package.

Once you know the license which applies to the translation package, place a copy of that license in the file LICENSE and add it to the git tree:
git add LICENSE
git commit -s -a -m "Added LICENSE terms"

==Changing the set of supported locales==
To add additional translations, you would add the translation name to LANGUAGES in translations.pro:
export LANGUAGES="en fi cz dk he"
cd ${BASE}/${PACKAGE}
sed -i -e "s,^LANGUAGES[ /t]*=.*$,LANGUAGES = ${LANGUAGES},g" translations.pro
qmake
make updatets
git add *ts
git commit -s -a -m "Updated languages to support '${LANGUAGES}' based on ${APP_PACKAGE} commit-id '${REVISION}'"

==Updating the .ts files to match latest source package==
cd ${BASE}/${PACKAGE}
export REVISION=$(git --git-dir=../${APP_PACKAGE}/.git log --pretty=format:"%h" HEAD^..HEAD)
make updatets
git commit -s -a -m "Updated .ts files to package ${APP_PACKAGE} commit-id '${REVISION}'"
'''NOTE:''' You only need to run '''make updatets''' periodically when new application releases are made. It should not be run when translations are being updated. Translators should never need to run the '''make updatets''' script.

=Packaging the translations=
Language packs should be provided as one RPM per locale. Typically, multiple packages would be built from a single OBS package.
==Creating the tar ball==
The first step of packaging is to create a tar file. In the following example, we set the version to 0.0.1. That version string should be updated to match the version of ${APP_PACKAGE} that is in OBS (the VERSION string is used for required dependency checking during package installation)
export '''VERSION=0.0.1'''
To create the tar file in ${BASE}/obs/${PACKAGE}/:
cd ${BASE}
[ ! -d ${BASE}/obs/${PACKAGE} ] && mkdir -p ${BASE}/obs/${PACKAGE}
tar cvjf ${BASE}/obs/${PACKAGE}/${PACKAGE}-${VERSION}.tar.bz2 ${PACKAGE} --exclude=.git

That above tar file would contain:
Makefile
sms-en.ts
sms-fi.ts
sms-de.ts
translations.pro

==Creating the OBS project==
The contents of the '''meego-handset-sms-translations''' OBS project for this example needs to consist of:
meego-handset-sms-translations-0.0.1.tar.bz2
meego-handset-sms-translations.yaml
meego-handset-sms-translations.spec
To create the .yaml file you can use the following script. This assumes the directory .tar.bz2 file was created and exists in ${BASE}/obs/${PACKAGE}:
cd ${BASE}/obs/${PACKAGE}
cat << EOF > ${PACKAGE}.yaml
Name: ${PACKAGE}
Summary: Translation files for ${APP_PACKAGE}
Version: ${VERSION}
Release: 1
Group: System/GUI/Other
License: Apache
URL: http://gitorious.org/meego-handset-ux/${PACKAGE}
Sources:
- "%{name}-%{version}.tar.bz2"
Description: Translation files for ${APP_PACKAGE}
Requires:
- ${APP_PACKAGE} >= %{version}

PkgConfigBR:
- QtCore >= 4.6.0
- meegotouch
Configure: none
Builder: make
NoFiles: yes
EOF
for locale in $(tar xf ${PACKAGE}-${VERSION}.tar.bz2 ${PACKAGE}/translations.pro -O | sed -ne 's,^LANGUAGES[ \t]*=[ \t]*$.*$,\1,p'); do
cat << EOF >> ${PACKAGE}.yaml
SubPackages:
- Name: ${locale}
Summary: ${locale} translation file for ${APP_PACKAGE}
Group: Base/System
Description: ${locale} translation file for ${APP_PACKAGE}
Files:
- "%lang(${locale}) %{_datadir}/l10n/meegotouch/%{name}_${locale}.qm"

EOF
done
See the sample .yaml file at the end of this page for an example of what the above script generates (the sample has additional comments that the above script does not add)

Once you have the .yaml file, you can create the .spec file via spectacle.
specify ${PACKAGE}.yaml

==Updating the OBS package==
Create a new translations package tar ball named meego-handset-sms-translations-${VERSION}.tar.bz2

${VERSION} value for the tar ball must correspond to the 'Version:' string in the yaml file:
sed -i -e 's,^Version:[ \t]*$.*$$,${VERSION},p' meego-handset-translations.yaml

=Sample yaml file=
#
# Use application package name + "-translations"
Name: meego-handset-sms-translations
Summary: Translation files for meego-handset-sms
#
# Keep version # in sync with the application package
Version: 0.0.1
Release: 1
Group: System/GUI/Other
#
# Use application package license; .ts files are derived works from application application
License: Apache
# Use GIT url for translations project on gitorious
URL: http://gitorious.org/meego-handset/meego-handset-sms-translations
Sources:
- "%{name}-%{version}.tar.bz2"
Description: Translation files for meego-handset-sms
# Require the application package - tie these
Requires:
- meego-handset-sms >= %{version}

PkgConfigBR:
- QtCore >= 4.6.0
Configure: none
Builder: make
NoFiles: yes
SubPackages:
- Name: en
Summary: en translation for meego-handset-sms
Group: System/GUI/Other
Description: en translation for meego-handset-sms
Files:
- "%lang(en) %{_datadir}/l10n/meegotouch/sms-en.qm"

- Name: fi
Summary: fi translation for meego-handset-sms
Group: System/GUI/Other
Description: fi translation for meego-handset-sms
Files:
- "%lang(fi) %{_datadir}/l10n/meegotouch/sms-fi.qm"

- Name: de
Summary: de translation for meego-handset-sms
Group: System/GUI/Other
Description: de translation for meego-handset-sms
Files:
- "%lang(de) %{_datadir}/l10n/meegotouch/sms-de.qm"

=Packaging engineering English=
cd ${BASE}/${APP_PACKAGE}
[ ! -e translations ] && mkdir translations
cd translations
cat << EOF >> translations.pro
LANGUAGES = # We only create engineering English in the application package
CATALOGNAME = ${APP_BINARY}
SOURCEDIR = ../${SOURCE_SUBDIR}
TRANSLATIONDIR = \$\$PWD
include(\$\$[QT_INSTALL_DATA]/mkspecs/features/meegotouch_defines.prf)
include(\$\$[QT_INSTALL_DATA]/mkspecs/features/meegotouch_translations.prf)
EOF
qmake
make
git add translations.pro
git commit -s -a -m "Engineering English translation project generated"
Now you need to add '''translations''' to the SUBDIRS in the top level project file (sms.pro in this example):
sed -i -e 's,$SUBDIRS = .*$,\1 translations,g' *.pro
You don't need to commit the .ts file to GIT. It will be extracted from the source code each time the build is run. This ensures the engineering English always provides all of the non-translated strings. Official English translation should be installed via the ${APP_PACKAGE}-translations-en package.

You now need to add the engineering English file to your yaml file for your project in OBS to the FILES section. Edit the yaml file and looking for Files and add the following:
- "%{_datadir}/l10n/meegotouch/%{name}.qm"
If you don't have a Files section in your yaml, you'll can add one to your yaml, or you can edit your spec file directly. See the sample yaml file above for an example how to add a Files section.

After you have done the above you can cut a new release, build, install, and test. All of the displayed strings should now be prefixed with "!!" until a translation package is provided.

[[Category: Localization]]

User:Margie

2010-10-31T18:21:14Z

Margie:

MeeGo Project Localization Maintainer 
I work for Intel and am based in Hillsboro, Oregon. 
I love to work with world-wide teams and have been involved in localization activities for most of my Intel career.

User:Margie

2010-10-31T18:20:44Z

Margie:

MeeGo Project Localization Maintainer
I work for Intel and am based in Hillsboro, Oregon.
I love to work with world-wide teams and have been involved in localization activities for most of my Intel career.

MeeGo Conference 2010/Unconference

2010-10-31T18:18:42Z

Margie: /* I plan to present ... */

Day 3 of the [http://conference2010.meego.com MeeGo Conference] will be primarily an unconference run in the BarCamp style. We will also have one room with scheduled activities running in parallel to the unconference for Birds of a Feather sessions, lightning talks and similar activities.

== What is an Unconference and Why should I attend? ==

We've been getting a lot of questions about the unconference day from people who aren't convinced that it is worth their time to attend. [[User:Dawnfoster|I (Dawn)]] have attended many unconferences and organized several of them, and I can honestly say that I usually get as much, if not more, out of them than I do from traditional conferences.

=== Brief Description ===

An unconference is an ad-hoc gathering organized by the attendees for the attendees. The concept originated out of a desire for people to share and learn in an open environment. It is an intense event with discussions, demos and interaction from participants. You never quite know what to expect at an unconference, since each one is shaped by the attendees. When you arrive on Wednesday morning, there will be an agenda framework (times / rooms), but the content for the sessions will be decided by the participants.

=== Why should I attend ===

'''To Present and Lead'''
* Anyone can present or lead a discussion, so you can talk about any topic of interest to you.
* If you submitted a session, and it wasn't approved for the main conference, but you still think it would be interesting, you can present it here.
* We will have plenty of smaller rooms for niche topics of interest to a few people - those rarely fit into a conference format, but work nicely in one of our smaller unconference rooms.
* It's a great opportunity to follow up on a topic presented in the first days and have a more detailed discussion.

'''To Collaborate and Network'''
* Use the time to collaborate with people on an interesting MeeGo project.
* Great opportunity to talk to experts about subjects not covered in the first two days.
* Network and meet other people interested in our work
* Learn more about what others need and get feedback on new ways to use MeeGo
* Collaborate on actual work related to MeeGo in smaller groups
* Have group discussions or meetings

'''To Learn and Innovate'''
* It is a great way to spot new talents, new movements, tendencies and upcoming technologies that weren't mature enough for the main conference.
* An unconference is basically like the conference, but with subjects chosen by the audience (by interest), which means there's a high chance of finding interesting topics.
* We have a community of interesting smart people, so we should expect plenty of interesting sessions.
* The flexible format allows for interesting out of the box ideas and ways to accommodate different formats.
* You are encouraged to use the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Law_of_Two_Feet Law of Two Feet] - if you go to a session and it isn't what you had hoped, you are encouraged to get up and move to another session.
* Come home with a fresh set of cutting-edge ideas and inspiration at the front of innovation within MeeGo.

=== More information ===
* [http://www.youtube.com/watch?v=7XlqEDIJzfw What is BarCamp? video] - short and worth your time to watch.
* [http://en.wikipedia.org/wiki/Barcamp BarCamp Wikipedia entry] with some history and other information.

== Session Ideas ==

'''IMPORTANT: Adding a session to the list below does not reserve a spot on the schedule board on Wednesday. The only way to guarantee a schedule slot is by showing up early and putting your session on the grid in person. See the [[#Schedule]] section below for more details.'''

=== Tips for Presenters ===

* Discussion formats work slightly better than standard conference presentations. Leading a group of people in a discussion is much more interactive and gives people a nice break from the past 2 days of presentations.
* Prepare in advance - if you plan to lead a session, prepare as you would for any other conference.
* Have a topic that isn't 45 minutes of material? Team up with one or more people with related topics and share the session.
* Respect people's time and do not allow your session to run longer than scheduled. Other people will be waiting to get into the room to set up for the next session.

=== I plan to present ... ===

Leave a note with the topic you plan to present along with your name and a link to more information about yourself.

* The title of an example topic description --[[User:Dawnfoster|Dawnfoster]] 22:09, 21 September 2010 (UTC)
* [http://conference2010.meego.com/session/accounts-sso Introduction to the new Accounts & Single Sign On framework] --[[User:Mardy|Mardy]] 24 Sep 2010 11:52:11 (UTC)
* [http://conference2010.meego.com/session/content-fw-my-god-its-full-data Introduction to Tracker/Content FW: one of really innovating bits in Meego] --[[User:Ifrade|Frade]] 06 Oct 2010 13:21:00 (EETC)
* [[MeeGo_Conference2010/QtM_BoF_Unconference|QtMobility & MeeGo BoF/Unconference]] -- [[User:mikeleib|mikeleib]] 06 Oct 2010 04:03 UTC
* [[MeeGo_Conference_2010/Unconference/ARM|MeeGo ARM Discussion Forum]] -- [[User:stskeeps|stskeeps]] 07 Oct 2010 15:57 UTC
* [[MeeGo_Conference_2010/Unconference/Plasma|Plasma and QtComponents BoF]] -- [[User:mart|mart]] 07 Oct 2010 23:10 UTC
* [http://conference2010.meego.com/session/grilo-enhancing-multimedia-experience-meego Grilo: Enhancing the multimedia experience in MeeGo] -- [[User:itoral|itoral]] 11 Oct 2010 07:10 UTC
* [[MeeGo_Conference_2010/Unconference/TrackerHandsOn|Hands on BOF on making efficient SPARQL queries and mastering the different APIs of MeeGo's metadata service, Tracker]] -- [[User:pvanhoof|pvanhoof]], [[User:abustany|abustany]] 11 Oct 2010 10:34 UTC
* [http://conference2010.meego.com/session/working-together-world-ready-meego-developers-and-translators MeeGo Internationalization and Localization Discussion] [[User:margie|margie]]--A continuation of the discussion of the new process we are proposing to use for the next MeeGo release

=== I would like to see someone talk about ... ===

Have something that you want to see someone else talk about? Feel free to use this space to brainstorm topics.

* Tips for contributing code to MeeGo and getting it accepted --[[User:Dawnfoster|Dawnfoster]] 22:09, 21 September 2010 (UTC)

== Schedule ==

=== Schedule Grid and Process for Scheduling Sessions ===

We will have a big grid on the wall where people can post their session ideas on the morning of the event (no sessions reserved in advance). Make sure you arrive on time if you plan to lead a session!

'''To Schedule a Session''':
* The schedule board will open up after the welcome is completed.
* Write your topic in big letters on your post it note.
* Include your contact information in smaller letters (name and cell phone or email address)
* Put your post it note on the board picking a room and time that looks good to you.
* Make sure that big meaty topics are in large rooms with niche topics in small rooms.

'''Things to keep in mind''':
* The schedule board is dynamic and may change at any time during the day.
* The schedule board on the wall is always the master.
* We may need to move sessions, so make sure you double check the board to make sure that you are going to the right room / time for the session you want to attend.
* Sessions that seem very similar may be asked to combine.
* We reserve the right to move things around to make sure that popular topics have large rooms.

=== Day Schedule and Grid Format ===

This is an example of how the grid will look and is for planning purposes only - '''please do not enter sessions or add other information to the grid'''

{| border="1"
!Time || Presidents 1 (sits 300) || Presidents 2 (sits 280) || Vavasour (sits 80) || 1872 area (sits 120) || Havelock (sits 130)||Box 1 (sits 20)||Box 2 (sits 20)|| Box 3 (sits 20)|| Box 4 (sits 20)|| Box 5 (sits 20)|| Box 6 (sits 20)|| Other
|-
!9:00 - 9:15 ||colspan=13|Atrium: Welcome - What is an unconference and how do I participate?
|-
!9:15 - 9:45 ||colspan=13|Atrium: Schedule board open - people post sessions on the grid.
|-
!9:45 - 10:00||colspan=13|Atrium: Schedule board adjustments (combine duplicates, adjust rooms, etc.)
|-
|10:00 - 10:45|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
|11:00 - 11:45|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
|12:00 - 12:45|| Lightning Talks || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
!12:45 - 13:45||colspan=13|Lunch and Networking
|-
|13:45 - 14:30|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
|14:45 - 15:30|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
!15:30 - 16:00||colspan=13|We need to be out of Aviva no later than 16:00.
|-
!17:45||colspan=13|Doors open for the Ireland / Norway Football game.
|-
|}

Note: The BOF / Scheduled session room is out of scope of the unconference team and will be decided and planned by the content committee.

== Requirements ==

* Rooms set up - confirm that we do plan to use all of the rooms on the schedule board & we need to know which rooms have projectors.
* A bunch of 4x6" post it notes
* A schedule board pre-printed with times and rooms with spaces large enough to accommodate 4x6" post it notes (alternative is painter's tape & a wall)
* Sharpie pens

== Organizing Team ==

* Lead: [[User:Dawnfoster|Dawn Foster]]
* Notes / wiki organizer - put a process in place to allow people to take notes and maintain a copy (physical board is the master) of the schedule in the wiki.
* Schedule volunteers - 2 people (2 shifts - each working half the day) to help manage the schedule board, help people get things scheduled, update schedule changes in the wiki copy, etc.
* Note taking volunteers - each session needs one or more people to take notes and put them in the wiki

MeeGo Conference 2010/Unconference

2010-10-31T18:16:32Z

Margie: /* I plan to present ... */

Day 3 of the [http://conference2010.meego.com MeeGo Conference] will be primarily an unconference run in the BarCamp style. We will also have one room with scheduled activities running in parallel to the unconference for Birds of a Feather sessions, lightning talks and similar activities.

== What is an Unconference and Why should I attend? ==

We've been getting a lot of questions about the unconference day from people who aren't convinced that it is worth their time to attend. [[User:Dawnfoster|I (Dawn)]] have attended many unconferences and organized several of them, and I can honestly say that I usually get as much, if not more, out of them than I do from traditional conferences.

=== Brief Description ===

An unconference is an ad-hoc gathering organized by the attendees for the attendees. The concept originated out of a desire for people to share and learn in an open environment. It is an intense event with discussions, demos and interaction from participants. You never quite know what to expect at an unconference, since each one is shaped by the attendees. When you arrive on Wednesday morning, there will be an agenda framework (times / rooms), but the content for the sessions will be decided by the participants.

=== Why should I attend ===

'''To Present and Lead'''
* Anyone can present or lead a discussion, so you can talk about any topic of interest to you.
* If you submitted a session, and it wasn't approved for the main conference, but you still think it would be interesting, you can present it here.
* We will have plenty of smaller rooms for niche topics of interest to a few people - those rarely fit into a conference format, but work nicely in one of our smaller unconference rooms.
* It's a great opportunity to follow up on a topic presented in the first days and have a more detailed discussion.

'''To Collaborate and Network'''
* Use the time to collaborate with people on an interesting MeeGo project.
* Great opportunity to talk to experts about subjects not covered in the first two days.
* Network and meet other people interested in our work
* Learn more about what others need and get feedback on new ways to use MeeGo
* Collaborate on actual work related to MeeGo in smaller groups
* Have group discussions or meetings

'''To Learn and Innovate'''
* It is a great way to spot new talents, new movements, tendencies and upcoming technologies that weren't mature enough for the main conference.
* An unconference is basically like the conference, but with subjects chosen by the audience (by interest), which means there's a high chance of finding interesting topics.
* We have a community of interesting smart people, so we should expect plenty of interesting sessions.
* The flexible format allows for interesting out of the box ideas and ways to accommodate different formats.
* You are encouraged to use the [http://en.wikipedia.org/wiki/Law_of_Two_Feet#Law_of_Two_Feet Law of Two Feet] - if you go to a session and it isn't what you had hoped, you are encouraged to get up and move to another session.
* Come home with a fresh set of cutting-edge ideas and inspiration at the front of innovation within MeeGo.

=== More information ===
* [http://www.youtube.com/watch?v=7XlqEDIJzfw What is BarCamp? video] - short and worth your time to watch.
* [http://en.wikipedia.org/wiki/Barcamp BarCamp Wikipedia entry] with some history and other information.

== Session Ideas ==

'''IMPORTANT: Adding a session to the list below does not reserve a spot on the schedule board on Wednesday. The only way to guarantee a schedule slot is by showing up early and putting your session on the grid in person. See the [[#Schedule]] section below for more details.'''

=== Tips for Presenters ===

* Discussion formats work slightly better than standard conference presentations. Leading a group of people in a discussion is much more interactive and gives people a nice break from the past 2 days of presentations.
* Prepare in advance - if you plan to lead a session, prepare as you would for any other conference.
* Have a topic that isn't 45 minutes of material? Team up with one or more people with related topics and share the session.
* Respect people's time and do not allow your session to run longer than scheduled. Other people will be waiting to get into the room to set up for the next session.

=== I plan to present ... ===

Leave a note with the topic you plan to present along with your name and a link to more information about yourself.

* The title of an example topic description --[[User:Dawnfoster|Dawnfoster]] 22:09, 21 September 2010 (UTC)
* [http://conference2010.meego.com/session/accounts-sso Introduction to the new Accounts & Single Sign On framework] --[[User:Mardy|Mardy]] 24 Sep 2010 11:52:11 (UTC)
* [http://conference2010.meego.com/session/content-fw-my-god-its-full-data Introduction to Tracker/Content FW: one of really innovating bits in Meego] --[[User:Ifrade|Frade]] 06 Oct 2010 13:21:00 (EETC)
* [[MeeGo_Conference2010/QtM_BoF_Unconference|QtMobility & MeeGo BoF/Unconference]] -- [[User:mikeleib|mikeleib]] 06 Oct 2010 04:03 UTC
* [[MeeGo_Conference_2010/Unconference/ARM|MeeGo ARM Discussion Forum]] -- [[User:stskeeps|stskeeps]] 07 Oct 2010 15:57 UTC
* [[MeeGo_Conference_2010/Unconference/Plasma|Plasma and QtComponents BoF]] -- [[User:mart|mart]] 07 Oct 2010 23:10 UTC
* [http://conference2010.meego.com/session/grilo-enhancing-multimedia-experience-meego Grilo: Enhancing the multimedia experience in MeeGo] -- [[User:itoral|itoral]] 11 Oct 2010 07:10 UTC
* [[MeeGo_Conference_2010/Unconference/TrackerHandsOn|Hands on BOF on making efficient SPARQL queries and mastering the different APIs of MeeGo's metadata service, Tracker]] -- [[User:pvanhoof|pvanhoof]], [[User:abustany|abustany]] 11 Oct 2010 10:34 UTC
* [http://conference2010.meego.com/session/working-together-world-ready-meego-developers-and-translators MeeGo Internationalization and Localization Discussion] [[User:margie|Margie Foster]]--A continuation of the discussion of the new process we are proposing to use for the next MeeGo release

=== I would like to see someone talk about ... ===

Have something that you want to see someone else talk about? Feel free to use this space to brainstorm topics.

* Tips for contributing code to MeeGo and getting it accepted --[[User:Dawnfoster|Dawnfoster]] 22:09, 21 September 2010 (UTC)

== Schedule ==

=== Schedule Grid and Process for Scheduling Sessions ===

We will have a big grid on the wall where people can post their session ideas on the morning of the event (no sessions reserved in advance). Make sure you arrive on time if you plan to lead a session!

'''To Schedule a Session''':
* The schedule board will open up after the welcome is completed.
* Write your topic in big letters on your post it note.
* Include your contact information in smaller letters (name and cell phone or email address)
* Put your post it note on the board picking a room and time that looks good to you.
* Make sure that big meaty topics are in large rooms with niche topics in small rooms.

'''Things to keep in mind''':
* The schedule board is dynamic and may change at any time during the day.
* The schedule board on the wall is always the master.
* We may need to move sessions, so make sure you double check the board to make sure that you are going to the right room / time for the session you want to attend.
* Sessions that seem very similar may be asked to combine.
* We reserve the right to move things around to make sure that popular topics have large rooms.

=== Day Schedule and Grid Format ===

This is an example of how the grid will look and is for planning purposes only - '''please do not enter sessions or add other information to the grid'''

{| border="1"
!Time || Presidents 1 (sits 300) || Presidents 2 (sits 280) || Vavasour (sits 80) || 1872 area (sits 120) || Havelock (sits 130)||Box 1 (sits 20)||Box 2 (sits 20)|| Box 3 (sits 20)|| Box 4 (sits 20)|| Box 5 (sits 20)|| Box 6 (sits 20)|| Other
|-
!9:00 - 9:15 ||colspan=13|Atrium: Welcome - What is an unconference and how do I participate?
|-
!9:15 - 9:45 ||colspan=13|Atrium: Schedule board open - people post sessions on the grid.
|-
!9:45 - 10:00||colspan=13|Atrium: Schedule board adjustments (combine duplicates, adjust rooms, etc.)
|-
|10:00 - 10:45|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
|11:00 - 11:45|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
|12:00 - 12:45|| Lightning Talks || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
!12:45 - 13:45||colspan=13|Lunch and Networking
|-
|13:45 - 14:30|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
|14:45 - 15:30|| BOFs / Scheduled || Unconf Session || Unconf Session || Unconf Session || Unconf Session||Unconf Session||Unconf Session || Unconf Session ||Unconf Session || Unconf Session || Unconf Session
|-
!15:30 - 16:00||colspan=13|We need to be out of Aviva no later than 16:00.
|-
!17:45||colspan=13|Doors open for the Ireland / Norway Football game.
|-
|}

Note: The BOF / Scheduled session room is out of scope of the unconference team and will be decided and planned by the content committee.

== Requirements ==

* Rooms set up - confirm that we do plan to use all of the rooms on the schedule board & we need to know which rooms have projectors.
* A bunch of 4x6" post it notes
* A schedule board pre-printed with times and rooms with spaces large enough to accommodate 4x6" post it notes (alternative is painter's tape & a wall)
* Sharpie pens

== Organizing Team ==

* Lead: [[User:Dawnfoster|Dawn Foster]]
* Notes / wiki organizer - put a process in place to allow people to take notes and maintain a copy (physical board is the master) of the schedule in the wiki.
* Schedule volunteers - 2 people (2 shifts - each working half the day) to help manage the schedule board, help people get things scheduled, update schedule changes in the wiki copy, etc.
* Note taking volunteers - each session needs one or more people to take notes and put them in the wiki

MeeGo-Meeting IRC Schedule

2010-10-27T19:19:11Z

Margie: /* October Schedule */

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

== Regular Meetings ==
* [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting]: The 1st and 3rd Tuesday, alternating between 05:00 and 14:00 UTC
* [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]: Every other Wednesday at 19:00 UTC
* [http://wiki.meego.com/SDK/Meetings SDK Meeting]: Every Wednesday at 7:30 EEST, 12:30 CST, 21:30 PDT
* [http://wiki.meego.com/L10n_meeting_schedule Localization / L10n Meetings]: Every other Thursday at 14:00 UTC
* [http://wiki.meego.com/Quality/QA-tools#Meetings QA Tools Meetings]: Every Tuesday at 12:00 UTC

== October Schedule ==
* October 19 14:00 UTC: [http://wiki.meego.com/Community_Office/Meetings Community Office Meeting] - Canceled
* October 27 19:00 UTC: [http://wiki.meego.com/Technical_Steering_Group_meetings Technical Steering Group Meeting]
* October 28 14:00 UTC: [http://wiki.meego.com/L10n_meeting_schedule Localization Group] CANCELED

== November Schedule ==
* November 4 14:00 UTC: [http://wiki.meego.com/L10n_meeting_schedule Localization Group]

=== Guidelines ===

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

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

2010-09-22T23:29:31Z

2010-09-22T23:10:38Z

Margie: /* Clone Project Translations */

Here is a proposed process for translating qt-based software until we have Transifex working.

===Purpose===
The goal of this document is to educate translators to use QtCreator and Linguist with the Qt/MTF-based MeeGo reference applications that have followed the [http://wiki.meego.com/Internationalization MeeGo Internationalization wiki]. This will not apply to '''all''' applications or libraries. The need for these steps is driven by the [http://wiki.meego.com/Internationalization recommended steps for internationalization of the Qt/MTF-based MeeGo Reference Applications]. Please read those instructions for any necessary context or explanation as to why it is the way it is.

As of the writing of this HOWTO (Septemper 22, 2010) the list of applications with translation projects already created include:
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-music-translations meego-handset-music-translations]
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-sms-translations meego-handset-sms-translations]
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-diaer-translations meego-handset-dialer-translations]
* [http://meego.gitorious.org/meego-handset-ux/fennec-qt-translations fennec-qt-translations]
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-chat-translations meego-handset-chat-translations]
* [http://meego.gitorious.org/meego-handset-ux/meegotouchcp-chat-translations meegotouchcp-chat-translations]
* [http://meego.gitorious.org/meego-handset-ux/meego-handset-socialweb-translations meego-handset-socialweb-translations]
* [http://meego.gitorious.org/meego-handset-ux/meegotouchcp-socialweb-translations meegotouchcp-socialweb-translations]

===Assumptions===
This process assumes the following environment will be used to perform translations:
* The project to be translated is structured according to the [http://wiki.meego.com/Internationalization Internationalization] wiki
* Translation is happening on a Linux OS (MeeGo and Ubuntu were tested, Fedora ''should'' work too)
* QtCreator package is installed
* Linguist package is installed
* The xdg-utils package is installed
* Git package is installed

It is also assumed that the translator is:
* Completely familiar with Linquist. It is beyond the scope of this document to help with the use of Linquist.
* Familiar with Linux-based OSes and how to install packages into the Linux OS they are using
* Familiar in principle with the basic concepts of Version Control Systems, in particular, Git.
* Has the necessary accounts and rights to push changes to source trees for translations hosted on gitorious.org

Finally, it is assumed that once Transifex has support for Qt projects and Linguist, this process will become obsolete and all further translations will occur through Transifex.

===Process Summary===
The basic process, detailed below is:
# Customize QtCreator to launch Linguist
# Check out project sources (read-only) to provide code context. This step is optional, but recommended
# Check out project translations (read-write)
# Make changes to .ts files
# Publish updated translations back to upstream translation project

==Set External Editor==
# Start QtCreator
# Select "Options..." from the "Tools" menu:

:[[Image:QtCreator-Tools-Options.png]]
# Select "Environment" -> "General" option
# Change the value of "External Editor:" as follows:
## Erase the default setting (can be restored by clicking the "Back Arrow" button to the right)
## Type in "xdg-open %f"
##* Assumes you have the xdg-utils package installed
##* %f will be replaced with the file name to be opened
## Click "OK"

:[[Image:QtCreator-Tools-Options-Environment-General.png]]

==Clone Project Source==
For Qt/MTF-based projects that used the [http://wiki.meego.com/Internationalization MeeGo Internationalization wiki] to prepare their code for translation, you must first clone the base project sources if you want Linguist to be able to load the code in the context pane while translating.
* Start QtCreator (if not already running)
* Select "New File or Project" from the "File" menu:

:[[Image:QtCreator-New.png]]

* Select "Git Repository Clone"

:[[Image:QtCreator-New-Git.png]]

* Click "OK"
* Set clone options as follows:
** Clone URL example: git://gitorious.org/meego-handset-ux/meego-handset-dialer.git
** '''NOTE:''' We are using the "git" protocol here since we really '''do not''' want to be able to push changes to this project. It is only being cloned for contextual reference
** Checkout Directory: meego-handset-dialer
** Path: ~/dev/translations/

:[[Image:QtCreator-New-Git-Clone-Options.png]]

* Press "Next"
* Press "Finish"

You will now have a new project opened that is cloned from the upstream sources. For translation purposes, there is never any need to edit any of these files, so for simplicity sake, and to avoid confusion, it would be safest to close this project now.

==Clone Project Translations==
Now you must open a new project that is a clone of the above projects' translation sources.
# Start QtCreator (if not already running)
# Select "New File or Project" from the "File" menu:

:[[Image:QtCreator-New.png]]

# Select "Git Repository Clone"

:[[Image:QtCreator-New-Git.png]]

# Click "OK"
# Set clone options as follows:
##* Clone URL example: git@gitorious.org:meego-handset-ux/meego-handset-dialer-translations.git
##: '''NOTE:''' We are using the "ssh" protocol here since we '''do''' want to be able to push changes to this project.
##: This assumes you've properly configured your local system's git configuration to work with gitorious.org and the SSH key-based authentication (this is beyond the scope of this document).
##* Checkout Directory: meego-handset-dialer-translations
##* Path: ~/dev/translations/

:[[Image:QtCreator-New-Git-Clone-Options-2.png]]

# Click "Next"
# Click "Finish"

You are now using the new project for the translations you want to work on. To see the list of files in QtCreator, change the "Projects" pane to "File System" and you will see the list of .ts files available to work on.

Now lets get to editing and saving your work...

Category [[Localization]]