DefangLabs / DefangLabs/defang
Look into making protos package in defang repo its own submodule
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 166
- Forks
- 24
- Avg merge
- 10h 8m
- Merged PRs (30d)
- 33
Description
Look into making the defang protos package it's own submodule to be build and imported into defang and defang-mvp repos.
Both repos have a dependency on the protos package but at current it's built as part of the defang repo. Protos changes are created as a separate PR with only protos changes. This suggests separating out the package into it's own repo which will also allow us to tag release versions.
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 how the protos package is built and imported in the defang and defang-mvp repositories. Determine whether it should move to its own repository or submodule and how releases would be tagged. Done means the separation approach, dependency changes, and release process are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100