FreeBSD

FreeBSD and Its Code of Conduct Anniversary

The FreeBSD Foundation posted its Code of Conduct on February 13, 2018. It included a system for reporting offenders as well as a code of conduct committee to review charges and issue sanctions. The story, which appeared on Slashdot on February 17, triggered 859 comments. Needless to say, it was controversial.

FreeBSD and Its Code of Conduct Anniversary

In 2020, a survey indicated that about 35% of the FreeBSD developer community were dissatisfied with their 2018 code of conduct, 34% were neutral, and only 30% were satisfied. So they set out to adopt a new COC. Another survey asked what code of conduct FreeBSD should adopt. 4% supported retaining the 2018 Code of Conduct, 33% supported the Go-derived Code of Conduct, and 63% supported the LLVM-derived Code of Conduct. The LLVM project code was adopted as such.

FreeBSD and Its Code of Conduct Anniversary

As a practical question, in 2018, I asked: Will this CoC lead to a better FreeBSD, more engagement, a larger, more productive community, and more market share? In other words, does CoC give FreeBSD an evolutionary advantage? Would FreeBSD be any different today if a different COC had been implemented? If so, in what way? The answer is not clear, so I present this story to gather input.

FreeBSD and Its Code of Conduct Anniversary

Read Also: Dom Hofmann’s Loot, With NFTs Of Random Lists Of Items Ostensibly From A Fantasy Video Game, Had $46M In Sales In Just 5 Days, Attaining A Market Cap Of $180M+ (Andrew Thurman/CoinDesk)

FreeBSD and Its Code of Conduct Anniversary
freebsd its code anniversary
freebsd code anniversary
freebsd its conduct anniversary
freebsd its anniversary
its code conduct anniversary
freebsd code conduct anniversary
freebsd conduct anniversary
freebsd its code conduct anniversary
freebsd its code conduct
freebsd its conduct
code conduct anniversary
freebsd its code
freebsd code conduct
freebsd anniversary