Doesn't talk much, but if I do it'll likely be about CS, soccer, or Breton music.
It's a generalization of the previous points, really.
I don't have a lot of time, so I'll usually spend my time on getting things done. If you post PRs that need hours to review and/or a lot of back&forth, you'll automatically gravitate to the back of the queue.
It's a generalization of the previous points, really.
I don't have a lot of time, so I'll usually spend my time on getting things done. If you post PRs that need hours to review and/or a lot of back&forth, you'll automatically gravitate to the back of the queue.
The notion of "necessary" varies, but essentially, don't include spurious reformatting, typo changes, drive-by bugfixed in neighbouring areas. Those can be their own PRs. Light refactoring *might* be OK if it makes your actual change easier.
The notion of "necessary" varies, but essentially, don't include spurious reformatting, typo changes, drive-by bugfixed in neighbouring areas. Those can be their own PRs. Light refactoring *might* be OK if it makes your actual change easier.
That's especially important for new features. New features means new code, and maintenance burden increases along with the size of the codebase. While you might intend to stick around to maintain it, I don't *know* that and statistics are not in your favor.
That's especially important for new features. New features means new code, and maintenance burden increases along with the size of the codebase. While you might intend to stick around to maintain it, I don't *know* that and statistics are not in your favor.