-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
import and merge vmware drivers? #5
Comments
@anfernee WDYT? |
@SvenDowideit and @gbraad our team is still in discussion where to host the drivers. should all drivers be in this organization or under the individual company's org. Is this organization a foundation or something? |
look forward to get working minikube with vmware workstation 😉 |
we are not a foundation, but rather a community representation. we are doing this with the ideal of keeping maintenance available to all drivers as they are part of this organization, as too often (even for company repos) we have seen deprecation or low maintenance/stganation while the community was/is more than willing to take over. |
but - if joining a foundation, or something like that helps, we'd be open to talking about it :) |
anyway, let's put the working code and testing infrastructure together first. I personally don't really mind where it lives as long as it is working ;) |
I believe we should start this process by moving @anfernee code into its own repo under |
I do not want to introduce a fork, but rather see the driver author doing
so himself.
|
In that case... Yes, please... Go ahead! |
sorry for the delay. occupied with events internally. The vmware repo is online. It basically works. And we need to work on docs, contributing guide, testing on different platforms, etc. We'll track those inside that repo. |
I think we can close this issue and create new issues accordingly in the driver or this discussion repo. |
kubernetes/minikube#2118
cos its really weird to have so many
The text was updated successfully, but these errors were encountered: