Language Selection

English French German Italian Portuguese Spanish

Gentoo fights flamewars and bad behaviour!

Filed under
Gentoo

Triggered by recent examples of bad behavior and dissatisfaction among developers and users alike, the Gentoo Council has drafted a new Code of Conduct that will be enforced for both developers and users.

The draft version of the Code of Conduct is currently being discussed on the Gentoo-dev mailing list. To subscribe, send an email to gentoo-dev+subscribe@lists.gentoo.org or read the archive. The Code of Conduct will be voted upon by the Gentoo Council Thursday, March 15th; implementation will be immediate upon final approval. The Code of Conduct describes what the Gentoo Council has deemed acceptable and unacceptable behavior. It also describes the punishment that will be enforced if the Code of Conduct is breached. The Gentoo Council expects the Code of Conduct to end the bad behavior shown by some and hope it will help Developer Relations enforce good behavior among the developers. The Gentoo Council has scheduled a Question and Answer session Wednesday, March 14th between 2100UTC and 2300UTC in the #gentoo-council channel on the Freenode IRC network, irc://irc.freenode.net. We welcome all interested parties to participate in the Question & Answer session.

From the Gentoo Weekly Newletter.

Gentoo's Code of Conduct.

More in Tux Machines

Android Leftovers

Security: Updates, SOS Fund, IR, ME, and WPA

  • Security updates for Friday
  • Seeking SOS Fund Projects
    I’m spending some time over the next few days looking for the next round of projects which might benefit from an SOS Fund security audit.
  • Strong Incident Response Starts with Careful Preparation
    Through working every day with organizations’ incident response (IR) teams, I am confronted with the entire spectrum of operational maturity. However, even in the companies with robust IR functions, the rapidly evolving threat landscape, constantly changing best practices, and surplus of available tools make it easy to overlook important steps during planning. As a result, by the time an incident occurs, it’s too late to improve their foundational procedures.
  • The Intel Management Engine: an attack on computer users' freedom
    Over time, Intel imposed the Management Engine on all Intel computers, removed the ability for computer users and manufacturers to disable it, and extended its control over the computer to nearly 100%. It even has access to the main computer's memory.
  • What Is WPA3, and When Will I Get It On My Wi-Fi?
    WPA2 is a security standard that governs what happens when you connect to a closed Wi-Fi network using a password. WPA2 defines the protocol a router and Wi-Fi client devices use to perform the “handshake” that allows them to securely connect and how they communicate. Unlike the original WPA standard, WPA2 requires implementation of strong AES encryption that is much more difficult to crack. This encryption ensures that a Wi-Fi access point (like a router) and a Wi-Fi client (like a laptop or phone) can communicate wirelessly without their traffic being snooped on.

First Impressions: Asus Tinkerboard and Docker

The board's standard OS is TinkerOS - a Linux variant of Debian 9. I've also read that Android is available but that doesn't interest us here. While Android may use forms of containerisation under the hood it doesn't mix with Docker containers. Rather than trying TinkerOS I flashed Armbian's release of Ubuntu 16.04.03. The stable build on the download page contains a full desktop, but if you want to run the board headless (like I do) then you can find a smaller image on the "other downloads" link. I initially used the stable image but had to swap to the nightly build due to a missing kernel module for Kubernetes networking. Having looked this up on Google I found the nightly build contained the fix to turn on the missing module. Read more

today's howtos