Channel Rules2017-05-18T16:03:08+00:00

Channel Rules

Please be polite to each other, and remember that you are in a channel which is mostly intended for discussion about Linux®.

Rules: ##Linux

  • English only. English does not include SMS-style abbreviations as these are hard for non-native speakers to follow.
  • Be nice. Abusive, insulting, derogatory, condescending and demeaning language use towards channel users is not allowed.
  • Elitism is also not allowed, and includes bashing other channel participants for their choice of distro.
  • Posting a destructive command is a bannable offence.
  • Foul language is strongly discouraged, excessive use of foul language is not allowed.
  • No flooding, no all-caps, no intentional annoyance. More than 3 lines all at once is considered flooding.
  • Stay on topic and stick to the discussion of Linux related topics.
  • No bots, automated responses or public logging allowed.
  • Don’t discuss channel policy in the channel. Do it by PM or take it up in ##Linux-OPs.
  • OPs judgement is final. If you wish to dispute it, follow the issue resolution procedure below.

Channel Vision

The purpose of ##Linux is to provide a fun and friendly medium for new and hardcore Linux® users alike seeking help, advice and constructive discussion on Linux® related topics. The channel is for ALL levels of user experience, including none.

Issue Resolution Procedure

If you have an issue, here is the procedure to get it resolved:

  1. Private message the op/user in question. Conduct yourself in a calm clear headed manner, if you are upset simply step away from your PC for 30-60 mins, take a deep breath and come back. Try resolve the matter between yourselves. Keep your logs.
  2. If you are unhappy with the outcome, join ##Linux-OPs and state your issue in channel, again in a calm clear headed manner. This is where the staff of ##Linux hang out. The issue can be discussed here for possible intervention by channel staff. Please, if you come into this channel and start going off on a tangent, swearing, insulting others … etc then you’re more than likely going to get ignored.
  3. If you are unhappy with the resolution provided by ##Linux-OPs, you need to compile a list of logs of the previous 2 steps you followed. Make a clear concise summary of what your issue is, why you think its not being dealt with properly and send a private message to the channel owner WildPikachu. If you skip the above steps, start with personal attacks … etc, you’re more than likely not going to get a reply.

How to be a good channel user/resident

  • Be Nice!
  • Polish your catalyst skills. The catalyst role is key to keeping channel interactions friendly and efficient. For more information on catalyst skills visit the freenode Catalyst Information Page.
  • Don’t be elitist. Today’s newbies are tomorrow’s experts. A support channel is a place where people with knowledge lead by example. Is the example you want to set that technical knowledge is a hierarchy of control, or that people with knowledge have an inherent social advantage over people who don’t? Please think before referring people to links, which combine suggestions for making support requests with a casual attitude of superiority over the newbie. Helping other people takes patience. It’s better not to answer a question than to use the opportunity to emphasize the limitations of the person you’re trying to help.
  • Avoid highlighting and repetition. Words and sentences in all-uppercase, heavy use of highlighting, beeping (^G) and repeating the same or similar lines over and over.
  • Avoid using foul language, remember we have a lot of young Linux® enthusiasts. In todays world people as young as 13 are installing and tinkering with Linux®.
  • Avoid advocacy debates. BSD versus GPL, vi versus emacs, centralized versus decentralized, RMS versus ESR, Linux® versus Windows: these discussions are frequently religious and may not involve significant new ideas.
  • Argue the point, not the person, i.e.: Don’t argue a point by attacking or appealing to a characteristic or belief of the person making the argument, rather address the substance of the argument or producing evidence against the claim.
  • You might not get too worked up if you’re arguing the relative merits of poll() or kqueue(), but if you walk into a discussion with a strong emotional need to “get your way”, consider the possibility you are simply arguing preference or personal affiliation. Advocacy discussions are best held quietly, via /msg, or on channels especially created for the purpose.
  • Pasting: Please use http://paste.linux.community to paste many lines of text and just share the link it gives you on the channel (or any other pastebin you like).
  • Don’t be caught by support burnout. It’s nearly impossible to answer every technical question that comes to your channel. In many cases, the problem doesn’t lie in the technical aspects of the question; cultural barriers may get in the way of communication, or it may be difficult to explain to a newbie just where to begin. When you try to answer every question, regardless of difficulty, you set yourself up for support burnout.

Off-topic Discussion

Channel operators (“ops”) will react differently to off-topic discussions at different times of the day. Various reactions may be:

  • Absolutely nothing.
  • Request the discussion cease and be moved elsewhere, either pvt (private messaging) or another channel.
  • Request the discussion simply cease. In that case, please respect that request and consider moving your conversation to a more appropriate place such as ##defocus or to a pm (private /query).
  • Muting (+q) one or several of the participants entertaining the off-topic discussion.
  • Kicking one or several of the participants entertaining the off-topic discussion.
  • Kicking and banning one or several of the participants entertaining the off-topic discussion.

