microsoft / microsoft/react-native-windows
Absorb ownership of tools created for RNW but sitting on @asklar
Open
Nobody has claimed this yet.
Area: Tooling
enhancement
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
I wasn't sure where else to track this, but we rely on multiple tools that @asklar spun up for RNW that are just sitting in his repo. Maybe we want them in a better place to maintain/update?
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
Review the three linked repositories—XamlTreeDump, unbroken, and winmd2md—and determine how they are currently used by RNW. Start by checking their ownership and maintenance needs; done means agreeing where these tools should live and recording or completing the ownership transfer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100