[Feature Request] Publish and maintain buf schema registry
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 133
- Forks
- 101
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 11
Description
Describe the solution you'd like
For others to use we want to publish and maintain a buf schema registry. This may be more challenging than it appears because we inline our google dependency which we need to make sure we don't publish. We could also consider generating code with buf but that is outside of the scope of this issue and we want to make sure raw protoc continues to work.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the repository's API and proto files and the proposed buf schema registry workflow. Determine how to publish the schemas without including the inlined Google dependency, while preserving raw protoc compatibility; code generation with buf is explicitly out of scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100