Problem Statement
The repository currently maintains contributor information directly inside README while also maintaining contributor-related information elsewhere. The README states that contributors are auto-updated via GitHub Actions, but contributor data is still tightly coupled to documentation files.
As contributor count grows, this creates a maintenance bottleneck and increases the risk of inconsistencies between contributor records.
Current Behavior
- Contributors are displayed in README.
- Contributor information is spread across multiple locations.
- Contributor additions frequently target documentation files directly.
- Future scaling may introduce merge conflicts and data drift.
Expected Behavior
Contributor information should be maintained from a single canonical source and automatically propagated wherever it needs to be displayed.
Proposed Solution
- Create a dedicated contributor registry file (contributors.json or contributors.yml).
- Generate contributor sections automatically.
- Update README and contributor-related documentation through automation.
- Eliminate manual contributor-list maintenance.
Alternatives Considered
No response
Additional Context
Benefits
- Reduces merge conflicts.
- Prevents contributor data drift.
- Improves maintainability.
- Scales better as contributor count increases.
Files Affected
README.md
CONTRIBUTORS.md
.github/workflows/*
Suggested labels:
NSOC'26
LEVEL 3
ENHANCEMENT
Problem Statement
The repository currently maintains contributor information directly inside README while also maintaining contributor-related information elsewhere. The README states that contributors are auto-updated via GitHub Actions, but contributor data is still tightly coupled to documentation files.
As contributor count grows, this creates a maintenance bottleneck and increases the risk of inconsistencies between contributor records.
Current Behavior
Expected Behavior
Contributor information should be maintained from a single canonical source and automatically propagated wherever it needs to be displayed.
Proposed Solution
Alternatives Considered
No response
Additional Context
Benefits
Files Affected
Suggested labels:
NSOC'26
LEVEL 3
ENHANCEMENT