You are right downvoting me, I did not specify my reasoning. Basically contributing features you need in a very large project that you did not initiate yourself

You are right downvoting me, I did not specify my reasoning. Basically contributing features you need in a very large project that you did not initiate yourself, leads to "featurism", more code to handle in the future, certain specific needs you accept mostly since they were contributed and saying no sometimes is hard. Instead work not interested to solve specific use cases tend to be consolidation work, or big general features work at least, where the goal is to fix something or do the right thing in some area, considering the whole public of such system, not your local needs. So the two approaches lead to different software philosophies and outcomes.