We believe that the best way to build software is to do it in close collaboration with the people who use it. We invite you to submit your ideas using the form below. Please be sure to include the problem for which you are solving and the benefits of implementing the idea.
We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories: will integrate into the product roadmap, further research is needed, unlikely to implement.
Thanks for collaborating with us!
Currently, we only supply ruby-plus-devkit for Windows clients that want to utilize Ruby in their habitat or effortless builds. This package is huge, and when updating it can take down networks and on-prem builders with the amount of traffic it generates at scale.
There are clients who would like to use ruby without the dev kit in their on-prem package builds. There would also be advantage to releasing chef/chef-infra-client without a dependency on devkit. The reason given for using devkit was that it's needed if customers need to build gems. They can't currently build gems on Windows systems in traditional chef-client, so why are we forcing a huge package on them for effortless? They could easily build their own chef-infra-client package if it turns out they do need that gem compiling capability.