Update README.md and CONTRIBUTING.md with updated links and information about...

Update README.md and CONTRIBUTING.md with updated links and information about how to connect via slack or email

CONTRIBUTING.md

@@ -3,60 +3,47 @@
 
 ## How Can I Contribute?
 
-### Helping translate
+### Get Connected
+Want to connect with contributors?
+* Join us on [Slack](https://join.slack.com/t/boincworkspace/shared_invite/enQtNzA3MTQ4NDA0Njc4LTM4NTEyZTY1MWEwZjAyNTVmOTg3NDA2NjVjZDQzMWQ3NmFjYTc4MTNkNTEyNjRkOTQ4MWU5Nzk3NzRhNTg0NDI)
+* Join the email lists:
+  * [BOINC Overall](https://groups.google.com/forum/#!forum/boinc_admin)
+  * [BOINC Projects](https://groups.google.com/a/ssl.berkeley.edu/forum/#!forum/boinc_projects)
+  * [BOINC Development](https://groups.google.com/a/ssl.berkeley.edu/forum/#!forum/boinc_dev)
+  * [BOINC Alpha Testing](https://groups.google.com/a/ssl.berkeley.edu/forum/#!forum/boinc_alpha)
+* Join one of the community calls:
+  * The BOINC Projects call occurs quarterly and is announced on the [BOINC Projects email list](https://groups.google.com/a/ssl.berkeley.edu/forum/#!forum/boinc_projects)
+  * The BOINC Contributor call occurs every other week and is announced on the [BOINC Development email list](https://groups.google.com/a/ssl.berkeley.edu/forum/#!forum/boinc_dev)
+
+### Promote Volunteer Computing
+Want to help promote volunteer computing and work on ways to attract new users? Join the #communications channel on [Slack](https://join.slack.com/t/boincworkspace/shared_invite/enQtNzA3MTQ4NDA0Njc4LTM4NTEyZTY1MWEwZjAyNTVmOTg3NDA2NjVjZDQzMWQ3NmFjYTc4MTNkNTEyNjRkOTQ4MWU5Nzk3NzRhNTg0NDI)  
+
+### Help Translate
 See: https://boinc.berkeley.edu/trac/wiki/TranslateIntro
 
-### Reporting Bugs
+### Help Test
+You can help new versions of the client.  
+* Become an (Alpha Tester)[https://boinc.berkeley.edu/trac/wiki/AlphaInstructions]
+* Signup to be a (BOINC Android Tester)[https://groups.google.com/forum/#!forum/boinc-android-testing]
+
+### Report Bugs
 Did you find a bug? Make a Bug report.
 * Ensure the bug was not already reported by searching on GitHub under [Issues](https://github.com/BOINC/boinc/issues).
 * If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/BOINC/boinc/issues/new).
 
-### Suggesting Enhancements
-Do you have a feture idea? Make a Feature request.
+### Suggest Enhancements
+Do you have a feature idea? Make a feature request.
 * Ensure the feature was not already requested by searching on GitHub under [Issues](https://github.com/BOINC/boinc/issues).
 * If you're unable to find an open issue addressing the idea, [open a new one](https://github.com/BOINC/boinc/issues/new).
 
-### Making Pull Requests
-**1. Fork & create a branch**
-
-[Fork BOINC](https://help.github.com/articles/fork-a-repo/) and create a branch with a descriptive name.
-A good branch name would be:
-```
-git checkout -b update-code-of-conduct
-```
-
-**2. Implement your fix or feature**
-
-At this point, you're ready to make your changes! Feel free to ask for help, everyone is a beginner at first. :wink:
-
-Development Practices:
-* Code has followed the [style guide for BOINC](http://boinc.berkeley.edu/trac/wiki/CodingStyle)
-* Commit does not contain unrelated code changes
-* Code uses [atomic commits](https://www.freshconsulting.com/atomic-commits/)
-
-**3. Sync changes made in the original repository with your fork**
-At this point, you should switch back to your master branch and [make sure it's up to date with BOINC's master branch](https://help.github.com/articles/configuring-a-remote-for-a-fork/):
-
-```
-git remote add upstream https://github.com/BOINC/boinc.git
-git checkout master
-git pull upstream master
-```
-
-Then update your branch from your local copy of master, and push it!
-
-```
-git checkout update-code-of-conduct
-git rebase master
-git push --set-upstream origin update-code-of-conduct
-```
-
-**4. Make a Pull Request** 
-
-Finally, go to GitHub and [make a Pull Request](https://help.github.com/articles/creating-a-pull-request-from-a-fork/).
+### Contribute Code
+Do you want to fix a bug or implement a new feature?  Read about how to [implement a code contribution](https://github.com/BOINC/boinc-policy/blob/master/Development_Documents/Development_Workflow.md#2-implementation).
 
 ## Styleguides
 
+### BOINC Coding Styles
+See https://boinc.berkeley.edu/trac/wiki/CodingStyle
+
 ### Git Commit Messages
 * Use the present tense ("Add feature" not "Added feature")
 * Use the imperative mood ("Move cursor to..." not "Moves cursor to...")

README.md

@@ -9,11 +9,8 @@ Project Website: https://boinc.berkeley.edu
 ## Want to create a project
 See: https://boinc.berkeley.edu/trac/wiki
 
-## Want to help translate
-See: https://boinc.berkeley.edu/trac/wiki/TranslateIntro
-
-## Want to contribute
-See: https://github.com/BOINC/boinc-policy
+## Want to help
+Read about all the [ways you can help](CONTRIBUTING.md)
 
 ### Note