[ruby-core:41693] Re: Ruby IRC Presence Problem

Group registration still takes ages, even with that from. We went through i=
t for Sinatra, where we needed to in order to claim or channel (no ops in t=
here), even with being a priority (due to channel already existing) and bot=
hering the freenode team every view days to weeks, it took over six months =
to officially become a group. Apparently a single person is in charge of de=
aling with group registration in his/her spare time.

Konstantin

On Dec 16, 2011, at 06:35 , Eero Saynatkari wrote:

> Hi,
>=20
> As some of you may remember, Ruby's IRC situation is slightly problematic=
, but recent developments offer a slightly simpler way of resolving the sit=
uation.
>=20
> TL;DR: Matz or a designated representative should assert rights over the =
#ruby channel.
>=20
>=20
> The Problem
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> I've tried to condense as much as possible. Please ask if anything's uncl=
ear.
>=20
> As designated on http://ruby-lang.org/en/community/, the official channel=
 is #ruby-lang on Freenode.=20
>=20
> Unfortunately around the same time, a channel named #ruby was also create=
d, and it was/is run mostly by people who had gotten banned from #ruby-lang=
.
>=20
> Many new people will automatically go to #ruby, assuming that it is the c=
orrect place. This was not a problem until 2008 or so because #ruby was gra=
cious enough to use their /topic to redirect people to #ruby-lang. At some =
point, however, #ruby removed the redirect and used other questionable mean=
s to retain people on their channel (such as telling people that #ruby-lang=
 was for language internals discussion).
>=20
> The current situation is that both channels have some 300 unique users. I=
 personally find this quite vexing, as it leads to unnecessary fragmentatio=
n and duplication of information. I do not have anything against there bein=
g two Ruby channels, just that the separation is artificial and based on fa=
lse premises.
>=20
> Freenode's policy is that only official channels may use the single hash =
namespace, but #ruby cannot be reassigned to ##ruby (for example) without a=
uthorization because it's been around for some time.
>=20
>=20
> Solutions
> =3D=3D=3D=3D=3D=3D=3D
>=20
> There are three possible solutions:
>=20
> 1. Do nothing, and let the fragmentation continue.
>=20
> 2. Designate #ruby as the official channel (incl. on ruby-lang.org), and =
have everyone move there by default. The problem is that the channel owners=
hip is lost, and in hands of a questionable history.
>=20
> 3. Assert rights on the #ruby namespace. This allows the unofficial #ruby=
 channel to be renamed ##ruby, and then either the name #ruby can be redire=
cted to #ruby-lang, or #ruby-lang can be renamed.
>=20
> Fortunately Freenode has made obtaining the rights a bit easier than it w=
as previously[1]. It can be done by filling out the group registration form=
[2], either by Matz or a designated representative (perhaps for example Dav=
id A. Black or Eric Hodel, who are the registrants for #ruby-lang?).
>=20
> [1] http://freenode.net/group_registration.shtml
> [2] http://freenode.net/group_registration_form.php=20
>=20
>=20
> I'd very much like to get opinions on the matter. Thanks!
>=20
>=20
>=20