[sage-devel] Re: #sage-devel IRC channel registration has lapsed

2010-12-14 Thread Keshav Kini
It seems that #sage is already registered, though nobody has said anything there since July of this year. I talked to the owner of the channel - he is a member of the USENIX Special Interest Group for Sysadmins ( http://sage.org/ ) and says that other users of that organization sometimes use #sage

[sage-devel] Re: #sage-devel IRC channel registration has lapsed

2010-12-14 Thread Dima Pasechnik
Hi William, could you perhaps take care of this? On Dec 14, 5:43 pm, Keshav Kini wrote: > After some consultation with a freenode oper, it seems that there is a > rather humongous backlog of group registration forms that have been > filled and are waiting for processing ("thousands"), but if a so

[sage-devel] Re: #sage-devel IRC channel registration has lapsed

2010-12-14 Thread Keshav Kini
After some consultation with a freenode oper, it seems that there is a rather humongous backlog of group registration forms that have been filled and are waiting for processing ("thousands"), but if a software project needs their group registration processed in order to regain control of a channel,

[sage-devel] Re: #sage-devel IRC channel registration has lapsed

2010-12-14 Thread Keshav Kini
There's actually a freenode policy which recommends against using "primary channels" (ones that start with # and not ##) unless they're associated with a "primary group", which is basically a software project registered with freenode and with known contact persons. Has anyone tried applying for "sa

[sage-devel] Re: #sage-devel IRC channel registration has lapsed

2010-12-14 Thread leif
On 14 Dez., 08:09, Keshav Kini wrote: > The #sage-devel IRC channel is not currently registered in anyone's > name on the freenode network (was it ever?), which means that nobody > can obtain operator privileges in it unless everyone leaves, the > channel thus gets purged, and then someone joins i