Move project code (golang) to v3
Open
kind/feature
status/never-stale
- Dominant language
- Go
- Stars
- 927
- Forks
- 387
- Avg merge
- 15h 5m
- Merged PRs (30d)
- 36
Description
### Requirement
When moving to v3, we should upgrade the project structure as well.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing project structure and the requirements for moving the project code to v3. The issue names no files, tests, entry points, or acceptance criteria, so clarify the intended structure and what completion should mean before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100