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

Graphics News

More of today's howtos

GNOME News: Black Lab Drops GNOME and Further GNOME Experiments in Meson

  • Ubuntu-Based Black Lab Enterprise Linux 11.0.1 Drops GNOME 3 for MATE Desktop
    Coming about two weeks after the release of Black Lab Enterprise Linux 11, which is based on the Ubuntu 16.04.2 LTS (Xenial Xerus) operating system using the HWE (hardware enablement) kernel from Ubuntu 16.10 (Yakkety Yak), Black Lab Enterprise Linux 11.0.1 appears to be an unexpected maintenance update addressing a few important issues reported by users lately.
  • 3.26 Developments
    My approach to development can often differ from my peers. I prefer to spend the early phase of a cycle doing lots of prototypes of various features we plan to implement. That allows me to have the confidence necessary to know early in the cycle what I can finish and where to ask for help.
  • Further experiments in Meson
    Meson is definitely getting more traction in GNOME (and other projects), with many components adding support for it in parallel to autotools, or outright switching to it. There are still bugs, here and there, and we definitely need to improve build environments — like Continuous — to support Meson out of the box, but all in all I’m really happy about not having to deal with autotools any more, as well as being able to build the G* stack much more quickly when doing continuous integration.

Fedora and Red Hat