forgejo/governance
40
34
Fork
You've already forked governance
35

teams: i18n: remove jadedctrl and ledyba #388

Merged
0ko merged 1 commit from 0ko/i18n-2026-04-removals into main 2026年04月06日 09:40:44 +02:00 AGit
Owner
Copy link

This removes the following team members with expired memberships:

@jadedctrl
@ledyba

Both memberships were renewed in March 2025 per #229: #236, #233. But last translation activity from both members was in 2024:

NOTE: Weblate doesn't show activity for strings that were removed. Or in our case migrated from INI to JSON. However, looking through Git commits, the last merges co-authored were forgejo/forgejo#2588 for @jadedctrl and forgejo/forgejo#5355 for @ledyba.

This removal is simply meant to clean up old inactive memberships. Everyone removed will be welcomed back anytime they feel like they want to get back to active participation 🤗

This removes the following team members with expired memberships: @jadedctrl @ledyba Both memberships were renewed in March 2025 per https://codeberg.org/forgejo/governance/issues/229: https://codeberg.org/forgejo/governance/issues/236, https://codeberg.org/forgejo/governance/issues/233. But last translation activity from both members was in 2024: * https://translate.codeberg.org/user/jadedctrl/#changes * https://translate.codeberg.org/user/ledyba/#changes NOTE: Weblate doesn't show activity for strings that were removed. Or in our case migrated from INI to JSON. However, looking through Git commits, the last merges co-authored were https://codeberg.org/forgejo/forgejo/pulls/2588 for @jadedctrl and https://codeberg.org/forgejo/forgejo/pulls/5355 for @ledyba. This removal is simply meant to clean up old inactive memberships. Everyone removed will be welcomed back anytime they feel like they want to get back to active participation 🤗
Author
Owner
Copy link
Rel: https://codeberg.org/forgejo/governance/pulls/382#issuecomment-11939448, https://codeberg.org/forgejo/governance/issues/387#issuecomment-12689328
Author
Owner
Copy link

Removed both Weblate users from the team on CBT.

Removed both Weblate users from the team on CBT.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Collecting stakeholders
We're in a decision-making process, figuring out the relevant stakeholders and bringing them into the process
[Decision] Documenting and implementing
We finished a decision-making process, now documenting and/or implementing the decision
[Decision] Gathering advice
We're in a decision-making process, waiting for people to add their feedback
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
[Decision] Phrasing shared motive
We're in a decision-making process, phrasing the shared question/problem/issue we want to tackle
Membership
Process of appointing a person as a team member.
Moderation
Moderation actions in Forgejo spaces
Money
Accounting, day to day management of money
Scheduled chores
Tasks that need to be done at a scheduled date in the future (paying the bills, renewing certificates, etc.)
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
forgejo/governance!388
Reference in a new issue
forgejo/governance
No description provided.
Delete branch "0ko/i18n-2026-04-removals"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?