Initial stub for conventions for devices (#284)

* Conventions for devices

* Update Devices-conventions.md

* Update Devices-conventions.md

* Update Devices-conventions.md

* Fix casing

Documentation/Devices-conventions.md

@@ -0,0 +1,25 @@
+# Conventions for devices APIs
+
+## Value returned by sensor
+
+- Prefer property (i.e. Temperature) rather than method (i.e. GetTemperature)
+- Use `double` when you need to return any floating point value
+- Use `Vector2/3/4` for returning vectors`*`
+- Value should conform to units conventions (see below)
+- Only the most useful APIs should be public, anything else which may be useful but will unlikely get used by most of the people should be protected (inheriting the class allows you to use it but it is not visible by default) or internal/private
+- Constructor should only require parameters it cannot work without - anything else should be a default value
+  - For more advanced settings or devices which require many parameters using designated Settings class is recommended
+- Invalid/unassigned pin should have number `-1` (as opposed to `Nullable<int>`)
+- If your device has internal register create an enum for the addresses (i.e. `enum Register : byte`)
+
+`*` -  Vector3 is currently backed by float, this may be changed in the future: https://github.com/dotnet/corefx/issues/25334
+
+## Units
+
+In the most common case units should match [International System of Units (aka. SI)](https://en.wikipedia.org/wiki/International_System_of_Units) with some exceptions:
+
+- Celsius should be used for temperature
+
+## Notes
+
+If you believe for your specific device it makes sense to break any of the rules it might be acceptable - please make sure to mention that in the pull request description.