Language Selection

English French German Italian Portuguese Spanish

New FreeBSD code of conduct

Filed under
BSD
  • New FreeBSD code of conduct
    Dear FreeBSD community,
    
    The FreeBSD Project has adopted a new LLVM-derived code of conduct.  The
    new code of conduct can be found at
    
    https://www.freebsd.org/internal/code-of-conduct.html
    
    BACKGROUND
    
    Active FreeBSD developers were invited to complete two surveys related
    to our Code of Conduct.
    
    The first survey, conducted in 2018, told us that:
    
       - 94% of developers believe respectful communication in the project
         is important; 1% disagreed
    
       - 89% believe FreeBSD should be welcoming to people of all
         backgrounds; 2% disagreed
    
       - 73% say toxic people should be removed from the Project regardless
         of their technical contribution; 9% disagreed
    
       - 35% were dissatisfied with the code of conduct adopted in 2018, 34%
         were neutral, and 30% were satisfied.
    
    These results indicated that there was sufficient dissatisfaction with
    the current code of conduct to warrant investigation.  After reviewing
    other open source codes of conduct, the FreeBSD Core Team investigated
    adopting either an LLVM-derived or a Go-derived code of conduct.
    
    A second survey was held at the start of June and had only one question:
    
      Which code of conduct should FreeBSD adopt?
    
       - An LLVM-derived code of conduct:
         https://github.com/freebsd/core.10-public-docs/blob/master/CoC/llvm-based.md
    
       - A Go-Derived code of conduct:
         https://github.com/freebsd/core.10-public-docs/blob/master/CoC/golang-based.md
    
       - 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.
    
    THANK YOU
    
    Thank you to the LLVM and Go communities, and our impassioned members
    who helped champion this evolution.
    
    -- 
    FreeBSD Core Team
    
  • FreeBSD Adopts A New Code of Conduct Based On The LLVM CoC

    Following a survey of FreeBSD developers gauging interest in a new Code of Conduct and then a follow-up survey of keeping their current CoC versus adopting one similar to the LLVM or Go projects, FreeBSD has now settled on a new document.

    Some 35% of the FreeBSD developer community was dissatisfied with their 2018 Code of Conduct, 34% were neutral, and only 30% satisfied so they set out to adopt a new CoC.

FreeBSD switches Code of Conduct

  • FreeBSD switches Code of Conduct

    There’s a reporting mechanism, at least (later on in the document).

    The previous version of the FreeBSD CoC was based on the Geek Feminism CoC which put enforcement much of in-your-face. I liked that. Something else I miss in the new CoC is some explicit attention for trans- and non-binary rights: Geek Feminism puts that front-and-center as well. I must admit that when that CoC first showed up in my FreeBSD world I had to ask “what’s a deadname!?” And that was an education, and now I know.

    So while I’m happy that the FreeBSD community (which I’m part of) continues to take Codes of Conduct seriously, I’m a bit apprehensive about the new wriggle-room. Time will tell, and we’ll have a new democratic round for the CoC in due course.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Video/Audio: Feren OS 2020.07, Curl, Command Line Heroes and More Red Hat

  • Feren OS 2020.07 Run Through

    In this video, we are looking at Feren OS 2020.07. Enjoy!

  • Daniel Stenberg: Video: Landing code in curl

    A few hours ago I ended my webinar on how to get your code contribution merged into curl.

  • Command Line Heroes - Season 5, episode 3: What Kind of Coder Will You Become?

    The 10x Coder is often positioned as a mythical developer who can always save the day. Saron Yitbarek and Clive Thompson investigate how much of that myth is grounded in truth.

  • How Quarkus fits into the Red Hat Runtimes formula

    There are plenty of new features to talk about in the world of Red Hat Runtimes. When I recently had the chance to speak with James Falkner, technical product manager for Red Hat Runtimes, he zeroed in on the Quarkus framework, or more specifically, the Red Hat branded build of Quarkus.

  • What the Dev?

    This week, we spoke to Eric Schabell, the portfolio architect director at Red Hat, about Agile integration. A lot of enterprises are moving in the direction of Agile teams all with an eye on the digital transformation story where they're headed towards delivering things in a cloud native fashion. You'll hear some of the best ways in which to achieve that Agile integration.

