open-feature / open-feature/flagd
[DOCS] Publish and maintain features matrix for providers
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
We have a feature-section for our SDKs (example in the Java SDK) which is used to build a feature matrix in our documentation. It would be great to have something similar for flagd providers, which covered key functionality like:
- RPC mode support
- in-process mode support
- unix socket support
- TLS support
- caching support
- etc, etc
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
Start with the Java SDK feature-section example and the SDK compatibility matrix linked in the issue. Inventory the flagd providers and determine which listed capabilities they support, then publish the provider matrix in the documentation and define how it will be kept current.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100