microsoft / microsoft/terminal
Pull conhost measurements with low/no future relevancy
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
After a meeting with the data team, we decided to pull a bunch of the interactivity measurements from conhost.exe that we're not planning on using ever again (primarily because Terminal is becoming/has become the face of user interactivity so we don't need to really measure how people are interacting with conhost.exe anymore to make a decision.)
This represents walking through the events and pulling them. We're still planning on leaving events that may influence feature decisions in the new Terminal (or help us identify people who cannot complete their workflow in Terminal and are stuck on conhost.exe.)
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
The issue identifies conhost.exe interactivity measurements and their events as the scope, but names no files or tests. Start by inventorying the events and confirming which may affect Terminal feature decisions; done means removing the low- or no-future-relevance measurements while retaining events that inform Terminal decisions or identify workflows still requiring conhost.exe.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- observability-sre, operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100