add vendor neutrality policy

This commit:
 - adds both a vendor neutrality declaration and explains Metal3-io's vendor
   neutrality related to hardware, feature and development infrastructure.

Signed-off-by: Adam Rozman <[email protected]>

VENDOR_NEUTRALITY.md

@@ -0,0 +1,33 @@
+# Metal3-io vendor neutrality declaration
+
+As a Cloud Native Computing Foundation project, Metal3-io will keep its
+[vendor neutrality](https://contribute.cncf.io/maintainers/community/vendor-neutrality/)
+
+**Hardware vendor neutrality**
+As it is stated in the [documentation](https://book.metal3.io/) Metal3-io is a
+CNCF project with a goal to provide bare metal life cycle management
+functionality regardless of the vendor of the  hardware. The only requirement
+is that the machines are equipped with a[BMC](https://www.servethehome.com/explaining-the-baseboard-management-controller-or-bmc-in-servers/)
+and support either [Redfish](https://redfish.dmtf.org/) or [IPMI](https://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface)
+protocols. Metal3 also supports vendor specific versions of the aforementioned
+protocols but that support is on top of the standard protocols and the reason
+is to provide full hardware compatibility  across the widest range of vendors
+possible.
+
+**Feature vendor neutrality**
+Metal3 features are developed with the specific aim to manage the life cycle
+of bare metal machines and  K8s clusters on top of those machines thus the
+Metal3  stack by nature only supports so called "self-hosted" scenarios,
+none of the Metal3's features require any sort of commercial infrastructure
+provider service (e.g. AWS, Azure etc...) to be usable. In regards to feature
+support for specific hardware it has to be mentioned that all of the
+functionality provided by Mteal3-io is hardware vendor agnostic.
+
+**Developement vendor neutrality**
+The Metal3-io community has decided to make its' own CI/CD/Q&A utilize
+CNCF resources as much as possible in order to not rely on any external
+organization to host the project's development infrastructure. There are
+certain development and Q&A use cases that  still require computational
+resources outside of the scope of the CNCF but those resources are provided by
+the maintainer organizations (Ericsson) and the long term goal is to minimize
+and if possible eliminate  such use cases.