feat: initial meta documents

Author: mmarchini

CODE_OF_CONDUCT.md

@@ -0,0 +1,5 @@
+# Code of Conduct
+
+This repository is committed to upholding the Node.js Code of Conduct.
+
+The Node.js Code of Conduct document can be found at nodejs/admin@master/CODE_OF_CONDUCT.md

CONTRIBUTING.md

@@ -0,0 +1,32 @@
+# Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+* (a) The contribution was created in whole or in part by me and I
+  have the right to submit it under the open source license
+  indicated in the file; or
+
+* (b) The contribution is based upon previous work that, to the best
+  of my knowledge, is covered under an appropriate open source
+  license and I have the right under that license to submit that
+  work with modifications, whether created in whole or in part
+  by me, under the same open source license (unless I am
+  permitted to submit under a different license), as indicated
+  in the file; or
+
+* (c) The contribution was provided directly to me by some other
+  person who certified (a), (b) or (c) and I have not modified
+  it.
+
+* (d) I understand and agree that this project and the contribution
+  are public and that a record of the contribution (including all
+  personal information I submit with it, including my sign-off) is
+  maintained indefinitely and may be redistributed consistent with
+  this project or the open source license(s) involved.
+
+## Moderation Policy
+
+The [Node.js Moderation Policy] applies to this repository.
+
+[Node.js Moderation Policy]:
+https://github.com/nodejs/admin/blob/master/Moderation-Policy.md

README.md

@@ -0,0 +1,14 @@
+# Future of Build Toolchain
+
+The goals of the "Future of Build Toolchain" Strategic Initiative are:
+
+  * Explore and test alternatives to the current build toolchain used by Node.js
+  * Map existing personas and use cases that rely on the build toolchain
+  * Prioritize personas, understanding what compromises are acceptable in the
+    next build toolchain
+    * Work with stakeholders to ensure compatibility with their use cases
+  * Create a migration plan to move to a new build toolchain
+  * Execute that plan
+
+This repository is used to discuss anything related to this strategic
+initiative, as well as to track its progress.