Re: Calling Experienced Localizers - Support the Add-ons Localization Campaign!

Am 06.06.18 um 07:52 schrieb Onno Ekker:
> On Tue, Jun 5, 2018 at 8:35 PM, Ruben Martin <[email protected]> wrote:
> 
> 
> Also, if you want more add-ons to be localized, I think it would be a great
> step to allow add-on authors to add their add-on to Pontoon somehow, so
> localizers can translate the add-on there. Now they have to use another
> platform, like BabelZilla, CrowdIn or Transvision, where it is much harder
> to find localizers and localizers that are used to Pontoon may find it
> easier to localize everything in one place. It would maybe even become
> possible to download localizations for installed add-ons from a Mozilla
> server whenever a user changes locale, so add-on authors don't need to
> package all the locales and locales get updated quicker, without the need
> to repackage the add-on and release a new version.

Just picking this snippet:

We need some features in pontoon before we're able to do this:

Notably the feature of "have someone create a project", i.e., we need 
more granular permission systems for project managers. We'll likely do 
this by introducing a concept of "organizations". The exact details 
we'll need to figure out.

We'll also need to decide how we're doing translation memory, once we 
have a more diverse set of copyright holders on pontoon.

And we'll need something like a user dashboard, I think. Once you have 
more than a few dozen projects, the team dashboard doesn't help you in 
most cases.

Once we have that, we'll need to decide if our current instance will be 
one or more of the orgs, or if we'd rather have a separate instance for 
add-ons.

And we'll need better support for the actual message.json localization 
format.

Finding time on the roadmap for these has been proven hard so far, so 
they're on the back burner right now. In case you're like me, that's a 
kitchen-inspired wording, not a jet-engine one. I find that very confusing.

Axel