Policy documentation

[PeterJohnson]

Document what types of vendordeps will be accepted into this repo, and if there are other indicators (e.g. blue checkmarks ala the vscode extension marketplace) that should be added to indicate what are vendor-supported items vs team or community maintained. Also determine whether other indicators would be helpful to teams looking for what to install outside of basic hardware support, such as download counts or star ratings.

[sciencewhiz]

Another consideration is whether we only want the authors of the vendordep to contribute, or let anyone PR a vendordep. For example in #81, someone PRed a vendordep the vendor wasn't ready to release.

[ThadHouse]

I'd 100% say anything that is a control system hardware driver (Which that one was) needs to be done by the vendor. And also that supporting specifically legal control system hardware must inherently come with some sort of support from the vendor.

[jasondaming]

I don't mind anyone PRing it but I think the owner should have to publicly bless it before we accept it. Really the owner should just PR it cause it isn't hard!