diff options
| author | Robby Workman <rworkman@slackware.com> | 2017-07-12 11:50:03 -0500 |
|---|---|---|
| committer | Robby Workman <rworkman@slackware.com> | 2017-07-12 11:50:03 -0500 |
| commit | 23b5f055aeb1b4919a0058bcff7bd0f9e8e22697 (patch) | |
| tree | 40989bc8ef0c7e1aad5b841e129569c9e7d6141d /index.html | |
| parent | 3b4714000047d3adcddaf8cf31e4e7eb57d2051c (diff) | |
| download | slackware-freenode-23b5f055aeb1b4919a0058bcff7bd0f9e8e22697.tar.xz | |
index.html: Add general info and channel rules
Diffstat (limited to 'index.html')
| -rw-r--r-- | index.html | 159 |
1 files changed, 159 insertions, 0 deletions
diff --git a/index.html b/index.html new file mode 100644 index 0000000..f828b2b --- /dev/null +++ b/index.html @@ -0,0 +1,159 @@ + +<html> + +<h3>##slackware (freenode) informational website</h3> + + <p>Welcome to the offical information page for Freenode's ##slackware. + This page contains a bit of (hopefully) helpful information along + with the channel rule/guidelines. + </p> + + <ul> + <li>Need a channel operator/moderator? Type "!ops" in your IRC + client. Note that there's no guarantee that an op will currently + be available; all of them are volunteers. + </li> + <li>You must be registered and authenticated with NickServ to talk + in ##slackware. + </li> + <li>Get Slackware here: <a href="http://slackware.com/getslack/"> + http://slackware.com/getslack/</a> + </li> + <li>Keep up with serurity and bugfix patches for your Slackware + version: <a href="https://mirrors.slackware.com/feeds/"> + Slackware RSS Feeds</a> + </li> + <li>If you're a new Slackware user, you should have a look at the + <a href="http://docs.slackware.com/slackware:beginners_guide"> + Slackware Beginner's Guide</a>. + </li> + </ul> + +<h3>##slackware channel rules/guidelines</h3> + <ul> + <li>Generally speaking, treat other users in the manner you'd like + to be treated. No "flames" or trolling or nonsense behavior is + welcome. + <ul> + <li> No, "flames" and "trolling" and "nonsense behavior" + will not be quantified or formally defined. + </li> + </ul> + </li> + <li>Don't post information that is deliberately detrimental to someone, + and especially not in a sneaky fashion (i.e. don't try to obfuscate + it). + </li> + <li>Don't flood the channel. Use #overflow or some such. If you need to + show a configuration file or long error message, make use of public + paste servers such as: + <ul> + <li>http://dpaste.net</li> + <li>http://pastebin.ca</li> + </ul> + </li> + <li>##slackware exists as a Slackware discussion channel and as a help + resource for users. Newcomers and "Old Hats" alike will be more + likely to receive quality assistance if they heed the following + suggestions: + <ol> + <li>When asking a question, be prepared to show evidence that + you've researched it on your own. We like to help, but we + don't want to do it for you. + </li> + <li>If you're asked for additional information, please provide + it. If you're unsure as to why some one wants to see a + config file or a routing statement or anything similar, + just ask them. In this way, you and others might learn + something about how the different parts of your Slackware + Linux system interact in addition to solving your problem. + </li> + </ol> + </li> + + <li>##slackware exists for Slackers to share their knowledge about + Slackware Linux and topics related to Slackware (e.g. system + administration and security concerns, networking Slackware with + other operating systems, etcetera). With that said, we do not mind + off-topic (OT) discussions or questions, but we ask that you + refrain from such discussions if someone wishes to discuss + something that *is* on-topic. Think of the channel in the same way + that you would think of a radio channel. When everyone talks at + once, the result is a jumble of confusion. By "vacating" the + channel of off-topic discussion when some one has an on-topic + discussion, we all benefit. + </li> + + <li>In recent years, it has become popular to "break" a few of the old + IRC netiquette conventions. Generally speaking, we can't stop all + of this, but repeat offenders will be dealt with. Specifically, as + simple courtesies to everyone, we request that you not do the + following things: + + <ul> + <li>Don't private message (/msg) people without first asking + and obtaining permission from them + <li> + <li>Don't use an IRC stat scripts. Nobody wants to see your + nick change when you walk away from the keyboard, and + nobody wants to see your current music selection announced. + However, some channel regulars IRC from work and suffix + "-work" or some such to their nickname when doing so. + </li> + <li>Name calling and particularly vulgar language is frowned + upon. With that said, we are not nannies and aren't going + to wash your mouth out with soap for petty offenses. + Racist, sexist, and similar language will not be tolerated + under any circumstances. Hackers know that someone's skin + color, gender, and/or sexual orientation has nothing to do + with ability to contribute to the group. Along similar + lines, your latest "bedroom conquests" aren't at all related + to Slackware and won't be tolerated (unless some how they + *are* related to Slackware, in which case we'd like to hear + about them. ;^) + </li> + <li> + Repeated/persistent personal attacks are not tolerated. + </li> + <li>If you have been banned or de-voiced from a channel, don't + try to avoid the punishment by changing nicks or similar + methods. We will ban your entire netblock if need be. If + you feel that you have been unfairly blocked, speak to one + of the channel ops politely. If you are indeed innocent or + have "learned your lesson", we will likely be happy to + remove the block. + </li> + <li>If you have questions about how to do something in some + other distribution, you should check in that distribution's + support forums and/or channels - ##slackware is for + Slackware support. + </li> + <li>Third party package management tools, such as slapt-get and + swaret, are not supported in ##slackware. This does not + necessarily mean that discussion is off-limits, nor does it + necessarily mean that you will not receive help if you + encounter problems from using them, but the best place for + support with those tools is in their respective channels + and/or support forums. The same principle applies to the + third-party gnome builds for Slackware. + <br /> <br /> + Third party packages vary widely in quality; some repos + are good and some are not so good. That being the case, + the best place to get support for third party packages is + from the person(s) who packaged them. + <br /> <br /> + The following links should not be construed as endorsements + or recommendations from ##slackware, but they might be + better sources of help with the respective projects: + <ul> + <li><a href="https://slackbuilds.org">SlackBuilds.org</a> #slackbuilds</li> + <li><a href="http://sbopkg.org">SBoPKG</a> #sbopkg</li> + </ul> + </li> + </ul> + </li> + <li>Have fun and Happy Slacking! + </li> + </ul> +</html> + |