open-feature / open-feature/protocol
OFREP 1.0 roadmap
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 56
- Forks
- 7
- Avg merge
- 1h 54m
- Merged PRs (30d)
- 1
Description
Hello
This issue is the parent issue to follow what we have to do before saying that OFREP is stable and can be released as 1.0.
[!NOTE]
The goal is to stabilise what OFREP offer already and note improve it for now.
We will consider improvement and evolution after the release of the 1.0.
List of things to do before being able to released a 1.0 version:
- Remove the
/ofrep/v1/configurationendpoint - #38 - Remove the
cacheablefield - #43 - Write server provider guidelines #41 #42
- Write client provider guidelines #14
- Add a documentation section for OFREP in the OpenFeature website
- Release OpenFeature Client providers for:
- Web (already exists but we need to check that everything is supported)
- Swift - https://github.com/open-feature/ofrep-swift-client-provider/pull/2
- Kotlin - https://github.com/open-feature/kotlin-sdk-contrib/pull/6
- Check compliance of existing server providers
- Create issues to create servers providers.
- .NET - https://github.com/open-feature/dotnet-sdk-contrib/issues/413 - https://github.com/open-feature/dotnet-sdk-contrib/pull/428
- Java - https://github.com/open-feature/java-sdk-contrib/issues/1413 - https://github.com/open-feature/java-sdk-contrib/pull/1429
- PHP - https://github.com/open-feature/php-sdk-contrib/issues/128
- Rust - https://github.com/open-feature/rust-sdk-contrib/issues/51 - https://github.com/open-feature/rust-sdk-contrib/pull/53
- Elixir - https://github.com/open-feature/elixir-sdk-contrib/issues/16
- Ruby - https://github.com/open-feature/ruby-sdk-contrib/issues/57
- Removing the WIP badge from this repository
- Create a blog post to announce the
1.0release.
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 linked issues #38, #43, #41, #42, and #14, then review the referenced client and server provider repositories and pull requests. Done means the listed OFREP 1.0 checklist is completed, including provider compliance, website documentation, removal of the WIP badge, and the release announcement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, elixir, go, java, javascript, kotlin, node.js, php, python, ruby, rust, swift
- Domain
- api, backend-api-design, documentation, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100