Roadmap - GitProxy v2 and beyond!
- Dominant language
- TypeScript
- Stars
- 249
- Forks
- 176
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 20
Description
# Roadmap
As discussed in previous community calls, GitProxy is direly in need of a Roadmap so that contributors can see more clearly the order in which things ought to be developed and merged into the project. It'll also help us start developing v2 on the right foot.
I've decided to write a quick draft after looking at *all* the open issues and PRs. I'm classifying most issues roughly based on need (engagement), difficulty and whether they'll cause breaking changes with our current setup.
Feel free to add the issues that are relevant to your organization!
**Note:** We might want to reorder these according to our perceived priority (my default sorting is older issues first).
## Easy wins
Anything that we could probably get done within a day or two.
- [x] #382
- [x] #505
- [x] #605
- [ ] #627
- [x] #654
- [ ] #745
- [x] #1002 (PR ready)
- [x] #1019
- [x] #1022
- [x] #1028
- [x] #1031
- [x] #1040
- [x] #1041
## Need, fixes and minor releases
Fixes and non-breaking features that will provide significant value to users.
- [x] #27
- [x] #61
- [x] #64
- [x] #510
- [ ] #594 and related PRs
- [x] #743
- [x] #759
- [x] #978
- [x] #985
- [x] #986
- [x] #1008
- [x] #1088
- [ ] #1104
## Need, but may cause breaking changes
Anything that requires deep refactoring/architectural changes may fall in this category. We will likely release these in GitProxy v3.
- [x] #425
- Lots of architectural changes here that will help pave the way for new features
- [x] #99
- [ ] #463
- Depends on #425
- [ ] #910
- Super valuable, may not strictly require v3 but changes are expected to be large
- [x] #946, #950
- Planned for v2 release
- [x] #980
## Nice-to-have, tech debt fixes
We don't strictly need these, but they'll help improve maintainability and user/developer experience.
### Tech Debt
- [x] #240
- Almost there, just a few % left
- [x] #276
- Almost there, just a few PRs left to merge #1065 #1063
- Related: #927
- [x] #394
- We do have E2E tests set up, we just need more coverage
- Related: #624
- [x] #399
- There is a PR for this almost ready to merge #508
- [x] #694
- PR ready for this #1115
- [x] #1113
### UI/UX-related
- [x] #50
- [x] #51
- [x] #428
- [x] #1106
Contributor guide
Assessment
This issue has not been assessed yet.