There are many cases of (former) opscode-cookbooks that have such „easy“ PRs waiting but wont get merged - for months. IMHO most cookbooks don’t lack PRs and issue reports but maintainer activity or willingness to adopt new maintainers if the current ones don’t have enough time or motivation anymore (which is fine, it’s OSS and shouldn’t be a burden). For example you may want to check your github notifications on the nginx cookbook (afaik you’re co-mainainer). I’ve worked through many open, unanswered issues last week to help users. Because I’m not a maintainer I cannot close issues or merge PRs so my efforts can’t bring any sustainable improvement. That’s why I can fully understand that many chef users become angry and or leaving chef behind. I clearly don’t understand Chef, inc. here… and I’m getting humiliated by Ansible users regularly when I try to present Chef :-( regards Roland |
Archive powered by MHonArc 2.6.16.