chore: EX-1155: ownership files update #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Approximately 685 entities currently belong to orphaned groups, resulting in invalid ownership for 47.3% of all registered entities. To ensure clarity of ownership across all entity types—including APIs, capabilities, components, user journeys, and more—the following changes are necessary.
Ownership for various entity types was determined using available data from the current Amped structure. Teams with a carryover score exceeding 50% were considered to have a 1:1 ownership mapping. For entities previously owned by teams with less than 50% carryover, ownership was assigned based on the commit history of the specific entity.
Proposed Changes
YAML File Updates:
CODEOWNERS File Updates:
Next Steps
Teams review all components are rightly assigned to them as needed using Backstage.
Reference Ticket and Useful Documentation
Jira epic
Doc