microsoft / microsoft/react-native-windows
Community module support principles
Open
Nobody has claimed this yet.
Agenda
enhancement
Needs: PM Design
Workstream: Module Support
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
What should be the bar for community modules our team produces?
e.g. is it ok for a module to not be accessible, etc.
What's our responsibility once we implement the module?
Do we have to write tests?
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.
Assessment
This issue has not been assessed yet.