diff --git a/contribution-policy.md b/contribution-policy.md
new file mode 100644
index 0000000..b32b1e4
--- /dev/null
+++ b/contribution-policy.md
@@ -0,0 +1,21 @@
+## Contribution Policy
+
+Individuals making significant and valuable contributions are given
+commit-access to the project. These individuals are identified by the TC and
+discussed during the weekly TC meeting.
+
+If you make a significant contribution and are not considered for commit-access
+log an issue and it will be brought up in the next TC meeting.
+
+Internal pull-requests to solicit feedback are required for any other
+non-trivial contribution but left to the discretion of the contributor.
+
+For significant changes wait a full 48 hours (72 hours if it spans a weekend)
+before merging so that active contributors who are distributed throughout the
+world have a chance to weigh in.
+
+Controversial changes and **very** significant changes should not be merged
+until they have been discussed by the TC which will make any final decisions.
+
+TC members nominate contributors to be added to the TC which the TC will vote
+on. They can nominate any individual during any meeting.
diff --git a/governance.md b/governance.md
new file mode 100644
index 0000000..4356ff1
--- /dev/null
+++ b/governance.md
@@ -0,0 +1,47 @@
+# Governance
+
+This repository is jointly governed by a technical
+committee, commonly referred to as the "TC."
+
+Initial membership invitations to the TC were given to individuals who had
+been active contributors to Node. Current membership is:
+
+```
+Fedor Indutny (@indutny)
+Trevor Norris (@trevnorris)
+Ben Noordhuis (@bnoordhuis)
+Isaac Z. Schlueter (@isaacs)
+Nathan Rajlich (@TooTallNate)
+Bert Belder (@piscisaureus)
+TJ Fontaine (@tjfontaine)
+Alexis Campailla (@orangemocha)
+```
+
+Additionally the TC may invite persons or representatives from certain projects
+to participate in a non-voting capacity. These invitees currently are:
+
+* A representative from [build](https://github.com/node-forward/build) chosen
+by that project.
+
+The TC has final authority over this project including:
+
+* Project governance and process
+* Contribution policy
+* GitHub repository hosting
+* nodejs.org website
+* Releases and Release process
+
+The TC can change its governance model if they deem it necessary. The current
+governance rules are:
+
+* [Consensus Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making)
+* Motions with voting when consensus cannot be reached.
+* Quorum of 2/3 (66%), simple definite majority wins.
+* No more than 1/3 (34%) of the TC membership can be affiliated with the same
+employer.
+
+## TC Meetings
+
+The TC meets weekly on a Google hangout. The meeting is run by a designated
+moderator, currently `Mikeal Rogers (@mikeal)`. Each meeting should be
+published to Youtube.