Language Selection

English French German Italian Portuguese Spanish

Gentoo's Proposed Code of Conduct Adopted

Filed under
Gentoo

In no small part due to the wide exposure of a high-profile article published earlier in the week on in-fighting and other disgraceful behaviors from developers and contributors, Gentoo announced a proposed Code of Conduct. Today, a vote on the proposed Gentoo Code of Conduct passed with votes tallying 6 to 1.


Some of the guidelines include:

Acceptable behaviour

Be courteous. Though respect is earned, it must start somewhere. Respect someones right for their own opinion and acknowledge that they do deserve a measure of politeness in your response.

Give accurate information in the spirit of being helpful.

Respectfully disagree with or challenge other members. The operative word here is respectfully.

Using the correct forum for your post. Bug reports and idle chatter do not belong on the gentoo-dev mailing list; discussion about a wide-ranging change to the tree probably does not belong on Bugzilla. Different fora will also have different standards of behaviour -- a joke that is perfectly acceptable on IRC will be taken differently when made on a mailing list.

Admit the possibility of fault and respect different point of views. No one is perfect -- you will get things wrong occasionally. Don't be afraid to admit this. Similarly, while something may seem perfectly obvious to you, others may see it differently.

If you screw up, take responsibility for your actions.

Unacceptable behaviour

Flaming and trolling. What is trolling? You are deemed to be trolling if you make comments intended to provoke an angry response from others. What is flaming? Flaming is the act of sending or posting messages that are deliberately hostile and insulting.

Posting/participating only to incite drama or negativity rather than to tactfully share information.

Being judgmental, mean-spirited or insulting. It is possible to respectfully challenge someone in a way that empowers without being judgemental.

Constantly purveying misinformation despite repeated warnings.


Disciplinary action can be imposed and will be up to the discretion of an official charged with the duty of maintaining good order. Breaches of the Code of Conduct guidelines can be reported to the proctors.

Full Document here

re: Gentoo

Isn't it fun watching a bunch of little children acting like grownups?

The only thing that "document" left out was "double dog dare you" rules and whose mother was going to take everyone home if they continued to misbehave.

How sad that a once bleeding edge distro falls into such disarray and childish behavior.

Business geeks the world over must look at projects like this and just laugh their collective asses off. Perhaps one of them will be kind enough to loan these guys a copy of "Business Management for Dummies" book.

re: Gentoo

Not really on topic to what you said, but I got to say how much better things are running with site under debian. Just one example, used to in gentoo when the nightly backups/crons would run, my site would just almost stop. Tar and cp would use up a good deal of the resources. I had them set up to run at nice 19, but still it was miserable. When the backups run now under debian, it doesn't even breath hard. In fact, the whole of memory management is handled much better in debian. Sure I was still using a 2.4 kernel on the server under gentoo, but copying large files under 2.6 on my desktop will make other things practically unusable until it's done. A few folks have told me that site seems to be faster now. I don't know what's up exactly, but I'm really glad I made the switch.

re: Gentoo

I guess it's not just me then. It's not perfect, but the pages are loading a -lot- better than they used to. Before, sometimes I would give up because it loaded so slow (no offense!) but now it's far easier to navigate. I am surprised it make such a big difference. Good to note.

Comment viewing options

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

More in Tux Machines

Leftovers: OSS

  • Anonymous Open Source Projects
    He made it clear he is not advocating for this view, just a thought experiment. I had, well, a few thoughts on this. I tend to think of open source projects in three broad buckets. Firstly, we have the overall workflow in which the community works together to build things. This is your code review processes, issue management, translations workflow, event strategy, governance, and other pieces. Secondly, there are the individual contributions. This is how we assess what we want to build, what quality looks like, how we build modularity, and other elements. Thirdly, there is identity which covers the identity of the project and the individuals who contribute to it. Solomon taps into this third component.
  • Ostatic and Archphile Are Dead
    I’ve been meaning to write about the demise of Ostatic for a month or so now, but it’s not easy to put together an article when you have absolutely no facts. I first noticed the site was gone a month or so back, when an attempt to reach it turned up one of those “this site can’t be reached” error messages. With a little checking, I was able to verify that the site has indeed gone dark, with writers for the site evidently losing access to their content without notice. Other than that, I’ve been able to find out nothing. Even the site’s ownership is shrouded in mystery. The domain name is registered to OStatic Inc, but with absolutely no information about who’s behind the corporation, which has a listed address of 500 Beale Street in San Francisco. I made an attempt to reach someone using the telephone number included in the results of a “whois” search, but have never received a reply from the voicemail message I left. Back in the days when FOSS Force was first getting cranked up, Ostatic was something of a goto site for news and commentary on Linux and open source. This hasn’t been so true lately, although Susan Linton — the original publisher of Tux Machines — continued to post her informative and entertaining news roundup column on the site until early February — presumably until the end. I’ve reached out to Ms. Linton, hoping to find out more about the demise of Ostatic, but haven’t received a reply. Her column will certainly be missed.
  • This Week In Creative Commons History
    Since I'm here at the Creative Commons 2017 Global Summit this weekend, I want to take a break from our usual Techdirt history posts and highlight the new State Of The Commons report that has been released. These annual reports are a key part of the CC community — here at Techdirt, most of our readers already understand the importance of the free culture licensing options that CC provides to creators, but it's important to step back and look at just how much content is being created and shared thanks to this system. It also provides some good insight into exactly how people are using CC licenses, through both data and (moreso than in previous years) close-up case studies. In the coming week we'll be taking a deeper dive into some of the specifics of the report and this year's summit, but for now I want to highlight a few key points — and encourage you to check out the full report for yourself.
  • ASU’s open-source 'library of the stars' to be enhanced by NSF grant
  • ASU wins record 14 NSF career awards
    Arizona State University has earned 14 National Science Foundation early career faculty awards, ranking second among all university recipients for 2017 and setting an ASU record. The awards total $7 million in funding for the ASU researchers over five years.

R1Soft's Backup Backport, TrustZone CryptoCell in Linux

  • CloudLinux 6 Gets New Beta Kernel to Backport a Fix for R1Soft's Backup Solution
    After announcing earlier this week the availability of a new Beta kernel for CloudLinux 7 and CloudLinux 6 Hybrid users, CloudLinux's Mykola Naugolnyi is now informing us about the release of a Beta kernel for CloudLinux 6 users. The updated CloudLinux 6 Beta kernel is tagged as build 2.6.32-673.26.1.lve1.4.26 and it's here to replace kernel 2.6.32-673.26.1.lve1.4.25. It is available right now for download from CloudLinux's updates-testing repository and backports a fix (CKSIX-109) for R1Soft's backup solution from CloudLinux 7's kernel.
  • Linux 4.12 To Begin Supporting TrustZone CryptoCell
    The upcoming Linux 4.12 kernel cycle plans to introduce support for CryptoCell hardware within ARM's TrustZone.

Lakka 2.0 stable release!

After 6 months of community testing, we are proud to announce Lakka 2.0! This new version of Lakka is based on LibreELEC instead of OpenELEC. Almost every package has been updated! We are now using RetroArch 1.5.0, which includes so many changes that listing everything in a single blogpost is rather difficult. Read more Also: LibreELEC-Based Lakka 2.0 Officially Released with Raspberry Pi Zero W Support

Leftovers: Gaming