Adding a "Localization" team #61

earl-warren commented 2024年01月20日 20:51:18 +01:00

Forgejo needs to bootstrap a localization team to ensure the existing translations are updated independently of the work done on the current proprietary platform. It is a large undertaking which requires many participants. It is described in more details in a separate issue.

For translations to be reliable, there need to be at least one person capable of reviewing the translation in all supported languages. This person will be trusted by the Forgejo community to verify the translations are accurate and that the quality is acceptable. For this reason, they need to apply to be a member of a team and shortly explain why they should be trusted with this responsibility.

Contrary to other teams, localization members will be responsible for delegating permissions, in weblate. It would be too heavy to require a casual weblate contributor to go through this process just to translate a few strings. Instead, their contribution would be "Accepted" by a member of the localization team, which is the equivalent of merging a pull request in the weblate parlance.

Thoughts?

Forgejo needs to bootstrap a localization team to ensure the existing translations are updated independently of the work done on the current proprietary platform. It is a large undertaking which requires many participants. It is described in more details [in a separate issue](https://codeberg.org/forgejo/discussions/issues/104). For translations to be reliable, there need to be at least one person capable of reviewing the translation in all supported languages. This person will be trusted by the Forgejo community to verify the translations are accurate and that the quality is acceptable. For this reason, they need to apply to be a member of a team and shortly explain why they should be trusted with this responsibility. Contrary to other teams, localization members will be responsible for delegating permissions, in weblate. It would be too heavy to require a casual weblate contributor to go through this process just to translate a few strings. Instead, their contribution would be "Accepted" by a member of the localization team, which is the equivalent of merging a pull request in the weblate parlance. Thoughts?

0ko commented 2024年01月21日 06:49:47 +01:00

Contrary to other teams, localization members will be responsible for delegating permissions, in weblate. It would be too heavy to require a casual weblate contributor to go through this process just to translate a few strings. Instead, their contribution would be "Approved" by a member of the localization team, which is the equivalent of merging a pull request in the weblate parlance.

Do you want the translation be closed with open suggestions or use string reviewing/approval mechanism? With open suggestions, applying the suggestion is called "Accept" in the UI. Just want to clarify.

> Contrary to other teams, localization members will be responsible for delegating permissions, in weblate. It would be too heavy to require a casual weblate contributor to go through this process just to translate a few strings. Instead, their contribution would be "Approved" by a member of the localization team, which is the equivalent of merging a pull request in the weblate parlance. Do you want the translation be closed with open suggestions or use string reviewing/approval mechanism? With open suggestions, applying the suggestion is called "Accept" in the UI. Just want to clarify.

earl-warren commented 2024年01月21日 13:25:32 +01:00

@0ko good catch, fixed.

@0ko good catch, fixed.

earl-warren commented 2024年01月21日 13:33:57 +01:00

@Werenter does that look ok to you?

@Werenter does that look ok to you?

Werenter commented 2024年01月21日 14:26:34 +01:00

I think that closed translations with suggestions is better because open translations is very vulnerable to trolls and spamers, moderators can't review every translation fast and bad translations can get into upstream.

I think that closed translations with suggestions is better because open translations is very vulnerable to trolls and spamers, moderators can't review every translation fast and bad translations can get into upstream.

earl-warren commented 2024年01月21日 16:12:00 +01:00

Could you please link to the weblate documetation related to "closed translations"?

Could you please link to the weblate documetation related to "closed translations"?

0ko commented 2024年01月21日 16:57:22 +01:00

"Closed" just means you can't directly edit strings - only suggest (in this case its about non-members). I think people call it like that because its equivalent to when the translation is automatically closed due to some error like Could not push to upstream, which is a bit common. A related link would be Peer review Workflow but its not that great at explaining this. There's also useful information about accepting suggestions in Suggestion voting but voting doesn't really make sense now for Forgejo translations and I haven't really seen it anywhere.

"Closed" just means you can't directly edit strings - only suggest (in this case its about non-members). I think people call it like that because its equivalent to when the translation is automatically closed due to some error like `Could not push to upstream`, which is a bit common. A related link would be [Peer review Workflow](https://docs.weblate.org/en/latest/workflows.html#peer-review) but its not that great at explaining this. There's also useful information about accepting suggestions in [Suggestion voting](https://docs.weblate.org/en/latest/admin/translating.html#suggestion-voting) but voting doesn't really make sense now for Forgejo translations and I haven't really seen it anywhere.

Werenter commented 2024年01月21日 18:59:26 +01:00

@earl-warren I did't read the docs. But i found it in the settings:

https://translate.codeberg.org/settings/forgejo/forgejo-test/#translation

изображение

Translate to English:

• Voting on a proposal

Users can only vote for proposals, but cannot translate directly.

@earl-warren I did't read the docs. But i found it in the settings: https://translate.codeberg.org/settings/forgejo/forgejo-test/#translation  Translate to English: - [ ] Voting on a proposal Users can only vote for proposals, but cannot translate directly.

earl-warren commented 2024年01月21日 20:10:44 +01:00

That's useful information to document the translation workflow. Since you're much more familiar with that, would you like to propose a pull request to update the developer documentation with this workflow?

That would be a new page here, visible in the developer guide and likely similar in spirit to the development workflow. It can be very short, a bullet list with links even.

That's useful information to document the translation workflow. Since you're much more familiar with that, would you like to propose a pull request to update the developer documentation with this workflow? That would be a new page [here](https://codeberg.org/forgejo/docs/src/branch/next/docs/developer), visible [in the developer guide](https://forgejo.org/docs/v1.21/developer/) and likely similar in spirit to [the development workflow](https://forgejo.org/docs/v1.21/developer/workflow/). It can be very short, a bullet list with links even.

earl-warren commented 2024年01月28日 11:33:54 +01:00

There was no concern expressed in a week, the team started organizing informally at forgejo/discussions#104.

There was no concern expressed in a week, the team started organizing informally at https://codeberg.org/forgejo/discussions/issues/104.