MeeGo wiki - User contributions [en]

MeeGo Conference 2010/Accommodation

2010-10-06T23:25:33Z

Glezos: /* Sponsored participants */

The MeeGo Conference has a deal with the [http://www.d4hotels.ie/ D4 Hotels]: we have made a group booking and they provide us 24h hackers rooms with great connectivity, a games room, basic infrastructure for the Early MeeGo Birds activities, etc.

If you haven't booked your room please do it now through this link: https://cpregistrations.com/MeeGo2010/

If you have booked elsewhere please consider re-booking at the D4 hotels, where most conference participants will be hosted. Thank you!

== Shared rooms ==
This table helps participants getting organized sharing rooms and costs. If you would like to share a double room with someone, please add your name to the table below.

{| border="1"
! Hotel
! Roommate 1
! Roommate 2
! Check in / check out / Considerations
|-
| Ballbridge Inn
|
|
|
|-
| Ballsbridge Towers
|
|
|
|-
| D4 Berkeley
|
|
|
|}

Add more lines to the table if needed. Just keep the rooms grouped by hotels.

== Sponsored participants ==

Sponsored participants get 4 nights in a shared double room covered by the organization. The reservation is done as a group booking by the organization directly.

'''Don't add yourself to this table unless you are an accepted sponsored participant.'''

If you want to swap room with a non-sponsored participant please do it directly at the hotel desk once you are in Dublin. To avoid mistakes, the group booking made by the organization will include only the names of the accepted sponsored participants included in this table.

{| border="1"
! # Room
! Roommate 1
! Roommate 2
! Check in / check out / Considerations
|-
| 1
| Dan Jensen (leinir)
|
| Arriving 13th - leaving 18th
|-
| 2
| Arek Stopczynski (hopbeat)
|
| arriving 14th - leaving 18th
|-
| 3
| Till Harbaum (harbaum)
|
| arriving 13th - leaving 17th
|-
| 4
| Brendan Le Foll (arfoll)
|
| arriving 14th - leaving 18th
|-
| 5
| Andrea Grandi (andreagrandi)
|
| arriving 13th - leaving ???
|-
| 6
| Lydia Pintscher (nightrose)
|
| arriving 14th - leaving 18th
|-
| 7
| Sivan Greenberg (sivang)
|
|
|-
| 8
| Randall Arnold (texrat)
| (awaiting word from eipi)
|
|-
| 9
| Kathryn Smith (RevdKathy)
|
| arriving 13th - leaving 17th
|-
| 10
| Dave Neary (dneary)
|
| Arriving Saturday, leaving Thursday (paying 1 extra night)
|-
| 11
| Leonardo da Mata (barroca)
|
| arriving 14th - leaving 18th (maybe arrive early paying 1 extra night)
|-
| 12
| Felipe Crochik (fcrochik)
|
| arriving 14th - leaving 18th (not confirmed yet)
|-
| 13
| Jonathan Tebaldi Petro (bioldo)
|
| arriving 14th - leaving 18th
|-
| 14
| timeless
|
| arriving 14th - leaving 18th (flights not booked yet...)
|-
| 15
| Dimitris Glezos (glezos)
| Diego Búrigo Zacarão (diegobz)
| arriving 14th - leaving 17th or 18th
|-
| 16
|
|
|
|}

Transifex Roadmap

2010-03-29T08:47:08Z

Glezos: Changed months into Quarters, as the beginning date for this schedule has yet to be finalized

# If MeeGo L10n will be hosted on Transifex.net, we need to develop support for Project Hubs, subdomain redirection (meego.transifex.net), theming, and a Hub dashboard (see qt.gitorious.org for an example).
# Make sure we connected with all necessary backend systems (gitorious, vcs.meego.com, etc.).
# Migrate projects from translate.moblin.org, users, and registered what's missing. Same for Maemo projects.

Transifex 0.8 (Q1/2010)

First bunch of community and basic features needed for Moblin, which will be inherited to MeeGo as well.
* Translation Teams
* Translation Reviews
* Timeline and Action History
* Project Releases
* Subversion over secure HTTP (https)
* Weekly Maintainer Reports
* User Nudging
* Lotte Filtering, support for more strings, Plurals, msgctxt, syntax checks

Transifex 0.9 (Q2/2010)
* Rough support for QT files
* API (notifications for automatic builds)
* Web hook: each project can define a URL which Transifex will hit with a POST request every time a file is submitted.
* OpenID support
* Signing a CLA
* Subdomains
* Better management of Releases (Copy release, mass editing)

Transifex 0.10 (Q2/2010)
* UI improvements: Improve usability, predictability, speed.
* Translation prioritization: What is important? What is urgent?
* User-to-user messaging
* Good documentation for everyone

Transifex 1.0 (Q3/2010)
* New storage backend is introduced
* Allow searching of existing translations
* Ability to start a new language (copy the POT file or an existing PO)
* Inline aspell-like spell checking in web editor
* Auto-modify the PO file headers (translator, last-updated field, copyright)
* PO files using logical IDs

Transifex 1.1 (Q3-Q4/2010)
* Support for Upstream: File splitting & export
* Per-string comments. To the developer, to other translators, etc.
* Translate from inside an emulator UI.
* Catch common translation errors between source and translated string.
* Lock selected languages for certain projects.
* Maintainer features to “thank” the translators before a release
* Kudos to translators. Something like a karma system maybe?

Transifex 1.1 (Q4/2010)
* API for automatic builds
* Better reviews (more fine-grained, with comments etc)
* Auto-merge with existing file and/or other branches

Transifex 1.2 (Q4/2010)
* Release “string-freezes” and “translation deadlines.”
* Calendar on homepage
* Translate Offline with Lotte OR integration with an offline tool.
* Glossary/Terminology
* Translator to define what he likes & receive notifications for new projects

Other tasks (not mounted)
Needs to support 1:n translations (needs more discussion). They will be used in Maemo 6 to provide strings with different length (e.g. portrait/landscape orientation). The number of variants may vary from language to language. Not sure exactly what's needed here.
<br />

Quality control<br />
Translation memory, suggestions, fuzzy matching. Pre-load other BSD-licensed projects and pre-fill the memory.

[[Category:Localization]]

Community Office

2010-03-29T08:40:07Z

Glezos: Added myself

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

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

== Mission ==

The Community working group defines the strategy for collaboration tools and processes within the MeeGo project, and observes its implementation.

== Structure ==

=== Coordination ===
The goals of the Community working group coordination are: '''(PROPOSAL)'''

* Overall guidance on tasks and priorities.
* Decision-making, when needed.
* Appointments within the working group.
* Connection with the MeeGo Technical Steering Group.

The coordinators are appointed by the TSG:
* [http://meego.com/users/dawnfoster Dawn Foster], since March 24, 2010. ''Intel's MeeGo community manager. I'm interested in helping out on a variety of community activities. I have past experience managing open source, developer and other types of online communities.''
* [http://meego.com/users/qgil Quim Gil], since March 24, 2010. ''Regular Nokia contact with the Maemo community and other free software projects. Nokia pays me to take care of open source / community matters in meego.com.''

=== Web infrastructure ===
Responsible of the maintenance of meego.com services and other MeeGo web services hosted elsewhere.

The overall facilitation is done by the [[Web infrastructure]] coordinators: (who?). See [[Single_sign-on]].

* [[Bugzilla]] team: [http://meego.com/users/lm lm]
* [[Drupal]] team: (who?). See [[News_and_Planet]].
* [[Extras/Downloads]] team:
* [[Forum]] team:
* [[Gitorious]] team:
* [[IRC]] team:
* [[OBS]] team:
* [[Mailman]] team: [http://meego.com/users/lm lm]
* [[MediaWiki]] team: (who?). See [[Special:LonelyPages]].
* [[Transifex]] team: (who?). See [[Transifex_Roadmap]].

=== Marketing ===
Internal and external communication, MeeGo identity, merchandising...

[[Marketing]] team: (who?).

See [[Metrics]].

=== Events ===
[[Events]] team: (who?).

See [[MeeGo Summit 2010]] - [http://meego.com/community/events/2010/linux-foundation-collaboration-summit MeeGo Workgroup @ Linux Collaboration Summit] and [http://meego.com/community/events other events]

=== Maemo/Moblin transition ===
Bringing the best from maemo.org and moblin.org to meego.com (urgent now, until the mission is fulfilled). See [[Maemo and Moblin community assets]].

Team: (a coordinator is needed).

== Work ==
The main channel of collaboration of this working group is the [MeeGo Community mailing list http://lists.meego.com/listinfo/meego-community]. You can also subscribe from [http://meego.com/profile your account page] on meego.com.

The plan is to have regular IRC meetings. There was a first [[Community_website_meeting_2010_2_24|Community website meeting]] on February 24, 2010.

== How to contribute ==
The immediate way of contributing is... contributing directly. Just go to your preferred corner of meego.com and help improving it!

If you want to formalize your contributions with an assigned role then look to the structure above. We need contributors in charge of core roles and tasks. Get involved in the team fitting best your interests and skills. If the team doesn't exist go to the meego-community mailing list and ask.

=== Contributors looking for a team ===

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

* [http://meego.com/users/Jeremiah Jeremiah C. Foster] - maemo.org's current debmaster. Recently I've taken on a role in the [http://genivi.org/ GENIVI Alliance] as Core Integration team lead. I would like to participate actively in helping develop MeeGO, keeping it open with a thriving community.

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

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

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

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

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

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

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

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

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

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

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

* [http://meego.com/users/w00t Robin Burchell] - maemo fan as of n900, wide variety of technical skills from C++ (yes, including Qt)/PHP to server administration. happy to help the community, however I can.

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

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

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

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

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

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

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

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

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

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

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

* [http://meego.com/users/niqt Nicola De Filippo] - maemo Qt4 contributor; technical skills: Qt (from 1997), C++, Javascript, Php, Java, Python

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

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

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

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

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

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

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

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

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

Localization team

2010-03-24T21:05:10Z

Glezos:

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

This is a request to the Technical Steering Group to approve the creation of a Localization working group. There is no procedure defined but we can can improvise with some common sense.

=== Announcement ===

There is an upcoming Technical Steering Group meeting on http://meego.com/community/irc-channel. The scheduled time is Wednesday, March 24th 2010 at 20:00 UTC. Please note that the channel chosen for this meeting is #meego-meeting. An agenda for the meeting is [http://meego.com/community/events/2010/meego-technical-steering-group-meeting here]. This L10N working group proposal will be considered by the Technical Steering Group during the meeting.

Current and older L10N meetings can be found [http://wiki.meego.com/L10n_meeting_schedule here].

=== How to contribute ===

To discuss and plan the localization of MeeGo, subscribe to the MeeGo l10n mailing list: http://lists.meego.com/listinfo/meego-l10n. You can also subscribe from your account page on meego.com.

=== Mission ===

The Localization working group defines the strategy for utilizing crowd-sourcing for translating MeeGo into multiple languages, and observes its implementation. Using [http://www.transifex.net/ Transifex] as the tool, our goal is to build a community of dedicated translators, editors, reviewers, and testers in multiple languages.

Related pages:
* [[L10n_plan]]
* [[L10N/RoadmapProposal]]

=== Areas ===

The main areas within the scope of the working group are (in no particular order):

* Maemo/Moblin transition: bringing the best of localization policies, procedures, and best-known methods from maemo.org and moblin.org to meego.com
* Transifex administration: deciding where to host the tool, determining a team of admins and other users with special permissions, server administration
* Crowd-sourcing infrastructure: selection and administration of online tools for l10n community collaboration
* Localization teams: [[Language specific working groups]].

=== Contributors ===

MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:

* [http://meego.com/users/margie Margie Foster] - I am currently the l10n project manager for Moblin, and will be transitioning my focus to MeeGo. Submitter of this proposal and happy to take an active role. Full disclosure: I am an [http://intel.com Intel] employee.
* [http://meego.com/users/glezos Dimitris Glezos] - I am the creator and lead developer for [http://www.transifex.net/ Transifex], the L10n tool powering the translations of [http://translate.moblin.org/ Moblin] and [http://www.transifex.net/collections/c/maemo-extras/ Maemo Extras], and also the L10n lead of the Fedora Project. I'd be happy to take an active role in the L10n engineering of MeeGo. Full disclosure: I am an [http://indifex.com/ Indifex] employee, the company sponsoring the development of Transifex.
* [http://meego.com/users/omaciel Og Maciel] - I am deeply involved with the translation efforts of several open source groups including GNOME, Xfce, LXDE, Openbox, Moblin, and some minor contributions to KDE and Fedora. I'd be very interested to also take a more active role in the engineering and steering process of making MeeGo internationalized. Full disclosure: I am a big Transifex supporter (for many reasons) and am huge on quality control!
* [http://meego.com/users/milo Milo Casagrande] - I'm involved with different translation groups (Ubuntu, GNOME, and the Translation Project), and I'm leading the Italian Ubuntu translators group. I've made contributions also to Debian and Fedora, although I'm not really involved with them. I'd be happy to help this new L10n group.
* [http://meego.com/users/timeless timeless] - I maintain alternate translations of Maemo 4 and 5 for en_US and en_GB, which are also the basis for Mer. I've been on the periphery of l10n concerns as a member of the [http://mozilla.org Mozilla community]. Full disclosure: I am a [http://nokia.com Nokia] employee.
* [http://meego.com/users/solt Marcin Sołtysiak] - [http://www.midgard-project.org/ Midgard]/MidCOM contributor and translator, [http://qaiku.com Qaiku] translator, [http://maemo.org/downloads/product/OS2008/os2008pl/ OS2008] (Chinook/Diablo) translator. Just a fan.

[[Category:Localization]]

L10n

2010-03-24T20:39:50Z

Glezos: Created page with '= MeeGo Localization = == Related pages == A complete list of the pages in this space can be found in the related category: :Category:Localization'

= MeeGo Localization =

== Related pages ==

A complete list of the pages in this space can be found in the related category:

[[:Category:Localization]]

Category:Localization

2010-03-24T20:24:58Z

Glezos: Created page with 'This is a collection of wiki pages related to Localization (L10n).'

This is a collection of wiki pages related to Localization ([[L10n]]).

L10N/RoadmapProposal

2010-03-05T15:47:20Z

Glezos:

= L10n Roadmap for MeeGo =

Localization is vital for MeeGo. Both Moblin and Maemo have identified this by running processes where feedback was collected on what's needed to establish a good Localization workflow which will ensure that the software and devices will be shipped in as many languages and as high quality as possible. To do this a vibrant community needs to be built with the necessary tools to work efficiently and effectively.

Both projects have decided to use Transifex for translations, which gives us the base to make some assumptions and see what we need to improve. What follows is an aggregated combined list of the requests collected from both projects about what they'd like to see to ensure the above.

This list is intended to serve as a starting point for a discussion on what needs to be done in a timeframe of e.g. 8-10 months.

== Establish a hosting platform for MeeGo Translations ==

# If MeeGo L10n will be hosted on Transifex.net, we need to develop support for Project Hubs, subdomain redirection (meego.transifex.net), theming, and a Hub dashboard (see qt.gitorious.org for an example).
# Make sure we connected with all necessary backend systems (gitorious, vcs.meego.com, etc.).
# Migrate projects from translate.moblin.org, users, and registered what's missing. Same for Maemo projects.

== Technical features needed ==

# Support for QT files (.ts) v3.0 which introduces multiple variants of translations for different screen sizes. The support should go from statistics to Lotte itself.
# PO files using logical IDs used in Fremantle. Logical IDs are used by Nokia internal software like, for example, the media player. Transifex needs to preserve these and make sure they work properly.
# Better backend support (API improvements) to hook-up with build services, etc. This will help issue automatic builds e.g. right after the translator deadline is finished, or 2 days before it (to review translations, whether they look OK on the screen and in the context).
# Needs to support 1:n translations (needs more discussion). They will be used in Maemo 6 to provided strings with different length (e.g. portrait/landscape orientation). The number of variants may vary from language to language. Not sure exactly what's needed here.
# Split distribution specific strings from upstream PO files.

== Translator workflow improvements ==

# Better reviews: The Reviews should happen on a string-level and not on file-level. A reviewer needs to see what has changed, be able to comment on specific strings etc. Right now the reviewing is pretty naive (you just upload a file similar to a bug report).
# Ability to start a new language (copy the POT file or an existing PO to a new one) from the UI, i.e. avoid to download it and re-upload it. Very useful for e.g. translate Brazilian Portuguese by cloning Portuguese.
# UI improvements (lots of them): Improve usability, predictability, speed. Sounds like a nice GsoC project as well.
# Translation prioritization: What is important? What is urgent? If I have two hours, what should I translate? This is very important – every translator is asking for this, although we rarely push its priority high enough.
# Inline aspell-like spell checking in web editor. It's a pity to not do this automatically since there are tools to do it.
# Release “string-freezes” and “translation deadlines”. Provide a nice calender with the collected release dates (important for translators to prioritize their work).
# Ability to report problems on strings to the developer, add comments on the string for other translators etc. If a translator gets an answer about what the string means, he should be able to annotate in Transifex and let everyone know.
# Auto-modify the PO file headers with the name of the translator, the last-translated field, copyright notice etc. Translators could properly be credited in the package/application.
# Uploads should be able to also merge with the file on the server: either with the existing file or with other stable branches. If it.po exists on Component1 but not on Component2, take c2.it = msgmerge(c1.it, c2.pot).
# Translate Offline with Lotte OR integration with an offline tool (eg. Poedit). So many people could translate on the train or in their free time. Also, since we're on it: Create a mobile version of the site, optimized for mobile devices?

== Quality control ==

# Translation memory, suggestions, fuzzy matching. Pre-load other BSD-licensed projects and pre-fill the memory.
# Glossary/Terminology: Ensure consistency. Generate a glossary for your language from existing translations.
# Allow searching of existing translations. Now it's done in the same PO File. We need to search across the whole Project.
# Translate from inside an emulator UI. Requires API changes and building the necessary SDK/IDE UI. Max-length for strings and other attributes could also be defined to have an easier implementation.
# Catch common translation errors between source and translated string, like punctuation, quotes, both strings start with capital letter, etc.
# Lock selected languages for certain projects (requested by Maemo, for example because this language for this project is being handled by another entity).
# Good documentation for everyone: Developers: How to write good strings, What to avoid when writing strings (positional arguments, ...). Translators: Translation best practices / common pitfalls, How to test your translations on the device, how to translate package names.

== Social/collaboration features ==

# OpenID support to authenticate using meego.com
# Signing a CLA: Show a license page, which translators have to agree to commit there translations.
# User-to-user messaging: It is vital to have a communication system inside the L10n platform, to comment in-line and in-context and avoid having mailing lists.
# Maintainer features to “thank” the translators before a release (collect their names, the number of strings they translated and languages). Useful to create a THANKS or CONTRIBUTORS file.
# Allow a translator to define what he likes translating (tags) and automatically notify him when new projects show up which could use his help.
# Kudos to translators. Something like a karma system maybe?

== Extra suggestions/RFEs ==

Add your own ponies here.

* ...

L10N/RoadmapProposal

2010-03-04T19:44:02Z

Glezos: typo

= L10n Roadmap for MeeGo =

Localization is vital for MeeGo. Both Moblin and Maemo have identified this by running processes where feedback was collected on what's needed to establish a good Localization workflow which will ensure that the software and devices will be shipped in as many languages and as high quality as possible. To do this a vibrant community needs to be built with the necessary tools to work efficiently and effectively.

Both projects have decided to use Transifex for translations, which gives us the base to make some assumptions and see what we need to improve. What follows is an aggregated combined list of the requests collected from both projects about what they'd like to see to ensure the above.

This list is intended to serve as a starting point for a discussion on what needs to be done in a timeframe of e.g. 8-10 months.

== Establish a hosting platform for MeeGo Translations ==

# If MeeGo L10n will be hosted on Transifex.net, we need to develop support for Project Hubs, subdomain redirection (meego.transifex.net), theming, and a Hub dashboard (see qt.gitorious.org for an example).
# Make sure we connected with all necessary backend systems (gitorious, vcs.meego.com, etc.).
# Migrate projects from translate.moblin.org, users, and registered what's missing. Same for Maemo projects.

== Technical features needed ==

# Support for QT files (.ts) v3.0 which introduces multiple variants of translations for different screen sizes. The support should go from statistics to Lotte itself.
# PO files using logical IDs used in Fremantle. Logical IDs are used by Nokia internal software like, for example, the media player. Transifex needs to preserve these and make sure they work properly.
# Better backend support (API improvements) to hook-up with build services, etc. This will help issue automatic builds e.g. right after the translator deadline is finished, or 2 days before it (to review translations, whether they look OK on the screen and in the context).
# Needs to support 1:n translations (needs more discussion). They will be used in Maemo 6 to provided strings with different length (e.g. portrait/landscape orientation). The number of variants may vary from language to language. Not sure exactly what's needed here.

== Translator workflow improvements ==

# Better reviews: The Reviews should happen on a string-level and not on file-level. A reviewer needs to see what has changed, be able to comment on specific strings etc. Right now the reviewing is pretty naive (you just upload a file similar to a bug report).
# Ability to start a new language (copy the POT file or an existing PO to a new one) from the UI, i.e. avoid to download it and re-upload it. Very useful for e.g. translate Brazilian Portuguese by cloning Portuguese.
# UI improvements (lots of them): Improve usability, predictability, speed. Sounds like a nice GsoC project as well.
# Translation prioritization: What is important? What is urgent? If I have two hours, what should I translate? This is very important – every translator is asking for this, although we rarely push its priority high enough.
# Inline aspell-like spell checking in web editor. It's a pity to not do this automatically since there are tools to do it.
# Release “string-freezes” and “translation deadlines”. Provide a nice calender with the collected release dates (important for translators to prioritize their work).
# Ability to report problems on strings to the developer, add comments on the string for other translators etc. If a translator gets an answer about what the string means, he should be able to annotate in Transifex and let everyone know.
# Auto-modify the PO file headers with the name of the translator, the last-translated field, copyright notice etc. Translators could properly be credited in the package/application.
# Uploads should be able to also merge with the file on the server: either with the existing file or with other stable branches. If it.po exists on Component1 but not on Component2, take c2.it = msgmerge(c1.it, c2.pot).
# Translate Offline with Lotte OR integration with an offline tool (eg. Poedit). So many people could translate on the train or in their free time. Also, since we're on it: Create a mobile version of the site, optimized for mobile devices?

== Quality control ==

# Translation memory, suggestions, fuzzy matching. Pre-load other BSD-licensed projects and pre-fill the memory.
# Glossary/Terminology: Ensure consistency. Generate a glossary for your language from existing translations.
# Allow searching of existing translations. Now it's done in the same PO File. We need to search across the whole Project.
# Translate from inside an emulator UI. Requires API changes and building the necessary SDK/IDE UI. Max-length for strings and other attributes could also be defined to have an easier implementation.
# Catch common translation errors between source and translated string, like punctuation, quotes, both strings start with capital letter, etc.
# Lock selected languages for certain projects (requested by Maemo, for example because this language for this project is being handled by another entity).
# Good documentation for everyone: Developers: How to write good strings, What to avoid when writing strings (positional arguments, ...). Translators: Translation best practices / common pitfalls, How to test your translations on the device, how to translate package names.

== Social/collaboration features ==

# Signing a CLA: Show a license page, which translators have to agree to commit there translations.
# User-to-user messaging: It is vital to have a communication system inside the L10n platform, to comment in-line and in-context and avoid having mailing lists.
# Maintainer features to “thank” the translators before a release (collect their names, the number of strings they translated and languages). Useful to create a THANKS or CONTRIBUTORS file.
# Allow a translator to define what he likes translating (tags) and automatically notify him when new projects show up which could use his help.
# Kudos to translators. Something like a karma system maybe?

== Extra suggestions/RFEs ==

Add your own ponies here.

* ...

L10N/RoadmapProposal

2010-03-04T19:42:50Z

Glezos:

= L10n Roadmap for MeeGo =

Localization is vital for MeeGo. Both Moblin and Maemo have identified this by running processes where feedback was collected on what's needed to establish a good Localization workflow which will ensure that the software and devices will be shipped in as many languages and as high quality as possible. To do this a vibrant community needs to be built with the necessary tools to work efficiently and effectively.

Both projects have decided to use Transifex for translations, which gives us the base to make some assumptions and see what we need to improve. What follows is an aggregated combined list of the requests collected from both projects about what they'd like to see to ensure the above.

This list is intended to serve as a starting point for a discussion on what needs to be done in a timeframe of e.g. 8-10 months.

== Establish a hosting platform for MeeGo Translations ==

# If MeeGo L10n will be hosted on Transifex.net, we need to develop support for Project Hubs, subdomain redirection (meego.transifex.net), theming, and a Hub dashboard (see qt.gitorious.org for an example).
# Make sure we connected with all necessary backend systems (gitorious, vcs.meego.com, etc.).
# Migrate projects from translate.moblin.org, users, and registered what's missing. Same for Maemo projects.

== Technical features needed ==

# Support for QT files (.ts) v3.0 which introduces multiple variants of translations for different screen sizes. The support should go from statistics to Lotte itself.
# PO files using logical IDs used in Fremantle. Logical IDs are used by Nokia internal software like, for example, the media player. Transifex needs to preserve these and make sure they work properly.
# Better backend support (API improvements) to hook-up with build services, etc. This will help issue automatic builds e.g. right after the translator deadline is finished, or 2 days before it (to review translations, whether they look OK on the screen and in the context).
# Needs to support 1:n translations (needs more discussion). They will be used in Maemo 6 to provided strings with different length (e.g. portrait/landscape orientation). The number of variants may vary from language to language. Not sure exactly what's needed here.

== Translator workflow improvements ==

# Better reviews: The Reviews should happen on a string-level and not on file-level. A reviewer needs to see what has changed, be able to comment on specific strings etc. Right now the reviewing is pretty naive (you just upload a file similar to a bug report).
# Ability to start a new language (copy the POT file or an existing PO to a new one) from the UI, i.e. avoid to download it and re-upload it. Very useful for e.g. translate Brazilian Portuguese by cloning Portuguese.
# UI improvements (lots of them): Improve usability, predictability, speed. Sounds like a nice GsoC project as well.
# Translation prioritization: What is important? What is urgent? If I have two hours, what should I translate? This is very important – every translator is asking for this, although we rarely push its priority high enough.
# Inline aspell-like spell checking in web editor. It's a pity to not do this automatically since there are tools to do it.
# Release “string-freezes” and “translation deadlines”. Provide a nice calender with the collected release dates (important for translators to prioritize their work).
# Ability to report problems on strings to the developer, add comments on the string for other translators etc. If a translator gets an answer about what the string means, he should be able to annotate in Transifex and let everyone know.
# Auto-modify the PO file headers with the name of the translator, the last-translated field, copyright notice etc. Translators could properly be credited in the package/application.
# Uploads should be able to also merge with the file on the server: either with the existing file or with other stable branches. If it.po
# exists on Component1 but not on Component2, take c2.it = msgmerge(c1.it, c2.pot).
# Translate Offline with Lotte OR integration with an offline tool (eg. Poedit). So many people could translate on the train or in their free time. Also, since we're on it: Create a mobile version of the site, optimized for mobile devices?

== Quality control ==

# Translation memory, suggestions, fuzzy matching. Pre-load other BSD-licensed projects and pre-fill the memory.
# Glossary/Terminology: Ensure consistency. Generate a glossary for your language from existing translations.
# Allow searching of existing translations. Now it's done in the same PO File. We need to search across the whole Project.
# Translate from inside an emulator UI. Requires API changes and building the necessary SDK/IDE UI. Max-length for strings and other attributes could also be defined to have an easier implementation.
# Catch common translation errors between source and translated string, like punctuation, quotes, both strings start with capital letter, etc.
# Lock selected languages for certain projects (requested by Maemo, for example because this language for this project is being handled by another entity).
# Good documentation for everyone: Developers: How to write good strings, What to avoid when writing strings (positional arguments, ...). Translators: Translation best practices / common pitfalls, How to test your translations on the device, how to translate package names.

== Social/collaboration features ==

# Signing a CLA: Show a license page, which translators have to agree to commit there translations.
# User-to-user messaging: It is vital to have a communication system inside the L10n platform, to comment in-line and in-context and avoid having mailing lists.
# Maintainer features to “thank” the translators before a release (collect their names, the number of strings they translated and languages). Useful to create a THANKS or CONTRIBUTORS file.
# Allow a translator to define what he likes translating (tags) and automatically notify him when new projects show up which could use his help.
# Kudos to translators. Something like a karma system maybe?

== Extra suggestions/RFEs ==

* ...

L10N/RoadmapProposal

2010-03-04T19:40:02Z

Glezos: Yeehaa!

= L10n Roadmap for MeeGo =

Localization is vital for MeeGo. Both Moblin and Maemo have identified this by running processes where feedback was collected on what's needed to establish a good Localization workflow which will ensure that the software and devices will be shipped in as many languages and as high quality as possible. To do this a vibrant community needs to be built with the necessary tools to work efficiently and effectively.

Both projects have decided to use Transifex for translations, which gives us the base to make some assumptions and see what we need to improve. What follows is an aggregated combined list of the requests collected from both projects about what they'd like to see to ensure the above.

This list is intended to serve as a starting point for a discussion on what needs to be done in a timeframe of e.g. 8-10 months.

== Establish a hosting platform for MeeGo Translations ==

# If MeeGo L10n will be hosted on Transifex.net, we need to develop support for Project Hubs, subdomain redirection (meego.transifex.net), theming, and a Hub dashboard (see qt.gitorious.org for an example).
# Make sure we connected with all necessary backend systems (gitorious, vcs.meego.com, etc.).
# Migrate projects from translate.moblin.org, users, and registered what's missing. Same for Maemo projects.

== Technical features needed ==

# Support for QT files (.ts) v3.0 which introduces multiple variants of translations for different screen sizes. The support should go from statistics to Lotte itself.
# PO files using logical IDs used in Fremantle. Logical IDs are used by Nokia internal software like, for example, the media player. Transifex needs to preserve these and make sure they work properly.
# Better backend support (API improvements) to hook-up with build services, etc. This will help issue automatic builds e.g. right after the translator deadline is finished, or 2 days before it (to review translations, whether they look OK on the screen and in the context).
# Needs to support 1:n translations (needs more discussion). They will be used in Maemo 6 to provided strings with different length (e.g. portrait/landscape orientation). The number of variants may vary from language to language. Not sure exactly what's needed here.

== Translator workflow improvements ==

# Better reviews: The Reviews should happen on a string-level and not on file-level. A reviewer needs to see what has changed, be able to comment on specific strings etc. Right now the reviewing is pretty naive (you just upload a file similar to a bug report).
# Ability to start a new language (copy the POT file or an existing PO to a new one) from the UI, i.e. avoid to download it and re-upload it. Very useful for e.g. translate Brazilian Portuguese by cloning Portuguese.
# UI improvements (lots of them): Improve usability, predictability, speed. Sounds like a nice GsoC project as well.
# Translation prioritization: What is important? What is urgent? If I have two hours, what should I translate? This is very important – every translator is asking for this, although we rarely push its priority high enough.
# Inline aspell-like spell checking in web editor. It's a pity to not do this automatically since there are tools to do it.
# Release “string-freezes” and “translation deadlines”. Provide a nice calender with the collected release dates (important for translators to prioritize their work).
# Ability to report problems on strings to the developer, add comments on the string for other translators etc. If a translator gets an answer about what the string means, he should be able to annotate in Transifex and let everyone know.
# Auto-modify the PO file headers with the name of the translator, the last-translated field, copyright notice etc. Translators could properly be credited in the package/application.
# Uploads should be able to also merge with the file on the server: either with the existing file or with other stable branches. If it.po
# exists on Component1 but not on Component2, take c2.it = msgmerge(c1.it, c2.pot).
# Translate Offline with Lotte OR integration with an offline tool (eg. Poedit). So many people could translate on the train or in their free time. Also, since we're on it: Create a mobile version of the site, optimized for mobile devices?

== Quality control ==

# Translation memory, suggestions, fuzzy matching. Pre-load other BSD-licensed projects and pre-fill the memory.
# Glossary/Terminology: Ensure consistency. Generate a glossary for your language from existing translations.
# Allow searching of existing translations. Now it's done in the same PO File. We need to search across the whole Project.
# Translate from inside an emulator UI. Requires API changes and building the necessary SDK/IDE UI. Max-length for strings and other attributes could also be defined to have an easier implementation.
# Catch common translation errors between source and translated string, like punctuation, quotes, both strings start with capital letter, etc.
# Lock selected languages for certain projects (requested by Maemo, for example because this language for this project is being handled by another entity).
# Good documentation for everyone: Developers: How to write good strings, What to avoid when writing strings (positional arguments, ...). Translators: Translation best practices / common pitfalls, How to test your translations on the device, how to translate package names.

== Social/collaboration features ==

# Signing a CLA: Show a license page, which translators have to agree to commit there translations.
# User-to-user messaging: It is vital to have a communication system inside the L10n platform, to comment in-line and in-context and avoid having mailing lists.
# Maintainer features to “thank” the translators before a release (collect their names, the number of strings they translated and languages). Useful to create a THANKS or CONTRIBUTORS file.
# Allow a translator to define what he likes translating (tags) and automatically notify him when new projects show up which could use his help.
# Kudos to translators. Something like a karma system maybe?

Who's who

2010-02-19T12:16:52Z

Glezos: /* MeeGo community */

== Technical Steering Group ==
''Members of the [http://meego.com/about/governance TSG]''

* [http://meego.com/users/imad Imad Sousou/imad] - Benevolent dictator
* [http://meego.com/users/valhalla Valtteri Halla] - Benevolent dictator
* ???

== Maemo community stakeholders ==
'' Official representatives of the Maemo community''

* [http://meego.com/users/qgil Quim Gil/qgil] - Nokia's Maemo Community Manager
* [http://meego.com/users/tekojo Tero Kojo/tekojo] - Nokia's Maemo Technical Project Manager
* [http://meego.com/users/xfade Niels Breet/X-Fade] - Maemo.org webmaster
* Dave Neary/dneary - Maemo.org docmaster
* [http://meego.com/users/andre André Klapper/andre_] - Maemo.org bugmaster
* [http://meego.com/users/jeremiah Jeremiah Foster/jeremiah] - Maemo.org debmaster
* [http://meego.com/users/reggie Reggie Suplido] - Maemo.org talkmaster
* [http://meego.com/users/stskeeps Carsten Munk/Stskeeps] - Maemo.org distmaster & Mer project lead
* [http://meego.com/users/bergie Henri Bergius/bergie] - Maemo.org web/Midgard developer
* [http://meego.com/users/vdvsx Valerio Valerio/VDVsx] - Maemo Community Council chair
* [http://meego.com/users/texrat Randall Arnold/Texrat] - Maemo Community Council member
* [http://meego.com/users/qole Alan Bruce/qole] - Maemo Community Council member
* [http://meego.com/users/penguinbait Matthew Lewis/penguinbait] - Maemo Community Council member
* Graham Cobb - Maemo Commnunity Council member

== Moblin community stakeholders ==
''Representatives of the Moblin community''

* [http://meego.com/users/dirkhh Dirk Hohndel/dirkhh] - Chief Linux and open source technologist at Intel
* [http://meego.com/users/townxelliot Elliot Smith/townxelliot] - Moblin.org & meego.com website techy
* [http://meego.com/users/mshaver Michael Shaver/mshaver] - Moblin.org webmaster & meego.com website developer
* [http://meego.com/users/margie Margie Foster/mlfoster] - Localization project manager for Moblin & meego.com website developer

== MeeGo developers ==
'' People paid to contribute to MeeGo and/or have commit rights''

* [http://meego.com/users/nashif Anas Nashif/anaZ] - Random developer
* [http://meego.com/users/hbons Hylke Bons/hbons] - User Experience Designer
* [http://meego.com/users/auke Auke Kok/auke] - Developer
* [http://meego.com/users/jku Jussi Kukkonen/jku] - Developer
* [http://meego.com/users/quang Quang Pham/quang] - Developer
* [http://meego.com/users/nmcgovern Neil McGovern/nmcgovern] - Developer

== MeeGo community ==
''Anyone not in the above sections'' (Please keep this list alphabetically-ordered, as it will make finding people easier.)

* [http://meego.com/users/aboaboit Andrea Borgia/aboaboit] - Maemo community member
* [http://meego.com/users/jaffa Andrew Flegg/Jaffa] - Long term gadget freak & Maemo community member
* [http://meego.com/users/lbt David Greaves/lbt] - Mer OBS build guy.
* [http://meego.com/users/glezos Dimitris Glezos/glezos] - Localization Engineer ([http://www.transifex.net/ Transifex])
* [http://borasky-research.net M. Edward (Ed) Borasky] - Linux capacity planning / audio / openSUSE / Twitter geek
* [http://meego.com/users/debernardis Ernesto de Bernardis/debernardis] - Maemo community member, mobile device tinkerer
* [http://meego.com/users/zerojay Jason Carter/zerojay] - Long term Maemo community member
* [http://meego.com/users/lpotter Lorn Potter/lpotter/ljp] - QDF, Mobility, Nokia,
* [http://meego.com/users/w00t Robin Burchell/w00t] - Developer of random things, gadget enthusiast, Maemo community member
* [http://meego.com/users/martinmohring Martin Mohring / ScriptRipper] - Buildservice developer, Linux Foundation member
* [http://meego.com/users/dl9pf Jan-Simon Möller / dl9pf ] - Build service developer, Linux Foundation member
* [http://meego.com/users/generalantilles Ryan Abel/GeneralAntilles] - Long term Maemo community member
* [http://meego.com/users/slauwers Sebastian Lauwers/crashanddie] - Community member, talk.maemo.org moderator / ActivIdentity Professional Services Technical Consultant
* [http://meego.com/users/timeless timeless/timeless] - Mozilla contributor, Nokia employee.
* [http://meego.com/users/corsac Yves-Alexis Perez / Corsac] - Debian developer, Maemo community member, security engineer
__NOTOC__ 

[[Category:Community]]

Localization team

2010-02-17T23:58:57Z

Glezos: adding dg as participant!

The role of MeeGo working groups are explained at http://meego.com/about/governance
This is a request to the Technical Steering Group to approve the creation of a Localization working group. There is no procedure defined but we can can improvise with some common sense.

To discuss and plan the localization of MeeGo, subscribe to the MeeGo l10n mailing list: http://lists.meego.com/listinfo/meego-l10n. You can also subscribe from your account page on meego.com.

Mission

The Localization working group defines the strategy for utilizing crowd-sourcing for translating MeeGo into multiple languages, and observes its implementation. Using Transifex as the tool, our goal is to build a community of dedicated translators, editors, reviewers, and testers in multiple languages.

Areas

The main areas within the scope of the working group are (in no particular order):

* Maemo/Moblin transition: bringing the best of localization policies, procedures, and best-known methods from maemo.org and moblin.org to meego.com
* Transifex administration: deciding where to host the tool, determining a team of admins and other users with special permissions, server administration
* Crowd-sourcing infrastructure: selection and administration of online tools for l10n community collaboration

Contributors

MeeGo members interested in taking an active role in this working group. Please detail your interests and what you can contribute to the group:

* Margie Foster - I am currently the l10n project manager for Moblin, and will be transitioning my focus to MeeGo. Submitter of this proposal and happy to take an active role. Full disclosure: I am an Intel employee.
* Dimitris Glezos - I am the creator and lead developer for [http://www.transifex.net/ Transifex], the L10n tool powering the translations of [http://translate.moblin.org/ Moblin] and [http://www.transifex.net/collections/c/maemo-extras/ Maemo Extras], and also the L10n lead of the Fedora Project. I'd be happy to take an active role in the L10n engineering of MeeGo. Full disclosure: I am an Indifex employee, the company sponsoring the development of Transifex.