Estimated development time.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 12k
- Forks
- 332
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 17
Description
Summary 💡
Can we add an extra output line where we mention an estimate of how many hours went into development?
I'm afraid there is no well-maintained library that implements this, but I believe any simple formula with simple assumptions will do.
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
No file, test, or entry point is identified in the issue. First clarify the assumptions and formula for estimating development hours, then identify where onefetch assembles its output and define the expected extra line and validation criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100