operator-framework / operator-framework/operator-sdk
[META] Scorecard Enhancements Tracker
Open
Nobody has claimed this yet.
lifecycle/frozen
needs discussion
scorecard
- Dominant language
- Go
- Stars
- 7.7k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
This ticket is to track suggested improvements and bug-fixes to the scorecard. If an item is be explored, a new issue should be created and linked back here.
- Disconnected environment scorecard images
- Additional fields to track optional junit/xunit types
- Support more/total environment configuration in SC config (eg. ServiceAccount)
- Split scorecard run/environment configurations
- Remove dependency on operator-framework/api updates for scorecard api changes
- Create scorecard tests to verify operator capability levels
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is a tracker rather than an implementation specification, so start by choosing one checklist item and creating the dedicated issue it requests. Review the scorecard configuration and existing scorecard tests first; the selected issue should define the requested behavior and what test coverage marks it done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100