I had to ask the maintainers of an open source project today: what's a reasonable cadence for me to submit PRs? I have SO MANY THINGS I want to contribute, but I don't want to overload you.
As a maintainer, it's clear that the best PR is small and clearly described. But even the…
Commit
952ff2e
As a maintainer, the best PR is that one that resolves a clear pain in the software. Not a small fix, or polishing some detail you like, but something that adds raw value.
How often?
The more you do, the more you understand, the more we trust your judgement.
What's the worst…
Couldn't disagree more. Issues are, and have always been, valuable. Assuming everyone has the same access to and efficacy with AI is a mistake.
I also don't agree that the best PR is *simply* one that resolves a clear pain in the software. Many bad PRs attempt to resolve clear pains but do so poorly. That's still a bad PR.
commit 952ff2e