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!
I am a frequent user of the public cookbook supermarket (As I believe most of the chef consumers are). I've recently noticed the cookbook rating system which apparently relies on the foodcritic. foodcritic is no longer able to make proper syntax checks.The supermarket also isn't looking at metadata.rb correctly and likely not even policyfile. It is my understanding that the new best practice for linting and correcting your chef code is cookstyle.
The supermarket should be delivering code that is created following chef best practices. If the public supermarket is using deprecated testing, we run the risk of delivering broken code to the public. While I would hope most users would test the code before pushing it, this could still potentially cause a breaking change.
I understand that this wouldn't be a simple change to the code, I do believe there should be some serious attention given to it though. This would benefit not only customers but, the entire OSS community as well.
This will be part of the upcoming 5.0 release
Attachments Open full size