Undocumented teams in TEAMS.md #57

oliverpool commented 2024年01月09日 17:32:59 +01:00

I just realized that some teams are not properly documented:

Unlisted:

• Owners Have access to secrets
• Secrets-Keeper Trusted with the credentials of all Forgejo resources
• Admins Administrators of all repositories (except secrets)
• Well-being (not used anymore, according to @Gusted) - deleted on 2024年01月26日

Incomplete:

• GitHub owners (addressed in #56)
• UserResearch (@delvh seems missing from the TEAMS.md)

Looks OK:

• Contributors
• Mergers (may be updated after #54)
• Releases
• Security

The Owner team should be documented.

I think the Secrets-Keeper team can be removed from codeberg (to have access to the secrets, one must belong to the Owners and share a public GPG key), but the users should be documented/elected somehow (maybe with a notice along the Owner team membership).

The Admins team (and its difference from the Owners team) should be documented as well.

I just realized that some [teams](https://codeberg.org/org/forgejo/teams) are not properly documented: Unlisted: - Owners `Have access to secrets` - Secrets-Keeper `Trusted with the credentials of all Forgejo resources` - Admins `Administrators of all repositories (except secrets) ` - Well-being (not used anymore, according to @Gusted) - deleted on 2024年01月26日 Incomplete: - GitHub owners (addressed in #56) - UserResearch (@delvh seems missing from the TEAMS.md) Looks OK: - Contributors - Mergers (may be updated after #54) - Releases - Security The `Owner` team should be documented. I think the `Secrets-Keeper` team can be removed from codeberg (to have access to the secrets, one must belong to the `Owners` and [share a public GPG key](https://forgejo.org/docs/latest/developer/secrets/)), but the users should be documented/elected somehow (maybe with a notice along the `Owner` team membership). The `Admins` team (and its difference from the `Owners` team) should be documented as well.

Gusted commented 2024年01月09日 18:10:15 +01:00

Well-being has not been used in the last 6 months. It's fine to have it removed. Moderation has taken over the task as far as I'm aware.

Well-being has not been used in the last 6 months. It's fine to have it removed. Moderation has taken over the task as far as I'm aware.

earl-warren commented 2024年06月07日 23:53:25 +02:00

• UserResearch (@delvh seems missing from the TEAMS.md)

They were removed. Given they are acting as a member of the TOC in Gitea, there is little chance they will participate in anything related to Forgejo in the next year.

> - UserResearch (@delvh seems missing from the TEAMS.md) They were removed. Given they are acting as a member of the TOC in Gitea, there is little chance they will participate in anything related to Forgejo in the next year.

delvh commented 2024年06月08日 19:36:22 +02:00

Probably true, unfortunately

Probably true, unfortunately

n0toose commented 2024年06月09日 08:43:25 +02:00

Probably true, unfortunately

Always welcome to change your mind. =)

> Probably true, unfortunately Always welcome to change your mind. =)

viceice commented 2024年06月14日 13:53:37 +02:00

Another missing group is the forgejo-helm¹ owner group, how should we handle that?

Current members: @earl-warren @viceice

Another missing group is the `forgejo-helm`[^1] owner group, how should we handle that? Current members: @earl-warren @viceice [^1]: https://code.forgejo.org/forgejo-helm

earl-warren commented 2024年06月14日 14:33:56 +02:00

The groups documented are those found in the https://codeberg.org/forgejo/ organization. In code.forgejo.org things are somewhat easier because there can be one organization per team, or even multipe ones. Since the Helm team already manages the following organizations:

• https://code.forgejo.org/forgejo-helm/
• https://code.forgejo.org/helm/
• https://code.forgejo.org/azure

I propose they are listed in the description of the Helm team so that new members know they will get access to those when they become a member.

Does that sound right?

The groups documented are those found in the https://codeberg.org/forgejo/ organization. In code.forgejo.org things are somewhat easier because there can be one organization per team, or even multipe ones. Since the Helm team already manages the following organizations: * https://code.forgejo.org/forgejo-helm/ * https://code.forgejo.org/helm/ * https://code.forgejo.org/azure I propose they are listed in the description of the Helm team so that new members know they will get access to those when they become a member. Does that sound right?

earl-warren commented 2024年07月24日 13:34:48 +02:00

I think this issue is mostly complete. Maybe the missing bits (there are a handful) can be addressed in individual, short lived issues?

I think this issue is mostly complete. Maybe the missing bits (there are a handful) can be addressed in individual, short lived issues?

viceice commented 2024年07月24日 13:46:41 +02:00

The groups documented are those found in the https://codeberg.org/forgejo/ organization. In code.forgejo.org things are somewhat easier because there can be one organization per team, or even multipe ones. Since the Helm team already manages the following organizations:

• https://code.forgejo.org/forgejo-helm/
• https://code.forgejo.org/helm/
• https://code.forgejo.org/azure

I propose they are listed in the description of the Helm team so that new members know they will get access to those when they become a member.

Does that sound right?

There is no team created yet, but we can create one.
Not sure about the helm and azure orgs, they are just to mirror actions 🤷‍♂️

> The groups documented are those found in the https://codeberg.org/forgejo/ organization. In code.forgejo.org things are somewhat easier because there can be one organization per team, or even multipe ones. Since the Helm team already manages the following organizations: > > * https://code.forgejo.org/forgejo-helm/ > * https://code.forgejo.org/helm/ > * https://code.forgejo.org/azure > > I propose they are listed in the description of the Helm team so that new members know they will get access to those when they become a member. > > Does that sound right? There is no team created yet, but we can create one. Not sure about the `helm` and `azure` orgs, they are just to mirror actions 🤷‍♂️

viceice commented 2024年07月24日 14:30:46 +02:00

btw: i added @earl-warren as owner to:

• https://code.forgejo.org/helm
• https://code.forgejo.org/azure

btw: i added @earl-warren as owner to: - https://code.forgejo.org/helm - https://code.forgejo.org/azure

earl-warren commented 2025年01月17日 10:29:15 +01:00

This issue is old and outdated enough that it no longer helps. It still has valuable information I suspect but the time needed to sort it out is probably longer than making a new tour of what is around. If you find something of interest, can I suggest to open an actionable issue focused on a smaller scope?

If you have a different opinion, please re-open.

This issue is old and outdated enough that it no longer helps. It still has valuable information I suspect but the time needed to sort it out is probably longer than making a new tour of what is around. If you find something of interest, can I suggest to open an actionable issue focused on a smaller scope? If you have a different opinion, please re-open.