my first thought exactly. however I mostly find that many devs simply put workarounds out of the library (and suffer great pains when update time comes) or fix

my first thought exactly. however I mostly find that many devs simply put workarounds out of the library (and suffer great pains when update time comes) or fix the library and never push the changes upstream consider that many fixes, even when proper, may not be ready for submission, and many companies are penny pinching devs already and can hardly justify prettying up a fix for submission and prefer to establish a culture of 'fix it in the least amount of time'. two days are a reasonable amount of time to get existing fixes in the codebase, clean them up to the library owner's guidelines, document them, the issue they solve, build a test case and deliver it upstream. two days are not enough for coding a workaround, and barely the minimum to prepare a patch properly. that I think was the intent. as you say devs need to fix up things anyway, and two day a month to push upstream goes a long way to reduce work further the line (and I'm purposely ignoring the 'do good' argument)