There are bad practices that no one should do when they get involved in opens source communities.
In this segment of the My Open Source Experience podcast Greg Kroah-Hartman shares three examples from Linux history where people followed some bad patterns, which then somtimes resulted in raising the bar for everyone else.
1. Merge and Disappear
Greg shares an example where someone contributed a big change to the core parts of the kernel, and then became unreachable. It took the Linux community quite some time to unwind the changes and clean up the code. All open source communities are based on trust, when someone betrays that they make it harder for other to build trust as well. The community is more flexible with changes that are well isolated, like a filesystem or a driver, but you still can't betray peopl's trust with any of your actions during the contrubution process.
2. Binary drivers
It's a NO, you also don't want that, but also, you just can't. Some companies used to apply a trick, but they've been coming around as well.
3. Never experiment on a community, especially without a consent
Greg shares the interesting story when a university professor and some students went ahead and wrote a paper about submitting and landing patches in the Linux kernel that introduced vulnerabilities. It turned out that they weren't truthful in their paper, and also forgot to notify everyone about the experiment. While the university was banned for a while, this turned out to be a story with a happy ending with students now contributing to the kernel as part of their studies.
Further advantage of open source SW development methods is that the change history is available online, the community can always go back and remove code if a controller becomes untrustworthy at any point in time after getting their changes merged.
#opensource #community #collaboration #experience #podcast
Hosted on Acast. See acast.com/privacy for more information.