cloudfoundry / cloudfoundry/cloud_controller_ng
**Charter:** Evaluate workflows where users might accidentally cause **downtime** when **modifying route destinations** with **ports**
Open
Nobody has claimed this yet.
unscheduled
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Objectives:
- Explore user workflows involving adding, removing, and updating route destinations with ports to determine which ones cause downtime
- Brainstorm solutions (technical or otherwise) to make the user experience more luxurious.
Deliverable:
- Probably a case table or something?
- Suggested workarounds for non-luxurious cases.
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 mapping workflows for adding, removing, and updating route destinations with ports. Record which cases cause downtime in a case table, then document suggested workarounds for cases that cannot provide a smoother user experience.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100