General Wine IRC Information

1. We are hosted on irc.freenode.net.

2. We have three channels: #winehq, #winehackers, #winehq-social.

3. #winehq is for Wine support.

4. #winehq-social is for off-topic chat for users and developers.

5. #winehackers is for development.

6. #crossover is for Crossover support.

7. Please read the FAQ for answers to commonly asked questions.

8. Check the AppDB to see what might be needed to get your application to work.

9. Check the download page to download and install the latest Wine.

Wine IRC Rules and Penalties

1. Penalties are listed right next to rules like so:

   • Rule. [Number of warnings prior to the first kick. | Number of kicks prior to first ban.]

2. Bans get progressively longer. The channel OP gets to decide how long the ban lasts, provided it is within the range given.
   • The first ban lasts up to 2 hours.
   • The second ban lasts forever.
3. Bans can be contested.

   • Go to #winehq-social and ask to be unbanned.

   • If you are also banned from #winehq-social, ask on the wine-devel@winehq.org mailing list.

   • Explain why you believe you were banned, and why you should be unbanned.

General Wine IRC Rules

1. Do not spam. [1 warning | 2 kicks]

2. Use a pastebin for pasting more than one or two lines. Websites such as http://winehq.pastebin.com and http://pastebin.ca work well. [0 warnings | 5 kicks] (The bot will kick you automatically.)

3. Talk in the appropriate channel. If unsure, ask in #winehq which channel to join. [2 warnings | 3 kicks]

#winehq Rules

1. Only Wine is supported. Sidenet, WineDoors, Cedega, IEs4Linux, etc. are not supported in #winehq. [2 warnings | 1 kick]

2. Always use the latest Wine version. This will be set in the topic. Use the following command to find your version: [3 warnings | 1 kick]

    wine --version

3. Wait your turn for help. [3 warnings | 1 kick]

4. Do not discuss pirated software. [1 warning | 1 kick]

#winehackers Rules

1. Only join this channel if you are thinking about helping Wine in some way. The following are all OK. Note: this list is not exhaustive. [Covered by IRC rule #3]

   • Writing code for Wine itself, the website, or something else relating to Wine.

   • Testing Wine and giving feedback to developers. This includes RegressionTesting.

   • Triaging bugs at http://bugs.winehq.org.

   • Writing Wine documentation.