MozillaWiki - User contributions [en]

L10n:Meetings/2016 Berlin hackathon

2016-05-16T13:04:32Z

Dwayne: /* Goals */ Add ZA goals

[[Category:L10n meetings|{{SUBPAGENAME}}]]
__NOTOC__
==Logistics==
;Where: Mozilla Berlin Office

6, Voltastraße 5, 13355

Map: https://bit.ly/1Q95Dst
;When: 3-6 June
;Lodging:
*Hotel: [http://www.motel-one.com/en/hotels/berlin/hotel-berlin-bellevue/#t=hotelinfo Motel One Berlin-Bellevue]
*Phone: +49/30/3 90 63 34-0
*Map: http://tinyurl.com/jj3gsfp
;Arriving at lodging:
*Suburban station: Bellevue / Subway station: Hansaplatz
*Bus stop: Paulstraße
**From the airport
**From the train station
**From long distance bus station
Best to go by bus TXL/187, https://goo.gl/maps/QULwbRT7kD42, should be 2,70 euros

;From lodging to Mozilla Berlin Office

Probably Bus 100, S2, https://goo.gl/maps/EqqRqaDaecA2.
We should probably take group tickets, a day for 5 persons.

;Reimbursement

Please keep all your receipts for transportation and send them to Peiying after you have completed all your travels. She will reimburse you through PayPal. Do let her know if you do *not* have a PayPal account. Your travel cost includes the plane, train and long distance bus travel as well as transportation in Berlin.

==Goals==
;German
**Valerie is more interested in experimental stuff
**Richard needs more training: Web l10n focused
**Fx 49 l10n

;English (British)

;English (South African)
* Leveraging en_ZA for locale redirection
* Avenues for specific en_ZA marketing

;Dutch

;Frisian

;Ukrainian

==Agenda==
===Saturday 4 June ===
;Morning - 930AM
*Welcome & spectrograms -- Axel & Pei
*Mozilla mission and org updates applied to your locales -- Axel & Pei
**L10n updates from [https://blog.mozilla.org/l10n/2016/01/08/mozlando-localization-sessions/ Mozlando]
;Lunch -- TBD
;Afternoon
;Dinner -- TBD

===Sunday 5 June ===
;Morning -- 930AM
;Lunch -- TBD
;Afternoon
*Update team wiki pages
*Take l10n hackathon survey.
*Begin plans for next l10n meetup.
*Group pictures.
;Dinner -- TBD

==Other==
*Hashtag for event: #mozberlinl10n
;Notes: https://public.etherpad-mozilla.org/p/berlin-l10n-meetup-notes
;Resources:
*[https://telegram.me/joinchat/DK3sqwe6_7KPIMn0IEL5aQ Berlin Hackathon Telegram Group]
*[https://l10n.mozilla.org Mozilla l10n home page]
*[http://mozilla.locamotion.org Pootle translation tool]
*[https://addons.mozilla.org/En-us/firefox/language-tools/ Firefox language pack add-ons]
*[https://lists.mozilla.org/listinfo/dev-l10n Mozilla l10n mailing list (please subscribe)]
*[https://twitter.com/mozilla_l10n @mozilla_l10n Twitter account]

L10n:Teams:nyn

2015-09-28T15:32:22Z

Dwayne: Initial Nkore page

__NOTOC__

===Nkore (nyn)===
''If you have an image, be sure to add one here and align it to the right.''

Team website:

====Active team members====

{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Desktop OS
! Tablet OS
! Mobile OS
! Hg Access?
! SVN Access?
|-
| Your Name
| yourname@example.com
| Toolkit/Browser Owner
| Ubuntu version #
| Windows 8 Metro
| Android ICS
| YES; Level 1 L10n (Add link to bug)
| YES (Add link to bug)
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
| row 2, cell 4
| row 2, cell 5
| row 2, cell 6
| row 2, cell 7
| row 2, cell 8
|}

====Localizers in training====

{| border="1" class="wikitable"
|-
! Name
! Email
! Project assignment
! Desktop OS
! Tablet OS
! Mobile OS
|-
| Your Name
| yourname@example.com
| SUMO localization
| Ubuntu version #
| Windows 8 Metro
| Android ICS
|-
| row 2, cell 1
| row 2, cell 2
| row 2, cell 3
| row 2, cell 4
| row 2, cell 5
| row 2, cell 6
|}

====Active projects====

''Which mozilla projects is your community actively localizing? Please add links to dashboards for these projects.''

====L10n kit====
''Please list here the tools your team uses, as well as links to your L10n assets (e.g., translation memories, termbases, style guides, etc.).''
;Tools:
;Translation Memory:
;Glossary:
;Style Guide:

====How to join this l10n team====
''Five steps for newcomers to learn how to join your l10n team''

====Team communication====

''Please add mailing lists, community websites, etc.''

<noinclude>[[category:L10n Teams|nyn]]</noinclude>

Fosdem:2014:Attendees

2014-01-16T09:38:52Z

Dwayne:

* Gervase Markham
* Delphine Lebédel
* Ziggy Maes
* Monique Brunel
* Antoine Duparay / Flaburgan
* Flore Allemandou
* Dirkjan Ochtman
* Francisco Picolini
* Redon Skikuli
* Giannis Konstantinidis
* Valentin Gosu
* Stephen John Murphy
* Alfredos-Panagiotis Damkalis
* Claire Corgnou
* Sara Prussak
* Antoine Duparay
* William Duyck
* Ashickur Rahman
* Sayak Sarkar
* Eduardo Urcullú Madrid
* Soumya Deb
* Priyanka Nag
* Srikar Ananthula
* Axel Hecht
* Pascal Chevrel
* Arky
* Henrik Skupin
* Dwayne Bailey

L10n:Teams:af

2012-12-03T09:50:32Z

Dwayne: /* L10n tools */ Fix link to Pootle

=== Afrikaans (af) ===

====Team members====

{| border="1" class="wikitable"
|-
! Name
! Email
! Role
! Hg/SVN Access?
|-
| Friedel Wolff
| friedel atsign translate dot org dot za
| Team lead
| YES
|-
| Dwayne Bailey
| dwayne@translate.org.za
| committer
| yes
|}

====Active projects====

* Mozilla Firefox
* Thunderbird was updated until 3.1. We hope to get back to that.

====L10n tools====
* Live translation and error reporting on Pootle: http://mozilla.locamotion.org/af/

====Additonal info====
Web page: [http://translate.org.za translate.org.za]

More on [[L10n:South-African locales]].

<noinclude>[[category:L10n Teams|af]]</noinclude>

MozCampAsia2012/Schedule

2012-11-14T15:09:56Z

Dwayne: /* Schedule */ Add l10n sprint

{{Template:Mozcampnav}}

<p style='font-size:2em;'>MozCamp Asia 2012 Schedule</p>

=Thursday, Nov 15th =

==Registration Desk @ V Hotel Lavender==

'''Time''': 10am - end of day

Please visit the registration desk at the hotel for:
*MRT map from hotel to venue
*An MRT pass (if you did not receive yours at the airport)

==Open Working Space==

A table will be reserved for Mozilla @ The Hub, [[MozCampAsia2012/Schedule#Open_Working_Space|see info below]].

== Firefox OS and MDN Developer Event ==

Developer Meet Up! An evening of talks targeted at local web developers and MozCamp attendees on Thursday evening, hosted by the MDN team. This event is open to the public, please register at [http://www.eventbrite.com/event/4738092763 Eventbrite]. Feel free to promote locally in Singapore as well!

'''Location''': Hub Level 2 (please see directions to the Hub below)

'''Time''': 6:30 - 9:30pm

=Friday, Nov 16th=

==Registration Desk @ V Hotel Lavender==

'''Time''': 8am - end of day

Please visit the registration desk at the hotel for:
*MRT map from hotel to venue
*An MRT pass (if you did not receive yours at the airport)

==Open Working Space==

A table will be reserved for Mozilla @ The Hub, [[MozCampAsia2012/Schedule#Open_Working_Space|see info below]].

==Community Building Meetup==

Working session of people building communities around their projects at Mozilla. If interested in attending, please contact [https://mozillians.org/en-US/davidwboswell David Boswell] about attending to make sure we have enough space available.

'''Time''': 9am - 4pm

'''Location''': Hub Level 1 (please see directions to the Hub below)

==Gear Assembly==

If interested, please come help us assemble the attendee gear bags on Friday afternoon!

'''Time''': 5:30 - 6pm

'''Location''': Scape (Warehouse Room)

==MozCamp Welcome Event==

Welcome event tonight will be at The Lawn at Youth Park.

'''Location''': 113 Somerset Road, Singapore 238165.<br>Lawn beside the National Youth Council building @ [http://singapore.the-hub.net/ The Hub]

'''Time''': 7-10:30pm
*[https://etherpad.mozilla.org/MozCampAsia2012-CountryFair Country Fair] from 7:30 - 8:30pm
*Please visit the Registration desk from 7:00 - 8:00pm for your badge, lanyard, venue map, and to find out who your Mission MozCamp partner is!

Directions from the V hotel to The Hub, here is a '''[https://docs.google.com/presentation/d/1dR-syay9zjnR923EQkmrRgUWyT74pp6CcF4pGj76GHY/edit?pli=1#slide=id.g32867beb_2_53 (Map)]''' as well as Step-by-Step directions which you can follow:

# Using MRT From Lavender Station, take the east west line towards Joo Koon.
# Alight at City Hall Station. Change to north south line towards Jurong East.
# Alight at Somerset Station, take Exit A and walk 291m to Bus stop at National Youth Council, look for a red building.

Here is the '''[https://docs.google.com/file/d/0B9BU22m9p7kqajhkUFNsOFNOcmc/edit detail direction from MRT station to Youth Park]'''.

=Saturday, Nov 17th=

[https://docs.google.com/presentation/d/1dR-syay9zjnR923EQkmrRgUWyT74pp6CcF4pGj76GHY/edit?pli=1#slide=id.g32867beb_2_59 Directions from hotel to SCAPE] / [https://docs.google.com/presentation/d/1dR-syay9zjnR923EQkmrRgUWyT74pp6CcF4pGj76GHY/edit?pli=1#slide=id.g32867beb_2_65 Pictures and map of SCAPE] / [https://docs.google.com/open?id=0B9BU22m9p7kqZ05ndm5hN1l2cmM SCAPE floorplan]

==Breakfast==

'''Time''': 8:00 - 9:00am

'''Location''': Scape (Warehouse Room)

'''Please note that we will NOT be eating breakfast at the hotel, breakfast will be served at the MozCamp venue.'''

==Schedule==

*'''Please find your Mission partner and sit at the same table during the morning activities'''

See track view: [[MozCampAsia2012/Schedule/desktopandmobile|Desktop and Mobile]], [[MozCampAsia2012/Schedule/appsandb2g|Apps and Boot-to-Gecko (Firefox OS)]], [[MozCampAsia2012/Schedule/GrowMozilla|Grow Mozilla]].

{| class="wikitable" |
|-
{{AsiaCamp12HeaderRow}}
|-
{{AsiaCamp12FullRow
|time=07:00 - 08:00
|all=Wake up and transport to Scape
}}
|-
{{AsiaCamp12FullRow
|time=08:00 - 09:00
|all=[[MozCampAsia2012/Schedule#Breakfast|Breakfast at Scape]]
}}
|-
{{AsiaCamp12FullRow
|time=09:01 - 9:05
|all= Welcome to MozCamp
}}
|-
{{AsiaCamp12FullRow
|time=09:05 - 9:35
|all= Mitchell Baker
}}
|-
{{AsiaCamp12FullRow
|time=09:36-10:06
|all= Johnathan Nightingale Keynote
}}
|-
{{AsiaCamp12FullRow
|time=10:06 - 10:24
|all= David Slater
}}
|-
{{AsiaCamp12FullRow
|time=10:30 - 11:20
|all= Design Session (Warehouse auditorium)
}}
|-
{{AsiaCamp12FullRow
|time=11:20 - 11:30
|all=Coffee break
}}
|-
{{AsiaCamp12FullRow
|time=11:30 - 12:05
|all= Keynotes (Warehouse auditorium)
}}
|-
{{AsiaCamp12FullRow
|time=12:05 - 13:05
|all= Lunch (Paid-staff Leadership Panel will happen from 12:25 - 1:05pm)
}}
|-
{{AsiaCamp12HeaderRow}}
|-
{{AsiaCamp12Row
|time=13:15 - 14:10
|Room 1= [[MozCampAsia2012/Schedule/GrowMozilla/China & Taiwan Market Insights|China+Taiwan Market Insights]] - Dr. Hong Tang, Natasha Ma
|Room 2=
|Room 3= [[MozCampAsia2012/Schedule/desktopandmobile/Release-Management|Here Come the Trains, Releasing Quality Mozilla Products]] - Lukas Blakk
|Room 4=
|Room 5=
}}
|-
{{AsiaCamp12Row
|time=14:20 - 15:50
|Room 1=
|Room 2=
|Room 3= [[MozCampAsia2012/Schedule/desktopandmobile/Creating_Add-ons_for_Android|Creating Add-ons for Firefox on Android]] - Jorge Villalobos
|Room 4= [[MozCampAsia2012/Schedule/GrowMozilla/WebFWD|WebFWD – Learn The Essentials Of Entrepreneurship: Business Model Canvas ]] - Didem Ersoz, Sau Sheong, and Arky + [[MozCampAsia2012/Schedule/GrowMozilla/Sculpting_a_vibrant_community| Sculpting a vibrant community]] - Ankit Gadgil & Sayak Sarkar
|Room 5= [[MozCampAsia2012/Schedule/desktopandmobile/Security_and_Privacy_in_Asia|Help the UX Team Understand Security and Privacy Concerns in Asia]] - Larissa Co and Paul Theriault
}}
|-
{{AsiaCamp12FullRow
|time=15:50 - 16:25
|all= Snack break
}}
|-
{{AsiaCamp12Row
|time=16:25 - 17:25
|Room 1=
|Room 2= [[MozCampAsia2012/Functional_testing_B2G_apps|Introduction to Functional/UI Testing B2G Apps using Marionette]] - Zac Campbell
|Room 3= Hacking Firefox made easy - Irakli / [[MozCampAsia2012/Schedule/desktopandmobile/Add-on_Localization|Add-on Localization]] - Jorge Villalobos
|Room 4=
|Room 5= TBA
}}
|-
{{AsiaCamp12Row
|time=17:25 - 18:35
|Room 1= [[MozCampAsia2012/Schedule/GrowMozilla/Finding_NeMo|Finding NeMo - let's take Mozilla to the masses]] – Deb, Kinshuk & Ahkeno
|Room 2=
|Room 3=
|Room 4= [[MozCampAsia2012/Schedule/GrowMozilla/Browser_pairs|Browser pairs: Mini HTML5 game, community campaign and much more]] <br><br> [[MozCampAsia2012/Schedule/GrowMozilla/events_of_Taiwan_community_evolution_challenges_and_survival|Events of Taiwan community: evolution, challenges, and survival in 2012 ]]
|Room 5=[[MozCampAsia2012/Schedule/GrowMozilla/SUMO_Magnet|The SUMO Magnet - or Why Is Support so Fun, Special, and Cool]] – Madalina Ana, Rosana Ardila & Bram Pitoyo
}}
|-
{{AsiaCamp12FullRow
|time=18:35 - 19:00
|all= [[MozCampAsia2012/Schedule#BoF_.28Birds_of_a_Feather.29_Talks|Birds of a Feather (BoF)]]
}}
|-
{{AsiaCamp12FullRow
|time=19:00 - 22:30
|all= [[MozCampAsia2012/Schedule#Saturday_Night_Dinner|Dinner]]
}}
|}

<br>

==Apps Hacking Lounge==

If you've heard the buzz around web apps but don't know where to start, the [[MozCampAsia2012/hackinglounge|Apps Hacking Lounge]] is for you. The lounge will be an interactive area where you can get started creating apps, test them on tablets and phones, see demos, and ask questions! We're giving out a special gift to everyone who makes an app!

Even if you don't get a chance to create an app at Mozcamp, no worries--take the [[MozCampAsia2012/apps-challenge|Apps Challenge]] and show off your great idea by the end of the year!

'''The Apps Hacking Lounge will take place on both Saturday and Sunday throughout MozCamp in the Warehouse Room (First Floor)'''

==BoF (Birds of a Feather) Talks==

If you would not like to host an entire session (or if you feel inspired(!) by a topic you are passionate about), please consider hosting a BoF talk @ MozCamp on Saturday afternoon.

The BoF talks can happen on Saturday afternoon from 6:35 - 7:00pm in each of the break-out rooms. If you would like to host a BoF talk, please '''[https://etherpad.mozilla.org/mozcampasia-bof-talks sign-up to do so here]'''.

In order to give people more time to hear about your talk, please try and enter your talk in the schedule by 4pm on Saturday.

==Contributor Spotlights==

Please sign-up to be interviewed about your experience as a Mozillian which could be utilized around our 15 year anniversary, Brand Engagement, on-boarding, the Get Involved Page and more! Sign-up to take part [https://etherpad.mozilla.org/mozcampasia-contributorspotlights here]

The Contributor Spotlights will take place in the 'Warehouse' room on the main stage. If you have any questions, please reach out to Shannon Prior at sprior@mozilla.com

== Saturday Night Dinner ==

Dinner will take place directly following the BoF talks on Saturday afternoon. Buses will be transporting us directly from Scape to the [http://www.reddotbrewhouse.com.sg/boatquay/rd_boatquay.php Red Dot Brewery RedDot Brewhouse @ BoatQuay Restaurant].

'''Each individual will be responsible for their own transportation returning from the restaurant to the V-Hotel.''' The last train departing at Raffles Place (which is the nearest train station for Reddot Brewhouse on 17th Nov) will be around 12am.

For more information on the Red Dot Brewery, please see [https://wiki.mozilla.org/MozCampAsia2012/attendeeresources-atmozcamp#Red_Dot_Brewery_.28Saturday_Night_Dinner.29 here]

=Sunday, Nov 18th=

==Schedule==

See track view: [[MozCampAsia2012/Schedule/desktopandmobile|Desktop and Mobile]], [[MozCampAsia2012/Schedule/appsandb2g|Apps and Boot-to-Gecko (Firefox OS)]], [[MozCampAsia2012/Schedule/GrowMozilla|Grow Mozilla]].

{| class="wikitable" |
|-
{{AsiaCamp12HeaderRow}}
|-
{{AsiaCamp12FullRow
|time=07:00 - 08:00
|all=Wake up and travel to Scape
}}
|-
{{AsiaCamp12FullRow
|time=08:00 - 09:00
|all=[[MozCampAsia2012/Schedule#Breakfast|Breakfast at Scape]]
}}
|-
{{AsiaCamp12FullRow
|time=09:00 - 9:02
|all=Welcome
}}
|-
{{AsiaCamp12FullRow
|time=09:00 - 9:30
|all=Brendan Eich ("The Web is the Platform")
}}
|-
{{AsiaCamp12FullRow
|time=09:30 - 9:58
|all=Rick Fant ("Firefox OS - unlock the Creative Power of Mobile")
}}
|-
{{AsiaCamp12FullRow
|time=09:58 - 10:13
|all=Li Gong & Dave Slater ("Firefox OS: Opportunity + Brand")
}}
|-
{{AsiaCamp12FullRow
|time=10:13 - 10:41
|all=Ryan Merkley ("You are a maker")
}}
|-
{{AsiaCamp12FullRow
|time=10:45 - 11:35
|all=Design session (Warehouse auditorium)
}}
|-
{{AsiaCamp12FullRow
|time=11:35 - 11:45
|all=Coffee break
}}
|-
{{AsiaCamp12FullRow
|time=11:45 - 12:00
|all=End of Design Session(Warehouse auditorium)
}}
|-
{{AsiaCamp12FullRow
|time=12:00 - 12:15
|all=Community Quilt
}}
|-
{{AsiaCamp12FullRow
|time=12:15 - 12:25
|all=Mitchell Baker ("Emeritus Project")
}}
|-
{{AsiaCamp12FullRow
|time=12:25 - 13:05
|all=Lunch
}}
|-
{{AsiaCamp12FullRow
|time=13:05 - 14:05
|all=Leadership panel (Warehouse auditorium)
}}
|-
{{AsiaCamp12HeaderRow}}
|-
{{AsiaCamp12Row
|time=14:20 - 15:50
|Room 1=[[MozCampAsia2012/Schedule/GrowMozilla/Mozilla_Reps|Mozilla Reps: Update and next Steps + Student Reps Planning (WilliamQ, Pierros, Kate)]]
|Room 2=[[MozCampAsia2012/l10n_sprint|Localization Sprint for B2G]] (DwayneBailey, Stas)
|Room 3=
|Room 4= [[MozCampAsia2012/Firefox_OS_Support_Article_Sprint|Fortify Firefox OS with Proactive Support!]] - Michael Verdi
|Room 5= [[MozCampAsia2012/Schedule/desktopandmobile/Firefox_Mobile_Creating_Value_to_Define_the_Future|Firefox Mobile: Defining Value to Define the Future]] - Karen Rudnitski
}}
|-
{{AsiaCamp12FullRow
|time=15:50 - 16:25
|all=Snack break
}}
|-
{{AsiaCamp12Row
|time=16:25 - 17:25
|Room 1= [[MozCampAsia2012/Schedule/GrowMozilla/Manifesto Evolution|Evolution of the Mozilla Manifesto Workshop]]
|Room 2= [[MozCampAsia2012/insight_gaia|Insight Gaia - OS Shell in <html>]]
|Room 3=
|Room 4=
|Room 5= TBA
}}
|-
{{AsiaCamp12Row
|time=17:25 - 18:35
|Room 1= [[MozCampAsia2012/Schedule/GrowMozilla/CreativeWishList|Creative Wish List: What tools and resources do you need to make your lives easier?]]
|Room 2=
|Room 3=
|Room 4=
|Room 5=
}}
|-
{{AsiaCamp12FullRow
|time=18:35 - 19:00
|all=Closing (Warehouse auditorium)
}}
|-
{{AsiaCamp12FullRow
|time=19:00 - 20:00
|all= Commute back to hotel
}}
|}
<br>

==Open Working Space==

''Keeping the Conversations Going...''

Open Working Space will be available at the Scape on Thursday, Friday and Sunday night (til. 10pm) to continue the discussions + workshops as needed.

Location:
* Thursday (Day): [http://singapore.the-hub.net/ The Hub]
* Friday (Day): [http://singapore.the-hub.net/ The Hub]
* Sunday night (until 10pm): Scape Hub Quarter @ 4, InfoComms Lab 3.

Sign-ups: If you would like to sign-up to utilize this room, please do so [https://etherpad.mozilla.org/MozCampAsia2012-breakouts-sundayevening here]

==Where is Firefox?==

For more information about:
* Where the Firefox costume will be located throughout the weekend
* To volunteer to wear it
* To sign-up to use it

Please see [http://etherpad.mozilla.com/mozcamp-asia-2012-costume here]

=Monday, November 19th=
Evangelism Reps training - become a speaker/blogger/face of Mozilla
10 am - 2 pm @ [http://singapore.the-hub.net/ The Hub]

Speaker training for Contributors interested in becoming better speakers for Mozilla - learn how to be an effective speaker from our Principal Evangelist Christian Heilmann. In this session, you will learn how to identify what makes a successful presentation, preparing yourself and your slides and have the opportunity to ask questions and gain valuable insight. Special guest Mitchell Baker will be joining for lunch.

Please sign up on the [https://etherpad.mozilla.org/EvangelismReps-Asia etherpad] if you plan to attend.

MozCampAsia2012/Buddyprogram/Dwayne Bailey

2012-10-26T15:33:51Z

Dwayne: Created page with "<h1>Name</h1> Dwayne Bailey <h1>Link to My Mozillians/Reps/Twitter Accounts</h1> * https://mozillians.org/en-US/dwaynebailey * http://twitter.com/dwaynebailey <h2>What is the..."

<h1>Name</h1>

Dwayne Bailey

<h1>Link to My Mozillians/Reps/Twitter Accounts</h1>

* https://mozillians.org/en-US/dwaynebailey
* http://twitter.com/dwaynebailey

<h2>What is the overall goal I want to accomplish by attending MozCamp Asia</h2>

I want to be better equipped to serve Asian localisers and have a deeper understanding of localisation and b2g.

<h2>What I want to achieve by Sunday (November 18th)</h2>

1. Meet as many Asian localisers as possible, especially those that are working on Pootle.
2. Learn all I can about b2g

<h3>What I will achieve by December 2nd</h3>

I hope to have completed migration of some new Asian languages to localise for easily using Pootle.

<h3>What I will achieve by December 16th</h3>

I'd like to have some teams having completed their b2g localisations on Pootle.

[[Category:MozCampAsia2012Buddy|{{SUBPAGENAME}}]]

MozCampAsia2012/l10n sprint

2012-10-15T21:59:52Z

Dwayne: Fix bullets

'''Title of Session (should also be the title of your Wiki page)''': Localization sprint for B2G

'''Facilitator(s)''': Dwayne Bailey

'''Are you paid or volunteer staff?''': Volunteer

'''Area of Contribution (Team Name)''': Localization

'''How are you currently involved with the community?''':

'''Location of Work (where do you reside?)''': United Kingdom/South Africa

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 120minutes

'''Summary''': We already use Pootle very successfully to localise Firefox in African and a growing number of Asian languages. It's working because the complexity is hidden from communities.

In this session we plan to teach teams about the features of Pootle that can benefit their communities. But more then that we plan to use this session to actually perform a translation sprint for b2g. For teams that are already translating b2g, this will be an opportunity to see how Pootle can help you. For those languages not localising b2g this is an opportunity to get started in translation.

We hope that at the end of the session we'll have screenshots and demonstration of some initial translations.

'''How your session furthers the MozCamp [https://wiki.mozilla.org/MozCampAsia2012/Tracks Goals]''':
* Community-based plans to increase usage in Asia - increasing usage through language
* Boot2Gecko contribution how-to workshop - using Pootle and localization as a platform for contribution to b2g

'''Expected Outcome or Deliverable''':

* Attendees know how to localise on Pootle
* Demoable localisation based on their work in the sprint

'''Desired Audience Type or Skill-set''':

* Localizers
* Non-English speakers with a passion to see local language Firefox

'''Equipment Needs (Video projector already included)''':

* Tables and chairs to allow comfortable sitting when translating

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

MozCampAsia2012/l10n sprint

2012-10-15T21:57:51Z

Dwayne: initial proposal

MozCampAsia2012/Schedule/appsandb2g

2012-10-15T21:43:38Z

Dwayne: /* Proposed Sessions */ l10n sprint

[[Category:MozCampAsia2012]]
==Proposed Sessions==

* [[MozCampAsia2012/r2d2b2g_ftw| R2D2B2G FTW]] - Jeff Griffiths
* [[MozCampAsia2012/firefoxos_apps_technical| Technical Resources for Firefox OS and Marketplace (Apps)]] - Desigan Chinniah
* [[MozCampAsia2012/ZeroToApp]] From Zero to App - An Open Web Apps Adventure! - Potch
* [https://wiki.mozilla.org/MozCampAsia2012/Schedule/FirefoxOsLaunch Firefox OS launch]
* [[MozCampAsia2012/insight_gaia|Insight Gaia]] - Tim Chien, Evelyn Hung
* [[MozCampAsia2012/Security_in_Firefox_OS|Security in Firefox OS]] - Paul Theriault
* [[MozCampAsia2012/Marketing my amazing apps|What Apps Should I Build for the FireFox Marketplace and How Can I Best Market Them?]] - Diana Livits
* [[MozCampAsia2012/Functional_testing_B2G_apps|Functional/Introduction to automated testing B2G apps using Marionette]] - Zac Campbell
* [[MozCampAsia2012/I_Reject_Because_I_Care|I Reject Because I Care: Resetting expectations of the app review process]] - Lisa Brewster
* [[MozCampAsia2012/How_to_build_quality_open_web_apps|How to build quality web apps]] - David Burns
* [[MozCampAsia2012/How_to_User_Test_Your_App|How to User Test Your App]] - Jennifer Morrow
* [[MozCampAsia2012/B2G_Localization|B2G Localization]] - Stas Malolepszy
* [[MozCampAsia2012/Firefox_OS_Support_Article_Sprint|Firefox OS Support Article Sprint]] - Michael Verdi & David Tenser
* [[MozCampAsia2012/Anatomy_of_an_App|Anatomy of an Open Web App--and How to Create Your Own Today ]] - r1cky and tofumatt
* [[MozCampAsia2012/mozilla_indonesia_community_local_app|FirefoxOS Local App To Support Mozilla Indonesia Community ]] - Finan Akbar
* [[ MozCampAsia2012/Flicks_2013_Firefox_OS|Our global short film contest for Firefox OS - Firefox Flicks 2013]] - Tobias Leingruber
* [[ MozCampAsia2012/l10n_sprint|Localization sprint for b2g]] - Dwayne Bailey

MozCampEU2012/Social Localisation with Verbatim

2012-07-26T23:14:57Z

Dwayne: initial proposal

'''Title of Session (should also be the title of your Wiki page)''': Social Localisation with Verbatim

'''Facilitator(s)''': Dwayne Bailey

'''Are you paid or volunteer staff?''': volunteer

'''Area of Contribution (Team Name)''': Localisation

'''How are you currently involved with the community?''': Support, encourage and assist African and other under-resourced language translators through the Firefox localisation process. Develop tools that assist in translating Mozilla products.

'''Location of Work (where do you reside?)''': South Africa/United Kingdom

'''Talk Length (please choose between 30, 60, 90, 120 minutes)''': 60 (15 minute recap, 45 minute idea generation)

'''Summary''': Localisation presents an under exploited opportunity to involve more people in the Mozilla community. It also provides an amazing differentiator for Mozilla products.

While most commercial companies will struggle to localise into 35 languages, social localisation has allowed companies to deliver 100+ translations. Mozilla and our users have the opportunity to take our products well beyond these number. To places where economics isn't the main driver, but rather where access to the open web becomes a key driver.

Verbatim is used to translate a number of [https://localize.mozilla.org/ Mozilla projects and initiatives] and is used for the [http://mozilla.locamotion.org/projects/firefox/ localisation of Firefox] into a number of African and other under-resourced languages.

Verbatim has recently undergone a major revamp and upgrade. We will spend the first part of the session going through new features as they relate to Social Localisation. In the second part the group will brainstorm what is needed to get greater community participation in localisation. They will then select the best of these ideas and create use cases, mockups or basic specs so that these ideas can be used to drive Verbatim to become an even richer Social Localisation platform.

'''How your session furthers the MozCamp Goals (https://wiki.mozilla.org/MozCampEU2012/Tracks)''': Exploiting language to grow usage in key European countries, Growing and building communities through language, Product localisation.

'''Expected Outcome or Deliverable''': Exposure of localisers to the new features of Verbatim. Basic scoping of 10 features that could boost Verbatim as a social translation platform.

'''Desired Audience Type or Skill-set''': Localisers, local language community members, non-English locales, anyone interested in growing community participation in Mozilla.

'''Equipment Needs (Video projector already included)''': Whiteboard and post-its.

--------------------------------------------------------------------

To Be Completed by the Audience-

(If you would like) Submit a Question for the Speaker(s) or indicate what
information you hope to gain by attending this talk here:

Place your name here if you would like to attend this talk:

MozCampEU2012/Schedule/GrowMozilla

2012-07-26T22:33:40Z

Dwayne: /* Grow Mozilla */ Social Localisation with Verbatim

==Grow Mozilla==

List of Participation Proposals:

1. [https://wiki.mozilla.org/MozCampEU2012/hack-core-security-code HowTo hack our core security code (C/C++ programming)]

2. [https://wiki.mozilla.org/MozCampEU2012/mozIT-and-you Mozilla IT and YOU: past, present and future]

3. [https://wiki.mozilla.org/MozCampEU2012/WebFWD-Grow WebFWD: Growing The Mozilla Mission Through Other Projects]

4. [https://wiki.mozilla.org/MozCampEU2012/moz-summer-of-code-experience Experience from hosting Mozilla Summer Of Code parties, why you should host one next time and what to do better ]

5. [[MozCampEU2012/Efficient localization with Translate Toolkit - the example of Fulah|Efficient localization with Translate Toolkit - the example of Fulah]]

6. [https://wiki.mozilla.org/MozCampEU2012/open-badges-experience Open Badges experience, or how a global project can take a place in a local community]

7. [https://wiki.mozilla.org/MozCampEU2012/evangelism-reps-training Evangelism Reps training - become a speaker/blogger/face of Mozilla]

8. [https://wiki.mozilla.org/MozCampEU2012/Governance_Workshop Governance Workshop] - discussion, comment and suggestions on governance issues, e.g. Code of Conduct, employee/volunteer relationships

9. [https://wiki.mozilla.org/MozCampEU2012/Contributing_to_Mozilla_Websites Contributing to Mozilla websites and webdev projects]

10. [https://wiki.mozilla.org/MozCampEU2012/Host_Your_Own_Developer_Event Host Your Own Developer Event]

11. [https://wiki.mozilla.org/MozCampEU2012/webmaker_sig Webmaker SIG: Building a Webmaker Special Interest Group within ReMo]

12. [https://wiki.mozilla.org/MozCampEU2012/resources-for-helping-potential-code-contributors Help Yourself Help Coders: Resources for helping potential coding contributors]

13. [[MozCampEU2012/GrowMozilla/Onboarding-new-localizers-to-your-community|Onboarding New Localizers to Your Community]]

14. [[MozCampEU2012/GrowMozilla/Preparing-Your-Projects-For-L10n|Preparing Your Projects for Localization]]

15. [[MozCampEU2012/SUMO_Kitsune_Development|SUMO Kitsune Development]]

16. [[MozCampEU2012/ReMo_Next_Steps|Mozilla Reps: update and next steps]]

17. [[MozCampEU2012/Workshop_Onboarding_New_Volunteers|How to Identify Volunteer Needs, Educate and Onboard New Volunteers, and Create More Rockstars!]]

18. [[MozCampEU2012/Diving_into_Mozilla_Communities|Diving into Mozilla Communities]]

19. [https://wiki.mozilla.org/MozCampEU2012/CreativeOfficeHours Creative Office Hours: Localizing Design]

20. [https://wiki.mozilla.org/MozCampEU2012/mozilla-for-mr-and-mrs-average Mozilla for Mr and Mrs Average]

21. [https://wiki.mozilla.org/MozCampEU2012/Manifesto_Evolution Evolution of the Mozilla Manifesto]

22. [[MozCampEU2012/Localize_MDN_Help_Start_a_l10n_team|Localize MDN — Start/Extend a localization (Workshop)]]

23. [[MozCampEU2012/Building_communities_with_few_people|Building communities with few people]]

24. [[MozCampEU2012/Pontoon|Pontoon: Are You Ready?]]

25. [[MozCampEU2012/New-Skies-For-Thunderbird|New Skies For Thunderbird]]

26. [[MozCampEU2012/SUMO_Magnet| The SUMO Magnet]]

27. [[MozCampEU2012/SUMO_L10n_Organization_and_Tools|SUMO l10n organization and tools]]

28. [[MozCampEU2012/SUMO_Support_Forum|SUMO Support Forum]]

29. [[MozCampEU2012/Thunderbird Community Working session| Thunderbird Community working session]]

30. [https://wiki.mozilla.org/MozCampEU2012/evolutionofmozillabrand Evolution of the Mozilla Brand]

31. [[MozCampEU2012/Marketing_Collective_Next_Steps |Marketing Collective Next Steps]]

32. [[MozCampEU2012/Capturing_Mozillians_Knowledge | Capturing Mozillians' Knowledge]]

33. [[MozCampEU2012/Social_Localisation_with_Verbatim|Social Localisation with Verbatim]]

L10n:Teams:en-ZA

2012-02-17T15:56:44Z

Dwayne: /* English (South Africa) (en-ZA) */ update

[[Category:L10n Teams]]
__NOTOC__

=== English (South Africa) (en-ZA) ===

====Team members====

{| border="1"
|-
! Name
! Email
! Role
! Hg/SVN Access?
|-
| Dwayne Bailey
| dwayne [AT] translate.org.za [DOT] org [DOT] ZA
| Team lead
| YES
|-
| Friedel Wolff
| friedel [AT] translate.org.za [DOT] org [DOT] ZA
| Peer
| YES
|}

====Active projects====

* Firefox
* Mobile

====L10n tools====

We make use of the Translate Toolkit and commit changes to the Translate subversion repository. We do put the translations up on [http://pootle.locamotion.org Pootle] for community corrections, but mostly we don't translate there.

====Additonal info====
* Team website: [http://translate.org.za translate.org.za]
* Live translation and error reporting: [http://pootle.locamotion.org pootle.locamotion.org]
* IRC: [irc://irc.freenode.net/#zaf #zaf]
* More on [[L10n:South-African locales]].

L10n:Pootle

2011-11-29T14:28:54Z

Dwayne: Add some explanations about what we do in the various cycles

= Quick Start =

== Register an account and login<br> ==

#Visit the Pootle server and [http://pootle.locamotion.org/accounts/register/ register an account].<br>
#[http://pootle.locamotion.org/accounts/login/ Login] to the Pootle server.<br>

== Make translation suggestions<br> ==

#Visit the [http://pootle.locamotion.org/projects/firefox/ Firefox project] on the Pootle translation server<br>
#Select your language from the list (e.g. [http://pootle.locamotion.org/af/firefox/ Afrikaans])<br>
#Look for the directory marked '''user1''', click on the link that says '[http://pootle.locamotion.org/af/firefox/user1/translate.html?unitstates=fuzzy,untranslated N words need attention]'<br>
#Type in a translation for the English text and submit the suggestions.<br>

Congratulations!  You've made your first contribution for your language.<br>

== Download and install Firefox ==

#Install the latest [http://www.mozilla.org/en-US/firefox/all-aurora.html Firefox Aurora] in your language.  If one doesn't exists then download one in English and then...
#Get a [http://downloads.locamotion.org/aurora/ language pack] in your language. If that doesn't exists then...
#Ask us to build a language pack for you.  But that is only userful if you have translated a large enough portion of '''user1'''.

= Is translating on Pootle for you?<br> =

We setup the Pootle translation server for you for these reasons:<br>

#Firefox translation can be very technical and very geeky.  We try to hide that from you.  You focus on translation and testing and our technical team and community will focus on the hard parts.<br>
#When you start translation you need a lot of hand holding.  We'll do that with you.<br>
#We have a friendly collaborative envionment.<br>
#We support under resourced languages across the globe.<br>

= Translating on Pootle<br> =

== Understanding Phases<br> ==

Our approach to translation is to allow you to focus on the most important things first.  So we've broken Firefox into various phases.  This ensures that you focus on the most important things and leave the rest to last.  You have limited time and resources so we want you to focus on the areas that impact your users.<br>

*The various directories at the first level of your translations (e.g. here in [http://pootle.locamotion.org/ak/firefox/ Akan]) correspond to the various phases.<br>
*The list of [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases phases] will show you what each contains<br>
*Follow the order in the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases phases file] closely to not waste your time and effort.<br>

== Translating<br> ==

Your major task will be translating.  You can always go directly to segments that need attention by clicking on the 'N words need attention' link.<br>

Don't forget to first view which phases need attention.<br>

Make sure you use the following features in Pootle:<br>

#Terminology - terminology hints, if a terminology file exists, will appear on the left of your translations.  Use this as a guide of which terms you should use.<br>
#Developer comments - the programmers might have supplied some useful information to help you understand the text.  This will appear above the English text.  Please always read this, if it doesn't make sense then ask a question.<br>
#Locations - if there are no developer comments you might see a location or variable name. This can sometimes be useful to understand the use of the string.<br>
#Translators comments - these are comments that translators have left for you.  Use this to leave comments for anyone who will follow you or to read what others have written.<br>

== Suggestions<br> ==

Suggestions will not be used in the final translation.  They are useful when you or your community want to suggest a correction.<br>

== Quality checks<br> ==

Everyone makes mistakes when translating.  If you click on the '''Review''' tab you will access the quality checks.  Remember that not all errors are mistakes.  If you are unsure then please ask.<br>

The important checks to get to zero are: variables, printf, accelerators.<br>

= Firefox translation process<br> =

== Understanding the 6 week cycle ==

#There are 4 stages to Firefox releases: nightlies, aurora, beta and release
#We focus on translating Aurora
#You Aurora translation will make it to release after 12 weeks.  6 weeks in Aurora and 6 weeks in beta.

== Aurora 6 week cycle and Pootle ==

#We will migrate your translations to the latest Aurora at the start of the cycle
#Mid cycle we will push your translations to Mozilla
#In the last week we will also push your translations to Mozilla

L10n:Pootle

2011-11-29T11:09:44Z

Dwayne: Add section about language packs

L10n:Pootle

2011-11-29T07:17:07Z

Dwayne: First draft of the Pootle translation guide

= Quick Start =

== Register an account and login<br> ==

#Visit the Pootle server and [http://pootle.locamotion.org/accounts/register/ register an account].<br>
#[http://pootle.locamotion.org/accounts/login/ Login] to the Pootle server.<br>

== Make translation suggestions<br> ==

#Visit the [http://pootle.locamotion.org/projects/firefox/ Firefox project] on the Pootle translation server<br>
#Select your language from the list (e.g. [http://pootle.locamotion.org/af/firefox/ Afrikaans])<br>
#Look for the directory marked '''user1''', click on the link that says '[http://pootle.locamotion.org/af/firefox/user1/translate.html?unitstates=fuzzy,untranslated N words need attention]'<br>
#Type in a translation for the English text and submit the suggestions.<br>

Congratulations!  You've made your first contribution for your language.<br>

= Is translating on Pootle for you?<br> =

We setup the Pootle translation server for you for these reasons:<br>

#Firefox translation can be very technical and very geeky.  We try to hide that from you.  You focus on translation and testing and our technical team and community will focus on the hard parts.<br>
#When you start translation you need a lot of hand holding.  We'll do that with you.<br>
#We have a friendly collaborative envionment.<br>
#We support under resourced languages across the globe.<br>

= Translating on Pootle<br> =

== Understanding Phases<br> ==

Our approach to translation is to allow you to focus on the most important things first.  So we've broken Firefox into various phases.  This ensures that you focus on the most important things and leave the rest to last.  You have limited time and resources so we want you to focus on the areas that impact your users.<br>

*The various directories at the first level of your translations (e.g. here in [http://pootle.locamotion.org/ak/firefox/ Akan]) correspond to the various phases.<br>
*The list of [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases phases] will show you what each contains<br>
*Follow the order in the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases phases file] closely to not waste your time and effort.<br>

== Translating<br> ==

Your major task will be translating.  You can always go directly to segments that need attention by clicking on the 'N words need attention' link.<br>

Don't forget to first view which phases need attention.<br>

Make sure you use the following features in Pootle:<br>

#Terminology - terminology hints, if a terminology file exists, will appear on the left of your translations.  Use this as a guide of which terms you should use.<br>
#Developer comments - the programmers might have supplied some useful information to help you understand the text.  This will appear above the English text.  Please always read this, if it doesn't make sense then ask a question.<br>
#Locations - if there are no developer comments you might see a location or variable name. This can sometimes be useful to understand the use of the string.<br>
#Translators comments - these are comments that translators have left for you.  Use this to leave comments for anyone who will follow you or to read what others have written.<br>

== Suggestions<br> ==

Suggestions will not be used in the final translation.  They are useful when you or your community want to suggest a correction.<br>

== Quality checks<br> ==

Everyone makes mistakes when translating.  If you click on the '''Review''' tab you will access the quality checks.  Remember that not all errors are mistakes.  If you are unsure then please ask.<br>

The important checks to get to zero are: variables, printf, accelerators.<br>

<br>

L10n:Teams:nso

2010-09-10T09:48:38Z

Dwayne: /* Northern Sotho (nso) */ add IRC and Pheledi

=== Northern Sotho (nso) ===

* Web page: [http://translate.org.za translate.org.za]
* Live translation and error reporting: [http://pootle.locamotion.org/nso/ locamotion.org]
* IRC: [irc://irc.freenode.net/#zaf #zaf]
* Registration bug: [https://bugzilla.mozilla.org/show_bug.cgi?id=496109 bug 496109]

; Owner: Dwayne Bailey <dwayne atsign translate.org.za>

; Peer: Friedel Wolff <friedel atsign translate dot org dot za>

; Translator: Pheledi Mathibela <pheledi atsign moesekolatranslation.co.za>

More on [[L10n:South-African locales]].

<noinclude>[[category:L10n Teams|nso]]</noinclude>

L10n:Teams:en-ZA

2010-09-10T09:46:05Z

Dwayne: Create en-ZA page

=== English (South Africa) (en-ZA) ===

* Web page: [http://translate.org.za translate.org.za]
* Live translation and error reporting: [http://pootle.locamotion.org pootle.locamotion.org]
* IRC: [irc://irc.freenode.net/#zaf #zaf]

; Owner : Dwayne Bailey <dwayne@translate.org.za> - [https://bugzilla.mozilla.org/show_bug.cgi?id=330370 CVS access: YES]

; Browser/toolkit peer : Friedel Wolff <friedel atsign translate dot org dot za> [https://bugzilla.mozilla.org/show_bug.cgi?id=330370]

More on [[L10n:South-African locales]].

<noinclude>[[category:L10n Teams|en-ZA]]</noinclude>

Websites/Mozilla.org/Archive/Localization wishlist

2010-08-27T14:54:01Z

Dwayne: Added a little about the Mozilla.org on Verbatim project

This page is a draft list of pages we'd like to localize on www.mozilla.org. Feel free to add links to other pages if you feel like we're leaving out anything important.

''Note: The site is in the middle of many changes in the style and content and most pages are not stable enough to be localized today.''

==Top Priority==

The top priority pages are the home page and main section pages. The Mission and Manifesto pages are also in here.

{| border="1" cellpadding="3" cellspacing="0" |
! page on mozilla.org !! page in repository !! l10n bug !! status
|-
| [http://www.mozilla.org Home] || [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/index.html?view=log /trunk/index.html] || [https://bugzilla.mozilla.org/show_bug.cgi?id=573073 bug 573073] || [http://davidwboswell.wordpress.com/2010/08/04/refreshing-the-mozilla-org-home-page/ being redesigned]
|-
| [http://www.mozilla.org/about/ About Mozilla] || [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/about/index.html?view=log /trunk/about/index.html] || [https://bugzilla.mozilla.org/show_bug.cgi?id=573076 bug 573076] || <font color="green">'''stable'''</font>
|-
| [http://www.mozilla.org/about/mission.html Mission] || [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/about/mission.html?view=log /trunk/about/mission.html] || [https://bugzilla.mozilla.org/show_bug.cgi?id=566657 bug 566657] || text will change soon
|-
| [http://www.mozilla.org/about/manifesto.html Manifesto] || [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/about/manifesto.html?view=log /trunk/about/manifesto.html] || [https://bugzilla.mozilla.org/show_bug.cgi?id=433928 bug 433928] || <font color="green">'''stable'''</font>
|-
| [http://www.mozilla.org/community Community Map] || [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/community/index.html?view=log /trunk/community/index.html] and [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/script/1.0/universe/data.json?view=log /trunk/script/1.0/universe/data.json] || [https://bugzilla.mozilla.org/show_bug.cgi?id=590223 bug 590223] || being updated
|-
| [http://www.mozilla.org/projects/ Our Projects] || [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/projects/index.html?view=log /trunk/projects/index.html] || [https://bugzilla.mozilla.org/show_bug.cgi?id=573077 bug 573077] || <font color="green">'''stable'''</font>
|-
| [http://www.mozilla.org/contribute Get Involved] || [http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/trunk/contribute/index.html?view=log /trunk/contribute/index.html] || [https://bugzilla.mozilla.org/show_bug.cgi?id=570716 bug 570716] || not ready for l10n
|}

==Nice To Have==

These are some key pages in the various sections.

* [http://www.mozilla.org/about/history.html History of the Mozilla Project]
* [http://www.mozilla.org/about/brochure/ Mozilla Brochure] (Already being localized -- [https://bugzilla.mozilla.org/show_bug.cgi?id=453528 bug 453528])
* others...

== How To Get Started ==

For now, people can contact ''david at mozillafoundation dot org'' if you are interested in helping us with translating site content. Once we [[Mozilla.org:Repository_Transition|migrate the site from CVS to SVN]], we need to plug into the existing web localizing processes:

* [[L10n:Web_parts|Web localization documentation]]
* [[L10n:Localizability/Web|More web localization documentation]]
* [http://groups.google.com/group/mozilla.dev.l10n.web/topics|Web localization newsgroup]
* [http://l10n.mozilla.org/webdashboard/|Web localization dashboard]

=== Translating Mozilla.org on Verbatim ===

Currently work is in progress to investigate translating of the Mozilla.org content on Verbatim (Pootle).

* An initial [http://translate.sourceforge.net/wiki/toolkit/index Translate Toolkit] converter is in place that allows the JSON data to be translated.
* The HTML/PHP pages are a little harder and we're investigating [http://translate.sourceforge.net/wiki/toolkit/html2po html2po]

User:AxelHecht/AMS meet with Dwayne June 2009

2009-07-14T08:31:07Z

Dwayne: /* localizer and tool authors meetup */

These are notes from a chat between Dwayne and I in Amsterdam, June 24th 2009. Edits should be mostly done by Dwayne or me, comments are OK on the Discussion page.

== l20n ==
Not got to that necessarily last night, but here's my list of things to figure out:

* plurals with symbolic names, too? DB: CLDR like name? See http://unicode.org/cldr/data/charts/supplemental/language_plural_rules.html
* UI paradigm to expose inflected placables within strings
* UI paradigm to expose variants of a localized string/object - DB: see latest Qt .ts format which seems to handle variants.

Notes to self here:

* overlay of properties of this localized object (depending on type and language, like gender) and grammar inflections. wikimedia found has some database?

Notes from Dwayne

* I'd really like to start with the simplest thing. Seems like gender related issues was the easiest and seemed to mimic current Gettext-like plurals.
* The general feeling I had is that most of the concepts can be aligned with the current plural input in gettest. The plurals as they are in l20n seem overly complex.
* I am very interested in ensuring that nothing gets exposed if nothing is defined. I.e. people see no plural interface if no plurals handling is defined for the language. Qt succeeds and PO fails on that count.

== ANLoc ==
Unlocking anloc should be OK with using langpack/beta/official release for Firefox. Key points that I recall are

* anloc funding based on both l10n work and community building, sustainability is key lesson learned from the 2.0 days attempt.
* expose progress on the web, with
** landing page for langpack, all.html exposure
** no-editor-review updates on AMO langpacks
** blog posts on progress, asking for feedback and recruiting testers, possibly MCS-based
* Offerings going beyond "shipping Firefox" as offerings, transparently done
** African language Firefox as tool to interest locals into localization of further software
** African language Firefox as tool to improve the web for locals
** possibly offering opportunities like global voices to shape the local web
* Offerings are not exclusive, it should be apparent why doing that in addition gets the locals what. Not a strict priority list that's just work items.
* Kick-off meeting in Africa with Axel and locals, need to find out where, when, and what's on the agenda. Earlier is better
** Aim for 3 teams who can help support other less technical teams
** KIck-off to decide strategies and approaches to ensure smooth collaboration between Mozilla and ANLoc
* Aiming at 10 languages, less ain't bad
** Need to figure out clear milestones to check in whether things work
** Some work already done on targeted list of files based on exposure

== l10n priority list ==
You guys have a list of well-chunked phases to do a Firefox l10n, we want to get that out into the public. Both the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases?view=markup descriptions of the phases] as well as the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phaselist?view=markup mapping of files to phases] are in zaf's svn.

These need update for fx 3.5? --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)
Might want to do another full review for 3.5, I manually added them as I saw fit but didn't do the visual debug build as before. Not much changed so I think its OK. [[User:Dwayne|Dwayne]] 08:27, 14 July 2009 (UTC)

== localizer and tool authors meetup ==

* Axel, Dwayne, Gisela on the hook
* two rounds of slow geeking of localizers showing how they work with tools, and tool authors how they think they tools should be used
* break out sessions unconference-style
* hack day?

Not sure about the size here. Should we split up Asia and EMEA? East-Asian websites make me think that the UI paradigms might be different there. Where? When? Size should probably be smaller than OTT? Got already some internal support for doing this. --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)

I'd like a hack day, definately unconference like. I think we'd get more value if we defined some use cases to which localisers would apply their tools. Mostly I'm interested in commercial localisers and their tools. Also we might want to define the outcomes, is it just to inform (that's OK) or do we define some development agenda's as an outcome. [[User:Dwayne|Dwayne]] 08:31, 14 July 2009 (UTC)

User:AxelHecht/AMS meet with Dwayne June 2009

2009-07-14T08:27:33Z

Dwayne: /* l10n priority list */

User:AxelHecht/AMS meet with Dwayne June 2009

2009-07-14T08:25:25Z

Dwayne: /* ANLoc */

These are notes from a chat between Dwayne and I in Amsterdam, June 24th 2009. Edits should be mostly done by Dwayne or me, comments are OK on the Discussion page.

== l20n ==
Not got to that necessarily last night, but here's my list of things to figure out:

* plurals with symbolic names, too? DB: CLDR like name? See http://unicode.org/cldr/data/charts/supplemental/language_plural_rules.html
* UI paradigm to expose inflected placables within strings
* UI paradigm to expose variants of a localized string/object - DB: see latest Qt .ts format which seems to handle variants.

Notes to self here:

* overlay of properties of this localized object (depending on type and language, like gender) and grammar inflections. wikimedia found has some database?

Notes from Dwayne

* I'd really like to start with the simplest thing. Seems like gender related issues was the easiest and seemed to mimic current Gettext-like plurals.
* The general feeling I had is that most of the concepts can be aligned with the current plural input in gettest. The plurals as they are in l20n seem overly complex.
* I am very interested in ensuring that nothing gets exposed if nothing is defined. I.e. people see no plural interface if no plurals handling is defined for the language. Qt succeeds and PO fails on that count.

== ANLoc ==
Unlocking anloc should be OK with using langpack/beta/official release for Firefox. Key points that I recall are

* anloc funding based on both l10n work and community building, sustainability is key lesson learned from the 2.0 days attempt.
* expose progress on the web, with
** landing page for langpack, all.html exposure
** no-editor-review updates on AMO langpacks
** blog posts on progress, asking for feedback and recruiting testers, possibly MCS-based
* Offerings going beyond "shipping Firefox" as offerings, transparently done
** African language Firefox as tool to interest locals into localization of further software
** African language Firefox as tool to improve the web for locals
** possibly offering opportunities like global voices to shape the local web
* Offerings are not exclusive, it should be apparent why doing that in addition gets the locals what. Not a strict priority list that's just work items.
* Kick-off meeting in Africa with Axel and locals, need to find out where, when, and what's on the agenda. Earlier is better
** Aim for 3 teams who can help support other less technical teams
** KIck-off to decide strategies and approaches to ensure smooth collaboration between Mozilla and ANLoc
* Aiming at 10 languages, less ain't bad
** Need to figure out clear milestones to check in whether things work
** Some work already done on targeted list of files based on exposure

== l10n priority list ==
You guys have a list of well-chunked phases to do a Firefox l10n, we want to get that out into the public. Both the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases?view=markup descriptions of the phases] as well as the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phaselist?view=markup mapping of files to phases] are in zaf's svn.

These need update for fx 3.5? --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)

== localizer and tool authors meetup ==

* Axel, Dwayne, Gisela on the hook
* two rounds of slow geeking of localizers showing how they work with tools, and tool authors how they think they tools should be used
* break out sessions unconference-style
* hack day?

Not sure about the size here. Should we split up Asia and EMEA? East-Asian websites make me think that the UI paradigms might be different there. Where? When? Size should probably be smaller than OTT? Got already some internal support for doing this. --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)

User:AxelHecht/AMS meet with Dwayne June 2009

2009-07-14T08:22:05Z

Dwayne: /* l20n */ notes on positive about exposing only what needs exposing

These are notes from a chat between Dwayne and I in Amsterdam, June 24th 2009. Edits should be mostly done by Dwayne or me, comments are OK on the Discussion page.

== l20n ==
Not got to that necessarily last night, but here's my list of things to figure out:

* plurals with symbolic names, too? DB: CLDR like name? See http://unicode.org/cldr/data/charts/supplemental/language_plural_rules.html
* UI paradigm to expose inflected placables within strings
* UI paradigm to expose variants of a localized string/object - DB: see latest Qt .ts format which seems to handle variants.

Notes to self here:

* overlay of properties of this localized object (depending on type and language, like gender) and grammar inflections. wikimedia found has some database?

Notes from Dwayne

* I'd really like to start with the simplest thing. Seems like gender related issues was the easiest and seemed to mimic current Gettext-like plurals.
* The general feeling I had is that most of the concepts can be aligned with the current plural input in gettest. The plurals as they are in l20n seem overly complex.
* I am very interested in ensuring that nothing gets exposed if nothing is defined. I.e. people see no plural interface if no plurals handling is defined for the language. Qt succeeds and PO fails on that count.

== ANLoc ==
Unlocking anloc should be OK with using langpack/beta/official release for Firefox. Key points that I recall are

* anloc funding based on both l10n work and community building, sustainability is key lesson learned from the 2.0 days attempt.
* expose progress on the web, with
** landing page for langpack, all.html exposure
** no-editor-review updates on AMO langpacks
** blog posts on progress, asking for feedback and recruiting testers, possibly MCS-based
* Offerings going beyond "shipping Firefox" as offerings, transparently done
** African language Firefox as tool to interest locals into localization of further software
** African language Firefox as tool to improve the web for locals
** possibly offering opportunities like global voices to shape the local web
* Offerings are not exclusive, it should be apparent why doing that in addition gets the locals what. Not a strict priority list that's just work items.
* Kick-off meeting in Africa with Axel and locals, need to find out where, when, and what's on the agenda. Earlier is better
* Aiming at 10 languages, less ain't bad
** Need to figure out clear milestones to check in whether things work

== l10n priority list ==
You guys have a list of well-chunked phases to do a Firefox l10n, we want to get that out into the public. Both the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases?view=markup descriptions of the phases] as well as the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phaselist?view=markup mapping of files to phases] are in zaf's svn.

These need update for fx 3.5? --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)

== localizer and tool authors meetup ==

* Axel, Dwayne, Gisela on the hook
* two rounds of slow geeking of localizers showing how they work with tools, and tool authors how they think they tools should be used
* break out sessions unconference-style
* hack day?

Not sure about the size here. Should we split up Asia and EMEA? East-Asian websites make me think that the UI paradigms might be different there. Where? When? Size should probably be smaller than OTT? Got already some internal support for doing this. --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)

User:AxelHecht/AMS meet with Dwayne June 2009

2009-07-14T08:19:50Z

Dwayne: /* l20n */

These are notes from a chat between Dwayne and I in Amsterdam, June 24th 2009. Edits should be mostly done by Dwayne or me, comments are OK on the Discussion page.

== l20n ==
Not got to that necessarily last night, but here's my list of things to figure out:

* plurals with symbolic names, too? DB: CLDR like name? See http://unicode.org/cldr/data/charts/supplemental/language_plural_rules.html
* UI paradigm to expose inflected placables within strings
* UI paradigm to expose variants of a localized string/object - DB: see latest Qt .ts format which seems to handle variants.

Notes to self here:

* overlay of properties of this localized object (depending on type and language, like gender) and grammar inflections. wikimedia found has some database?

Notes from Dwayne

* I'd really like to start with the simplest thing. Seems like gender related issues was the easiest and seemed to mimic current Gettext-like plurals.

== ANLoc ==
Unlocking anloc should be OK with using langpack/beta/official release for Firefox. Key points that I recall are

* anloc funding based on both l10n work and community building, sustainability is key lesson learned from the 2.0 days attempt.
* expose progress on the web, with
** landing page for langpack, all.html exposure
** no-editor-review updates on AMO langpacks
** blog posts on progress, asking for feedback and recruiting testers, possibly MCS-based
* Offerings going beyond "shipping Firefox" as offerings, transparently done
** African language Firefox as tool to interest locals into localization of further software
** African language Firefox as tool to improve the web for locals
** possibly offering opportunities like global voices to shape the local web
* Offerings are not exclusive, it should be apparent why doing that in addition gets the locals what. Not a strict priority list that's just work items.
* Kick-off meeting in Africa with Axel and locals, need to find out where, when, and what's on the agenda. Earlier is better
* Aiming at 10 languages, less ain't bad
** Need to figure out clear milestones to check in whether things work

== l10n priority list ==
You guys have a list of well-chunked phases to do a Firefox l10n, we want to get that out into the public. Both the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases?view=markup descriptions of the phases] as well as the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phaselist?view=markup mapping of files to phases] are in zaf's svn.

These need update for fx 3.5? --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)

== localizer and tool authors meetup ==

* Axel, Dwayne, Gisela on the hook
* two rounds of slow geeking of localizers showing how they work with tools, and tool authors how they think they tools should be used
* break out sessions unconference-style
* hack day?

Not sure about the size here. Should we split up Asia and EMEA? East-Asian websites make me think that the UI paradigms might be different there. Where? When? Size should probably be smaller than OTT? Got already some internal support for doing this. --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)

User:AxelHecht/AMS meet with Dwayne June 2009

2009-07-14T08:19:04Z

Dwayne: /* l20n */ note about gender first

These are notes from a chat between Dwayne and I in Amsterdam, June 24th 2009. Edits should be mostly done by Dwayne or me, comments are OK on the Discussion page.

== l20n ==
Not got to that necessarily last night, but here's my list of things to figure out:

* plurals with symbolic names, too? DB: CLDR like name? See http://unicode.org/cldr/data/charts/supplemental/language_plural_rules.html
* UI paradigm to expose inflected placables within strings
* UI paradigm to expose variants of a localized string/object

Notes to self here:

* overlay of properties of this localized object (depending on type and language, like gender) and grammar inflections. wikimedia found has some database?

Notes from Dwayne

* I'd really like to start with the simplest thing. Seems like gender related issues was the easiest and seemed to mimic current Gettext-like plurals.

== ANLoc ==
Unlocking anloc should be OK with using langpack/beta/official release for Firefox. Key points that I recall are

* anloc funding based on both l10n work and community building, sustainability is key lesson learned from the 2.0 days attempt.
* expose progress on the web, with
** landing page for langpack, all.html exposure
** no-editor-review updates on AMO langpacks
** blog posts on progress, asking for feedback and recruiting testers, possibly MCS-based
* Offerings going beyond "shipping Firefox" as offerings, transparently done
** African language Firefox as tool to interest locals into localization of further software
** African language Firefox as tool to improve the web for locals
** possibly offering opportunities like global voices to shape the local web
* Offerings are not exclusive, it should be apparent why doing that in addition gets the locals what. Not a strict priority list that's just work items.
* Kick-off meeting in Africa with Axel and locals, need to find out where, when, and what's on the agenda. Earlier is better
* Aiming at 10 languages, less ain't bad
** Need to figure out clear milestones to check in whether things work

== l10n priority list ==
You guys have a list of well-chunked phases to do a Firefox l10n, we want to get that out into the public. Both the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phases?view=markup descriptions of the phases] as well as the [http://zaf.svn.sourceforge.net/viewvc/zaf/trunk/po/fftb/phaselist?view=markup mapping of files to phases] are in zaf's svn.

These need update for fx 3.5? --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)

== localizer and tool authors meetup ==

* Axel, Dwayne, Gisela on the hook
* two rounds of slow geeking of localizers showing how they work with tools, and tool authors how they think they tools should be used
* break out sessions unconference-style
* hack day?

Not sure about the size here. Should we split up Asia and EMEA? East-Asian websites make me think that the UI paradigms might be different there. Where? When? Size should probably be smaller than OTT? Got already some internal support for doing this. --[[User:AxelHecht|Pike]] 12:27, 8 July 2009 (UTC)

User:AxelHecht/AMS meet with Dwayne June 2009

2009-07-14T08:17:53Z

Dwayne: Link to CLDR

Summit2008/Sessions/Proposals/PR Training Presentation

2008-07-22T10:13:55Z

Dwayne: /* Interested People */

==Session Title==
Mozilla Media Training

==Session Leaders==
* Melissa Shapiro
* Two outside professional media trainers

==Summary==
Press coverage, media relations and speaking opportunities have been a key part of Mozilla’s success to date. The PR team at Mozilla is consciously looking to expand the number of trained community spokespeople who can speak with press about their involvement in the Mozilla project.

This session provides community members with the training necessary to become effective spokespeople on behalf of Mozilla. Attendees will learn how to effectively communicate with trade, business, print and broadcast media.

Among the areas that will be covered include tips for acing interviews, how to talk to print and broadcast media, helpful pointers on how to avoid touchy issues, how to keep interviews on topic, and how to talk about Mozilla to the media.

The session focuses on:
* Understanding your audience’s interests and expectations
* Overview of different types of media and how to help journalists meet their objectives
* Interview techniques through mock interviews with immediate feedback

==Estimated length==
Attendance for the full two hour training is mandatory for this session.

==Expected turnout==
20-30 people

If there's a positive initial response, I'll look into adding a second session to accommodate more attendees. We cannot have more than 30 people in each session.

Who should come? Anyone who on occasion has been called on to speak to a reporter or regularly attends conferences and wants to learn how they can be effective Mozilla spokespeople to the general public and media.

==Agenda==
* Intro to the media
* Overview of Mozilla top-line messages
* Attendees practice interview skills in mock media Q&As

==Equipment needs==
* Projector

==Interested People==
* Zak Greant
* Dwayne Bailey

Summit2008/Sessions/Proposals

2008-07-21T12:37:45Z

Dwayne: /* L10n Related */ Add idea for Anloc discussion

__TOC__

==2008 Firefox Summit Session Overview==

The Firefox 2008 Summit will include three full days of sessions. All Firefox 2008 Summit attendees are invited to propose and lead sessions.

Session is the generic term covering "presentations," "tutorials," "[http://en.wikipedia.org/wiki/Birds_of_a_Feather_(computing) BoF]s," etc.

Please only propose a session that you intend to lead. If you'd like someone else to run a session, talk with or email them directly to discuss.

Please create a new wiki page for your proposal that includes headers for Session Title, Session Leaders, Summary, and Agenda.

Please let us know if you think there is a benefit from having an open session to include people who are not attending the summit. We will do our best to accommodate, but we may not be able to.

==General Proposals==

Link your Summit session proposals here. Put them in the general tracks listed in the TOC if that makes sense

* Managing/working with remote people [mrz, would be interested in a round-table discussion]
* <strike>Customizing Distributions: What, Why, and How (and what's planned) [kev]</strike> (withdrawn)
* <strike>Partnering: What the heck does it mean, anyways [kev, who will also try and rope jay into participating; gen also happy to help here]</strike> (withdrawn)
* How to stop guessing what the community thinks—the Community Surveys project [sethb, stas]
* How user-to-user support is the gateway into Mozilla for non-developers [sumo team]
* [[Summit2008/Sessions/Proposals/Firebug&Chromebug|Firebug and Chromebug]] [johnjbarton]
* [[Summit2008/Sessions/Proposals/The new and improved MDC|The new and improved MDC]] [sheppy]
* [[Summit2008/Sessions/Proposals/Problems people find using Firefox and how to solve them|Problems people find using Firefox and how to solve them]] [iacchi] (projector)
* What's happening with the www.mozilla.org site [davidwboswell]
* Relationships and communication with Linux distros [caillon]
* Keeping multiple balls in the air: Juggling BOF [melissa and dietrich]
* Why I Didn't Write a Test: Stuff that's hard to test, and what we could do to fix it [ted]
* [[Summit2008/Sessions/Proposals/Sharing tests: cross browser tests project|Sharing tests: cross browser tests project]] [syp] (projector)
* [[Summit2008/Sessions/Proposals/LightOfFirefox|Light of Firefox]] [Dr.Kakehi]

=== Add-ons Related ===
* Ways to increase add-on adoption & discoverability (lifestyle themes/add-ons, favorite-ing, recommender, international reach, news feed) [basil]
* Add-Ons Management in Firefox (Add-Ons Mgr, add-on locale packs, languages, dictionaries, plugins, dependency, updates) [mossop]
* AMO Features & Roadmap (site improvements, role of sandbox, new ideas) [basil, clouserw, morgamic]
* [[Summit2008/Sessions/Proposals/Add-ons/Metrics|Add-on Metrics & Stats]]
* AMO Editorial Process (streamlining editorial work, policy needs, recruiting, etc...) [basil]
* Catering to Add-on Developers (authoring and publishing process, docs, platform services, Fx API changes, newsletter, authoring tools, AMO API's) [Mfinkle?]
* Extension lifecycle: How to get from the idea to the extension (short), finding testers for first development versions, stabilizing and maintaining code, submission to AMO and how AMO editors make public and review it, conditions for hosting on AMO, getting the extension localized for broader international acceptance, how to keep up to date with AMO, Mozilla products and your extension [Archaeopteryx]
* AMO L10n processes using Verbatim (roadmap, current challenges, ideas for improvements) [clouserw, mic, etc.]
* Mozdev and the wider developer community. Deeper ties with AMO, added value, and more [kinger,davidwboswell,ericjung]

=== Web Platform Related ===
* Rich Media on the Web [vlad]
* Web Standards and Strategy [arun]
* [[Summit2008/Sessions/Proposals/Platform/WebPerformanceTools|Performance and memory tools for the Web platform]] [dbaron] Large

=== Mozilla Platform Related ===
* Using [[MDC:Mercurial]] [bsmedberg,jorendorff] Large (projector)
* [[XPCOMGC]] introduction and planning [bsmedberg] Medium (projector)
* Hardware Acceleration & Gecko [vlad] Large (projector)
* 1.9.1 progress updates and feature culling [roc] Medium* (projector)
* Mozilla static analysis and rewriting tools and projects [dmandelin,taras] Medium
* Positioning XULRunner as a general purpose platform [mfinkle] Medium
* Tamarin Tracing JIT intro, how it works [jimb] Medium
* DTrace [alfred.peng, sayrer] Medium (projector)
* Priorities for code cleanup and improvement projects [roc] Medium
* Layout meeting [roc,dbaron] Small

=== Mobile Related ===
* Device APIs [dougt, aza] Mid Size Round Table (projector)
* Fennec: Mobile Firefox [christian]- Larger Room
** A presentation of where Fennec is now and where it is heading followed by a demo.
** Need projector for slides and mobile phone projector
* [[Summit2008/Sessions/Proposals/Mobile/Embedding|Embedding]]: [blizzard,mfinkle,dcamp] Mid size (white board)
* Zephyr: The Firefox Phone [aza] (possibly combined w/ below)
* Mobile UX: [aza,madhava] Mid Size (projector)
* L10n process for mobile [mic, christian]- discussion Larger Room (white board)
* Writing add-ons for mobile [mfinkle] Mid Size (Projector)

=== comm-central (Messaging/MailNews/Calendar/Thunderbird/SeaMonkey Related) ===

* Brainstorm: How to ensure quality for Thunderbird with 1 full-time staff? [davida, nth10sd (Gary)]
** This is also worth discussion for Calendar (2 full-time developers, 1 full time QA, part time UX)
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* Radical ideas for making Thunderbird massively popular [davida]
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* Thunderbird 3 planning [momo staff, etc]
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* MailNews Refactoring [KaiRo, momo staff, etc.]
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: after the Hg session

* Next Generation Instant Messaging
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* Beyond protocols: thinking about user experiences of communication [clarkbw, davida, ?]
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* Thunderbird + Labs brainstorming (also listed under labs)
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* What should we do about SUMO/Thunderbird/Mozillazine/etc.? [davida, dtenser]
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* Plans for the move of Thunderbird/SeaMonkey/MailNews to Mercurial incl. Calendar's role in the future repository world [sipaq, KaiRo, ...]
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* Raising developer interest and general interest in the calendar products [sipaq, daniel]
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* Improving calendar community communication [sipaq]
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* Calendar/TB3 integration plans
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime

* Extensibility of Sunbird/Lightning [philipp]
** size: 30-60 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: anytime
** On the next day, the team could hold a talk discussing the top 10 ideas and how much of it is possible and how much is needed (optional)

* SeaMonkey 2 planning/status [KaiRo]
** size: 10-20 people
** equipment: whiteboards, projector & screens
** style: BoF, free thinking, open brainstorming, inspirational
** timing: Tuesday?

=== Labs ===
(DRAFT)
* Thinking About Web Services, Context and the Role of the Browser [cbeard]
* Weave [thunder]
* Snowl - an experiment around messaging in the browser [myk]
** size: 25-50
** style: demonstration & discussion
** equipment: projector & screen
** timing: any time after the main labs presentation
* Ubiquity [aza]
* Mixing desktop & browser and easing extension development pains [atul, aza]
* Prism [mfinkle]
* Lifecycle of a Labs Project []
* Open Innovation at Scale []
* Brainstorming Session []
* JavaScript Tricks used in Labs Prototypes [thunder]
* Thunderbird + Labs brainstorming (also listed under messaging)

=== Mozilla Mission and Identity ===

I'd like to have a series of sessions relating to Mozilla identity, mission and relationship to other open source and "open" projects. I'm thinking of the following; comments, suggestions welcome. Other session leaders '''very''' welcome as well; it's helpful to me to participate without leading sometimes.

* [[Summit2008/Sessions/Proposals/Mozilla-Identity|Mozilla Identity]] [mitchell]
* [[Summit2008/Sessions/Proposals/Visualizing-Mozilla|Visualizing the Mozilla project]] [mitchell]
* [[Summit2008/Sessions/Proposals/2-year-goals|Promoting the Mozilla mission through Firefox and platform - 2 year goals]] [mitchell]
* [[Summit2008/Sessions/Proposals/Historical|Historical Curiosities]] [mitchell]

* [[Summit2008/Sessions/Proposals/MoFo|Mozilla Foundation 2.0]] [hecker]
* Fostering "consensus" in an open community [arun]

=== Marketing/PR Related ===
* Guerrilla marketing brainstorming session [polvi (& William)] Medium Working Session
* [[Summit2008/Sessions/Proposals/MozillaInAsia|Developing Mozilla in Asia]] (Asia ex-China, ex-Japan) [gen] Medium Working Session
* [[Summit2008/Sessions/Proposals/PR_Case_Studies|Mozilla PR case studies]] [melissa & nicole] Medium Presentation (projector)
* The Firefox brand: what it means and how to use it [jslater] (additional note: this might work well in a trademark/partnerships/logo track with some sessions that Harvey and Kev are developing) Medium Presentation (projector)
* Mozilla in Europe - the impact of Fx 3 and initiatives for strong 2H08 growth[Jane] Medium Presentation (projector)
* Europe - lessons in open source, community and culture [Gandalf/Jane] Large Presentation (projector)
* Open Source Marketing - engaging the community and spreading Firefox in ways that are consistent with Mozilla values [jslater, mary, alix, rolnitzky, others] Large Presentation (projector)
* Firefox in China - Firefox 3.0 and beyond [Jack] Medium Presentation (projector)
* Thunderbird marketing - how should we do it? [davida] Medium Working Session
* State of spreadfirefox: what's working today, what should v3 look like? [alix] Medium Working Session
* Firefox 3 spreading in Japan - [Shigeru] Presentation Medium
* Plan about the new issue handling site for end-user in Japan - [himorin]
** size : 20 to 30 or so (i think)
** equipment : projector + screen and whiteboard
** style : free thinking and open discussion after a short presentation of current state
** timing : anytime
** host : shimono (me), masayuki (+ some other Mozilla Japan staffs)
* Foxkeh more global/official [shigeru, kaori] Presentation Meium

=== L10n Related ===
* Localizing Firefox 3: Analysis of good and not so. "[http://de.wikipedia.org/wiki/Sepp_Herberger Nach dem Spiel ist vor dem Spiel.]" [Axel/Mic/L10n-drivers]
** size: 50-100 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: 60 to 90 minutes

* Expanding and better supporting international communities - community portal ideas [Seth/Mic/Gandalf]
** size: 50-100 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: 60 to 90 minutes

* Discussion on targeted community development and localization. How do we do a better job of recruiting, and bringing critical localizations and communities into the mix in upcoming releases? [chofmann/sethb]
** size: 50-100 people
** equipment: projector & screens
** style: presentation followed by discussion
** timing: 30-60 minutes

* How can we scale better across all our products in more languages including emerging markets like Asia, Africa, etc. [Mic/Chofmann/Axel]
** size: 50-100 people
** equipment: whiteboards, projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: 60 to 90 minutes

* Problems of small translation teams with the l10n process. What can be done to make translation easier and more effective? [erdal]
** size: 50-100 people
** equipment: projector & screen
** style: small presentation, discussion/brainstorming
** timing: 60-90 minutes

* moz2po and the rest of the Translate Toolkit - How to use them for Mozilla localisation, and some features that you might not be familiar with. Come and help to shape the next development phase of the tools which will specifically address Mozilla requirements (dwayne/friedel)
** size: +-70
** equipment: projector
** style: presentation, discussion
** timing: 60-90 minutes

* Narro - Find out how you can speed up the localization process, increase the translation quality, make translations open to anyone and use Narro for translating almost anything [Alexandru Szasz aka alexxed]
** size: 50 people
** equipment: projector
** style: presentation, discussion
** timing: 60 minutes

* Localizing SUMO - What should be the localization policy of SUMO? How do we get coverage for more locales for product help and prioritize knowledge base articles for translation? Do we want to ensure tier 1 locales always have all prioritized articles translated, or do we want it to be community-driven? [djst/mconnor]
** size: 25-50 people
** equipment: whiteboards
** style: discussion
** timing: 60 minutes

* India - starting a viable, sustainable, smoldering Mozilla movement in a zany market. What are the opportunities for webtools and for l10n? [arun / sethb]
** size: 15-20 people
** equipment: whiteboards
** style: discussion
** timing: 60 minutes

* QA on translation - Presentation of the pt-PT and french automated QA system - discussion of how to use QA and related translation memories. (Philippe and João Miguel Neves)
** size: +-70
** equipment: projector, computer, internet access
** style: presentation, discussion
** timing: 40 minutes

* Anloc (pronounced Unlock) - adding 10 African languages to Firefox. An introductions to the Firefox localisation component of the global Anloc project. Discussion on how to help, support and mentor African Firefox localisers that will grow the African language community and sustain their localisation efforts. (Dwayne)
** size: 15-20 people
** equipment: whiteboard
** style: discussion
** timing: 60 minutes

=== Security ===
* keeping an eye on malware trends. metrics, investigations, partnerships with scanning vendors (chofmann, dtenser, dveditz)
* Updates around NSS and SSL. Planning for better handling of mixed security content. [kaie]
* Manual penetration testing and how to practice good security techniques [pvnick]

=== Firefox, Product Development & User Experience Design ===
* [[Firefox3.1/themes/browserin2015|History & Future: Imagining the web browser of 2015]] [faaborg, wei]
** size: 100-200 people
** equipment: projector & screens
** style: free thinking, open brainstorming, inspirational
** timing: early in the day, anytime during the week

* Firefox 3 Post Mortem [beltzner]
** size: 50-100 people
** equipment: projector & screens (will do laptop notetaking)
** style: open discussion, roundtable
** timing: early in the week

* The Mozilla Design Process & How to Listen to Feedback [beltzner]
** size: 50-100 people
** equipment: projector & screens
** style: presentation & discussion
** timing: doesn't matter

* Design Demos [faaborg, boriss]
** size: 100+ people
** equipment: projector & screens
** style: demonstration & discussion
** timing: end of day

* [[Summit2008/Sessions/Proposals/Life After Awesome|Life After Awesome]]: How can we further improve the location bar? Where else should we apply the awesome-sauce of adaptive learning and multivariate scoring? [dietrich]
** size: 25-50 people
** equipment: whiteboards / easel pads
** style: discussion & brainstorm
** timing: doesn't matter

* [[Firefox3.1/themes/whatCanPeopleDoWithBrowsers|What are people doing with web browsers]] [wei]
** size: 50-100 people
** equipment: projector & screens
** style: presentation & discussion
** timing: end of dayish

* Make with the Pretty: BOF/Tutorial for visual design at Mozilla making icons, mockups, graphics [faaborg, boriss, shorlander?, tango team?]
** size: 0-50 people
** equipment: projector & screens
** style: tutorial & discussion
** timing: anytime

=== IT ===
* Infrastructure overview Medium Projectors [Justin, MRZ]
* How to build your application to best utilize IT's infrastructure Medium [Jeremy, MRZ]

=== Metrics ===
* What data do you need to be able to improve your contribution to Mozilla? [deinspanjer/ken]
** size: 25-50
** equipment:
** style: collaboration/round table
** timing: after the metrics first talk
* What questions should we be asking with our data? [ken]
** size: 25-50
** equipment:
** style: brainstorm
** timing: after the metrics first talk

=== QA ===
* [http://wiki.mozilla.org/Summit2008/Sessions/Proposals/QA_Tools:_Litmus/Hendrix How to get involved into QA - Overview over the QA Tools (Litmus, Hendrix, etc)] [Tomcat]
* Automating Firefox UI actions through Gristmill as a means of accessible QA automation. [Clint, Mikeal, Adam, etc]
* Leak Testing Demonstration [Tomcat]
* [[Summit2008/Sessions/Proposals/Bug_Triage|Bug triage]] (discussion/BOF) [jesse, sam sidler]
* <strike>Reducing testcases with Lithium [jesse]</strike>

==== Accessibility ====
* [http://wiki.mozilla.org/Summit2008/Sessions/Proposals/Accessibility:An_Overview_Of_APIs_And_Standards_Firefox_Supports An Overview of APIs and web standards Firefox supports] - MarcoZ
* [http://wiki.mozilla.org/Summit2008/Sessions/Proposals/Accessibility:Experience_Accessibility_Hands-on Experience accessibility hands-on] - a live demo and hands-on session taking accessibility down to the real-life level many people work with every day - MarcoZ, Aaronlev

=== Webdev ===
* MozillaID - community identity and single sign on. [laura]
** size: 10-20 people
** equipment: whiteboards, projector & screen
** style: discussion
** timing: 60 minutes

User:Dwayne

2008-06-02T07:27:04Z

Dwayne: /* Dwayne Bailey */ link to moz2po

= Dwayne Bailey =

I work for [http://translate.org.za Translate.org.za] which focuses on the localisation of Open Source Software into South African languages.

I also work on the tools that we developed:

* [http://translate.sourceforge.net/wiki/toolkit/index Translate Toolkit] - includes the widely used [http://translate.sourceforge.net/wiki/toolkit/moz2po moz2po] which allows you to translate Mozilla products using PO files.
* [http://translate.sourceforge.net/wiki/pootle/index Pootle] - allows you to expose your translations to a broader community of volunteer translators.

The Translate Toolkit is used by a large number of Firefox localisers while Pootle will soon be tested for use by the Mozilla web team.

User:Dwayne

2008-06-02T07:26:24Z

Dwayne: /* Dwayne Bailey */

= Dwayne Bailey =

I work for [http://translate.org.za Translate.org.za] which focuses on the localisation of Open Source Software into South African languages.

I also work on the tools that we developed:

* [http://translate.sourceforge.net/wiki/toolkit/index Translate Toolkit] - includes the widely used moz2po which allows you to translate Mozilla products using PO files.
* [http://translate.sourceforge.net/wiki/pootle/index Pootle] - allows you to expose your translations to a broader community of volunteer translators.

The Translate Toolkit is used by a large number of Firefox localisers while Pootle will soon be tested for use by the Mozilla web team.

User:Dwayne

2008-06-02T07:25:34Z

Dwayne: New page: = Dwayne Bailey = I work for [http://translate.org.za Translate.org.za] which focuses on the localisation of Open Source Software into South African languages. I also work on the tools t...

= Dwayne Bailey =

I work for [http://translate.org.za Translate.org.za] which focuses on the localisation of Open Source Software into South African languages.

I also work on the tools that we developed:

* [http://translate.sourceforge.net/wiki/toolkit/index Translate Toolkit] - includes the widely used moz2po which allows you to translate Mozilla products using PO files.
* [http://translate.sourceforge.net/wiki/pootle/index Pootle] - allows you to expose your translations to a broader community of volunteer translators.

The Translate Toolkit is used by a large number of Firefox localisers while Pootle will soon be tested for use by the Mozilla web team.

Summit2008/Sessions/Proposals

2008-06-02T07:21:57Z

Dwayne: /* Proposals */ moz2po

__NOTOC__
==2008 Firefox Summit Session Proposals==

The Firefox 2008 Summit will include three full days of sessions. All Firefox 2008 Summit attendees are invited to propose and lead sessions.

Sessions is the generic term covering "presentations," "tutorials," "[http://en.wikipedia.org/wiki/Birds_of_a_Feather_(computing) BoF]s," etc.

Please only propose a session that you intend to lead. If you'd like someone else to run a session, talk with or email them directly to discuss.

Please create a new wiki page for your proposal that includes headers for Session Title, Session Leaders, Summary, and Agenda.

Please let us know if you think there is a benefit from having an open session to include people who are not attending the summit. We will do our best to accommodate, but we may not be able to.

==Proposals==
Link your Summit session proposals here.
* Managing/working with remote people [mrz, would be interested in a round-table discussion]
* Customizing Distributions: What, Why, and How (and what's planned) [kev]
* Partnering: What the heck does it mean, anyways [kev, who will also try and rope jay into participating]
* Localizing Firefox 3: Analysis of good and not so. "[http://de.wikipedia.org/wiki/Sepp_Herberger Nach dem Spiel ist vor dem Spiel.]" [Axel, l10n-drivers]
** The world of l10n through the eyes of a small translation team [erdal]
** moz2po - using them for Mozilla localisation including some that you might not be familiar with. Help shape the next development phase of the tools which will specifically address Mozilla requirements (dwayne/friedel)
* Evening hackathon (teams gather together to prototype cool bluesky ideas, do demos at the end) [zach]
* How to stop guessing what the community thinks—the Community Surveys project [sethb, stas]
* Guerrilla marketing brainstorming session [polvi (& William)]
* Discussion on growing Mozilla in Asia (focus on Asia ex-China, ex-Japan) [gen]
* Behind the smoke and mirrors: Mozilla PR case studies - better title tbd [melissa & nicole]
* What questions should we be asking with our data? [ken]
* How user-to-user support is the gateway into Mozilla for non-developers [sumo team]
* Firebug/Chromebug (put where you like) [johnjbarton]
* [[Summit2008/Sessions/Proposals/The new and improved MDC|The new and improved MDC]] [sheppy]
* The Firefox brand: what it means and how to use it [jslater] (additional note: this might work well in a trademark/partnerships/logo track with some sessions that Harvey and Kev are developing)
* [[Summit2008/Sessions/Proposals/Life After Awesome|Life After Awesome]]: How can we further improve the location bar? Where else should we apply the awesome-sauce of adaptive learning and multivariate scoring? [dietrich]
* Which problems users find using Firefox and how to solve them [iacchi, flod]

=== Add-ons Related ===
* Ways to increase add-on adoption & discoverability (lifestyle themes/add-ons, favorite-ing, recommender, international reach, news feed) [basil]
* Add-Ons Management in Firefox (Add-Ons Mgr, add-on locale packs, languages, dictionaries, plugins, dependency, updates) [mossop]
* AMO Features & Roadmap (site improvements, role of sandbox, new ideas) [basil, clouserw, morgamic]
* [[Summit2008/Sessions/Proposals/Add-ons/Metrics|Add-on Metrics & Stats]]
* AMO Editorial Process (streamlining editorial work, policy needs, recruiting, etc...) [basil]
* Catering to Add-on Developers (authoring and publishing process, docs, platform services, Fx API changes, newsletter, authoring tools, AMO API's) [Mfinkle?]
* AMO L10n processes (roadmap, current challenges, ideas for improvements) [clouserw, mic, etc.]
* Mozdev and the wider developer community. Deeper ties with AMO, added value, and more [kinger,davidwboswell]

=== Web Platform Related ===
* Rich Media on the Web [vlad]
* Malware 2.0: Security concerns about the Web as a dominant application platform [ma1]

=== Mozilla Platform Related ===
* Using [[MDC:Mercurial]] [bsmedberg,jorendorff]
* [[XPCOMGC]] introduction and planning [bsmedberg]
* Hardware Acceleration & Gecko [vlad]
* 1.9.1 progress updates and feature culling [roc]
* Mozilla static analysis and rewriting tools and projects [dmandelin,taras?]

=== Mobile Related ===
* Device APIs [dougt, aza]
* Fennec Update [christian]
* Embedding [blizzard]
* Zephyr: The Firefox Phone [aza]
* Mobile UX: [aza,madhava]
* L10n [mic]

=== Messaging/MailNews/Thunderbird Related ===

* Brainstorm: How to ensure quality for Thunderbird with 1 full-time staff? [davida, ???]
* Radical ideas for making Thunderbird massively popular [davida]
* Thunderbird 3 planning [momo staff, etc]
* MailNews Refactoring [kairo, momo staff, etc.]
* Next Generation Instant Messaging
* Beyond protocols: thinking about user experiences of communication [clarkbw, davida, ?]
* Mozilla in Europe - the impact of Fx 3 and initiatives for strong
2H08 growth (Jane)

* ..

=== Labs ===
(DRAFT)
* Thinking About Web Services, Context and the Role of the Browser [cbeard]
* Weave [thunder]
* Snowl [myk]
* Ubiquity [aza]
* Mixing desktop & browser and easing extension development pains [atul, aza]
* Prism [mfinkle]
* Lifecycle of a Labs Project []
* Open Innovation at Scale []
* Brainstorming Session []
* Javascript Tricks used in Labs Prototypes [thunder]

L10n:Pain points

2007-10-18T09:32:19Z

Dwayne: The Translate.org.za way and pain

=== Gandalf's approach ===

I'm describing the pitfalls of localizer from the very beginning of his work with first translation, until he's a fully featured maintainer of the localization.

== Initial localization ==

* need to know CVS
* need to install CVS
* need to read long instructions to get the trick that you can actually unzip the .jar file with WinZip on your windows machine
* need to understand that source l10n structure and final l10n structure are very different
* need to suffer possible effects of the previous ones, and reorganize the structure soon after initial idea of localization of ./chrome/en-US.jar file
* need to be super-cautious about the formatting of the files. ANY change including often invisible BOM characters at the beginning of the file (added automatically by many editors) or any mistake that causes DTD file to be unparseable by Gecko is fatal
* the results of such mistakes are very hard to discover early, you usually know about it after new build is created from tinderbox
* or, you have to set up WHOLE Firefox build environment, which is horribly complicated on every OS.
* if you even discover it, it's hardly debuggable. Usually localizer see yellow screen with some red letters that are pointless, since they don't show the whole message. If the mistake was made in .properties file, you're down. Until you have debug build and console you cannot find why firefox doesn't work for you, it hits in silence.
* It's impossible to know the position of the entity on the screen
* Mozilla localizers cannot use the well known simplifiers used by all other projects on earth allowing them to check, by a single click, where such word is used elsewhere in the app, to keep the consistency
* same with ability to easily search through the messages
* Mozilla I18n does not expect that many languages have declensions, multiply plural forms etc.
* Localizer see "<ENTITY foo.x "Make $1%S go $2%S over $3%S">" and we wish him a pleasant nightmare
* there's no way to manage the team work using any automated way. You have to physically select files, send them to localizers, gather the result, combine into structure and cross-fingers hoping there's no syntax bug, missing entity, etc that will cause everything to go down
* On each and every level of localization you have absolutely no idea if you're doing the right thing
* once you're ready, you still have to wait for someone to build Firefox with your locale to test it, or get it accepted to CVS and wait for tinderbox to provide you a build. If you fix a bug, you can confirm that only after waiting for a new build.

== Working with localization ==

* To get an idea of what has changed since your last localization round and find new entities you either have to learn CVS diff, or digg the website bonsai.mozilla.org. Each of those is good to get an IDEA that something has changed, but it's horrible to work with it.
* Localizers have to develop a internal DIFF algorithm in their heads to transparently see every en-US diff and apply it on their locale by hand.
* Did I already successfully screamed the message that literally everything is done by hand? Beside of compare-locales script.
* There are two most common things I'm doing as a localizer.
** Translate new string
What can we offer? In the ideal world, the localizer should be notified in the nice way that there are new/untranslated strings, he should have an access to them with one click, localize those in the same UI and all other localizers in the team should instantly know that it's already done.
** Check how my updated string looks in the build
In the ideal world we should repackage the ab-CD.jar in his firefox and relaunch Firefox to let him see the change live.

== Dwayne's approach ==

This is a description of my work in localisation using the [http://translate.sourceforge.net/wiki/toolkit/index Translate Toolkit] and [http://translate.sourceforge.net/wiki/pootle/index Pootle]. I think the pain is considerably less then Gandalf's approach but still has some common pains on either end.

=== Starting ===

* Lots of hoops to get bug reports to get access to CVS and to get access to actually do the localisation in that language. More bug reports to create components, etc. Luckily you only have to do this once. But unfortunately the knowledge of what to do is scattered across a wide field. Its seems easy to those that work in it every day but black to those coming in.
* The task of working out what to do, language packs, jars, building, getting the actual files that you actually need to translate from CVS. It has got better with tools that can checkout only l10n work and that can build the structure in l10n/
* Finding out which branch you should be on. What the tag is. How to work on multiple products. Black magic

=== Translating ===

OK this is where I think our process is way way easier.

* Use l10n make to create an l10n/en-US
* Use moz2po to create POT files from the files in l10n/en-US
* Update your PO files using the new POT files using a Translation Memory to make sure that you get good reuse
* Edit in your favourite PO editor allowing you a familiar interface for ALL your localsation. You have full access to LOCALIZATION NOTES, accelerator keys are mostly merged and certain config options are highlighted.
* Do some QA with pofilter, this traps all common bugs that usually break a build
* Use po2moz to create a set of PO files ready for committing to Mozilla CVS
* Make a diff - check it and make sure that nothing terribly damaging is happening
* Use a script that creates a language pack
* Test the language pack. Iterate

=== Completing ===

* Check that you've been working on the right stuff
* Make a bug report with your diff
* Watch it like a hawk as this might slip through the cracks
* Get it approved
* Checkin the difference
* Check builds in Tinderbox (which I think you needed to ask to be enabled also)

=== Last minute ===

* Discovering snippets, license approval and other pain at a very late stage in the whole process.

=== Heartache ===

* Seeing your hard work miss a deadline and sit in limbo for years without a hope of exposure
* Taking ages to go from beta to live (luckily now solved by exposing beta builds)
* Starting it all over again :)

=== Love ===

* But once its live its amazingly rewarding.
** Firefox makes a real difference in people's lives
** Seeing figures of downloads makes you realise the work is pulling in new people all of who pull in others and hopefully a few will join you in the localisation.

=== Gandalf comparison ===

Honestly I think we've eliminated 100% of the translation pain:
* We don't worry at all about breaking langpacks through broken variables
* Almost all accelerators are correctly placed
* We have all context we need including LOCALIZATION NOTES
* All Unicode related issues are fixed, no BOMs, etc
* We know what was added, what changed and we can find and fix it quickly
* Adding the Pootle dimension we make it very easy for occasional translators to submit fixes and to translate without any tools.
* We translate almost all files in one tool and in one format

Update:RequirementsStats

2007-10-12T09:17:19Z

Dwayne: Add some data about stats I'd love to see in AMO and for l10n

This a wishlist of AMO and Addons key metrics.

Some of these metrics already exist in various parts of the AMO admin control panel but may require consolidation

= TO DO =
* Add priorities for items
* Determine if they are Mozilla dashboard or AMO dashboard features

= Editor Community Metrics =
* How many Reviews are currently in the Moderation Queue
* How many Add-Ons are currently in the Pending Updates Queue
* How many Add-Ons are currently in the Nominated Queue

Over the last week/month
* How many Reviews were processed from the Moderation Queue
* How many Add-Ons were processed from the Pending Updates Queue
* How many Add-Ons were processed from the Nominated Queue

* How many editors do we have?
* What percentage of the work over the past week/month is done by each editor?

= Add-ons Population =
(H=hosted, S=sandboxed, O=offsite)

* How many grand total (hosted, sandboxed, offsite)?

* Total for each app: (H,S, O)
** Firefox
** Thunderbird
** Seamonkey
** Sunbird

* Theme Count:
** {each app by H S O}
* Dictionary Count:
** {each app by H S O}
* Search Plugin Count:
** {each app by H S O}
* Plugin Count:
** {each app by H S O}
* Firefox Themes:
** {each app by H S O}
* For Firefox Extensions:
** {Per category by H S O}

= Add-ons Population Velocity =
During the last week/month, which category areas have seen the most activity? (Top 10)
** Most addons updates & nominated from sandbox
** Most user reviews
** Most user discussion

= Add-ons Rating Popularity =
* Top 20 most highly rated addons for all time/last week/last month

= Add-On Usage =
* Total number of active daily pings (today, avg for last week, avg for last month)
* Total number of active users
* Average number of Addons Per User
* Top 250 most update ping'ed add-ons
** By Browser Version
** By OS
** By Locale

= Add-ons Downloads & Activity =
* Total number of addons downloaded all time/last week/last month
** By Browser Version
** By Operating System
** By Locale
* Top 20 most downloaded addons for all time/last week/last month
* Top 20 most downloaded (non-recommended) addons for all time/last week/last month
* Peak Session Count for last week, last month, average session count per day

= Basic Site Stats (urchin) =
* Page Views
* Unique Users
* Page Views (Search Result Pages)
* Top 50 search terms
** {By Browser Version, OS}
** {By AMO Site Locale - e.g. 60% en-US, etc...}

= Localization Stats =
* For each supported locale
** Add-On Availability
** Add-On Metadata Availability

== Localization Metrics for langpack producers ==
* This is not just AMO but the main l10n work in the product
* Pings from active users
* Downloads (separate from upgrades)
* CSV format
* Platform data

= Addons Developers view =
* Downloads per week/month (preferably as CSV data) - to see new user penetration. Should differentiate upgraders from new users
* Pings per week/month - to see active users.

L10n:Tools

2007-10-10T09:41:12Z

Dwayne: /* Links */ Add link to localisation guide

== Localization Tools ==
Several tools can be used to localize Mozilla-based products.
* [[L10n:MozillaTranslator|Mozilla Translator]] is a Java program which has been used for a long time
* [http://translate.sourceforge.net/wiki/toolkit/moz2po Translate Toolkit] converts files to Gettext PO format to allow you to use any PO editor, widely used after Firefox 1.0 (includes many other tools to check quality)
* [http://moztw.org/tools/mozlcdb MozLCDB] similiar to PO but more dedicated to Mozilla products
* Or any UTF-8-aware text editor to do all stuff manually (this doesn't cover .properties files)
* Still under development: [[L10n:Tool|Tool]]
* [http://translate.sourceforge.net/wiki/pootle/index Pootle] a web server for localisation that allows web-based contributions and management. Combined with the Translate Toolkit it allows Mozilla products to be localised online.

If you want to create localized Windows installers:
* For Mozilla Suite, get [http://moztw.org/tools/ mozip].
* For Firefox and Thunderbird, get [http://www.7-zip.org/ 7-zip].

In any case, you'll have to connect to the CVS repository before and after this task. You can also use an IDE with CVS support, like the Eclipse platform (see below).

== Tool standards ==
Still under development: [[L10n:ToolStandards|Tool Standards]]

== Using the Eclipse platform ==
The [http://www.eclipse.org/downloads/index.php Eclipse platform] (about 100MB download, Java Runtime Environment required) has an integrated CVS support. If you have a l10n CVS account you can use it to work directly on your l10n source files. Eclipse doesn't support natively the kind of SSH keys used by cvs.mozilla.org though. You'll need a running external SSH agent while you're working on it.

=== Linux ===
Use the script provided on the [http://www.mozilla.org/cvs-ssh-faq.html CVS-SSH FAQ] (assuming your private key is ~/.ssh/id_dsa):
eval `ssh-agent -s`
ssh-add ~/.ssh/id_dsa
$SHELL
ssh-agent -k
exit

=== Windows ===
You can use the pageant tool provided on [http://www.chiark.greenend.org.uk/~sgtatham/putty/ putty's website]. Have it loaded in the taskbar, click on "Add Key" and pick your private key file.

Additionaly, you'll have to configure eclipse to use plink[http://www.tortoisecvs.org/faq.html#eclipse]. You can either use the one provided with [http://www.tortoisecvs.org TortoiseCVS] (which should be located at C:\Program Files\TortoiseCVS\TortoisePlink.exe) or the one coming with putty (see above).

To do so, open eclipse and go to "Window > Preferences > Team > CVS > Ext connection method". For CVS_RSH, hit the browse button and find (Tortoise)Plink.exe. The other settings are fine at their defaults. Create a new Repository Location using ext, not extssh. Connect to cvs.mozilla.org and checkout your project.

=== Editing .properties files ===
You can safely use UTF-8 for .properties files these days. There are still some ASCII-based files in our CVS repository, though, so while eclipse can natively open .properties files, they will appear in their ASCII form which is not very pretty if your language uses other Unicode characters. You can install the [http://propedit.sourceforge.jp/index_en.html Properties editor plugin] which provides additional syntax highlighting and handles the Unicode conversion. Follow [http://propedit.sourceforge.jp/howto_eclipseplugin_install_en.html these instructions] to install the plugin.

== Locale Inspector ==
There is a command line tool to check locales. The
following items can be verified:

* byte order mark (BOM)
* entities
* placeholders (%S, #1, $var$ ...)
* access keys
* keybindings

The application also allows merging a locale into the en-US
one. So, a valid translation can be created in seconds. See
the "merge" line in the .ini file.

Download the application here:
http://downloads.mozdev.org/br/locale-inspector.zip

This is a .NET application, therefore the Microsoft .NET Framework
1.1 or Mono is required in order to run it.

The application can be controlled with an .ini file.

== Links ==
* [http://www.mozilla.org/projects/l10n/mlp_tools.html Localization & Leveraging Tools]
* [http://translate.sourceforge.net/wiki/guide/start Localization Guide] broad localization information from tools, objective setting, common errors. A useful resource for those starting to localize.

[[category:L10n]]

L10n:Tools

2007-10-10T09:38:35Z

Dwayne: /* Localization Tools */ Add Pootle

L10n:Tools

2007-10-10T09:36:31Z

Dwayne: /* Localization Tools */ Add better description and correctly name Translate Toolkit

== Localization Tools ==
Several tools can be used to localize Mozilla-based products.
* [[L10n:MozillaTranslator|Mozilla Translator]] is a Java program which has been used for a long time
* [http://translate.sourceforge.net/wiki/toolkit/moz2po Translate Toolkit] converts files to Gettext PO format to allow you to use any PO editor, widely used after Firefox 1.0 (includes many other tools to check quality)
* [http://moztw.org/tools/mozlcdb MozLCDB] similiar to PO but more dedicated to Mozilla products
* Or any UTF-8-aware text editor to do all stuff manually (this doesn't cover .properties files)
* Still under development: [[L10n:Tool|Tool]]

If you want to create localized Windows installers:
* For Mozilla Suite, get [http://moztw.org/tools/ mozip].
* For Firefox and Thunderbird, get [http://www.7-zip.org/ 7-zip].

In any case, you'll have to connect to the CVS repository before and after this task. You can also use an IDE with CVS support, like the Eclipse platform (see below).

== Tool standards ==
Still under development: [[L10n:ToolStandards|Tool Standards]]

== Using the Eclipse platform ==
The [http://www.eclipse.org/downloads/index.php Eclipse platform] (about 100MB download, Java Runtime Environment required) has an integrated CVS support. If you have a l10n CVS account you can use it to work directly on your l10n source files. Eclipse doesn't support natively the kind of SSH keys used by cvs.mozilla.org though. You'll need a running external SSH agent while you're working on it.

=== Linux ===
Use the script provided on the [http://www.mozilla.org/cvs-ssh-faq.html CVS-SSH FAQ] (assuming your private key is ~/.ssh/id_dsa):
eval `ssh-agent -s`
ssh-add ~/.ssh/id_dsa
$SHELL
ssh-agent -k
exit

=== Windows ===
You can use the pageant tool provided on [http://www.chiark.greenend.org.uk/~sgtatham/putty/ putty's website]. Have it loaded in the taskbar, click on "Add Key" and pick your private key file.

Additionaly, you'll have to configure eclipse to use plink[http://www.tortoisecvs.org/faq.html#eclipse]. You can either use the one provided with [http://www.tortoisecvs.org TortoiseCVS] (which should be located at C:\Program Files\TortoiseCVS\TortoisePlink.exe) or the one coming with putty (see above).

To do so, open eclipse and go to "Window > Preferences > Team > CVS > Ext connection method". For CVS_RSH, hit the browse button and find (Tortoise)Plink.exe. The other settings are fine at their defaults. Create a new Repository Location using ext, not extssh. Connect to cvs.mozilla.org and checkout your project.

=== Editing .properties files ===
You can safely use UTF-8 for .properties files these days. There are still some ASCII-based files in our CVS repository, though, so while eclipse can natively open .properties files, they will appear in their ASCII form which is not very pretty if your language uses other Unicode characters. You can install the [http://propedit.sourceforge.jp/index_en.html Properties editor plugin] which provides additional syntax highlighting and handles the Unicode conversion. Follow [http://propedit.sourceforge.jp/howto_eclipseplugin_install_en.html these instructions] to install the plugin.

== Locale Inspector ==
There is a command line tool to check locales. The
following items can be verified:

* byte order mark (BOM)
* entities
* placeholders (%S, #1, $var$ ...)
* access keys
* keybindings

The application also allows merging a locale into the en-US
one. So, a valid translation can be created in seconds. See
the "merge" line in the .ini file.

Download the application here:
http://downloads.mozdev.org/br/locale-inspector.zip

This is a .NET application, therefore the Microsoft .NET Framework
1.1 or Mono is required in order to run it.

The application can be controlled with an .ini file.

== Links ==
* [http://www.mozilla.org/projects/l10n/mlp_tools.html Localization & Leveraging Tools]

[[category:L10n]]

L10n:Tools

2007-10-10T09:34:18Z

Dwayne: /* Localization Tools */ Link more directly to the toolkit

== Localization Tools ==
Several tools can be used to localize Mozilla-based products.
* [[L10n:MozillaTranslator|Mozilla Translator]] is a Java program which has been used for a long time
* [http://translate.sourceforge.net/wiki/toolkit/moz2po GNU gettext PO style], widely used after Firefox 1.0
* [http://moztw.org/tools/mozlcdb MozLCDB] similiar to PO but more dedicated to Mozilla products
* Or any UTF-8-aware text editor to do all stuff manually (this doesn't cover .properties files)
* Still under development: [[L10n:Tool|Tool]]

If you want to create localized Windows installers:
* For Mozilla Suite, get [http://moztw.org/tools/ mozip].
* For Firefox and Thunderbird, get [http://www.7-zip.org/ 7-zip].

In any case, you'll have to connect to the CVS repository before and after this task. You can also use an IDE with CVS support, like the Eclipse platform (see below).

== Tool standards ==
Still under development: [[L10n:ToolStandards|Tool Standards]]

== Using the Eclipse platform ==
The [http://www.eclipse.org/downloads/index.php Eclipse platform] (about 100MB download, Java Runtime Environment required) has an integrated CVS support. If you have a l10n CVS account you can use it to work directly on your l10n source files. Eclipse doesn't support natively the kind of SSH keys used by cvs.mozilla.org though. You'll need a running external SSH agent while you're working on it.

=== Linux ===
Use the script provided on the [http://www.mozilla.org/cvs-ssh-faq.html CVS-SSH FAQ] (assuming your private key is ~/.ssh/id_dsa):
eval `ssh-agent -s`
ssh-add ~/.ssh/id_dsa
$SHELL
ssh-agent -k
exit

=== Windows ===
You can use the pageant tool provided on [http://www.chiark.greenend.org.uk/~sgtatham/putty/ putty's website]. Have it loaded in the taskbar, click on "Add Key" and pick your private key file.

Additionaly, you'll have to configure eclipse to use plink[http://www.tortoisecvs.org/faq.html#eclipse]. You can either use the one provided with [http://www.tortoisecvs.org TortoiseCVS] (which should be located at C:\Program Files\TortoiseCVS\TortoisePlink.exe) or the one coming with putty (see above).

To do so, open eclipse and go to "Window > Preferences > Team > CVS > Ext connection method". For CVS_RSH, hit the browse button and find (Tortoise)Plink.exe. The other settings are fine at their defaults. Create a new Repository Location using ext, not extssh. Connect to cvs.mozilla.org and checkout your project.

=== Editing .properties files ===
You can safely use UTF-8 for .properties files these days. There are still some ASCII-based files in our CVS repository, though, so while eclipse can natively open .properties files, they will appear in their ASCII form which is not very pretty if your language uses other Unicode characters. You can install the [http://propedit.sourceforge.jp/index_en.html Properties editor plugin] which provides additional syntax highlighting and handles the Unicode conversion. Follow [http://propedit.sourceforge.jp/howto_eclipseplugin_install_en.html these instructions] to install the plugin.

== Locale Inspector ==
There is a command line tool to check locales. The
following items can be verified:

* byte order mark (BOM)
* entities
* placeholders (%S, #1, $var$ ...)
* access keys
* keybindings

The application also allows merging a locale into the en-US
one. So, a valid translation can be created in seconds. See
the "merge" line in the .ini file.

Download the application here:
http://downloads.mozdev.org/br/locale-inspector.zip

This is a .NET application, therefore the Microsoft .NET Framework
1.1 or Mono is required in order to run it.

The application can be controlled with an .ini file.

== Links ==
* [http://www.mozilla.org/projects/l10n/mlp_tools.html Localization & Leveraging Tools]

[[category:L10n]]

L10n:Teams:af

2007-06-05T08:34:17Z

Dwayne: /* Afrikaans (South Africa) */ don't need regional specifier

=== Afrikaans ===

* Web page: [http://translate.org.za translate.org.za]
* Live translation and error reporting: [http://pootle.translate.org.za pootle.translate.org.za]

Owner : Friedel Wolff <fridel at translate dot org dot za>

<noinclude>[[category:L10n Teams|af-ZA]]</noinclude>

L10n:Teams:af

2007-06-05T08:33:15Z

Dwayne: /* Afrikaans (South Africa) */ fix links

=== Afrikaans (South Africa) ===

* Web page: [http://translate.org.za translate.org.za]
* Live translation and error reporting: [http://pootle.translate.org.za pootle.translate.org.za]

Owner : Friedel Wolff <fridel at translate dot org dot za>

<noinclude>[[category:L10n Teams|af-ZA]]</noinclude>

L10n:Teams:af

2007-06-05T08:32:08Z

Dwayne: First mash up for af-ZA l10n team

=== Afrikaans (South Africa) ===

Web page: [http://translate.org.za]
Live translation and error reporting: [http://pootle.translate.org.za]

Owner : Friedel Wolff <fridel at translate dot org dot za>

<noinclude>[[category:L10n Teams|af-ZA]]</noinclude>

L10n:South-African locales

2006-08-28T11:51:12Z

Dwayne: Add links to other 7 South African language FF tinderboxes

== Built ==
; Afrikaans (af) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-af Tinderbox]
; English (South African) (en-ZA) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-en-ZA Tinderbox]
; Ndebele (nr) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-nr Tinderbox]
; Northern Sotho (nso) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-nso Tinderbox]
; Swati (ss) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-ss Tinderbox]
; Southern Sotho (st) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-st Tinderbox]
; Tswana (tn) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-tn Tinderbox]
; Tsonga (ts) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-ts Tinderbox]
; Venda (ve) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-ve Tinderbox]
; Xhosa (xh) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-xh Tinderbox]
; Zulu (zu) : [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla1.8-l10n-zu Tinderbox]