Build a backend service that maps every file or logical part of a connected codebase to a list of team members, weighted by percentage of participation.
The goal is to infer ownership and likely responders from git history so outages and incidents can be routed more accurately. Recent activity should carry more weight than older activity.
This should produce a topology that can answer questions like which members are most involved in a file, directory, or broader area of the codebase.
Depending on performance, the topology should likely be stored and incrementally updated rather than recomputed from scratch. A repository-oriented table or similar structure can be used to persist the mapping and refresh affected files on commits to the default branch.
This work should align with the team and member model defined in #12, so participation can be attached to the right members and teams.
Build a backend service that maps every file or logical part of a connected codebase to a list of team members, weighted by percentage of participation.
The goal is to infer ownership and likely responders from git history so outages and incidents can be routed more accurately. Recent activity should carry more weight than older activity.
This should produce a topology that can answer questions like which members are most involved in a file, directory, or broader area of the codebase.
Depending on performance, the topology should likely be stored and incrementally updated rather than recomputed from scratch. A repository-oriented table or similar structure can be used to persist the mapping and refresh affected files on commits to the default branch.
This work should align with the team and member model defined in #12, so participation can be attached to the right members and teams.