Merge pull request #62 from sdemos/rust

*: rewrite coreos-metadata in rust

.github/tailor.yaml

@@ -0,0 +1,15 @@
+rules:
+  - name: commit title scope
+    description: all commit titles must have a lowercase scope
+    expression:  |-
+      .commits all((.title test "^[a-z1-9/*,:_-]+:") or (.title test "^Revert"))
+
+  - name: commit title length
+    description: all commit titles must be no more than 50 characters
+    expression:  |-
+      .commits all((.title length < 51) or (.title test "^Revert"))
+
+  - name: commit description
+    description: all commits must have a description with each line having no more than 72 characters
+    expression: |-
+      .commits all((.description lines all(. length < 73) and (.description lines length > 0)) or (.title test "^Revert"))

.gitignore

@@ -1,2 +1,2 @@
-bin/
-gopath/
+target/
+**/*.rs.bk

.travis.yml

@@ -1,12 +1,8 @@
-language: go
+language: rust
+rust:
+  - stable
+  - beta
+  - nightly
 matrix:
-  include:
-    - go: 1.5
-      env: GO15VENDOREXPERIMENT=1
-    - go: 1.6
-
-install:
-  -
-
-script:
-  - ./test
+  allow_failures:
+    - rust: nightly

CONTRIBUTING.md

@@ -5,26 +5,33 @@ GitHub pull requests.  This document outlines some of the conventions on
 development workflow, commit message formatting, contact points and other
 resources to make it easier to get your contribution accepted.
 
-# Certificate of Origin
+## Certificate of Origin
 
 By contributing to this project you agree to the Developer Certificate of
 Origin (DCO). This document was created by the Linux Kernel community and is a
 simple statement that you, as a contributor, have the legal right to make the
 contribution. See the [DCO](DCO) file for details.
 
-# Email and Chat
+## Email and Chat
 
 The project currently uses the general CoreOS email list and IRC channel:
 - Email: [coreos-dev](https://groups.google.com/forum/#!forum/coreos-dev)
 - IRC: #[coreos](irc://irc.freenode.org:6667/#coreos) IRC channel on freenode.org
 
+Please avoid emailing maintainers found in the MAINTAINERS file directly. They
+are very busy and read the mailing lists.
+
+##  Reporting a security vulnerability
+
+Due to their public nature, GitHub and mailing lists are not appropriate places for reporting vulnerabilities. Please refer to CoreOS's [security disclosure][disclosure] process when reporting issues that may be security related.
+
 ## Getting Started
 
 - Fork the repository on GitHub
 - Read the [README](README.md) for build and test instructions
 - Play with the project, submit bugs, submit patches!
 
-## Contribution Flow
+### Contribution Flow
 
 This is a rough outline of what a contributor's workflow looks like:
 
@@ -37,17 +44,21 @@ This is a rough outline of what a contributor's workflow looks like:
 
 Thanks for your contributions!
 
+### Code Style
+
+Code should be formatted according to the output of [rustfmt](https://github.com/rust-lang-nursery/rustfmt)
+
 ### Format of the Commit Message
 
 We follow a rough convention for commit messages that is designed to answer two
 questions: what changed and why. The subject line should feature the what and
 the body of the commit should describe the why.
 
 ```
-environment: write new keys in consistent order
+scripts: add the test-cluster command
 
-Go 1.3 randomizes the ordering of keys when iterating over a map.
-Sort the keys to make this ordering consistent.
+this uses tmux to setup a test cluster that you can easily kill and
+start for debugging.
 
 Fixes #38
 ```
@@ -66,3 +77,6 @@ The first line is the subject and should be no longer than 70 characters, the
 second line is always blank, and other lines should be wrapped at 80 characters.
 This allows the message to be easier to read on GitHub as well as in various
 git tools.
+
+
+[disclosure]: https://coreos.com/security/disclosure/