I completely understand the feeling about focus and slowing down.
I referred to this above, but big partners working on meaty objectives is actually a positive success criteria that the governance model is built for.
That said, we try very hard to ensure that the flow of the project remains unencumbered.
Docker is a community project; one of the beautiful benefits of that is that Docker can change as long as you can reach critical consensus on any design proposal.
Without the partnership, Docker could be brought to Windows at some undetermined point in the future as soon as those native capabilities existed.
With the partnership, we have a set of dedicated Engineers from Microsoft and the community who are eager to build consensus around getting Docker integrated to the new API/Services that they're creating as soon as possible.
There's no free lunch - if the contributions don't stand the scrutiny of the maintainers, they will continue to work with them until it does.
I referred to this above, but big partners working on meaty objectives is actually a positive success criteria that the governance model is built for.
That said, we try very hard to ensure that the flow of the project remains unencumbered.
Docker is a community project; one of the beautiful benefits of that is that Docker can change as long as you can reach critical consensus on any design proposal.
Without the partnership, Docker could be brought to Windows at some undetermined point in the future as soon as those native capabilities existed.
With the partnership, we have a set of dedicated Engineers from Microsoft and the community who are eager to build consensus around getting Docker integrated to the new API/Services that they're creating as soon as possible.
There's no free lunch - if the contributions don't stand the scrutiny of the maintainers, they will continue to work with them until it does.
I hope that helps - happy to discuss further!