[Numpy-discussion] Taking back control of the #numpy irc channel

[Sebastian Berg]

On Mon, 2018-08-06 at 21:52 -0700, Ralf Gommers wrote:
> 
> 
> On Mon, Aug 6, 2018 at 7:15 PM, Nathan Goldbaum <nathan12343 at gmail.co
> m> wrote:
> > Hi,
> > 
> > I idle in #scipy and have op in there. I’m happy start idling in
> > #numpy and be op if the community is willing to let me.
> > 
> 
> Thanks Nathan. Sounds useful.
> 

Sounds good. I haven't really hung out there for a long time (frankly,
I never hung out in #numpy, I thought people just use #scipy).

Can we just give a few names (such as Matti, Nathan, maybe me, anyone
else right now?) and add others later ourselves?
I can get in contact with freenode (unless someone already did).

> There's also a Gitter numpy channel. AFAIK few/none core devs are
> regularly active on either IRC or Gitter. I would suggest that we
> document both these channels as community-run at
> https://scipy.org/scipylib/mailing-lists.html, and give Nathan and
> others who are interested the permissions they need.
> 

Yeah, the gitter seems pretty inactive as well. But I guess it doesn't
hurt to mention them.

- Sebastian


> I think our official recommendation for usage questions is
> StackOverflow.
> 
> Cheers,
> Ralf
> 
> 
> > I’m also in the process of getting ops for #matplotlib for similar
> > spam-related reasons. I’d say all the scientific python IRC
> > channels I’m in get a decent amount of traffic (perhaps 10% of the
> > number of questions that get asked on StackOverflow) and it’s a
> > good venue for asking quick questions. Let’s hope that forcing
> > people to register doesn’t kill that, although there’s not much we
> > can do given the spam attack.
> > 
> > Nathan
> > 
> > On Mon, Aug 6, 2018 at 9:03 PM Matti Picus <matti.picus at gmail.com>
> > wrote:
> > > Over the past few days spambots have been hitting freenode's IRC 
> > > channels[0, 1]. It turns out the #numpy channel has no operator,
> > > so we 
> > > cannot make the channel mode "|+q $~a"[2] - i.e. only registered 
> > > freenode users can talk but anyone can listen.
> > > 
> > > I was in touch with the freenode staff, they requested that
> > > someone from 
> > > the steering council reach out to them at ||projects at freenode.net
> > > , here 
> > > is the quote from the discussion:
> > > 
> > > "
> > > it's pretty much a matter of them sending an email telling us who
> > > they'd 
> > > like to represent them on freenode, which channels and cloak
> > > namespaces 
> > > they want, and any info we might need on the project
> > > "
> > > 
> > > In the mean time they set the channel mode appropriately, so this
> > > is 
> > > also a notice that if you want to chat on the #numpy IRC channel
> > > you 
> > > need to register.
> > > 
> > > Hope someone from the council picks this up and reaches out to
> > > them, and 
> > > will decide who is to able to become channel operators (the
> > > recommended 
> > > practice is to use it like sudo, only assume the role when needed
> > > then 
> > > turn it back off).
> > > 
> > > Matti
> > > 
> > > [0] https://freenode.net/news/spambot-attack
> > > [1] https://freenode.net/news/spam-shake
> > > [2] https://nedbatchelder.com/blog/201808/fighting_spam_on_freeno
> > > de.html
> > > |
> > > _______________________________________________
> > > NumPy-Discussion mailing list
> > > NumPy-Discussion at python.org
> > > https://mail.python.org/mailman/listinfo/numpy-discussion
> > 
> > _______________________________________________
> > NumPy-Discussion mailing list
> > NumPy-Discussion at python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> > 
> 
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20180807/6de0724b/attachment-0001.sig>