git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Krüger" <jk@jk.gs>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "Kevin Daudt" <me@ikke.info>, "Taylor Blau" <me@ttaylorr.com>,
	"Jeff King" <peff@peff.net>,
	"Michal Suchánek" <msuchanek@suse.de>,
	"Jonathan Nieder" <jrnieder@gmail.com>,
	"Emily Shaffer" <emilyshaffer@google.com>,
	"Git List" <git@vger.kernel.org>
Subject: Re: Should we do something with #git-devel on Freenode?
Date: Fri, 28 May 2021 10:00:41 +0200	[thread overview]
Message-ID: <b8e48d464858c0ef6da2629dab507ebc@jk.gs> (raw)
In-Reply-To: <87im33ltqr.fsf@evledraar.gmail.com> (sfid-20210528_000327_229190_A43C0CF3)

On 27.05.2021 23:54, Ævar Arnfjörð Bjarmason wrote:
> How have the channels been destroyed?
> 
> I'm still joined on freenode and #git has ~700ish users

#git was not affected, but many others were, including #git-devel...

> I see there was a mass action to revert topics that stated that 
> channels
> had moved

If that was all that had happened, I would totally agree. Unfortunately,
they did quite a bit more than that. They made a script that
automatically ran the following actions on channels that mentioned
"libera" in the topic:

* sent a vague message about a ToS violation to the channel;
* dropped the registration, including the full access list;
* set the channel to moderated;
* removed all ops;
* set an auto-forward to a similarly named topic channel (e.g.
   #git-devel forwarded to ##git-devel);
* made no attempt to give control of the topic channel to the previous
   community, i.e. the new channel would usually end up completely
   op-less and thus impossible to register at all. If it had been
   squatted by unrelated people beforehand, it would stay in their
   control.

This is equivalent to utter destruction in my view. #git was only not
affected because our message in the topic did not mention Libera by
name. Now of course we could just consider ourselves lucky and move on,
but personally I am deeply suspicious of a team that will do this kind
of thing seemingly on a whim, without even letting anyone know in
advance that this was considered a violation. Who knows what else they
are going to do on a whim in the future?

> I agree that ~300/~700 is quite the arbitrary quorum :)

I misspoke - it was an arbitrary quorum of the people who spend a lot of
time being active in #git, i.e. the people who are the most responsible
for keeping the channel alive. And the decision wasn't about killing the
freenode channel anyway...

> I'm not going to weigh in on whatever pissing contest is going on over
> at Freenode and related networks other than to say that it seems to me
> that the goal(s) of the new owner/team or whatever is to try to prevent
> some mass adversiting of the nature of "this network is
> deprecated". "Destroying" prominent channels seems to be
> conterproductive to that goal.

And yet that is what they did.

> In any case, I agree with Jeff King's earlier comments that our primary
> goal here should not be to pick sides, but to direct our users to 
> useful
> venues where they can get help, discuss git etc.

Sure... but several of us spoke about this and none of the particularly
active regulars I talked to want to keep being active on freenode
indefinitely. This will likely have effects on how active each channel
will be. Right now, several of us are still answering questions on
freenode, and nobody has made any attempt to shut down the channel
there. If it gets shut down, it will not be due to our actions. Maybe
due to our inaction, but even then there's nothing stopping others from
keeping the channel going.

I've updated my little page about this whole issue, to clarify that the
freenode channel is not closed or anything - but I feel like it's
relevant that several of the most active people intend on moving away
from it, and so I think it still makes sense leaving that message out
there. If it turns out that there is a significant fraction of active
"helpers" that intend to stay on freenode, I'll update again to reflect
that.

  parent reply	other threads:[~2021-05-28  8:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-19 17:47 Should we do something with #git-devel on Freenode? Emily Shaffer
2021-05-19 19:08 ` Jonathan Nieder
2021-05-19 23:22   ` Junio C Hamano
2021-05-20  7:11   ` Michal Suchánek
2021-05-20 17:19     ` Jeff King
2021-05-20 18:08       ` Emily Shaffer
2021-05-20 21:20       ` Junio C Hamano
2021-05-21 11:19         ` Kevin Daudt
2021-07-02 12:15         ` Ævar Arnfjörð Bjarmason
2021-07-02 15:23           ` Junio C Hamano
2021-05-21 18:38       ` Felipe Contreras
2021-05-21 20:12         ` Randall S. Becker
2021-05-26 23:35         ` Ævar Arnfjörð Bjarmason
2021-05-26 23:59           ` Felipe Contreras
2021-05-27  0:24           ` Đoàn Trần Công Danh
2021-05-26 18:47       ` Taylor Blau
2021-05-26 20:01         ` Kevin Daudt
2021-05-27 17:18           ` Jan Krüger
2021-05-27 21:54             ` Ævar Arnfjörð Bjarmason
2021-05-28  1:26               ` Felipe Contreras
2021-05-28  1:36                 ` Taylor Blau
2021-05-28  3:29                   ` Felipe Contreras
2021-05-28  8:00               ` Jan Krüger [this message]
2021-05-28 14:37                 ` Phillip Susi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b8e48d464858c0ef6da2629dab507ebc@jk.gs \
    --to=jk@jk.gs \
    --cc=avarab@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=me@ikke.info \
    --cc=me@ttaylorr.com \
    --cc=msuchanek@suse.de \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).