[FEAT-concept]: functional differences from moving from targeting the feasibility modeling to late scoping modeling
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
The issue body names no files, tests, or entry points. First clarify the functional differences between feasibility modeling and late scoping modeling, then identify which chart-docs materials would need changes. Done means the scope and affected documentation are agreed and the updated behavior is documented.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from USACE/chart-docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
USACE/chart-docs#756 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
USACE/chart-docs#750 ·
-
[FEAT-API/UI]: Add ability to download hydrograph input / outputPossibly taken @noarevalo-bah claimed this 1 day ago. Open
USACE/chart-docs#759 · 1 assignee ·
-
[FEAT-Infra]: Research how to properly handle converting to single APIPossibly taken @martyheynbah claimed this 2 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
USACE/chart-docs#758 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
USACE/chart-docs#755 ·
All issues in USACE/chart-docs
Similar issues
-
Scrub the retired Kaizen target out of the deploy runbookPossibly taken @mcannonbrookes claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
atlassian-labs/roving-office#25 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
P4: low tooling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
jeffknupp/association#318 ·
-
documentation good first issue hacktoberfest size/small type/docs up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Redo-San/RedoSan-Authenticity#511 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100