Revision as of 22:54, 1 February 2009

Managing traffic in #haskell

Motivation

The #haskell channel is such a busy place that we're moving away from our core principles of being newbie friendly.

It is now not uncommon to hear or see newbie questions go unanswered.

Goal

We want to reduce non-newbie question related traffic, so that we again achieve maximum newbie friendliness.

Strategy

Create a 'deep' channel for in-depth hard topics
- this channel shall be a subset of #haskell users (old hands mostly, and theory heads)
- those people should also stay in #haskell to answer questions

Deep/hard topics should move into this channel to make way for newbie traffic in #haskell
lambdabot and other noisy services will be monitored and have non-newbie related content reduced.

Evaluation

We monitor success by how much we reduce traffic, without reducing newbies

We must also be careful to ensure there's a clear path for new users into the -advanced channel.

@@ Line 14: / Line 14: @@
 * Create a 'deep' channel for in-depth hard topics
-** this channel shall be a subet of #haskell users (old hands mostly, and theory heads)
+** this channel shall be a subset of #haskell users (old hands mostly, and theory heads)
-** those people should also say in #haskell to answer questions
+** those people should also stay in #haskell to answer questions
-* Deep / hard topics should move into this channel ,to make way for newbie traffic in #haskell
+* Deep/hard topics should move into this channel to make way for newbie traffic in #haskell
 * lambdabot and other noisy services will be monitored and have non-newbie related content reduced.
@@ Line 24: / Line 24: @@
 We monitor success by how much we reduce traffic, without reducing newbies
-We must also be careful to ensure there's a clear path for new users into the -advanced chan.
+We must also be careful to ensure there's a clear path for new users into the -advanced channel.