3 ms·
I don't understand this comment, every single software project in existence is like that. The pacing and threshold of what they'll accept is just different betw
by BrightGlow 5y ago
I don't understand this comment, every single software project in existence is like that. The pacing and threshold of what they'll accept is just different between projects. If you had some patches that get rejected, that's unfortunate. But that's a risk you take with any project, and you're also asking the developers to take a risk by accepting your patch. Some may have higher risk tolerance than others.
- grandinj 5y agoAnd by rejecting patches that don't match up with "your way" you risk of alienating talent and resources that could have improved your project.
- BrightGlow 5y agoYes that's true. But by accepting an unusual patch you could also risk having a feature that doesn't fit in well with the rest of the project, breaks something unexpected in another area of the project, takes up a lot of maintainer time that could be spent on other things, could break further in the future and need to be removed, which would further upset the users... So it's a trade-off that every project must decide to make in their own way. AFAIK it's not possible for a project to bend to every potential contributor's will, else the project drifts into the old unmaintainable big ball of mud. If you knew a way to develop software like that where everyone could get their way all the time, please let me know, we could turn that into a product and get really rich selling it to every software company.