Fedora: Kernel Testing, OpenShift OKD and Project Intern

  • Contribute at the Fedora Test Week for Kernel 5.8

    The kernel team is working on final integration for kernel 5.8. This version was just recently released and will arrive soon in Fedora. As a result, the Fedora kernel and QA teams have organized a test week from Monday, August 17, 2020 through Monday, August 24, 2020. Refer to the wiki page for links to the test images you’ll need to participate. Read below for details.

  • OpenShift OKD on Fedora CoreOS on DigitalOcean Part 1: Deployment

    This blog post is the second in a series that illustrates how to set up an OpenShift OKD cluster on DigitalOcean. The first post in the series covered some background information and pre-requisites needed for deploying a cluster. At this point you should have chosen the domain for your cluster, set up your registrar to point to DigitalOcean nameservers, installed all necessary software (doctl, openshift-install, oc, aws cli, etc..), and configured appropriate credentials in your environment (DIGITALOCEAN_ACCESS_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY).

  • Closing in on the end of the Summer

    Can you believe we’re two weeks through August already! And I’m so happy that my internship has been extended so last week isn’t my last week, even if it is the last full time week for awhile.

Linux Foundation Broadens Relationship With Surveillance

  • Facebook joins The Linux Foundation as a platinum member

    Most web-based companies are built on Linux and open-source software. Two-billion member social network Facebook is no different. For years, Facebook has not only relied on open-source, it's been an active contributor to major open-source projects. These include the React JavaScript library; the Open Compute Project, which open sources data-center hardware; and Linux's cGroup2 container software. Now Facebook is joining The Linux Foundation membership at the Platinum level. [...] While Facebook has been criticized for how it deals with privacy and politics, it has impeccable open-source credentials. It was already the lead contributor of many Linux Foundation-hosted projects, such as Presto, GraphQL, Osquery, and ONNX. The company also employs many Linux kernel key developers and maintainers.

  • Amundsen Joins LF AI as New Incubation Project

    LF AI Foundation (LF AI), the organization building an ecosystem to sustain open source innovation in artificial intelligence (AI), machine learning (ML), and deep learning (DL), today is announcing Amundsen as its latest Incubation Project.

  • LF AI Accepts Amundsen as Incubation Project

    The Amundsen data discovery project has joined the LF AI as an incubation project. Amundsen is a data discovery and metadata engine aiming to improve the productivity of data analysts, data scientists and engineers by indexing data resources. “Think of it as Google search for data,” the LF AI announcement said.

Graphics: Mesa 20.2 RC2 and DXVK 1.7.1

  • mesa 20.2.0-rc2
    Hi list,
    
    Available today is mesa 20.2.0-rc2. This is the second release candidate for
    the 20.2 release. Currently our open to close ratio on blocking bugs is looking
    really good. This release is dominated by changes to radeonsi, radv, and aco,
    with a few additional changes sneaking in for freedreno, meson,  etnaviv,
    st/mesa, anv, and a few utility fixes.
    
    Dylan
    
    
  • Mesa 20.2-RC2 Released With Many Fixes For RadeonSI + RADV Drivers

    The second weekly release candidate of the forthcoming Mesa 20.2 is now available for testing. Mesa 20.2 is aiming for release around the end of August or early September depending upon how the bug situation plays out. This quarterly feature release to Mesa3D brings many new Vulkan extensions, the RADV driver using ACO by default, initial support for Navi 2 GPUs, initial support for Intel Rocket Lake and DG1, OpenGL 4.3 for LLVMpipe, and much more as outlined in last week's article.

  • DXVK 1.7.1 Released With Many Game Fixes For Direct3D Over Vulkan

    It's been nearly three months without a new DXVK release for mapping Direct3D 9/10/11 atop the Vulkan API while finally today there is a big feature release out. DXVK 1.7.1 was released a few minutes ago as the first update since May. While the version number isn't significant, this version does have many changes.

  • Direct3D to Vulkan translation layer DXVK 1.7.1 is out, lots of game fixes

    After a few months since 1.7 went out, DXVK 1.7.1 is now live to further improve Direct3D to Vulkan translation. This is the project that helps to power Proton, the compatibility layer for Steam Play. This release adds support for newer Vulkan extensions, fixes bugs and has new GPU driver requirements. On the driver side, the VK_EXT_transform_feedback extension is now required which has been supported in drivers on Linux since late 2018 / early 2019. Specifically you will need at least NVIDIA 415.22 and for AMD / Intel it looks like Mesa 19 covers both.