move relevant information from tessel/onboarding/README into team-members getting started

Author: Frijol

TEAM-MEMBERS.md

@@ -1,11 +1,12 @@
 # Team Member Guide
 
-This guide is intended to help Team Members (TMs) for the Tessel Project understand and fulfill their role. Collaborators moderate and review contributions and conversations surrounding the Tessel project.
+This guide is intended to help Team Members (TMs) for the Tessel Project understand and fulfill their role. Team Members moderate and review contributions and conversations surrounding the Tessel project.
 
 ---
 
 **Contents**
 
+* [Getting started as a Team Member](#getting-started-as-a-team-member)
 * [Approving or rejecting modifications to assets (bug fixes etc)](#approving-or-rejecting-modifications-to-assets-such-as-bug-fixes-code-refactoring-or-minor-api-or-feature-changes)
 * [Managing feature requests and RFCs](#managing-feature-requests-and-rfcs)
 * [Maintaining strong communication with the community](#maintaining-strong-communication-with-the-community)
@@ -16,6 +17,24 @@ This guide is intended to help Team Members (TMs) for the Tessel Project underst
 TMs should be familiar with the guidelines for new contributors in [the Contribution Guide](CONTRIBUTING.md). For a definition of Team Member and information on how to become a Team Member, see the [GOVERNANCE](GOVERNANCE.md) document.
 
 ---
+## Getting started as a team member
+The [Steering Committee](https://github.com/tessel/project/blob/master/GOVERNANCE.md) invites contributors to become Team Members, typically after they have made some substantial contribution to the project.
+
+* **Your first PR.** Officially add yourself as a Team Member. You can do so by opening up a Pull Request on the [tessel/project repo's  Team page](https://github.com/tessel/project/blob/master/TEAM.md). Check out [this PR as an example](https://github.com/tessel/project/pull/63).
+
+* **Get started with your Tessel 2.** Go to the [Tessel 2 start page](http://tessel.github.io/t2-start/) and try it out! This should get you set up with using the CLI, connecting to Wifi, and using modules.
+
+* **Get to know T2's tech stack and repos.** You'll be much more equipped to make meaningful contributions if you read the [Tessel 2 Technical Overview](https://tessel.gitbooks.io/t2-docs/content/debugging/Technical_Overview.html). This guide goes over the main repositories, where you can find relevant code and design files, and how the Tessel 2 system architecture works.
+
+* **Get to know your mentor.** Once you're part of the team and you have a high-level understanding of how Tessel 2 works, get in touch with the person that introduced you to the project and set up a time to chat. This informal call will help you understand the current state of the project, where your help is needed most, and how you can get started. If you're not sure who to contact, get in touch with the person who accepted [your first PR](#2-get-started-with-your-tessel-2) or [jump on Slack and let us know you're ready to get started](https://tessel-slack.herokuapp.com/).
+
+* **Get to know the team.** Our primary communication channel is [Slack](https://tessel-slack.herokuapp.com/). We recommend keeping it open while you're working on Tessel; it's very useful for asking quick questions. Important channels:
+
+  * #engineering for most of your technical questions
+  * #team-members for discussion with your fellow Team Members
+  * #events-speaking if you're interested in giving conference talks
+
+* **Do something!** Your mentor can help you find something to work on, or the [T2 Completeness Checklist](https://github.com/tessel/project/issues/70) is a good place to start. Pick something, ask questions, and get started!
 
 ## Approving or rejecting modifications to assets (such as bug fixes, code refactoring, or minor API or feature changes)
 
@@ -42,7 +61,7 @@ Guidelines:
 
 ### Blog Posts
 
-TMs are encouraged to post new features or interesting facets of the project to the blog. Credentials to the technical.io blog (Tumblr) will be shared with TMs and they should feel free to post any time. Kelsey ([@selkeymoonbeam](//twitter.com/selkeymoonbeam)) is happy to review and offer suggestions on any posts prior to publishing.
+TMs are encouraged to post new features or interesting facets of the project to the blog. Please make a PR to [this repo](https://github.com/tessel/this-week-in-tessel) with your post!
 
 ## Ensuring open and respectful discourse