Reputation label assicated with organizations and repositories.

[AdamMajer]

Feature Description

When you have a forge, anyone can create anything. The issue is then what can users trust. For instances that want to manage this trust, there should be some label that indicates this.

Proposal here is to be able to have a "reputation label" or "reputation score" associated with a repository and/or organization. This would be Forge Owner (so admin) managed label that allows various organizations or repositories to have different tags.

In UI, this could be listed as a tag, similar to a tag next to repository when it's a SHA256 repository. In the Explore menu, we can then have a filter to limit visibility to specific "reputation label".

These labels are policy specific, so up to individual instance if they define them or not.

Screenshots

No response

[Ubayed-Bin-Sufian]

I tried to search for autogits repo and found there are lots of forks which i got confused at first. Below is an screenshot of gist of what i understood and i think implementing this feature would help the community. I have also successfully setup the local instance.

is there any guidelines you would like to suggest i can start so that i go step by step for the success of this feature?

[lunny]

We now have user badges in #36752. It might make sense to support assigning badges to organizations as well.

[bircni]

I think we also should have a discussion about badges overall because I am not really happy how I implemented it tbh
I don't see any real usability for supporting images

[eeyrjmr]

We now have user badges in #36752. It might make sense to support assigning badges to organizations as well.

Not to fork this discussion but yes the "user badges" might offer some additional capabilities... Say centralised TEAMS... as an org team access could depend on a "user badge" as means to indicate a cross-org capabilities.

Im being selfish on this one as my R&T instance has several orgs and then real-world teams (say Firmware, review) and its an overhead to add and remove on a per org/repo basis. NOTE: there is an issue on site-wide team management so ill end this point here

[lunny]

We now have user badges in #36752. It might make sense to support assigning badges to organizations as well.

Not to fork this discussion but yes the "user badges" might offer some additional capabilities... Say centralised TEAMS... as an org team access could depend on a "user badge" as means to indicate a cross-org capabilities.

Im being selfish on this one as my R&T instance has several orgs and then real-world teams (say Firmware, review) and its an overhead to add and remove on a per org/repo basis. NOTE: there is an issue on site-wide team management so ill end this point here

It seems #3642 will match your requirement.

[Ubayed-Bin-Sufian]

We now have user badges in #36752. It might make sense to support assigning badges to organizations as well.

Thank you for the reply. This PR would be a great for me to analyze it and understand the codebase and implement the feature.

after setting it up locally, i have found that while I assign the badges, the visibility is limited.

Screenshots

Badge assigned and visible to the user profile

Right now, i cannot see any visual cues whether the user has the badge assigned when i see from a admin/org pov.

Details

Image 1	Image 2

The only way i could see the badges with assigned users is through Site administration --> Badges --> Users with badges assigned

My Question:

1. is this the intended approach of the badges?
2. should we be expanding the badges feature to org and repo level?
3. should we focus on the goal as mentioned in Reputation label assicated with organizations and repositories. #36334 (comment)

[bircni]

Currently badges expose information about a user instance-wide.

The original implementation by @techknowlogick
#20607 introduced badges mainly as achievement badges.

I think this here mixes two different concepts:

• achievements (badges)
• reputation / trust / role signaling

Instead of extending badges further, it could make sense to introduce a separate concept: Reputation Labels.

Reputation labels could be assignable to:

• users
• repositories
• organizations

Each label would have:

• name
• color
• optional description

Examples:

• Trusted Contributor
• Maintainer
• Security Team
• Verified Organization

Assignment could be:

• manual by admins/moderators
• optional application workflow
• or rule-based in the future

I also considered like an automatic Admin badge, but publicly exposing admins might be bad for public instances, so this should remain optional/configurable.

Separating achievements from reputation would keep the model cleaner and more flexible.

[AdamMajer]

I really like the Reputation Labels idea (considering the Issue title 😆). But at same time, it would be nicer to repurpose current concepts already implemented and to generalize them instead of adding completely new ones. Here I'm thinking from DB schema point of view. This needs further investigation how to proceed.