4 ms·
Exactly right — and I think his intro explains the difference: if you’re used to working on closed source projects, you have dedicated staffing to deal with thi
by acdha 5y ago
Exactly right — and I think his intro explains the difference: if you’re used to working on closed source projects, you have dedicated staffing to deal with this ongoing work and it’s likely that all of the parties involved work for the same place. Open source maintainers rarely have anywhere near that much available time and will get random complaints from people around the world saying that their project sucks because some unreleased version of GCC on RISC-V gets a warning[1]. For cases like this, I generally go back to what the goal is: helping the developers be safer – turning it on in CI testing is nice because it gives feedback when you’re already working on it, but having it in build scripts run by strangers is inviting support requests.
1. This will take a couple weeks of back and forth before the person who filed it either updates to the latest version or admits that the error was in a modification they were working on.