Simplify localization team renewals #298

0ko commented 2025年06月14日 06:09:42 +02:00

Localization is the largest team with formal applications, so the applications can cause significant bureaucratic overhead. As past shows, people almost always forget to reapply to it unless someone asks them to (#229, #246), even if they stick around.

It is also an overhead from translator standpoint. If someone translates many projects, complexity of participating in Forgejo translation likely stands out because of these renewals.

Proposal

Let admins of the localization team decide to renew memberships of non-admin team members.

Such decision can be made if:

• there was any activity from this member recently (i.e. in the past 6 months)
• there were no objections or no uncertainty around changes made by this member

Such decision can be made like so:

• a new issue in this repo created by an admin, which lists (and mentions) all members it proposes to renew. Optionally it can list (mention) people whose membership expires soon but it was decided to not do the simplified renewal due to some factors like the ones listed above, and propose them to create a renewal manually.
• it lasts for two weeks, and then renewal happens
• TEAMS entries can be updated like so:
  • keep the old application
  • add (renewed in #N) and link to the issue

Advantages

Translators are not bothered by complex renewal process. Responsible people spend less time on housekeeping.

Localization is the [largest](https://codeberg.org/forgejo/governance/src/commit/237176cd875089375efe3b412d735a4f7e6944c7/TEAMS.md#localization) team with formal applications, so the applications can cause significant bureaucratic overhead. As past shows, people almost always forget to reapply to it unless someone asks them to (https://codeberg.org/forgejo/governance/issues/229, https://codeberg.org/forgejo/governance/issues/246), even if they stick around. It is also an overhead from translator standpoint. If someone translates many projects, complexity of participating in Forgejo translation likely stands out because of these renewals. ## Proposal Let admins of the localization team decide to renew memberships of non-admin team members. Such decision can be made if: * there was any activity from this member recently (i.e. in the past 6 months) * there were no objections or no uncertainty around changes made by this member Such decision can be made like so: * a new issue in this repo created by an admin, which lists (and mentions) all members it proposes to renew. Optionally it can list (mention) people whose membership expires soon but it was decided to not do the simplified renewal due to some factors like the ones listed above, and propose them to create a renewal manually. * it lasts for two weeks, and then renewal happens * TEAMS entries can be updated like so: * keep the old application * add `(renewed in #N)` and link to the issue ## Advantages Translators are not bothered by complex renewal process. Responsible people spend less time on housekeeping.

earl-warren commented 2025年06月14日 08:12:31 +02:00

This is a sensible thing to do.

The membership of the contributors team could be managed in the same way, by members of the merges team. The relationship between the two teams is similar:

• There are a few mergers only
• There are many contributors

The difference is that there is no application / election process for contributors at the moment and therefore no overhead at all. This has never caused any problem when a member was added. But that may be a surprise and trigger negative reactions when someone is removed and it should be documented instead of not.

I'll propose to amend the contributors team description accordingly.

This is a sensible thing to do. The membership of the [contributors team](https://codeberg.org/forgejo/governance/src/branch/main/TEAMS.md#contributors) could be managed in the same way, by members of the [merges team](https://codeberg.org/org/forgejo/teams/mergers). The relationship between the two teams is similar: - There are a few mergers only - There are many contributors The difference is that there is no application / election process for contributors at the moment and therefore no overhead at all. This has never caused any problem when a member was added. But that may be a surprise and trigger negative reactions when someone is removed and it should be documented instead of not. I'll propose to amend the contributors team description accordingly.

0ko commented 2025年06月15日 11:16:52 +02:00

There are too few expiring applications to mass-renew at the moment. I've worked for a bit on a template for this renewal process.

> [!NOTE]
> The [simplified renewal proposal](https://codeberg.org/forgejo/governance/issues/298) was not accepted yet, but by the time this issue will be acceptable it might be.
> [!NOTE]
> This issue can be used as a template for further #298-style renewals.
## Summary for translators
Memberships of any team in Forgejo normally last for a year after the application has been accepted. To decrease overhead, admins of the localization team can renew memberships, so you don't have to create a new application every year. This renewal doesn't obligate you to participate in translations and you can resign at any time.
## Summary for everyone
This issue proposes membership renewal of the following localization team members:
* li
* li
* li
_Insert decision making, objections and two weeks_.

There are too few expiring applications to mass-renew at the moment. I've worked for a bit on a template for this renewal process. ``` > [!NOTE] > The [simplified renewal proposal](https://codeberg.org/forgejo/governance/issues/298) was not accepted yet, but by the time this issue will be acceptable it might be. > [!NOTE] > This issue can be used as a template for further #298-style renewals. ## Summary for translators Memberships of any team in Forgejo normally last for a year after the application has been accepted. To decrease overhead, admins of the localization team can renew memberships, so you don't have to create a new application every year. This renewal doesn't obligate you to participate in translations and you can resign at any time. ## Summary for everyone This issue proposes membership renewal of the following localization team members: * li * li * li _Insert decision making, objections and two weeks_. ```

earl-warren commented 2025年06月16日 07:59:40 +02:00

s/admins of localization/admins of the localization/?

s/admins of localization/admins of the localization/?

0ko commented 2025年06月30日 14:36:44 +02:00

The proposal got no objections but general support in form of reactions. I consider it as accepted and will use when needed.

May worth mentioning it in the monthly report.

The proposal got no objections but general support in form of reactions. I consider it as accepted and will use when needed. May worth mentioning it in the [monthly report](https://codeberg.org/forgejo/website/issues/591).

Beowulf commented 2025年06月30日 16:52:32 +02:00

@0ko will you open a PR adding this to the Admins section of https://codeberg.org/forgejo/governance/src/branch/main/TEAMS.md#localization ?

@0ko will you open a PR adding this to the Admins section of https://codeberg.org/forgejo/governance/src/branch/main/TEAMS.md#localization ?

0ko commented 2025年06月30日 17:02:42 +02:00

Actually, yes, should do that. 👍

Actually, yes, should do that. 👍