git@vger.kernel.org list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: "Michal Suchánek" <msuchanek@suse.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Emily Shaffer" <emilyshaffer@google.com>,
	"Git List" <git@vger.kernel.org>, "Jan Krüger" <jk@jk.gs>
Subject: Re: Should we do something with #git-devel on Freenode?
Date: Thu, 20 May 2021 09:11:41 +0200	[thread overview]
Message-ID: <20210520071141.GZ8544@kitsune.suse.cz> (raw)
In-Reply-To: <YKViF9OVLeA95JPH@google.com>

On Wed, May 19, 2021 at 12:08:07PM -0700, Jonathan Nieder wrote:
> Hi,
> 
> Emily Shaffer wrote[0]:
> 
> > Seems like there's been some kerfuffle with Freenode staff and new
> > ownership[1][2][3]. What does this mean for Git project? I think #git
> > on Freenode isn't maintained by Git developers directly, right?
> 
> https://gitirc.eu/ involved a lot of work by Jan Krüger (thanks!), so
> cc-ing him since he likely knows who else is active there.
> 
> [...]
> >                                                             We do
> > theoretically keep up #git-devel on Freenode, though it's largely
> > silent. Should we be worrying? Migrating?
> 
> The main practical struggle on #git-devel has been spam.  I don't know
> that any particular IRC network is better at spam prevention than
> others.
> 
> It looks like most of the Freenode admins have moved to
> https://libera.chat/, so that would be a close equivalent.  Another
> alternative is OFTC <https://www.oftc.net/>, which is used by
> irc.debian.org, for example.
> 
> There are also other real-time chat programs such as Zulip (open
> source, used in Outreachy), Discord (used by LLVM), and Slack (used by
> Chromium); each has its benefits and flaws.

Or Matrix used by Mozilla, GNOME, and others.

Unlike the others Matrix intends to be not just a chat application
(opensource or proprietary) but open standard which has multiple
implementetions of both the server and the client.

In that way it is the most flexible option allowing communication
between people with different UX preferences.

Thanks

Michal

  parent reply	other threads:[~2021-05-20  7:11 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 [this message]
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
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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=20210520071141.GZ8544@kitsune.suse.cz \
    --to=msuchanek@suse.de \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=jk@jk.gs \
    --cc=jrnieder@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).