- Close any issues that can be closed
- Solve any issues that can be solved
- Assign any outstanding issues to the correct members on the React Native team, and give them enough information to be able to act on them
- Push pull requests through
- Improve the signal:noise ratio
- Be nice & welcoming, and appreciative to everyone's efforts to contribute
-
Read through issues to identify and address:
- already solved
- non-issues (eg: questions about how something works, answer these!)
- duplicates
- vague descriptions
- x is broken
- why doesn't y work? -> try to reproduce these in either a public repo of your own, or on rnplay.org -> if you can't reproduce it, push it back to the issue creator
- similar issues that you have faced, augment with another example
- any temporary workarounds that you're using
- fix it if you can!
- politely redirect questions about how to do x to StackOverflow
-
Read through pull requests and:
- do a code review
- test their fixes on your own
- if it's stale and has pending questions, take it over and make any necessary changes to make it ready again
- make note of any issues that are solved by this pr in the comments
Ping @brentvatne and/or @ide on each of your comments
Also, join us in irc Freenode #reactnative or Slack (Reactiflux.com #react-native)