As the issue of off-topic debate is a sensitive topic for many people, factors influencing the ops decisions are briefly outlined below:

  • Time of day affect ops decisions, what is acceptable at early hours of the morning when only two people are active may not be acceptable at the busiest times of the day.
  • When on-topic discussion is taking place, it is more likely for off-topic discussion to be discouraged.
  • When the participants in the discussion seem to have little care for which channel they’re in. If two people join the channel in a short time period and start discussing off-topic issues, they will more than likely be dealt with more harshly than someone that has taken part in on-topic discussion and knows what the purpose of the channel is.
  • The response ops get to warnings or actions taken. Swearing at, threatening, arguing with ops regarding a case of off-topic discussion is not a good idea.
  • The amount of and frequency of off-topic discussion.
  • Subject of the off-topic discussion, Topics that are more likely to generate a lot of traffic from random people like (politics, sex, movies … etc) are more than likely to get a response from an op.
  • As “unfair” as it may seem, it doesn’t matter if those in the channel are regulars or newbies, channels on IRC have a purpose and a topic.

Discussions that have come up frequently enough to make specific mention for off-topic or borderline discussions are outlined below:

  • Installing Linux® as a dual boot OS is considered on-topic, if you can assist another Linux® user in running Linux® on his machine along with another OS, please do.
  • Non-standard devices and emulators: Nintendo, Playstation, X-Box, TiVo, etc, where the EULA contains provisions against reverse engineering or otherwise re-implementing the technology or modifying the hardware. Discussing these is considered off-topic. It is furthermore presumed that you agreed to such terms by the use of such a device. Installing Linux® on a Playstation 3 is similarly off-topic, as Sony clearly prohibits it. Using an emulator to play such games uses reimplemented and copyrighted technology and is therefore also off-topic.
  • Android: While Android uses Linux® as its kernel, it’s highly modified for each device running it and lacks much or most of the userland and toolsets of common GNU/Linux® distributions. While we don’t directly support or discourage the use of Android, there is a channel dedicated to it in #Android, and is officially sanctioned by Google.
  • VPS & Hosting services: You may have Linux® through the use of a VPS or other hosting provider. Though it may be running Linux®, it may also be having problems beyond even your control to work with, fix, diagnose, etc. If you’re having problems with it, it’s always best to contact your provider’s help, because either it’s a restriction, terms-of-use issue, or just something that cannot be evaluated very clearly it is more up to the service provider to help you, and you are paying them for that fact. Setting up services like Apache and such will be acceptable if there’s no major complications that may be a result of VPS/Hosting setup.
  • Cygwin: Cygwin is made to be a Linux® like environment for Windows. It does not use the Linux® kernel, and has a lot of the GNU tools, but are compiled for use in Windows. The support channel for Cygwin is #cygwin and you may get better support there for any questions or issues you may have.
  • Torrents/Metalinks: Discussing torrents, metalinks and the like for purposes which do not clearly relate to GNU/Linux® is off-topic. For those wishing to discuss the BitTorrent protocol, the channel ##BitTorrent may be more suited to your needs.

Despite this long and fascist-sounding list, ##Linux ops are generally sane people and if you make a minimal effort to respect the channel rules and guidelines you shouldn’t have any problem.

Rules: ##Linux-Ops

This is the ##Linux operators channel used to resolve user issues and discuss channel policy. The channel exercises a relaxed no-idle policy. This means that once your issue has been sorted out, you’re kindly requested to leave the channel.

  • English only.
  • No idling.
  • No excessive swearing. This probably won’t help you anyway in getting any point across.

ChangeLog

[2017-05-18] Removed section on official channel bots channel logging to the site, as they do not do this.

[2016-08-06] Changed paste.linux.chat to paste.linux.community. Further clarified that the allowed ##Linux bots log all traffic and make it publicly available (as LinuxBot has done with the stats for the past 10-16+ years).

[2015-05-27] Changed paste.linuxassist.net to paste.linux.chat.

[2014-10-13] First rule clarified. SMS-style abbreviations are not English.

[2014-01-10] Rules updated. Bots clarified to include logging.

[2013-07-27] Rules updated.

[2012-06-27] Rules published for ##Linux-OPs and no-idle policy enacted.

[2012-06-04] Added resolution procedure. Slight rewording on Cygwin paragraph. Clarification of channel owners stance on torrents.