Issues
- 29
Getting involved in the React Native Community
#46 opened by kelset - 2
- 1
- 4
BOTs in the org
#30 opened by kelset - 6
Organisation updates - PLEASE READ ❤️
#40 opened by kelset - 3
Migrating a repo into the React Native Community
#34 opened by kelset - 6
Sustainability in the React Native Community
#41 opened by kelset - 8
- 2
Maintainers Permission over the repo they maintain
#54 opened by kelset - 8
Good reasons why your company should get involved
#52 opened by kelset - 11
Lean Core repositories
#45 opened by kelset - 5
- 0
white s
#75 opened by NITISHSHARMA12 - 2
Governance in the React Native Community
#42 opened by kelset - 1
- 2
how to move react-native-qrcode-scanner to be a @react-native-community package instead
#73 opened by renatobenks - 1
- 1
Migrate react-native-config to community
#67 opened by luancurti - 6
Take over : react-native-orientation
#61 opened by xstable - 8
TODO: complete the guidelines
#2 opened by kelset - 1
Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
#55 opened by devika7 - 5
Can we have a drawing pad or signature pad?
#53 opened by hmheng - 1
- 2
- 14
TODO: Complete Maintainers file
#1 opened by kelset - 14
Discussion: Removing "react-native" from repo names and moving packages to @react-native-community
#33 opened by xzilja - 7
Permissions
#5 opened by grabbou - 6
- 5
Standardise folder organisation and naming
#17 opened by xzilja - 4
Standardise type definitions
#14 opened by xzilja - 1
- 4
NPM publish maintainers
#7 opened by rborn - 1
Discussion: Standardise the release process
#24 opened by matt-oakes - 6
PR code review guidelines
#8 opened by rborn - 6
Handling github issues
#6 opened by rborn - 1
Repository organisation guidelines
#13 opened by xzilja