Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Wednesday June 10 2020, @01:46PM   Printer-friendly
from the setting-a-breakpoint-so-humans-can-try-to-debug-a-code-(of-conduct) dept.

FreeBSD has announced a new LLVM-derived code of conduct.

According to a 2018 survey "35% were dissatisfied with the code of conduct adopted in 2018, 34% were neutral, and 30% were satisfied." So, they held another survey at the start start of June:

Which code of conduct should FreeBSD adopt?

Retain the current code of conduct:
https://web.archive.org/web/20200108075747/https://www.freebsd.org/internal/code-of-conduct.html

RESULTS

  • 4% favoured keeping the current code of conduct
  • 33% favoured the Go-derived code of conduct
  • 63% favoured the LLVM-derived code of conduct.

Thus, the Core Team, following the preference of a majority of active
FreeBSD developers, adopted the LLVM-derived code of conduct.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Interesting) by meustrus on Wednesday June 10 2020, @04:43PM (1 child)

    by meustrus (4961) on Wednesday June 10 2020, @04:43PM (#1005864)

    Oh, he wasn't kicked out based on a CoC, you'll say. But he would be under FreeBSD's CoC, no doubt using the same logic Mozilla used.

    The logic Mozilla used is that their former CEO's political leanings was a bad look for the company. He was a prominent representative of the company, and they decided that their market would punish the company for the politics of its representative.

    Not saying it's impossible for a lowly coder to be kicked out for the same politics. It's possible, though unlikely, for a prominent enough coder to create a similar PR problem. I don't think it would be covered by CoC, though, since everything is outside of development communication channels.

    But I don't support that political position, you say, so he ought to be punished.

    I can't speak for everyone, but I personally don't believe people ought to be punished for their beliefs. Punished for creating unnecessary arguments about politics in development communication channels, absolutely. But not for anything a person believes or says outside the project. Up to and including allowing contributions from convicted serial killers, as long as they aren't going around talking about the importance of culling the weak or whatever batshit craziness they believe.

    How on earth did engineering organizations get along CoC free before?

    Well, the assholes brought their asshole ideology to the project, and anybody that didn't like it left. Not a whole lot of people like it, though, so the project would then belong solely to the assholes.

    This could work for a project with solid requirements. Throw it over the fence, get back good code. But it doesn't work so well when you have to communicate with users. Nobody wants to deal with the assholes. It's a great way for a project to die in obscurity.

    --
    If there isn't at least one reference or primary source, it's not +1 Informative. Maybe the underused +1 Interesting?
    Starting Score:    1  point
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 1, Insightful) by Anonymous Coward on Sunday June 14 2020, @01:58PM

    by Anonymous Coward on Sunday June 14 2020, @01:58PM (#1007751)

    He hadn't merely donated to anti-Gay Marriage. He'd donated enough that it had to be reported as a political contribution (I forget if it was 1k or 10k, but it was a LOT OF MONEY), which is what lead to the internal politicking when it came out. This wasn't merely having a differing opinion, this was paying a donation sufficient to pay any of their developers for 2-3 months, and was about to increase his salary into the 6 figures. Mozilla's pay scales are insane for middle and upper management compared to the people actually producing the code. And if we want to talk about HIS code contributions: Javascript. If that isn't reason enough to fire him, I don't know what is!)