Improve usage attribution in workspace start
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
Following up from https://github.com/gitpod-io/gitpod/pull/11777, in parallel with the improvements needed for the usage attribution interaction in user settings (https://github.com/gitpod-io/gitpod/issues/11498), improvements are also needed during workspace start. Cc @jankeromnes @geropl
Possibly the same elements can be reused in both places and can be tackled at one step, but breaking this down into a separate MVC issue for better planning.
Proposal
TBD (To be discussed)
See also https://github.com/gitpod-io/gitpod/issues/11498#issuecomment-1205281686.
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 reading PR #11777 and issue #11498, then trace the workspace-start flow to understand how usage attribution currently works. The proposal is still TBD, so work is not ready until the desired interaction and reuse between workspace start and user settings are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100