1488256 - Add mozilla/activate.mozilla.community to Pontoon

Status: RESOLVED FIXED

(Localization Infrastructure and Tools :: Administration / Setup, task)

Description

[Michael Kohler [:mkohler]]

Project Name: Mozilla Activate
Repo: https://github.com/mozilla/activate.mozilla.community
Locales files: https://github.com/mozilla/activate.mozilla.community/tree/master/public/locales
Website URL: http://activate.mozilla.community/

Requested locales:
* es
* fr-FR
* bd-bn
* id
* pt-BR
* hi
* it-IT

Questions:
1) Does Pontoon create the necessary folders by itself or should I do this for the requested languages?
2) Is it ok to have the locales folder within public/? If not, I'm happy to move it to the root of the repo

Also, would it be possible to add me and Konstantina to the admin list so we can enable new locales ourselves?

Is there anything else you need? Happy to help!

Thanks in advance!

Comment 1

[Francesco Lodolo [:flod]]

Not sure if this should be moved to Pontoon, CCing a few folks in case.

From a quick look: over 450 strings and 7000 words, this is not a small project.

Comment 2

[Francesco Lodolo [:flod]]

Side note: please exclude Italian from the initial list. I've double checked with Daniele and the rest of the localization team, and we're already struggling to keep up with the amount of requests for existing projects. 

In case things will change (more volunteers and time) we'll ask for the locale to be added.

Comment 3

[Jeff Beatty [:gueroJeff]]

Thanks Michael. Pontoon isn't meant to be a self-service tool. In other words, we lack a tier of l10n service where we give people outside of the l10n-drivers admin rights and allow them to manage their own projects. If we made you and Konstantina admins, those rights would extend to every project in Pontoon and not be limited to this one.

Comment 4

[Jeff Beatty [:gueroJeff]]

Also, I'm flagging Peiying on this, as she manages Web l10n projects.

Comment 5

[Peiying Mo [:CocoMo]]

> 
> Questions:
> 1) Does Pontoon create the necessary folders by itself or should I do this
> for the requested languages?

@Matjaz, Is this a one way street that the locale needs to be set up in the repo before it syncs up in Pontoon? I attempted to set it up and nothing showed up on staging. 

> 2) Is it ok to have the locales folder within public/? If not, I'm happy to
> move it to the root of the repo

AMO Linter is set up this way and it works: https://github.com/mozilla/addons-linter/tree/master/locale

Comment 6

[Peiying Mo [:CocoMo]]

@mkohler, please provide me the following:
- Project description: what this project/product is about
- Dev and staging servers URL, whichever is applicable
- Development cycle (sprint or frequency the project follows): 
1). When new strings are pushed for localization 
2). When localized content is pushed to production? 
3). If corrections are made in localization, how soon can it be verified on staging?
4). Can localizers request to add locales outside of what you listed above.
- Priority of this project, is this deadline driven or whenever the localization is complete for the locale?

 
It's ok if you don't have all the info now.

Comment 7

[Matjaz Horvat [:mathjazz]]

(In reply to Peiying Mo [:CocoMo] from comment #5)
> @Matjaz, Is this a one way street that the locale needs to be set up in the
> repo before it syncs up in Pontoon? I attempted to set it up and nothing
> showed up on staging. 

The reason nothing showed up is because first sync failed due to bad configuration. The repository URLs were wrong.

I've fixed them, please see:
https://mozilla-pontoon-staging.herokuapp.com/admin/projects/mozilla-activate/

The project syncs properly now:
https://mozilla-pontoon-staging.herokuapp.com/projects/mozilla-activate/

Comment 8

[Michael Kohler [:mkohler]]

(In reply to Peiying Mo [:CocoMo] from comment #6)
> @mkohler, please provide me the following:
> - Project description: what this project/product is about

@Lucy: do you want to provide this description here?

> - Dev and staging servers URL, whichever is applicable

Right now we directly deploy from gh-pages. My idea was to create a script that runs on every commit to master to deploy to gh-pages. This doesn't give much room for a staging env, though if required by l10n, we could certainly do something around that.

> - Development cycle (sprint or frequency the project follows): 
> 1). When new strings are pushed for localization 

Once they are integrated in the code.

> 2). When localized content is pushed to production? 

