Evaluate forked dependencies to see cost/benefit
Open
Nobody has claimed this yet.
area/stability
jira
kind/cleanup
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Description
Feature Request
We have some forked dependencies of upstream code bases that we are maintaining. We should probably evaluate these deps to see:
- if there is any way the features could be merged upstream
- if it's worth maintaining over time, considering we'd have to maintain it forever
There is at least:
Any others?
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 reviewing the forked coreos/go-json dependency and inventory any other maintained forks in the repository. For each one, check whether its changes could be merged upstream and document the long-term maintenance cost and recommendation. Done means the dependency list and cost-benefit conclusions are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100