open-feature / open-feature/spec
Migrate (or implement) multi-provider directly in SDKs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 58
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 2
Description
The multi-provider is quite valuable and offers a lot of utility, but it's not implemented in all languages.
Additionally, in most implementations, it exists in the "contrib" repo as an optional extension. In these cases, we want to remove it from contribs and into the SDK directly, also taking advantage of the access to SDK internals to simplify the implementations where possible.
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 by inventorying the SDK implementations and the optional multi-provider extensions in the contrib repositories; the issue names no specific files or tests. Done means multi-provider support exists in every relevant SDK and the contrib implementations have been removed, with simpler implementations where SDK internals allow.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100