User:Jbeatty

From MozillaWiki
Jump to: navigation, search
Jeff Beatty
[[Image:Jbeatty remo photo.jpg|none|200px|Jeff Beatty]]
Personal Information
City: Provo
Country: USA
Mozilla-specific Information
Wiki-Userame: Jbeatty
Bugzilla-Mail: jbeatty@mozilla.com
Mentor: User:Izel
Miscellaneous Information
private Mail: jbeatty@mozilla.com
GPG-Key: {{{gpg}}}
Website: [elmeroguero.blogspot.com Jeff's Website]
Twitter: @gueroJeff
Identi.ca: {{{identi.ca}}}
Jabber: {{{jabber}}}
IRC: gueroJeff on irc.mozilla.org in
#l10n, #l10n-drivers, #mozilla-hispano, #mozillians, #planning
 

Background

I'm L10n Program Manager on the Mozilla l10n team. I like to call myself the L10n Whisperer.

More about me here: http://blog.mozilla.org/l10n/2012/04/06/get-to-know-a-l10n-driver-jeff-beatty/

Background
  • MSc in Global Computing and Localisation in progress
  • B.A. Spanish Translation; minor in Computational Linguistics
Experience
  • 3-4 years as freelance translator
  • 1.5 years as technical writer/l10n manager/scrum master
  • A summer as court interpreter for State of Wyoming

Events

  • MozCamp EU 2011
  • FOSDEM 2012
  • MozCamp LATAM 2012
  • MozCamp EU 2012
  • Localization World Seattle 2012

Monthly reports

Here are the monthly reports of this user:


  • Property "Gpg" (as page type) with input value "{{{gpg}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Using "identi.ca" as property chain is not permitted during the annotation process.
  • Property "Jabber" (as page type) with input value "{{{jabber}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • "{{{sigmentors}}}" is not recognized as a Boolean (true/false) value.
  • "{{{sigpr}}}" is not recognized as a Boolean (true/false) value.
  • "{{{sigmarketing}}}" is not recognized as a Boolean (true/false) value.
  • "{{{sigdev}}}" is not recognized as a Boolean (true/false) value.
  • Property "Sigsumo" (as page type) with input value "{{{sigsumo}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Property "Sigqa" (as page type) with input value "{{{sigqa}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.



Profile

Background
  • MSc in Multilingual Computing and Localisation in progress
  • B.A. Spanish Translation; minor in Computational Linguistics

Experience:

  • 3-4 years as freelance translator
  • 1.5 years as technical writer/l10n manager/scrum master
  • A summer as court interpreter for State of Wyoming

Contact and social media:


Quarterly goals

Projects

These are some of the projects that I'm currently working on.

L10n Wiki Documentation

Below you'll find some detailed information on current & past projects I'm working on involving the l10n wiki documentation.

L10n Doc Inventory - Ongoing

Ask me for login info if you want to edit the list. The username is mozl10n.

Community Surveys - Oct. 2011

Here are the l10n community surveys that I've conducted:

Tools directories - Q4 2011

Here are some ideas for the tools directories that I plan to create for both WikiMo and MDN:

Idea #1:
For the wikimo, the tools directory will be more about description of features and use within the overall process (reflecting the high-level PM features). This may be directed more at intermediate/advanced users or in-house developers.
For the MDN, tools directory will contain tutorials on using the tool on it's own from the stand point of newcomers. Additional tutorials can be provided for advanced users (e.g., beginner Verbatim tutorial on using Verbatim to translate / intermediate tutorial on updating from VCS and the role of the approver / advanced tutorial on using Verbatim with an external .po editor).
Tools should also be broken up into categories for easy wiki navigation and organizational structure. Proposed categories: localizing tools with sub-categories coordinated with project categories, L10n QA tools, L10n repo/build tools, & L10n PM tools (e.g., dashboards).

Projects directories - Q4 2011

There is an absense of direction for how to localize the unique projects contained within the Mozilla project itself. Here are some ideas on how to address this:

Idea #1:

For the WikiMo, will be high-level PM processes on where categorical projects fit within the overall process. Most commonly used tools will be noted as part of high-level view. Proposed categories: product & web

For the MDN, projects to be organized by category and categories are determined by tool type. Since so much of what a localizer contributes is based on the tools they are using, it is important to blend the two directories and their tutorials as much as possible. By delineating categories based on groupings of tools, this will help to present the notion that the project the localizer selects to participate in will limit their tools options and vice-versa. Documentation for MDN will be technical tutorials on how projects from each category are localized. Most commonly used tools will be added to the tutorials to display preferences. May be best to separate the Create a new localization page into multiple pages and have one page per project category. Proposed categories: product, web, add-ons

Social Media

Mozilla l10n Blog

https://etherpad.mozilla.org/l10n-socialmedia

Release plan: https://etherpad.mozilla.org/l10n-socialmedia-releases

Mozilla l10n Podcast

https://etherpad.mozilla.org/l10n-socialmedia

Release plan: https://etherpad.mozilla.org/l10n-socialmedia-releases

Mozilla l10n Twitter Feed

https://etherpad.mozilla.org/l10n-socialmedia

Release plan: https://etherpad.mozilla.org/l10n-socialmedia-releases


Presentations