microsoft / microsoft/terminal
Author a KB article documenting DxD and how to disable it
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
When DxD hits broadly, it will be good for us to have some official Microsoft documentation on (1) what happened, (2) the anticipated risk to applications and (3) how to revert to a known-good state. Enterprises can fall back on this documentation, and we can point users to it.
Why a KB article, instead of Terminal Docs?
We should do both, but a KB article is more "official." They're not user-editable, and they document "best practice" and compatibility risks and things like that.
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 repository file, test, or entry point is named. Start from the issue's three requested topics: what happened, application risk, and reverting to a known-good state. Done means producing an official Microsoft KB article that documents DxD and its disabling or rollback guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100