This is the ideal. And I have done so when I can. But you're missing a step: > Fork, understand, fix, create PR That 2nd step is more time-consuming for some

This is the ideal. And I have done so when I can. But you're missing a step: > Fork, understand, fix, create PR That 2nd step is more time-consuming for some dependencies than others. I'm a strong proponent for understanding how your dependencies work, but there are always limits to the depth of knowledge of the internals of every one.