Change 959998 had a related patch set uploaded (by Abijeet Patro; author: Abijeet Patro):

[mediawiki/extensions/Maintenance@master] createExtensionTable.php: Add translate_translatable_bundles

https://gerrit.wikimedia.org/r/959998

Change 959998 abandoned by Abijeet Patro:

[mediawiki/extensions/Maintenance@master] createExtensionTable.php: Add translate_translatable_bundles

Reason:

Wrong repo

https://gerrit.wikimedia.org/r/959998

Change 959999 had a related patch set uploaded (by Abijeet Patro; author: Abijeet Patro):

[mediawiki/extensions/WikimediaMaintenance@master] createExtensionTable.php: Add translate_translatable_bundles

https://gerrit.wikimedia.org/r/959999

@Albertoleoncio

1. The project is missing the message documentation (qqq.json file). You can read more about it here: https://translatewiki.net/wiki/Translating:Localisation_for_developers#Message_documentation and you can see an example of how this file looks here: https://github.com/toolforge/video2commons/blob/master/video2commons/frontend/i18n/qqq.json
2. The https://github.com/translatewiki GitHub user account will need access to commit to the repository so that we can push translations from translatewiki to GitHub.

1. The project is missing the message documentation (qqq.json file). You can read more about it here: https://translatewiki.net/wiki/Translating:Localisation_for_developers#Message_documentation and you can see an example of how this file looks here: https://github.com/toolforge/video2commons/blob/master/video2commons/frontend/i18n/qqq.json

I never did documentation for each variable. Would it be possible to do it directly on TranslateWiki?

2. The https://github.com/translatewiki GitHub user account will need access to commit to the repository so that we can push translations from translatewiki to GitHub.

Done.

In T347244#9197492, @Albertoleoncio wrote:

1. The project is missing the message documentation (qqq.json file). You can read more about it here: https://translatewiki.net/wiki/Translating:Localisation_for_developers#Message_documentation and you can see an example of how this file looks here: https://github.com/toolforge/video2commons/blob/master/video2commons/frontend/i18n/qqq.json

I never did documentation for each variable. Would it be possible to do it directly on TranslateWiki?

It is possible to do it on translatewiki.net after the project is added.

In T347244#9197492, @Albertoleoncio wrote:

2. The https://github.com/translatewiki GitHub user account will need access to commit to the repository so that we can push translations from translatewiki to GitHub.

Done.

Thanks, accepted.

Change 961330 had a related patch set uploaded (by Wangombe; author: Wangombe):

[translatewiki@master] Add Wikiscore project

https://gerrit.wikimedia.org/r/961330

Change 961330 merged by jenkins-bot:

[translatewiki@master] Add WikiScore project

https://gerrit.wikimedia.org/r/961330

WikiScore is now available for translation on translatewiki.net: https://translatewiki.net/wiki/Translating:WikiScore

Translations will be exported out later today

@Albertoleoncio, you can add message documentation here:

@abi_ I saw that the translations were already published today on GitHub, but not to WikiScore. Something went wrong?

In T347244#9217579, @Albertoleoncio wrote:

@abi_ I saw that the translations were already published today on GitHub, but not to WikiScore. Something went wrong?

I manually pushed out the changes today: https://github.com/WikiMovimentoBrasil/wikiscore/commit/ea3886bf0a363be9bffbdd2f703f80cb1d8f8b9b

I'd still like to monitor to see if the automatic push works. We should be pushing out translations again on Thursday.

Em T347244#9219851, @abi_ escreveu:

I'd still like to monitor to see if the automatic push works. We should be pushing out translations again on Thursday.

Well... It didn't. Is there any way I can activate it manually? Or can I just download the JSONs?
Another thing: I had published the Brazilian Portuguese translations as "pt", but I noticed that they had started translating as "pt-br". To avoid duplication, I renamed the file on GitHub but the change was not replicated on TranslateWiki.

In T347244#9231090, @Albertoleoncio wrote:

Well... It didn't. Is there any way I can activate it manually? Or can I just download the JSONs?

This happened there were some changes made to source strings (English) that need to be manually reviewed by administrators. The system blocks exports until these have been reviewed. I've now reviewed them, and translations should be exported out on Thursday.

In T347244#9231090, @Albertoleoncio wrote:

Another thing: I had published the Brazilian Portuguese translations as "pt", but I noticed that they had started translating as "pt-br". To avoid duplication, I renamed the file on GitHub but the change was not replicated on TranslateWiki.

This should be now imported. This is again a by product of not reviewing the incoming translations changes from the GitHub repository.

In T347244#9236236, @abi_ wrote:

In T347244#9231090, @Albertoleoncio wrote:

Well... It didn't. Is there any way I can activate it manually? Or can I just download the JSONs?

This happened there were some changes made to source strings (English) that need to be manually reviewed by administrators. The system blocks exports until these have been reviewed. I've now reviewed them, and translations should be exported out on Thursday.

We again had changes pending for review from the project due to changes to the source language so exports were skipped again. I'll try to review changes before the exports next Monday.

Em T347244#9246146, @abi_ escreveu:

In T347244#9236236, @abi_ wrote:

In T347244#9231090, @Albertoleoncio wrote:

Well... It didn't. Is there any way I can activate it manually? Or can I just download the JSONs?

This happened there were some changes made to source strings (English) that need to be manually reviewed by administrators. The system blocks exports until these have been reviewed. I've now reviewed them, and translations should be exported out on Thursday.

We again had changes pending for review from the project due to changes to the source language so exports were skipped again. I'll try to review changes before the exports next Monday.

I'm still trying to understand the bot's workflow. Exactly what prevents automatic export? Does any change to the source JSON other than the addition of new snippets, or even the addition of new snippets prevent export?

In T347244#9246640, @Albertoleoncio wrote:

Em T347244#9246146, @abi_ escreveu:

In T347244#9236236, @abi_ wrote:

In T347244#9231090, @Albertoleoncio wrote:

Well... It didn't. Is there any way I can activate it manually? Or can I just download the JSONs?

This happened there were some changes made to source strings (English) that need to be manually reviewed by administrators. The system blocks exports until these have been reviewed. I've now reviewed them, and translations should be exported out on Thursday.

We again had changes pending for review from the project due to changes to the source language so exports were skipped again. I'll try to review changes before the exports next Monday.

Does any change to the source JSON other than the addition of new snippets, or even the addition of new snippets prevent export?

Yes in a way, it requires a manual review of the change from the translation administrators. If we don't do that before the automated exports run exports for that project will be skipped.

Incoming changes were reviewed on the 11th Oct, but we did not review the incoming changes on 12th Oct which is when this change was made. Its a miss on our part.