Initial commit for up-subscribe-rust

.gitignore

@@ -0,0 +1,17 @@
+# Generated by Cargo
+# will have compiled files and executables
+debug/
+target/
+
+# Remove Cargo.lock from gitignore if creating an executable, leave it for libraries
+# More information here https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
+#Cargo.lock
+
+# These are backup files generated by rustfmt
+**/*.rs.bk
+
+# MSVC Windows builds of rustc generate these, which store debugging information
+*.pdb
+
+.vscode/
+.idea/

CONTRIBUTING.md

@@ -0,0 +1,54 @@
+# Contributing to Eclipse uProtocol
+
+Thanks for your interest in this project. Contributions are welcome!
+
+## Developer resources
+
+Information regarding source code management, builds, coding standards, and
+more.
+
+<https://projects.eclipse.org/proposals/eclipse-uprotocol>
+
+The project maintains the following source code repositories
+
+<https://github.com/eclipse-uprotocol>
+
+## Eclipse Contributor Agreement
+
+Before your contribution can be accepted by the project team contributors must
+electronically sign the Eclipse Contributor Agreement (ECA).
+
+<http://www.eclipse.org/legal/ECA.php>
+
+Commits that are provided by non-committers must have a Signed-off-by field in
+the footer indicating that the author is aware of the terms by which the
+contribution has been provided to the project. The non-committer must
+additionally have an Eclipse Foundation account and must have a signed Eclipse
+Contributor Agreement (ECA) on file.
+
+For more information, please see the Eclipse Committer Handbook:
+<https://www.eclipse.org/projects/handbook/#resources-commit>
+
+## Setting up a development environment
+
+You can use any development environment you like to contribute to the uSubscription Rust. However, it is mandatory to use the Rust linter ('[clippy](<https://github.com/rust-lang/rust-clippy>)') for any pull requests you do.
+To set up VSCode to run clippy per default every time you save your code, have a look here: [How to use Clippy in VS Code with rust-analyzer?](https://users.rust-lang.org/t/how-to-use-clippy-in-vs-code-with-rust-analyzer/41881)
+
+Similarly, the project requests that markdown is formatted and linted properly - to help with this, it is recommended to use [markdown linters](https://marketplace.visualstudio.com/items?itemName=DavidAnson.vscode-markdownlint).
+
+During development, before submitting a PR, you can use `./tools/fmt_clippy_doc.sh` to run these checks on the workspace.
+
+There also exists a helper script in ./tools to generate test results and test code coverage reports. These reports are placed in the `./target/tarpaulin` directory. If you use VSCode with the [Coverage Gutters](https://marketplace.visualstudio.com/items?itemName=ryanluker.vscode-coverage-gutters) extension, you can enable display of code coverage information with these settings:
+
+``` json
+  "coverage-gutters.coverageBaseDir": "**",
+  "coverage-gutters.coverageFileNames": [
+    "target/tarpaulin/lcov.info",
+  ],
+```
+
+## Contact
+
+Contact the project developers via the project's "dev" list.
+
+<https://accounts.eclipse.org/mailing-list/uprotocol-dev>