dra-evolution: "vendor" vs. "driver developer"

[pohly]

#14 and also KEPs sometimes talk about a "driver vendor". Sometimes "driver developer" is used instead. We should pick one and use it consistently.

Advantage of "vendor": familiar term, matches well with "hardware vendor".
Disadvantage: some drivers maintained by an open source developer or community don't have a vendor.

Disadvantage of "driver developer": that sounds like the person doing the work, which is not appropriate in some places ("Driver name must be a DNS subdomain and should end with a DNS domain owned by the vendor of the driver.").

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[pohly]

I think "vendor" has won in terms of popularity.

/close

[k8s-ci-robot]

@pohly: Closing this issue.

In response to this:

I think "vendor" has won in terms of popularity.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.