One of the saddest parts of an #opensource maintainer's life is having to reject PRs, sometimes thousands of lines long, for no better reason than "this is not the project's direction right now and it will interfere with what we're working on".
I don't know where the "write code first ask questions later" approach came from, but I really wish we'd communicate with each other more. The fallout of not doing so isn't fun for anyone.
@imsnif in some (many?) cases the feature in the PR is going to be written regardless of whether a maintainer wants it or not because that's the feature some paid them to add or their personal project/side hustle needed. What many contributors are hoping is someone else maintains and improves the feature as the project moves forward so they don't have to maintain a fork.
Add comment