Adding context to the .po files on AMO has been one of our challenges since
we started localizing the site. The solution we decided to use, place
holder strings, is non-standard and can be difficult to use for someone that
is used to how gettext normally works.
I've been the lead of the AMO 3.4.x
development release cycles which have been going on for about 8 weeks. During
that time we've been a little more structured with our release schedule. The
general plan has been a code freeze every other Monday at midnight and a push to
production the following Thursday. This gives us roughly ten days of coding and
two days of QA and L10n for each push. It's a compromise but it means
that we're never too far away from bug fixes and new features. The short turn
around cycle also means there aren't dramatic changes which lead to confusion
and panic (I'm looking at you mozillaZine ;) ).
We're planning several sessions at the
upcoming Firefox summit including one specifically about AMO and L10n in which we hope to connect with localizers and
start looking at some of the pain points of localizing AMO. With that in mind
I've been collecting topic ideas and I'd like to hear any others you have. On
my list so far:
The webdev and L10n-drivers teams have been
talking about implementing an online localization tool for a few months and I’m
happy to report that a plan is progressing. Seth Bindernagel has been giving updates
about the planning process and the direction we’re going in. Our planning
decisions will probably come up but my focus here will be on the actual
implementation of the tool.