3 ms·
>How does backward compatibility mean a project is unhealthy? It doesn't mean it is, yes. Compat or not isn't a "healthy metric" at all. >How is someone who s
by wut42 4y ago
>How does backward compatibility mean a project is unhealthy?
It doesn't mean it is, yes. Compat or not isn't a "healthy metric" at all.
>How is someone who shows up and volunteers to help not a contributor by default?
As a maintainer of a serious project, would you accept a PR adding back backward compatibility, with the premises of "i'll maintain it", from a random person ? It's not an healthy decision at all for the project to accept that, actually, depending on the project and the implications.
- phendrenad2 4y agoSo what does one need to do in order to go from "random person" to "accepted contributor"? Do I need to fix typos on the README for awhile? Do I need to fix random bugs for awhile? Or do I need to go to work for the company that sponsors the project? We shouldn't automatically assume that a more restrictive approach is more "healthy" here. It all comes with tradeoffs.
- wut42 4y agoYes, it was the point I was trying to make: it all comes with tradeoffs. Sidekiq choosed to not go forward with backwards compat, and I don't feel it make them "bad citizens" like you implied in your original comment.