I don’t think it would’ve in our case, at least. I actually quite like our OSS policy: basically, we don’t want to be in the business of maintaining forks, so all changes should try to get upstreamed if at all possible. It‘s good client service as well: when our clients ask about the libraries we use, we’d much rather be able to tell them “the latest public version” than “here’s our fork”.
We also want to engage with and donate to the projects we use, mostly out of risk management: if they go unmaintained that’s bad for us.
We also want to engage with and donate to the projects we use, mostly out of risk management: if they go unmaintained that’s bad for us.