freenode vs. oftc

Karsten 'quaid' Wade kwade at redhat.com
Tue Mar 13 17:05:56 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/13/2012 09:21 AM, Steve Gordon wrote:

> 
> Usually this is done by registering the channel, and setting it up
> to kick everyone who joins with a kick message indicating where to 
> go/what to do. If you leave any possibility for joining/lurking
> you end up with two communities for active discussion which in my
> opinion is far worse that just happening to be on a 'less popular'
> network.

As it happens, this is what was done with #ovirt on Freenode.

Despite the clear message, though, people have approached me wondering
why they are "banned" from #ovirt.

Anyway, in the process of getting permissions so we can actually
control that channel, we removed the kickban. The /topic now says to
go to OFTC, etc., and there is zero discussion on the Freenode channel.

So the consensus of this list seems to be, "Leave things as they are,"
and in this case it seems to be better that the channel is populated
but quiet.

Let's go ahead and move discussions that start on Freenode to OFTC
wherever possible.

- - Karsten
- -- 
name:  Karsten 'quaid' Wade, Sr. Community Architect
team:    Red Hat Community Architecture & Leadership
uri:              http://communityleadershipteam.org
                         http://TheOpenSourceWay.org
gpg:                                        AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPX3502ZIOBq0ODEERAmJzAJwM6Vq2C8bC9h3hG9j/2riC1YzZEQCgubre
yiUbzBl0FstWeBVPRL4tRe8=
=nVd+
-----END PGP SIGNATURE-----



More information about the Arch mailing list