[sldev] Translations
Soft Linden
soft at lindenlab.com
Fri Jul 27 09:23:14 PDT 2007
On 7/27/07, Nicholaz Beresford <nicholaz at blueflash.cc> wrote:
> Daniel Nylander wrote:
> > Yes, I submitted that bugreport. Since I don't know if I have done
> > everything correct, I'm not sure how to proceed.
>
> Oh, I guess you've seen it, but if not, check this post on their blog.
> http://blog.secondlife.com/2007/07/26/the-jira-bug-triage-lowdown-a-recap-of-the-oldies-and-introducing-internationalization/#comments
>
> If you have the time, go to the meeting and pester Iridium Linden
> about the issue.
Please please consider doing this!
Current policy is that we only accept patches against languages that
are already supported - some of the language files will carry an
annotation to this effect in a coming release to avoid anyone
embarking on work that may not get used. The problem is that
maintaining translations involves a lot of ongoing QA time, and right
now we simply don't have the resources to support that.
Two things:
- If any of you have ideas on how we can better handle translation,
especially by migrating to existing open source tools or lending
expertise from past translation efforts, the triage would be a great
place to start a discussion. If we can lower overhead, I'd hope we
could get more languages in sooner.
- More experienced QA engineers would help too! If any of you love
Second Life and want a job in QA, or have friends with testing
experience who do... having a couple extra languages under the belt
would be a huge bonus, possibly sweetening the pot enough to warrant
avoiding relocation. There's information about our QA processes at the
QA portal... having some of that knowledge and being able to speak to
related experience would be helpful if applying:
https://wiki.secondlife.com/wiki/QA_Portal
As for actually applying, there's information on lindenlab.com. A
recognizable name from sldev or office hours really helps here. Don't
be afraid to drop the names of Lindens with whom you've established a
good rapport through past contributions. That can help squeeze you
through HR filters. :)
More information about the SLDev
mailing list