spring-projects / spring-projects/spring-grpc
Consider Taking Over reactive-grpc
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 413
- Forks
- 95
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 2
Description
As mentioned in this issue https://github.com/salesforce/reactive-grpc/issues/337,
reactive-grpc has effectively been paused.
How about taking over reactive-grpc (probably only the reactor support) in Spring gRPC?
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 reading the linked reactive-grpc issue 337 and this proposal to understand the paused project and the suggested Reactor-only scope. Before implementation, establish which reactive-grpc functionality Spring gRPC would take over and what completion criteria the maintainers accept.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, java, spring
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100