See above, this currently would be on every push to master.

> 3). If corrections are made in localization, how soon can it be verified on
> staging?

See above, this would currently be directly in production.

> 4). Can localizers request to add locales outside of what you listed above.

Yes, the process is documented here: https://github.com/mozilla/activate.mozilla.community#submit-a-new-localization

> - Priority of this project, is this deadline driven or whenever the
> localization is complete for the locale?

Whenever complete, I've written >95% in the README. Would you advise to put this to 100%?

Comment 9

[Peiying Mo [:CocoMo]]

@Matjaz, thank you. I missed prefix "/mozilla" in the link. 

@mkohler, the project and the locales are enabled. Just to make sure you asked for international "es".

Comment 10

[Peiying Mo [:CocoMo]]

(In reply to Michael Kohler [:mkohler] from comment #8)
> (In reply to Peiying Mo [:CocoMo] from comment #6)
> > @mkohler, please provide me the following:
> > - Project description: what this project/product is about
> 
> @Lucy: do you want to provide this description here?
> 
> > - Dev and staging servers URL, whichever is applicable
> 
> Right now we directly deploy from gh-pages. My idea was to create a script
> that runs on every commit to master to deploy to gh-pages. This doesn't give
> much room for a staging env, though if required by l10n, we could certainly
> do something around that.

Will push to production be daily or immediately after a sync when there is a localization change? Pontoon and GitHub can sync every 20 minutes (not sure if this is by default of something you have to configure)
> 
> > - Priority of this project, is this deadline driven or whenever the
> > localization is complete for the locale?
> 
> Whenever complete, I've written >95% in the README. Would you advise to put
> this to 100%?
I think 95% is fine. This assumes you have code change every so often. New strings, revised strings will affect the locales that are already on production, given the production push process you have mentioned. 

https://pontoon.mozilla.org/projects/mozilla-activate/

Comment 11

[Michael Kohler [:mkohler]]

(In reply to Peiying Mo [:CocoMo] from comment #9)
> @mkohler, the project and the locales are enabled. Just to make sure you
> asked for international "es".

Correct.

(In reply to Peiying Mo [:CocoMo] from comment #10)
> > > - Dev and staging servers URL, whichever is applicable
> > 
> > Right now we directly deploy from gh-pages. My idea was to create a script
> > that runs on every commit to master to deploy to gh-pages. This doesn't give
> > much room for a staging env, though if required by l10n, we could certainly
> > do something around that.
> 
> Will push to production be daily or immediately after a sync when there is a
> localization change? Pontoon and GitHub can sync every 20 minutes (not sure
> if this is by default of something you have to configure)

It's not set up yet, as we haven't pushed the new version out yet (coming very soon). But then the idea is to directly push it out to production whenever Pontoon syncs to the master branch.

Thanks a lot! Looks good to me!

Comment 12

[Francesco Lodolo [:flod]]

(In reply to Michael Kohler [:mkohler] from comment #11)
> It's not set up yet, as we haven't pushed the new version out yet (coming
> very soon). But then the idea is to directly push it out to production
> whenever Pontoon syncs to the master branch.

Note that you're going to end up with multiple pushes within a few seconds, depending on the number of locales. Maybe it would be worth building gh-pages from a different branch, periodically updated from master.

Comment 13

[Michael Kohler [:mkohler]]

(In reply to Francesco Lodolo [:flod] from comment #12)
> (In reply to Michael Kohler [:mkohler] from comment #11)
> > It's not set up yet, as we haven't pushed the new version out yet (coming
> > very soon). But then the idea is to directly push it out to production
> > whenever Pontoon syncs to the master branch.
> 
> Note that you're going to end up with multiple pushes within a few seconds,
> depending on the number of locales. Maybe it would be worth building
> gh-pages from a different branch, periodically updated from master.

Oh, that's good input. Thanks! That sounds like the better approach then. :)